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
{{ message }}
This repository has been archived by the owner on Jan 10, 2020. It is now read-only.
Django 1.8 is well underway in development, and is currently in the beta stage. It's expected to land in May.
Django 1.8 will mark another LTS for Django, and land a lot of new features, including Postgres specific features and a complete rewrite of the Template system (it will now be possible to choose your own template engine, since the Template system has been rewritten into a generalized API).
There are also a number of other changes going on, some of which can be easily implemented already in Django 1.7 projects (for example, new syntax for urls.py for the future).
This likely wont make it into 4.0 of the Stregsystem, and we should likely wait until 1.8.1 anyway, before upgrading. However, besides from some changes here and there, there shouldn't be many changes needed for a smooth upgrade (we're already fiddling with some upgrades internally).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Django 1.8 is well underway in development, and is currently in the beta stage. It's expected to land in May.
Django 1.8 will mark another LTS for Django, and land a lot of new features, including Postgres specific features and a complete rewrite of the Template system (it will now be possible to choose your own template engine, since the Template system has been rewritten into a generalized API).
There are also a number of other changes going on, some of which can be easily implemented already in Django 1.7 projects (for example, new syntax for
urls.py
for the future).Read more about the changes here: https://docs.djangoproject.com/en/dev/releases/1.8/
The text was updated successfully, but these errors were encountered: