Django版本 和 django-registration-redux 的版本对应关系
2018-01-31 16:58
267 查看
Upgrade guide
The 2.0 release of django-registration-redux is not compatible with the legacy django-registration (previously maintained by James Bennett). Major backwards incompatible changes will be recorded here, but for a full list of changes between versions you should refer to the CHANGELOG.
Django version requirement
As of 2.0, django-registration-redux requires Django 1.11 or newer; older Django releases may work, but are officially unsupported. Additionally, django-registration-redux officially supports Python 2.7, 3.4, and 3.5, 3.6.
Backwards-incompatible changes
Version 2.0
Removed support for Django < 1.11.
Removed registration/urls.py in favor of registration/backends/default/urls.py
Version 1.9
Change of return signature of RegistrationProfileManager.activate_user. A tuple containing the User instance and a boolean of whether or not said user was activated is now returned.
Version 1.8
None
Version 1.7
None
Version 1.6
None
Version 1.5
Support for Django 1.7 is removed, and Django 1.8 or newer is required.
Change signature of RegistrationProfileManager.activate_user. site is now a required positional argument. See #244.
Version 1.4
Remove unnecessary _RequestPassingFormView. See #56. Please ensure that you update any subclassed views to reference self.request instead of accepting request as an argument.
Version 1.3
Django 1.7 or newer is required. Please ensure you upgrade your Django version before upgrading.
Version 1.2
Native migration support breaks South compatibility: An initial native migration for Django > 1.7 has been provided. South users will need to configure a null migration with (SOUTH_MIGRATION_MODULES) in settings.py as shown below:
SOUTH_MIGRATION_MODULES = {
‘registration’: ‘registration.south_migrations’,
register method in RegistrationView has different parameters: The parameters of the
Version 1.1
base.html template required: A base.html template is now assumed to exist. Please ensure that your project provides one for django-registration-redux to inherit from.
HTML email templates: django-registration-redux now uses HTML email templates. If you previously customized text email templates, you need to do the same with the new HTML templates.
链接来自 官网
The 2.0 release of django-registration-redux is not compatible with the legacy django-registration (previously maintained by James Bennett). Major backwards incompatible changes will be recorded here, but for a full list of changes between versions you should refer to the CHANGELOG.
Django version requirement
As of 2.0, django-registration-redux requires Django 1.11 or newer; older Django releases may work, but are officially unsupported. Additionally, django-registration-redux officially supports Python 2.7, 3.4, and 3.5, 3.6.
Backwards-incompatible changes
Version 2.0
Removed support for Django < 1.11.
Removed registration/urls.py in favor of registration/backends/default/urls.py
Version 1.9
Change of return signature of RegistrationProfileManager.activate_user. A tuple containing the User instance and a boolean of whether or not said user was activated is now returned.
Version 1.8
None
Version 1.7
None
Version 1.6
None
Version 1.5
Support for Django 1.7 is removed, and Django 1.8 or newer is required.
Change signature of RegistrationProfileManager.activate_user. site is now a required positional argument. See #244.
Version 1.4
Remove unnecessary _RequestPassingFormView. See #56. Please ensure that you update any subclassed views to reference self.request instead of accepting request as an argument.
Version 1.3
Django 1.7 or newer is required. Please ensure you upgrade your Django version before upgrading.
Version 1.2
Native migration support breaks South compatibility: An initial native migration for Django > 1.7 has been provided. South users will need to configure a null migration with (SOUTH_MIGRATION_MODULES) in settings.py as shown below:
SOUTH_MIGRATION_MODULES = {
‘registration’: ‘registration.south_migrations’,
register method in RegistrationView has different parameters: The parameters of the
registermethod in RegistrationView have changed.
Version 1.1
base.html template required: A base.html template is now assumed to exist. Please ensure that your project provides one for django-registration-redux to inherit from.
HTML email templates: django-registration-redux now uses HTML email templates. If you previously customized text email templates, you need to do the same with the new HTML templates.
链接来自 官网
相关文章推荐
- HLS草案与版本对应关系
- Class版本号和Java版本对应关系
- Android platform 、 API Level 、版本名称(以食物命名)的对应关系图
- [转]Cocos Studio和Cocos2d-x版本对应关系
- web.xml各版本头文件及与JDK、Tomcat版本对应关系
- Android版本API级别与代号对应关系
- Cocos Studio和Cocos2d-x版本对应关系
- CentOS以及Oracle数据库发展历史及各版本新功能介绍, 便于构造环境时有个对应关系
- Visual Studio各版本工程文件之间对应关系
- Android对应关系——版本、源码和API Level对应关系
- Android版本和API Level对应关系 以及ADT中源码的关联
- Android版本和API Level对应关系
- Android的API版本和名称对应关系
- Android的API版本和名称对应关系
- Android SDK与API版本的对应关系
- servlet版本,tomcat版本,java版本,对应关系及选择
- Android--系统版本与API等级对应关系表
- Mysql java connector 与MySQL版本对应关系
- Shader Model 版本与DirectX的关系(OpenGL对应的呢?)
- 各个Zend Guard版本与Zend Optimizer各版本的对应关系