Don't evaluate fault_timezone when a custom timezone is set.Return NotImplemented from ErrorDetails._ne_.Stop calling set_context on Validators.Enforce is_valid(raise_exception=False) as a keyword-only argument.Add -api-version CLI option to generateschema management command.You can determine your currently installed version using pip show: pip show djangorestframework To upgrade Django REST framework to the latest version, use pip: pip install -U djangorestframework Note that in line with Django's policy, any parts of the framework not mentioned in the documentation should generally be considered private API, and may be subject to change. Version 1.3 would remove the deprecated bits of API entirely. Version 1.2 would escalate these warnings to subclass DeprecationWarning, which is loud by default. For example if you start running your tests using python -Wd manage.py test, you'll be warned of any API changes you need to make. These warnings are silent by default, but can be explicitly enabled when you're ready to start migrating any required changes. Version 1.1 would remain fully backwards compatible with 1.0, but would raise RemovedInDRF13Warning warnings, subclassing PendingDeprecationWarning, if you use the feature that are due to be deprecated. The timeline for deprecation of a feature present in version 1.0 would work as follows: REST framework releases follow a formal deprecation policy, which is in line with Django's deprecation policy.
Major version numbers (x.0.0) are reserved for substantial project milestones. You should read the release notes carefully before upgrading between medium point releases. Medium version numbers (0.x.0) may include API changes, in line with the deprecation policy. You should be able to upgrade between minor point releases without any other code changes. Minor version numbers (0.0.x) are used for changes that are API compatible.
0 kommentar(er)
