You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Django 2.0 is scheduled to release in December 2017.
Django 1.9 extended support ends in April 2017.
This is low-priority for us right now, but we will need to evaluate what impact this will have on our codebase. How hard would it be for us to migrate to Python 3 and Django 2.0?
If the effort required is too much, I recommend taking this opportunity to create a new repository and fundamentally refactor the project. Bug-fixes on this repository should be continued regardless, of course, but before adding new features, I think it's important to address this topic. I have some ideas in this regard, and I think that the new API-based admin will enable some exciting possibilities down the line, but I wanted to field this question as-is first, before presenting other options.
Just wanted to share a relevant link that has been forwarded my way:
https://www.reddit.com/r/programming/comments/5ovwi8/django_20_will_not_support_python_2/
https://github.com/django/django/pull/7867/files
https://www.djangoproject.com/weblog/2015/jun/25/roadmap/
Django 2.0 is scheduled to release in December 2017.
Django 1.9 extended support ends in April 2017.
This is low-priority for us right now, but we will need to evaluate what impact this will have on our codebase. How hard would it be for us to migrate to Python 3 and Django 2.0?
If the effort required is too much, I recommend taking this opportunity to create a new repository and fundamentally refactor the project. Bug-fixes on this repository should be continued regardless, of course, but before adding new features, I think it's important to address this topic. I have some ideas in this regard, and I think that the new API-based admin will enable some exciting possibilities down the line, but I wanted to field this question as-is first, before presenting other options.
Related: #292, #102
The text was updated successfully, but these errors were encountered: