{ "info": { "author": "Nirupam Biswas, Nicolas Pantel", "author_email": "admin@applegrew.com", "bugtrack_url": null, "classifiers": [ "Development Status :: 4 - Beta", "Environment :: Web Environment", "Framework :: Django", "Intended Audience :: Developers", "License :: OSI Approved :: Apache Software License", "Operating System :: OS Independent", "Programming Language :: Python" ], "description": "Django-Select2\n==============\n\nThis is a [Django](https://www.djangoproject.com/) integration of [Select2](http://ivaynberg.github.com/select2/).\n\nThe app includes Select2 driven Django Widgets and Form Fields.\n\nInstallation\n============\n\n1. Install `django_select2`\n\n pip install django_select2\n\n2. Add `django_select2` to your `INSTALLED_APPS` in your project settings.\n\n3. When deploying on production server, run :-\n\n python manage.py collectstatic\n\nDocumentation\n=============\n\nDocumentation available at http://django-select2.readthedocs.org/.\n\nMore details\n============\n\nMore details can be found on my blog at - http://blog.applegrew.com/2012/08/django-select2/.\n\nExternal Dependencies\n=====================\n\n* Django - This is obvious.\n* jQuery - This is not included in the package since it is expected that in most scenarios this would already be available.\n* Memcached (python-memcached) - If you plan on running multiple python processes with `GENERATE_RANDOM_SELECT2_ID` enabled, then you need to turn on `ENABLE_SELECT2_MULTI_PROCESS_SUPPORT`. In that mode it is highly recommended that you use Memcached, to minimize DB hits.\n\nExample Application\n===================\nPlease see `testapp` application. This application is used to manually test the functionalities of this package. This also serves as a good example.\n\nYou need only Django 1.4 or above to run that. It might run on older versions but that is not tested.\n\nSpecial Thanks\n==============\n\n* Samuel Goldszmidt (@ouhouhsami) for reporting many fundamental issues with the code, because of which versions 2.0 and 2.0.1 were released.\n\nChangelog Summary\n=================\n\n### v4.2.1\n\n* Finally fixed performance issue[#54](https://github.com/applegrew/django-select2/issues/54) (and issue[#41](https://github.com/applegrew/django-select2/issues/41)) in widgets when backing field is based on models and the field has an initial value.\n\n### v4.2.0\n\n* Updated Select2 to version 3.4.2. **Please note**, that if you need any of the Select2 locale files, then you need to download them yourself from http://ivaynberg.github.com/select2/ and add to your project.\n* Tagging support added. See [Field API reference](http://django-select2.readthedocs.org/en/latest/ref_fields.html) in documentation.\n\n### v4.1.0\n\n* Updated Select2 to version 3.4.1. **Please note**, that if you need any of the Select2 locale files, then you need to download them yourself from http://ivaynberg.github.com/select2/ and add to your project.\n* Address isssue[#36](https://github.com/applegrew/django-select2/issues/36) - Fix importerror under django1.6.\n* Fuxed the way `setup.py` handles unicode files while minfying them during package build.\n* Address isssue[#39](https://github.com/applegrew/django-select2/issues/39) - MultipleSelect2HiddenInput.render() should use mark_safe().\n* Address isssue[#45](https://github.com/applegrew/django-select2/issues/45) - MultipleSelect2HiddenInput returns bad has_changed value.\n\n### v4.0.0\n\n* Main version number bumped to bring your attention to the fact that the default Id generation scheme has now changed. Now Django Select2 will use hashed paths of fields to generate their Ids. The old scheme of generating random Ids are still there. You can enable that by setting `GENERATE_RANDOM_SELECT2_ID` to `True`.\n\n### v3.3.1\n\n* Addressed issue[#30](https://github.com/applegrew/django-select2/issues/30).\n* Merged pull request[#31](https://github.com/applegrew/django-select2/issues/31).\n* Added `light` parameter to `import_django_select2_js`, `import_django_select2_css` and `import_django_select2_js_css` template tags. Please see doc's \"Getting Started\", for more details.\n\n### v3.3.0\n\n* Updated Select2 to version 3.3.1.\n* Added multi-process support. ([Issue#28](https://github.com/applegrew/django-select2/issues/28)).\n* Addressed issue[#26](https://github.com/applegrew/django-select2/issues/26).\n* Addressed issue[#24](https://github.com/applegrew/django-select2/issues/24).\n* Addressed issue[#23](https://github.com/applegrew/django-select2/issues/23).\n* Addressed some typos.\n\n### v3.2.0\n\n* Fixed issue[#20](https://github.com/applegrew/django-select2/issues/20). Infact while fixing that I realised that heavy components do not need the help of cookies, infact due to a logic error in previous code the cookies were not being used anyway. Now Django Select2 does not use cookies etc.\n* Few more bugs fixed in `heav_data.js`.\n* Now production code will use minimized versions of js and css files.\n* Codes added in `setup.py` to automate the task of minimizing js and css files, using a web service.\n\n### v3.1.5\n\n* Merged pull request (issue[#17](https://github.com/applegrew/django-select2/issues/17)). Which allows the user to pass some extra data to Select2 clients-side component.\n* Updated License. The previous one was inadequently worded. Now this project use Apache 2.0 license.\n\n### v3.1.4\n\n* Manually merged changes from pull request (issue[#16](https://github.com/applegrew/django-select2/issues/16)).\n* Django Select2 widgets now allow passing of any Select2 Js options. Previously it used to allow only white-listed options. Now it will block only black-listed options. For example, Light Select2 widgets won't allow you to set `multiple` option, since it is an error to set them when Select2 Js is bound to `