Django 1.10 release
See original GitHub issue(…)lib/python2.7/site-packages/selectable/forms/fields.py:27: RemovedInDjango110Warning: BaseAutoCompleteField._has_changed
method should be renamed has_changed
.
class BaseAutoCompleteField(forms.Field):
Can you create new version (0.10?) and send it to pypi?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Django 1.10 release notes
These release notes cover the new features, as well as some backwards ... Like Django 1.9, Django 1.10 requires Python 2.7, 3.4, or...
Read more >Django 1.10 documentation - DevDocs
Django 1.10.8 API documentation with instant search, offline support, keyboard shortcuts, mobile version, and more.
Read more >Django 1.10 released | Hacker News
Channels will get there. It just wasn't quite ready on time for 1.10. Hopefully it will be ready on time for 1.11, and...
Read more >[ANNOUNCE] Django 1.10 and 1.9.9 released
With the release of Django 1.10, Django 1.9 has reach end of mainstream support. It will continue to receive security and data loss...
Read more >Django - endoflife.date
Feature releases (A.B, A.B+1, etc.) will happen roughly every eight months. These releases will contain new features, improvements to existing features, and ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@mlavin any idea when a Django 1.10 compatible version will be pushed to pypi? The current master branch is compatible with 1.10.
I looked into https://github.com/mlavin/django-selectable/issues/179 and couldn’t reproduce. Concerning the other issues you’re linking to, they don’t seem specific to the master branch or to Django 1.10. Why would issuing a new minor version impact these issues?