Changelog
### 1.14.9
```
======
* api-change:``ecs``: Update ecs client to latest version
* api-change:``opsworkscm``: Update opsworkscm client to latest version
* api-change:``workspaces``: Update workspaces client to latest version
* api-change:``datasync``: Update datasync client to latest version
* api-change:``eks``: Update eks client to latest version
```
### 1.14.8
```
======
* api-change:``rds``: Update rds client to latest version
* api-change:``iam``: Update iam client to latest version
```
### 1.14.7
```
======
* api-change:``ec2``: Update ec2 client to latest version
* api-change:``codepipeline``: Update codepipeline client to latest version
* api-change:``discovery``: Update discovery client to latest version
* api-change:``iotevents``: Update iotevents client to latest version
* api-change:``marketplacecommerceanalytics``: Update marketplacecommerceanalytics client to latest version
```
### 1.14.6
```
======
* api-change:``lambda``: Update lambda client to latest version
* api-change:``application-insights``: Update application-insights client to latest version
* api-change:``ec2``: Update ec2 client to latest version
* api-change:``cloudwatch``: Update cloudwatch client to latest version
* api-change:``kms``: Update kms client to latest version
* api-change:``alexaforbusiness``: Update alexaforbusiness client to latest version
```
### 1.14.5
```
======
* api-change:``mediaconvert``: Update mediaconvert client to latest version
* api-change:``neptune``: Update neptune client to latest version
* api-change:``cloudhsmv2``: Update cloudhsmv2 client to latest version
* api-change:``redshift``: Update redshift client to latest version
* api-change:``batch``: Update batch client to latest version
* api-change:``ecs``: Update ecs client to latest version
```
### 1.14.4
```
======
* api-change:``ec2``: Update ec2 client to latest version
* api-change:``sagemaker``: Update sagemaker client to latest version
* api-change:``ds``: Update ds client to latest version
```
### 1.14.3
```
======
* api-change:``securityhub``: Update securityhub client to latest version
* api-change:``ssm``: Update ssm client to latest version
* api-change:``ec2``: Update ec2 client to latest version
* api-change:``organizations``: Update organizations client to latest version
```
### 1.14.2
```
======
* api-change:``ec2``: Update ec2 client to latest version
```
### 1.14.1
```
======
* api-change:``efs``: Update efs client to latest version
* api-change:``ec2``: Update ec2 client to latest version
* api-change:``backup``: Update backup client to latest version
```
### 1.14.0
```
======
* api-change:``sagemaker``: Update sagemaker client to latest version
* api-change:``chime``: Update chime client to latest version
* api-change:``transfer``: Update transfer client to latest version
* api-change:``ec2``: Update ec2 client to latest version
* feature:Python: Dropped support for Python 2.6 and 3.3.
* api-change:``workspaces``: Update workspaces client to latest version
* api-change:``rds``: Update rds client to latest version
```
### 1.13.50
```
=======
* api-change:``logs``: Update logs client to latest version
```
### 1.13.49
```
=======
* api-change:``fms``: Update fms client to latest version
* api-change:``translate``: Update translate client to latest version
* api-change:``ce``: Update ce client to latest version
```
### 1.13.48
```
=======
* api-change:``codebuild``: Update codebuild client to latest version
* api-change:``mgh``: Update mgh client to latest version
* api-change:``xray``: Update xray client to latest version
```
### 1.13.47
```
=======
* api-change:``comprehend``: Update comprehend client to latest version
* api-change:``mediapackage``: Update mediapackage client to latest version
* api-change:``ec2``: Update ec2 client to latest version
```
### 1.13.46
```
=======
* api-change:``lex-models``: Update lex-models client to latest version
* api-change:``ecr``: Update ecr client to latest version
* api-change:``lightsail``: Update lightsail client to latest version
* api-change:``ce``: Update ce client to latest version
```
### 1.13.45
```
=======
* api-change:``fsx``: Update fsx client to latest version
* api-change:``health``: Update health client to latest version
* api-change:``detective``: Update detective client to latest version
```
### 1.13.44
```
=======
* api-change:``transcribe``: Update transcribe client to latest version
* api-change:``eks``: Update eks client to latest version
* api-change:``ec2``: Update ec2 client to latest version
* api-change:``rds``: Update rds client to latest version
* api-change:``ssm``: Update ssm client to latest version
* api-change:``redshift``: Update redshift client to latest version
* api-change:``pinpoint``: Update pinpoint client to latest version
* api-change:``securityhub``: Update securityhub client to latest version
* api-change:``devicefarm``: Update devicefarm client to latest version
```
### 1.13.43
```
=======
* api-change:``transcribe``: Update transcribe client to latest version
* api-change:``dlm``: Update dlm client to latest version
* api-change:``lex-models``: Update lex-models client to latest version
* api-change:``personalize-runtime``: Update personalize-runtime client to latest version
* api-change:``ssm``: Update ssm client to latest version
* api-change:``codestar-connections``: Update codestar-connections client to latest version
* api-change:``gamelift``: Update gamelift client to latest version
* api-change:``ec2``: Update ec2 client to latest version
```
### 1.13.42
```
=======
* api-change:``ec2``: Update ec2 client to latest version
* api-change:``s3``: Update s3 client to latest version
* api-change:``resourcegroupstaggingapi``: Update resourcegroupstaggingapi client to latest version
* api-change:``cloudfront``: Update cloudfront client to latest version
* enhancement:``s3``: Add support for opting into using the us-east-1 regional endpoint.
* api-change:``opsworkscm``: Update opsworkscm client to latest version
```
### 1.13.41
```
=======
* api-change:``kinesisanalyticsv2``: Update kinesisanalyticsv2 client to latest version
* api-change:``ssm``: Update ssm client to latest version
* api-change:``medialive``: Update medialive client to latest version
* api-change:``iot``: Update iot client to latest version
* api-change:``ecs``: Update ecs client to latest version
* api-change:``ec2``: Update ec2 client to latest version
```
### 1.13.40
```
=======
* api-change:``mq``: Update mq client to latest version
* api-change:``comprehendmedical``: Update comprehendmedical client to latest version
* api-change:``ec2``: Update ec2 client to latest version
```
### 1.13.39
```
=======
* api-change:``codebuild``: Update codebuild client to latest version
* api-change:``detective``: Update detective client to latest version
* api-change:``sesv2``: Update sesv2 client to latest version
```
### 1.13.38
```
=======
* api-change:``accessanalyzer``: Update accessanalyzer client to latest version
```
Links
- PyPI: https://pypi.org/project/botocore
- Changelog: https://pyup.io/changelogs/botocore/
- Repo: https://github.com/boto/botocore
Changelog
### 2.0.0
```
* Added support for newer Django and Python versions
* Added an extensibility that applications to add their own labels to middleware (request/response) metrics
* Allow overriding and setting custom bucket values for request/response latency histogram metric
* Internal improvements:
* use tox
* Use pytest
* use Black
* Automate pre-releases on every commit ot master
* Fix flaky tests.
```
Links
- PyPI: https://pypi.org/project/django-prometheus
- Changelog: https://pyup.io/changelogs/django-prometheus/
- Repo: http://github.com/korfuri/django-prometheus
Changelog
### 3.0.2
```
==========================
*January 2, 2020*
Django 3.0.2 fixes several bugs in 3.0.1.
Bugfixes
========
* Fixed a regression in Django 3.0 that didn't include columns referenced by a
``Subquery()`` in the ``GROUP BY`` clause (:ticket:`31094`).
* Fixed a regression in Django 3.0 where ``QuerySet.exists()`` crashed if a
queryset contained an aggregation over a ``Subquery()`` (:ticket:`31109`).
* Fixed a regression in Django 3.0 that caused a migration crash on PostgreSQL
10+ when adding a foreign key and changing data in the same migration
(:ticket:`31106`).
* Fixed a regression in Django 3.0 where loading fixtures crashed for models
defining a :attr:`~django.db.models.Field.default` for the primary key
(:ticket:`31071`).
==========================
```
### 3.0.1
```
==========================
*December 18, 2019*
Django 3.0.1 fixes a security issue and several bugs in 3.0.
CVE-2019-19844: Potential account hijack via password reset form
================================================================
By submitting a suitably crafted email address making use of Unicode
characters, that compared equal to an existing user email when lower-cased for
comparison, an attacker could be sent a password reset token for the matched
account.
In order to avoid this vulnerability, password reset requests now compare the
submitted email using the stricter, recommended algorithm for case-insensitive
comparison of two identifiers from `Unicode Technical Report 36, section
2.11.2(B)(2)`__. Upon a match, the email containing the reset token will be
sent to the email address on record rather than the submitted address.
.. __: https://www.unicode.org/reports/tr36/Recommendations_General
Bugfixes
========
* Fixed a regression in Django 3.0 by restoring the ability to use Django
inside Jupyter and other environments that force an async context, by adding
an option to disable :ref:`async-safety` mechanism with
``DJANGO_ALLOW_ASYNC_UNSAFE`` environment variable (:ticket:`31056`).
* Fixed a regression in Django 3.0 where ``RegexPattern``, used by
:func:`~django.urls.re_path`, returned positional arguments to be passed to
the view when all optional named groups were missing (:ticket:`31061`).
* Reallowed, following a regression in Django 3.0,
:class:`~django.db.models.expressions.Window` expressions to be used in
conditions outside of queryset filters, e.g. in
:class:`~django.db.models.expressions.When` conditions (:ticket:`31060`).
* Fixed a data loss possibility in
:class:`~django.contrib.postgres.forms.SplitArrayField`. When using with
``ArrayField(BooleanField())``, all values after the first ``True`` value
were marked as checked instead of preserving passed values (:ticket:`31073`).
========================
```
### 3.0
```
========================
*December 2, 2019*
Welcome to Django 3.0!
These release notes cover the :ref:`new features <whats-new-3.0>`, as well as
some :ref:`backwards incompatible changes <backwards-incompatible-3.0>` you'll
want to be aware of when upgrading from Django 2.2 or earlier. We've
:ref:`dropped some features<removed-features-3.0>` that have reached the end of
their deprecation cycle, and we've :ref:`begun the deprecation process for
some features <deprecated-features-3.0>`.
See the :doc:`/howto/upgrade-version` guide if you're updating an existing
project.
Python compatibility
====================
Django 3.0 supports Python 3.6, 3.7, and 3.8. We **highly recommend** and only
officially support the latest release of each series.
The Django 2.2.x series is the last to support Python 3.5.
Third-party library support for older version of Django
=======================================================
Following the release of Django 3.0, we suggest that third-party app authors
drop support for all versions of Django prior to 2.2. At that time, you should
be able to run your package's tests using ``python -Wd`` so that deprecation
warnings appear. After making the deprecation warning fixes, your app should be
compatible with Django 3.0.
.. _whats-new-3.0:
What's new in Django 3.0
========================
MariaDB support
---------------
Django now officially supports `MariaDB <https://mariadb.org/>`_ 10.1 and
higher. See :ref:`MariaDB notes <mariadb-notes>` for more details.
ASGI support
------------
Django 3.0 begins our journey to making Django fully async-capable by providing
support for running as an `ASGI <https://asgi.readthedocs.io/>`_ application.
This is in addition to our existing WSGI support. Django intends to support
both for the foreseeable future. Async features will only be available to
applications that run under ASGI, however.
There is no need to switch your applications over unless you want to start
experimenting with asynchronous code, but we have
:doc:`documentation on deploying with ASGI </howto/deployment/asgi/index>` if
you want to learn more.
Note that as a side-effect of this change, Django is now aware of asynchronous
event loops and will block you calling code marked as "async unsafe" - such as
ORM operations - from an asynchronous context. If you were using Django from
async code before, this may trigger if you were doing it incorrectly. If you
see a ``SynchronousOnlyOperation`` error, then closely examine your code and
move any database operations to be in a synchronous child thread.
Exclusion constraints on PostgreSQL
-----------------------------------
The new :class:`~django.contrib.postgres.constraints.ExclusionConstraint` class
enable adding exclusion constraints on PostgreSQL. Constraints are added to
models using the
:attr:`Meta.constraints <django.db.models.Options.constraints>` option.
Filter expressions
------------------
Expressions that output :class:`~django.db.models.BooleanField` may now be
used directly in ``QuerySet`` filters, without having to first annotate and
then filter against the annotation.
Enumerations for model field choices
------------------------------------
Custom enumeration types ``TextChoices``, ``IntegerChoices``, and ``Choices``
are now available as a way to define :attr:`.Field.choices`. ``TextChoices``
and ``IntegerChoices`` types are provided for text and integer fields. The
``Choices`` class allows defining a compatible enumeration for other concrete
data types. These custom enumeration types support human-readable labels that
can be translated and accessed via a property on the enumeration or its
members. See :ref:`Enumeration types <field-choices-enum-types>` for more
details and examples.
Minor features
--------------
:mod:`django.contrib.admin`
~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Added support for the ``admin_order_field`` attribute on properties in
:attr:`.ModelAdmin.list_display`.
* The new :meth:`ModelAdmin.get_inlines()
<django.contrib.admin.ModelAdmin.get_inlines>` method allows specifying the
inlines based on the request or model instance.
* Select2 library is upgraded from version 4.0.3 to 4.0.7.
* jQuery is upgraded from version 3.3.1 to 3.4.1.
:mod:`django.contrib.auth`
~~~~~~~~~~~~~~~~~~~~~~~~~~
* The new ``reset_url_token`` attribute in
:class:`~django.contrib.auth.views.PasswordResetConfirmView` allows
specifying a token parameter displayed as a component of password reset
URLs.
* Added :class:`~django.contrib.auth.backends.BaseBackend` class to ease
customization of authentication backends.
* Added :meth:`~django.contrib.auth.models.User.get_user_permissions()` method
to mirror the existing
:meth:`~django.contrib.auth.models.User.get_group_permissions()` method.
* Added HTML ``autocomplete`` attribute to widgets of username, email, and
password fields in :mod:`django.contrib.auth.forms` for better interaction
with browser password managers.
* :djadmin:`createsuperuser` now falls back to environment variables for
password and required fields, when a corresponding command line argument
isn't provided in non-interactive mode.
* :attr:`~django.contrib.auth.models.CustomUser.REQUIRED_FIELDS` now supports
:class:`~django.db.models.ManyToManyField`\s.
* The new :meth:`.UserManager.with_perm` method returns users that have the
specified permission.
* The default iteration count for the PBKDF2 password hasher is increased from
150,000 to 180,000.
:mod:`django.contrib.gis`
~~~~~~~~~~~~~~~~~~~~~~~~~
* Allowed MySQL spatial lookup functions to operate on real geometries.
Previous support was limited to bounding boxes.
* Added the :class:`~django.contrib.gis.db.models.functions.GeometryDistance`
function, supported on PostGIS.
* Added support for the ``furlong`` unit in
:class:`~django.contrib.gis.measure.Distance`.
* The :setting:`GEOIP_PATH` setting now supports :class:`pathlib.Path`.
* The :class:`~django.contrib.gis.geoip2.GeoIP2` class now accepts
:class:`pathlib.Path` ``path``.
:mod:`django.contrib.postgres`
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* The new :class:`~django.contrib.postgres.fields.RangeOperators` helps to
avoid typos in SQL operators that can be used together with
:class:`~django.contrib.postgres.fields.RangeField`.
* The new :class:`~django.contrib.postgres.fields.RangeBoundary` expression
represents the range boundaries.
* The new :class:`~django.contrib.postgres.operations.AddIndexConcurrently`
and :class:`~django.contrib.postgres.operations.RemoveIndexConcurrently`
classes allow creating and dropping indexes ``CONCURRENTLY`` on PostgreSQL.
:mod:`django.contrib.sessions`
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* The new
:meth:`~django.contrib.sessions.backends.base.SessionBase.get_session_cookie_age()`
method allows dynamically specifying the session cookie age.
:mod:`django.contrib.syndication`
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Added the ``language`` class attribute to the
:class:`django.contrib.syndication.views.Feed` to customize a feed language.
The default value is :func:`~django.utils.translation.get_language()` instead
of :setting:`LANGUAGE_CODE`.
Cache
~~~~~
* :func:`~django.utils.cache.add_never_cache_headers` and
:func:`~django.views.decorators.cache.never_cache` now add the ``private``
directive to ``Cache-Control`` headers.
File Storage
~~~~~~~~~~~~
* The new :meth:`.Storage.get_alternative_name` method allows customizing the
algorithm for generating filenames if a file with the uploaded name already
exists.
Forms
~~~~~
* Formsets may control the widget used when ordering forms via
:attr:`~django.forms.formsets.BaseFormSet.can_order` by setting the
:attr:`~django.forms.formsets.BaseFormSet.ordering_widget` attribute or
overriding :attr:`~django.forms.formsets.BaseFormSet.get_ordering_widget()`.
Internationalization
~~~~~~~~~~~~~~~~~~~~
* Added the :setting:`LANGUAGE_COOKIE_HTTPONLY`,
:setting:`LANGUAGE_COOKIE_SAMESITE`, and :setting:`LANGUAGE_COOKIE_SECURE`
settings to set the ``HttpOnly``, ``SameSite``, and ``Secure`` flags on
language cookies. The default values of these settings preserve the previous
behavior.
* Added support and translations for the Uzbek language.
Logging
~~~~~~~
* The new ``reporter_class`` parameter of
:class:`~django.utils.log.AdminEmailHandler` allows providing an
``django.views.debug.ExceptionReporter`` subclass to customize the traceback
text sent to site :setting:`ADMINS` when :setting:`DEBUG` is ``False``.
Management Commands
~~~~~~~~~~~~~~~~~~~
* The new :option:`compilemessages --ignore` option allows ignoring specific
directories when searching for ``.po`` files to compile.
* :option:`showmigrations --list` now shows the applied datetimes when
``--verbosity`` is 2 and above.
* On PostgreSQL, :djadmin:`dbshell` now supports client-side TLS certificates.
* :djadmin:`inspectdb` now introspects :class:`~django.db.models.OneToOneField`
when a foreign key has a unique or primary key constraint.
* The new :option:`--skip-checks` option skips running system checks prior to
running the command.
* The :option:`startapp --template` and :option:`startproject --template`
options now support templates stored in XZ archives (``.tar.xz``, ``.txz``)
and LZMA archives (``.tar.lzma``, ``.tlz``).
Models
~~~~~~
* Added hash database functions :class:`~django.db.models.functions.MD5`,
:class:`~django.db.models.functions.SHA1`,
:class:`~django.db.models.functions.SHA224`,
:class:`~django.db.models.functions.SHA256`,
:class:`~django.db.models.functions.SHA384`, and
:class:`~django.db.models.functions.SHA512`.
* Added the :class:`~django.db.models.functions.Sign` database function.
* The new ``is_dst`` parameter of the
:class:`~django.db.models.functions.Trunc` database functions determines the
treatment of nonexistent and ambiguous datetimes.
* ``connection.queries`` now shows ``COPY … TO`` statements on PostgreSQL.
* :class:`~django.db.models.FilePathField` now accepts a callable for ``path``.
* Allowed symmetrical intermediate table for self-referential
:class:`~django.db.models.ManyToManyField`.
* The ``name`` attributes of :class:`~django.db.models.CheckConstraint`,
:class:`~django.db.models.UniqueConstraint`, and
:class:`~django.db.models.Index` now support app label and class
interpolation using the ``'%(app_label)s'`` and ``'%(class)s'`` placeholders.
* The new :attr:`.Field.descriptor_class` attribute allows model fields to
customize the get and set behavior by overriding their
:py:ref:`descriptors <descriptors>`.
* :class:`~django.db.models.Avg` and :class:`~django.db.models.Sum` now support
the ``distinct`` argument.
* Added :class:`~django.db.models.SmallAutoField` which acts much like an
:class:`~django.db.models.AutoField` except that it only allows values under
a certain (database-dependent) limit. Values from ``1`` to ``32767`` are safe
in all databases supported by Django.
* :class:`~django.db.models.AutoField`,
:class:`~django.db.models.BigAutoField`, and
:class:`~django.db.models.SmallAutoField` now inherit from
``IntegerField``, ``BigIntegerField`` and ``SmallIntegerField`` respectively.
System checks and validators are now also properly inherited.
* :attr:`.FileField.upload_to` now supports :class:`pathlib.Path`.
* :class:`~django.db.models.CheckConstraint` is now supported on MySQL 8.0.16+.
* The new ``allows_group_by_selected_pks_on_model()`` method of
``django.db.backends.base.BaseDatabaseFeatures`` allows optimization of
``GROUP BY`` clauses to require only the selected models' primary keys. By
default, it's supported only for managed models on PostgreSQL.
To enable the ``GROUP BY`` primary key-only optimization for unmanaged
models, you have to subclass the PostgreSQL database engine, overriding the
features class ``allows_group_by_selected_pks_on_model()`` method as you
require. See :ref:`Subclassing the built-in database backends
<subclassing-database-backends>` for an example.
Requests and Responses
~~~~~~~~~~~~~~~~~~~~~~
* Allowed :class:`~django.http.HttpResponse` to be initialized with
:class:`memoryview` content.
* For use in, for example, Django templates, :attr:`.HttpRequest.headers` now
allows lookups using underscores (e.g. ``user_agent``) in place of hyphens.
.. _whats-new-security-3.0:
Security
~~~~~~~~
* :setting:`X_FRAME_OPTIONS` now defaults to ``'DENY'``. In older versions, the
:setting:`X_FRAME_OPTIONS` setting defaults to ``'SAMEORIGIN'``. If your site
uses frames of itself, you will need to explicitly set ``X_FRAME_OPTIONS =
'SAMEORIGIN'`` for them to continue working.
* :setting:`SECURE_CONTENT_TYPE_NOSNIFF` setting now defaults to ``True``. With
the enabled :setting:`SECURE_CONTENT_TYPE_NOSNIFF`, the
:class:`~django.middleware.security.SecurityMiddleware` sets the
:ref:`x-content-type-options` header on all responses that do not already
have it.
* :class:`~django.middleware.security.SecurityMiddleware` can now send the
:ref:`Referrer-Policy <referrer-policy>` header.
Tests
~~~~~
* The new test :class:`~django.test.Client` argument
``raise_request_exception`` allows controlling whether or not exceptions
raised during the request should also be raised in the test. The value
defaults to ``True`` for backwards compatibility. If it is ``False`` and an
exception occurs, the test client will return a 500 response with the
attribute :attr:`~django.test.Response.exc_info`, a tuple providing
information of the exception that occurred.
* Tests and test cases to run can be selected by test name pattern using the
new :option:`test -k` option.
* HTML comparison, as used by
:meth:`~django.test.SimpleTestCase.assertHTMLEqual`, now treats text, character
references, and entity references that refer to the same character as
equivalent.
* Django test runner now supports headless mode for selenium tests on supported
browsers. Add the ``--headless`` option to enable this mode.
* Django test runner now supports ``--start-at`` and ``--start-after`` options
to run tests starting from a specific top-level module.
* Django test runner now supports a ``--pdb`` option to spawn a debugger at
each error or failure.
.. _backwards-incompatible-3.0:
Backwards incompatible changes in 3.0
=====================================
``Model.save()`` when providing a default for the primary key
-------------------------------------------------------------
:meth:`.Model.save` no longer attempts to find a row when saving a new
``Model`` instance and a default value for the primary key is provided, and
always performs a single ``INSERT`` query. In older Django versions,
``Model.save()`` performed either an ``INSERT`` or an ``UPDATE`` based on
whether or not the row exists.
This makes calling ``Model.save()`` while providing a default primary key value
equivalent to passing :ref:`force_insert=True <ref-models-force-insert>` to
model's ``save()``. Attempts to use a new ``Model`` instance to update an
existing row will result in an ``IntegrityError``.
In order to update an existing model for a specific primary key value, use the
:meth:`~django.db.models.query.QuerySet.update_or_create` method or
``QuerySet.filter(pk=…).update(…)`` instead. For example::
>>> MyModel.objects.update_or_create(pk=existing_pk, defaults={'name': 'new name'})
>>> MyModel.objects.filter(pk=existing_pk).update(name='new name')
Database backend API
--------------------
This section describes changes that may be needed in third-party database
backends.
* The second argument of ``DatabaseIntrospection.get_geometry_type()`` is now
the row description instead of the column name.
* ``DatabaseIntrospection.get_field_type()`` may no longer return tuples.
* If the database can create foreign keys in the same SQL statement that adds a
field, add ``SchemaEditor.sql_create_column_inline_fk`` with the appropriate
SQL; otherwise, set ``DatabaseFeatures.can_create_inline_fk = False``.
* ``DatabaseFeatures.can_return_id_from_insert`` and
``can_return_ids_from_bulk_insert`` are renamed to
``can_return_columns_from_insert`` and ``can_return_rows_from_bulk_insert``.
* Database functions now handle :class:`datetime.timezone` formats when created
using :class:`datetime.timedelta` instances (e.g.
``timezone(timedelta(hours=5))``, which would output ``'UTC+05:00'``).
Third-party backends should handle this format when preparing
:class:`~django.db.models.DateTimeField` in ``datetime_cast_date_sql()``,
``datetime_extract_sql()``, etc.
* Entries for ``AutoField``, ``BigAutoField``, and ``SmallAutoField`` are added
to ``DatabaseOperations.integer_field_ranges`` to support the integer range
validators on these field types. Third-party backends may need to customize
the default entries.
* ``DatabaseOperations.fetch_returned_insert_id()`` is replaced by
``fetch_returned_insert_columns()`` which returns a list of values returned
by the ``INSERT … RETURNING`` statement, instead of a single value.
* ``DatabaseOperations.return_insert_id()`` is replaced by
``return_insert_columns()`` that accepts a ``fields``
argument, which is an iterable of fields to be returned after insert. Usually
this is only the auto-generated primary key.
:mod:`django.contrib.admin`
---------------------------
* Admin's model history change messages now prefers more readable field labels
instead of field names.
:mod:`django.contrib.gis`
-------------------------
* Support for PostGIS 2.1 is removed.
* Support for SpatiaLite 4.1 and 4.2 is removed.
* Support for GDAL 1.11 and GEOS 3.4 is removed.
Dropped support for PostgreSQL 9.4
----------------------------------
Upstream support for PostgreSQL 9.4 ends in December 2019. Django 3.0 supports
PostgreSQL 9.5 and higher.
Dropped support for Oracle 12.1
-------------------------------
Upstream support for Oracle 12.1 ends in July 2021. Django 2.2 will be
supported until April 2022. Django 3.0 officially supports Oracle 12.2 and 18c.
Removed private Python 2 compatibility APIs
-------------------------------------------
While Python 2 support was removed in Django 2.0, some private APIs weren't
removed from Django so that third party apps could continue using them until
the Python 2 end-of-life.
Since we expect apps to drop Python 2 compatibility when adding support for
Django 3.0, we're removing these APIs at this time.
* ``django.test.utils.str_prefix()`` - Strings don't have 'u' prefixes in
Python 3.
* ``django.test.utils.patch_logger()`` - Use
:meth:`unittest.TestCase.assertLogs` instead.
* ``django.utils.lru_cache.lru_cache()`` - Alias of
:func:`functools.lru_cache`.
* ``django.utils.decorators.available_attrs()`` - This function returns
``functools.WRAPPER_ASSIGNMENTS``.
* ``django.utils.decorators.ContextDecorator`` - Alias of
:class:`contextlib.ContextDecorator`.
* ``django.utils._os.abspathu()`` - Alias of :func:`os.path.abspath`.
* ``django.utils._os.upath()`` and ``npath()`` - These functions do nothing on
Python 3.
* ``django.utils.six`` - Remove usage of this vendored library or switch to
`six <https://pypi.org/project/six/>`_.
* ``django.utils.encoding.python_2_unicode_compatible()`` - Alias of
``six.python_2_unicode_compatible()``.
* ``django.utils.functional.curry()`` - Use :func:`functools.partial` or
:class:`functools.partialmethod`. See :commit:`5b1c389603a353625ae1603`.
* ``django.utils.safestring.SafeBytes`` - Unused since Django 2.0.
New default value for the ``FILE_UPLOAD_PERMISSIONS`` setting
-------------------------------------------------------------
In older versions, the :setting:`FILE_UPLOAD_PERMISSIONS` setting defaults to
``None``. With the default :setting:`FILE_UPLOAD_HANDLERS`, this results in
uploaded files having different permissions depending on their size and which
upload handler is used.
``FILE_UPLOAD_PERMISSION`` now defaults to ``0o644`` to avoid this
inconsistency.
New default values for security settings
----------------------------------------
To make Django projects more secure by default, some security settings now have
more secure default values:
* :setting:`X_FRAME_OPTIONS` now defaults to ``'DENY'``.
* :setting:`SECURE_CONTENT_TYPE_NOSNIFF` now defaults to ``True``.
See the *What's New* :ref:`Security section <whats-new-security-3.0>` above for
more details on these changes.
Miscellaneous
-------------
* ``ContentType.__str__()`` now includes the model's ``app_label`` to
disambiguate models with the same name in different apps.
* Because accessing the language in the session rather than in the cookie is
deprecated, ``LocaleMiddleware`` no longer looks for the user's language in
the session and :func:`django.contrib.auth.logout` no longer preserves the
session's language after logout.
* :func:`django.utils.html.escape` now uses :func:`html.escape` to escape HTML.
This converts ``'`` to ``&x27;`` instead of the previous equivalent decimal
code ``&39;``.
* The ``django-admin test -k`` option now works as the :option:`unittest
-k<unittest.-k>` option rather than as a shortcut for ``--keepdb``.
* Support for ``pywatchman`` < 1.2.0 is removed.
* :func:`~django.utils.http.urlencode` now encodes iterable values as they are
when ``doseq=False``, rather than iterating them, bringing it into line with
the standard library :func:`urllib.parse.urlencode` function.
* ``intword`` template filter now translates ``1.0`` as a singular phrase and
all other numeric values as plural. This may be incorrect for some languages.
* Assigning a value to a model's :class:`~django.db.models.ForeignKey` or
:class:`~django.db.models.OneToOneField` ``'_id'`` attribute now unsets the
corresponding field. Accessing the field afterwards will result in a query.
* :func:`~django.utils.cache.patch_vary_headers` now handles an asterisk
``'*'`` according to :rfc:`7231section-7.1.4`, i.e. if a list of header
field names contains an asterisk, then the ``Vary`` header will consist of a
single asterisk ``'*'``.
* On MySQL 8.0.16+, ``PositiveIntegerField`` and ``PositiveSmallIntegerField``
now include a check constraint to prevent negative values in the database.
* ``alias=None`` is added to the signature of
:meth:`.Expression.get_group_by_cols`.
* Support for ``sqlparse`` < 0.2.2 is removed.
* ``RegexPattern``, used by :func:`~django.urls.re_path`, no longer returns
keyword arguments with ``None`` values to be passed to the view for the
optional named groups that are missing.
.. _deprecated-features-3.0:
Features deprecated in 3.0
==========================
``django.utils.encoding.force_text()`` and ``smart_text()``
-----------------------------------------------------------
The ``smart_text()`` and ``force_text()`` aliases (since Django 2.0) of
``smart_str()`` and ``force_str()`` are deprecated. Ignore this deprecation if
your code supports Python 2 as the behavior of ``smart_str()`` and
``force_str()`` is different there.
Miscellaneous
-------------
* ``django.utils.http.urlquote()``, ``urlquote_plus()``, ``urlunquote()``, and
``urlunquote_plus()`` are deprecated in favor of the functions that they're
aliases for: :func:`urllib.parse.quote`, :func:`~urllib.parse.quote_plus`,
:func:`~urllib.parse.unquote`, and :func:`~urllib.parse.unquote_plus`.
* ``django.utils.translation.ugettext()``, ``ugettext_lazy()``,
``ugettext_noop()``, ``ungettext()``, and ``ungettext_lazy()`` are deprecated
in favor of the functions that they're aliases for:
:func:`django.utils.translation.gettext`,
:func:`~django.utils.translation.gettext_lazy`,
:func:`~django.utils.translation.gettext_noop`,
:func:`~django.utils.translation.ngettext`, and
:func:`~django.utils.translation.ngettext_lazy`.
* To limit creation of sessions and hence favor some caching strategies,
:func:`django.views.i18n.set_language` will stop setting the user's language
in the session in Django 4.0. Since Django 2.1, the language is always stored
in the :setting:`LANGUAGE_COOKIE_NAME` cookie.
* ``django.utils.text.unescape_entities()`` is deprecated in favor of
:func:`html.unescape`. Note that unlike ``unescape_entities()``,
``html.unescape()`` evaluates lazy strings immediately.
* To avoid possible confusion as to effective scope, the private internal
utility ``is_safe_url()`` is renamed to
``url_has_allowed_host_and_scheme()``. That a URL has an allowed host and
scheme doesn't in general imply that it's "safe". It may still be quoted
incorrectly, for example. Ensure to also use
:func:`~django.utils.encoding.iri_to_uri` on the path component of untrusted
URLs.
.. _removed-features-3.0:
Features removed in 3.0
=======================
These features have reached the end of their deprecation cycle and are removed
in Django 3.0.
See :ref:`deprecated-features-2.0` for details on these changes, including how
to remove usage of these features.
* The ``django.db.backends.postgresql_psycopg2`` module is removed.
* ``django.shortcuts.render_to_response()`` is removed.
* The ``DEFAULT_CONTENT_TYPE`` setting is removed.
* ``HttpRequest.xreadlines()`` is removed.
* Support for the ``context`` argument of ``Field.from_db_value()`` and
``Expression.convert_value()`` is removed.
* The ``field_name`` keyword argument of ``QuerySet.earliest()`` and
``latest()`` is removed.
See :ref:`deprecated-features-2.1` for details on these changes, including how
to remove usage of these features.
* The ``ForceRHR`` GIS function is removed.
* ``django.utils.http.cookie_date()`` is removed.
* The ``staticfiles`` and ``admin_static`` template tag libraries are removed.
* ``django.contrib.staticfiles.templatetags.staticfiles.static()`` is removed.
==========================
```
### 2.2.9
```
==========================
*December 18, 2019*
Django 2.2.9 fixes a security issue and a data loss bug in 2.2.8.
CVE-2019-19844: Potential account hijack via password reset form
================================================================
By submitting a suitably crafted email address making use of Unicode
characters, that compared equal to an existing user email when lower-cased for
comparison, an attacker could be sent a password reset token for the matched
account.
In order to avoid this vulnerability, password reset requests now compare the
submitted email using the stricter, recommended algorithm for case-insensitive
comparison of two identifiers from `Unicode Technical Report 36, section
2.11.2(B)(2)`__. Upon a match, the email containing the reset token will be
sent to the email address on record rather than the submitted address.
.. __: https://www.unicode.org/reports/tr36/Recommendations_General
Bugfixes
========
* Fixed a data loss possibility in
:class:`~django.contrib.postgres.forms.SplitArrayField`. When using with
``ArrayField(BooleanField())``, all values after the first ``True`` value
were marked as checked instead of preserving passed values (:ticket:`31073`).
==========================
```
Links
- PyPI: https://pypi.org/project/django
- Changelog: https://pyup.io/changelogs/django/
- Homepage: https://www.djangoproject.com/
Changelog
### 0.16
```
=========================
.. Note::
Docutils 0.15.x is the last version supporting Python 2.6, 3.3 and 3.4.
Docutils 0.16.x supports Python 2.7 and Python >= 3.5 natively,
without the use of the ``2to3`` tool.
* reStructuredText:
- Keep `backslash escapes`__ in the document tree. This allows, e.g.,
escaping of author-separators in `bibliographic fields`__.
__ http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.htmlescaping-mechanism
__ docs/ref/rst/restructuredtext.htmlbibliographic-fields
* LaTeX writer:
- Informal titles of type "rubric" default to bold-italic and left aligned.
- Deprecate ``\docutilsrole`` prefix for styling commands:
use ``\DUrole`` instead.
- Fix topic subtitle.
- Add "latex writers" to the `config_section_dependencies`.
- Ignore classes for `rubric` elements
(class wrapper interferes with LaTeX formatting).
* tools/buildhtml.py
- New option "--html-writer" allows to select "html__" (default),
"html4" or "html5".
__ html: docs/user/html.htmlhtml
* docutils/io.py
- Remove the `handle_io_errors` option from io.FileInput/Output.
* docutils/nodes.py
- If `auto_id_prefix`_ ends with "%", this is replaced with the tag name.
.. _auto_id_prefix: docs/user/config.htmlauto-id-prefix
* Various bugfixes and improvements (see HISTORY_).
```
Links
- PyPI: https://pypi.org/project/docutils
- Changelog: https://pyup.io/changelogs/docutils/
- Homepage: http://docutils.sourceforge.net/
Changelog
### 1.4.7
```
This is a minor release focused on KafkaConsumer performance, Admin Client
improvements, and Client concurrency. The KafkaConsumer iterator implementation
has been greatly simplified so that it just wraps consumer.poll(). The prior
implementation will remain available for a few more releases using the optional
KafkaConsumer config: `legacy_iterator=True` . This is expected to improve
consumer throughput substantially and help reduce heartbeat failures / group
rebalancing.
Client
* Send socket data via non-blocking IO with send buffer (dpkp / PR 1912)
* Rely on socket selector to detect completed connection attempts (dpkp / PR 1909)
* Improve connection lock handling; always use context manager (melor,dpkp / PR 1895)
* Reduce client poll timeout when there are no in-flight requests (dpkp / PR 1823)
KafkaConsumer
* Do not use wakeup when sending fetch requests from consumer (dpkp / PR 1911)
* Wrap `consumer.poll()` for KafkaConsumer iteration (dpkp / PR 1902)
* Allow the coordinator to auto-commit on old brokers (justecorruptio / PR 1832)
* Reduce internal client poll timeout for (legacy) consumer iterator interface (dpkp / PR 1824)
* Use dedicated connection for group coordinator (dpkp / PR 1822)
* Change coordinator lock acquisition order (dpkp / PR 1821)
* Make `partitions_for_topic` a read-through cache (Baisang / PR 1781,1809)
* Fix consumer hanging indefinitely on topic deletion while rebalancing (commanderdishwasher / PR 1782)
Miscellaneous Bugfixes / Improvements
* Fix crc32c avilability on non-intel architectures (ossdev07 / PR 1904)
* Load system default SSL CAs if `ssl_cafile` is not provided (iAnomaly / PR 1883)
* Catch py3 TimeoutError in BrokerConnection send/recv (dpkp / PR 1820)
* Added a function to determine if bootstrap is successfully connected (Wayde2014 / PR 1876)
Admin Client
* Add ACL api support to KafkaAdminClient (ulrikjohansson / PR 1833)
* Add `sasl_kerberos_domain_name` config to KafkaAdminClient (jeffwidman / PR 1852)
* Update `security_protocol` config documentation for KafkaAdminClient (cardy31 / PR 1849)
* Break FindCoordinator into request/response methods in KafkaAdminClient (jeffwidman / PR 1871)
* Break consumer operations into request / response methods in KafkaAdminClient (jeffwidman / PR 1845)
* Parallelize calls to `_send_request_to_node()` in KafkaAdminClient (davidheitman / PR 1807)
Test Infrastructure / Documentation / Maintenance
* Add Kafka 2.3.0 to test matrix and compatibility docs (dpkp / PR 1915)
* Convert remaining `KafkaConsumer` tests to `pytest` (jeffwidman / PR 1886)
* Bump integration tests to 0.10.2.2 and 0.11.0.3 (jeffwidman / 1890)
* Cleanup handling of `KAFKA_VERSION` env var in tests (jeffwidman / PR 1887)
* Minor test cleanup (jeffwidman / PR 1885)
* Use `socket.SOCK_STREAM` in test assertions (iv-m / PR 1879)
* Sanity test for `consumer.topics()` and `consumer.partitions_for_topic()` (Baisang / PR 1829)
* Cleanup seconds conversion in client poll timeout calculation (jeffwidman / PR 1825)
* Remove unused imports (jeffwidman / PR 1808)
* Cleanup python nits in RangePartitionAssignor (jeffwidman / PR 1805)
* Update links to kafka consumer config docs (jeffwidman)
* Fix minor documentation typos (carsonip / PR 1865)
* Remove unused/weird comment line (jeffwidman / PR 1813)
* Update docs for `api_version_auto_timeout_ms` (jeffwidman / PR 1812)
```
Links
- PyPI: https://pypi.org/project/kafka-python
- Changelog: https://pyup.io/changelogs/kafka-python/
- Repo: https://github.com/dpkp/kafka-python
Changelog
### 2.8.1
```
==========================
Data updates
------------
- Updated tzdata version to 2019c.
Bugfixes
--------
- Fixed a race condition in the ``tzoffset`` and ``tzstr`` "strong" caches on
Python 2.7. Reported by kainjow (gh issue 901).
- Parsing errors will now raise ``ParserError``, a subclass of ``ValueError``,
which has a nicer string representation. Patch by gfyoung (gh pr 881).
- ``parser.parse`` will now raise ``TypeError`` when ``tzinfos`` is passed a
type that cannot be interpreted as a time zone. Prior to this change, it
would raise an ``UnboundLocalError`` instead. Patch by jbrockmendel (gh pr
891).
- Changed error message raised when when passing a ``bytes`` object as the time
zone name to gettz in Python 3. Reported and fixed by labrys () (gh issue
927, gh pr 935).
- Changed compatibility logic to support a potential Python 4.0 release. Patch
by Hugo van Kemenade (gh pr 950).
- Updated many modules to use ``tz.UTC`` in favor of ``tz.tzutc()`` internally,
to avoid an unnecessary function call. (gh pr 910).
- Fixed issue where ``dateutil.tz`` was using a backported version of
``contextlib.nullcontext`` even in Python 3.7 due to a malformed import
statement. (gh pr 963).
Tests
-----
- Switched from using assertWarns to using pytest.warns in the test suite. (gh
pr 969).
- Fix typo in setup.cfg causing PendingDeprecationWarning to not be explicitly
specified as an error in the warnings filter. (gh pr 966)
- Fixed issue where ``test_tzlocal_offset_equal`` would fail in certain
environments (such as FreeBSD) due to an invalid assumption about what time
zone names are provided. Reported and fixed by Kubilay Kocak (gh issue 918,
pr 928).
- Fixed a minor bug in ``test_isoparser`` related to ``bytes``/``str``
handling. Fixed by fhuang5 (gh issue 776, gh pr 879).
- Explicitly listed all markers used in the pytest configuration. (gh pr 915)
- Extensive improvements to the parser test suite, including the adoption of
``pytest``-style tests and the addition of parametrization of several test
cases. Patches by jbrockmendel (gh prs 735, 890, 892, 894).
- Added tests for tzinfos input types. Patch by jbrockmendel (gh pr 891).
- Fixed failure of test suite when changing the TZ variable is forbidden.
Patch by shadchin (gh pr 893).
- Pinned all test dependencies on Python 3.3. (gh prs 934, 962)
Documentation changes
---------------------
- Fixed many misspellings, typos and styling errors in the comments and
documentation. Patch by Hugo van Kemenade (gh pr 952).
Misc
----
- Added Python 3.8 to the trove classifiers. (gh pr 970)
- Moved as many keys from ``setup.py`` to ``setup.cfg`` as possible. Fixed by
FakeNameSE, aquinlan82, jachen20, and gurgenz221 (gh issue 871, gh pr
880).
- Reorganized ``parser`` methods by functionality. Patch by jbrockmendel (gh
pr 882).
- Switched ``release.py`` over to using ``pep517.build`` for creating releases,
rather than direct invocations of ``setup.py``. Fixed by smeng10 (gh issue
869, gh pr 875).
- Added a "build" environment into the tox configuration, to handle dependency
management when making releases. Fixed by smeng10 (gh issue 870,r
gh pr 876).
- GH 916, GH 971
```
Links
- PyPI: https://pypi.org/project/python-dateutil
- Changelog: https://pyup.io/changelogs/python-dateutil/
- Docs: https://dateutil.readthedocs.io
Changelog
### 5.0.1
```
------
* Fix packaging to indicate only Python 3.5+ compatibiity (thanks `mdalp
<https://github.com/mdalp>`_).
```
### 5.0
```
----
.. note:: This is a major version bump, but only because it removes Python 2
compatibility. If you were already running under Python 3 then there should
be no breaking changes.
WhiteNoise is now tested on Python 3.5--3.8 and Django 2.0--3.0.
Other changes include:
* Fix incompatibility with Django 3.0 which caused problems with Safari
(details `here <https://github.com/evansd/whitenoise/issues/240>`_). Thanks
`paltman <https://github.com/paltman>`_ and `giilby
<https://github.com/giilby>`_ for diagnosing.
* Lots of improvements to the test suite (including switching to py.test).
Thanks `NDevox <https://github.com/ndevox>`_ and `Djailla
<https://github.com/djailla>`_.
```
Links
- PyPI: https://pypi.org/project/whitenoise
- Changelog: https://pyup.io/changelogs/whitenoise/
- Homepage: http://whitenoise.evans.io
Changelog
### 5.0.3
```
----------------------------
- A performance improvement in 5.0.2 didn't work for test suites that changed
directory before combining data, causing "Couldn't use data file: no such
table: meta" errors (`issue 916`_). This is now fixed.
- Coverage could fail to run your program with some form of "ModuleNotFound" or
"ImportError" trying to import from the current directory. This would happen
if coverage had been packaged into a zip file (for example, on Windows), or
was found indirectly (for example, by pyenv-virtualenv). A number of
different scenarios were described in `issue 862`_ which is now fixed. Huge
thanks to Agbonze O. Jeremiah for reporting it, and Alexander Waters and
George-Cristian Bîrzan for protracted debugging sessions.
- Added the "premain" debug option.
- Added SQLite compile-time options to the "debug sys" output.
.. _issue 862: https://github.com/nedbat/coveragepy/issues/862
.. _issue 916: https://github.com/nedbat/coveragepy/issues/916
.. _changes_502:
```
### 5.0.2
```
----------------------------
- Programs that used multiprocessing and changed directories would fail under
coverage. This is now fixed (`issue 890`_). A side effect is that debug
information about the config files read now shows absolute paths to the
files.
- When running programs as modules (``coverage run -m``) with ``--source``,
some measured modules were imported before coverage starts. This resulted in
unwanted warnings ("Already imported a file that will be measured") and a
reduction in coverage totals (`issue 909`_). This is now fixed.
- If no data was collected, an exception about "No data to report" could happen
instead of a 0% report being created (`issue 884`_). This is now fixed.
- The handling of source files with non-encodable file names has changed.
Previously, if a file name could not be encoded as UTF-8, an error occurred,
as described in `issue 891`_. Now, those files will not be measured, since
their data would not be recordable.
- A new warning ("dynamic-conflict") is issued if two mechanisms are trying to
change the dynamic context. Closes `issue 901`_.
- ``coverage run --debug=sys`` would fail with an Attribute
pyup-bot
commented
4 years ago
Update boto3 from 1.10.34 to 1.11.9.
Changelog
### 1.11.9 ``` ====== * api-change:``ecs``: [``botocore``] Update ecs client to latest version * api-change:``opsworkscm``: [``botocore``] Update opsworkscm client to latest version * api-change:``workspaces``: [``botocore``] Update workspaces client to latest version * api-change:``datasync``: [``botocore``] Update datasync client to latest version * api-change:``eks``: [``botocore``] Update eks client to latest version ``` ### 1.11.8 ``` ====== * api-change:``rds``: [``botocore``] Update rds client to latest version * api-change:``iam``: [``botocore``] Update iam client to latest version ``` ### 1.11.7 ``` ====== * api-change:``ec2``: [``botocore``] Update ec2 client to latest version * api-change:``codepipeline``: [``botocore``] Update codepipeline client to latest version * api-change:``discovery``: [``botocore``] Update discovery client to latest version * api-change:``iotevents``: [``botocore``] Update iotevents client to latest version * api-change:``marketplacecommerceanalytics``: [``botocore``] Update marketplacecommerceanalytics client to latest version ``` ### 1.11.6 ``` ====== * api-change:``lambda``: [``botocore``] Update lambda client to latest version * api-change:``application-insights``: [``botocore``] Update application-insights client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version * api-change:``cloudwatch``: [``botocore``] Update cloudwatch client to latest version * api-change:``kms``: [``botocore``] Update kms client to latest version * api-change:``alexaforbusiness``: [``botocore``] Update alexaforbusiness client to latest version ``` ### 1.11.5 ``` ====== * api-change:``mediaconvert``: [``botocore``] Update mediaconvert client to latest version * api-change:``neptune``: [``botocore``] Update neptune client to latest version * api-change:``cloudhsmv2``: [``botocore``] Update cloudhsmv2 client to latest version * api-change:``redshift``: [``botocore``] Update redshift client to latest version * api-change:``batch``: [``botocore``] Update batch client to latest version * api-change:``ecs``: [``botocore``] Update ecs client to latest version ``` ### 1.11.4 ``` ====== * api-change:``ec2``: [``botocore``] Update ec2 client to latest version * api-change:``sagemaker``: [``botocore``] Update sagemaker client to latest version * api-change:``ds``: [``botocore``] Update ds client to latest version ``` ### 1.11.3 ``` ====== * api-change:``securityhub``: [``botocore``] Update securityhub client to latest version * api-change:``ssm``: [``botocore``] Update ssm client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version * api-change:``organizations``: [``botocore``] Update organizations client to latest version ``` ### 1.11.2 ``` ====== * api-change:``ec2``: [``botocore``] Update ec2 client to latest version ``` ### 1.11.1 ``` ====== * api-change:``efs``: [``botocore``] Update efs client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version * api-change:``backup``: [``botocore``] Update backup client to latest version ``` ### 1.11.0 ``` ====== * api-change:``sagemaker``: [``botocore``] Update sagemaker client to latest version * feature:Python: Dropped support for Python 2.6 and 3.3. * api-change:``chime``: [``botocore``] Update chime client to latest version * api-change:``transfer``: [``botocore``] Update transfer client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version * feature:Python: [``botocore``] Dropped support for Python 2.6 and 3.3. * api-change:``workspaces``: [``botocore``] Update workspaces client to latest version * api-change:``rds``: [``botocore``] Update rds client to latest version ``` ### 1.10.50 ``` ======= * api-change:``logs``: [``botocore``] Update logs client to latest version ``` ### 1.10.49 ``` ======= * api-change:``fms``: [``botocore``] Update fms client to latest version * api-change:``translate``: [``botocore``] Update translate client to latest version * api-change:``ce``: [``botocore``] Update ce client to latest version ``` ### 1.10.48 ``` ======= * api-change:``codebuild``: [``botocore``] Update codebuild client to latest version * api-change:``mgh``: [``botocore``] Update mgh client to latest version * api-change:``xray``: [``botocore``] Update xray client to latest version ``` ### 1.10.47 ``` ======= * api-change:``comprehend``: [``botocore``] Update comprehend client to latest version * api-change:``mediapackage``: [``botocore``] Update mediapackage client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version ``` ### 1.10.46 ``` ======= * api-change:``lex-models``: [``botocore``] Update lex-models client to latest version * api-change:``ecr``: [``botocore``] Update ecr client to latest version * api-change:``lightsail``: [``botocore``] Update lightsail client to latest version * api-change:``ce``: [``botocore``] Update ce client to latest version ``` ### 1.10.45 ``` ======= * api-change:``fsx``: [``botocore``] Update fsx client to latest version * api-change:``health``: [``botocore``] Update health client to latest version * api-change:``detective``: [``botocore``] Update detective client to latest version ``` ### 1.10.44 ``` ======= * api-change:``transcribe``: [``botocore``] Update transcribe client to latest version * api-change:``eks``: [``botocore``] Update eks client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version * api-change:``rds``: [``botocore``] Update rds client to latest version * api-change:``ssm``: [``botocore``] Update ssm client to latest version * api-change:``redshift``: [``botocore``] Update redshift client to latest version * api-change:``pinpoint``: [``botocore``] Update pinpoint client to latest version * api-change:``securityhub``: [``botocore``] Update securityhub client to latest version * api-change:``devicefarm``: [``botocore``] Update devicefarm client to latest version ``` ### 1.10.43 ``` ======= * api-change:``transcribe``: [``botocore``] Update transcribe client to latest version * api-change:``dlm``: [``botocore``] Update dlm client to latest version * api-change:``lex-models``: [``botocore``] Update lex-models client to latest version * api-change:``personalize-runtime``: [``botocore``] Update personalize-runtime client to latest version * api-change:``ssm``: [``botocore``] Update ssm client to latest version * api-change:``codestar-connections``: [``botocore``] Update codestar-connections client to latest version * api-change:``gamelift``: [``botocore``] Update gamelift client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version ``` ### 1.10.42 ``` ======= * api-change:``ec2``: [``botocore``] Update ec2 client to latest version * api-change:``s3``: [``botocore``] Update s3 client to latest version * api-change:``resourcegroupstaggingapi``: [``botocore``] Update resourcegroupstaggingapi client to latest version * api-change:``cloudfront``: [``botocore``] Update cloudfront client to latest version * api-change:``opsworkscm``: [``botocore``] Update opsworkscm client to latest version ``` ### 1.10.41 ``` ======= * api-change:``kinesisanalyticsv2``: [``botocore``] Update kinesisanalyticsv2 client to latest version * api-change:``ssm``: [``botocore``] Update ssm client to latest version * api-change:``medialive``: [``botocore``] Update medialive client to latest version * api-change:``iot``: [``botocore``] Update iot client to latest version * api-change:``ecs``: [``botocore``] Update ecs client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version ``` ### 1.10.40 ``` ======= * api-change:``mq``: [``botocore``] Update mq client to latest version * api-change:``comprehendmedical``: [``botocore``] Update comprehendmedical client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version ``` ### 1.10.39 ``` ======= * api-change:``codebuild``: [``botocore``] Update codebuild client to latest version * api-change:``detective``: [``botocore``] Update detective client to latest version * api-change:``sesv2``: [``botocore``] Update sesv2 client to latest version ``` ### 1.10.38 ``` ======= * api-change:``accessanalyzer``: [``botocore``] Update accessanalyzer client to latest version ``` ### 1.10.37 ``` ======= * api-change:``ec2``: [``botocore``] Update ec2 client to latest version ``` ### 1.10.36 ``` ======= * api-change:``kendra``: [``botocore``] Update kendra client to latest version ``` ### 1.10.35 ``` ======= * bugfix:s3: [``botocore``] Add stricter validation to s3 control account id parameter. * api-change:``quicksight``: [``botocore``] Update quicksight client to latest version * api-change:``kms``: [``botocore``] Update kms client to latest version * api-change:``ssm``: [``botocore``] Update ssm client to latest version * api-change:``kafka``: [``botocore``] Update kafka client to latest version ```Links
- PyPI: https://pypi.org/project/boto3 - Changelog: https://pyup.io/changelogs/boto3/ - Repo: https://github.com/boto/boto3Update botocore from 1.13.37 to 1.14.9.
Changelog
### 1.14.9 ``` ====== * api-change:``ecs``: Update ecs client to latest version * api-change:``opsworkscm``: Update opsworkscm client to latest version * api-change:``workspaces``: Update workspaces client to latest version * api-change:``datasync``: Update datasync client to latest version * api-change:``eks``: Update eks client to latest version ``` ### 1.14.8 ``` ====== * api-change:``rds``: Update rds client to latest version * api-change:``iam``: Update iam client to latest version ``` ### 1.14.7 ``` ====== * api-change:``ec2``: Update ec2 client to latest version * api-change:``codepipeline``: Update codepipeline client to latest version * api-change:``discovery``: Update discovery client to latest version * api-change:``iotevents``: Update iotevents client to latest version * api-change:``marketplacecommerceanalytics``: Update marketplacecommerceanalytics client to latest version ``` ### 1.14.6 ``` ====== * api-change:``lambda``: Update lambda client to latest version * api-change:``application-insights``: Update application-insights client to latest version * api-change:``ec2``: Update ec2 client to latest version * api-change:``cloudwatch``: Update cloudwatch client to latest version * api-change:``kms``: Update kms client to latest version * api-change:``alexaforbusiness``: Update alexaforbusiness client to latest version ``` ### 1.14.5 ``` ====== * api-change:``mediaconvert``: Update mediaconvert client to latest version * api-change:``neptune``: Update neptune client to latest version * api-change:``cloudhsmv2``: Update cloudhsmv2 client to latest version * api-change:``redshift``: Update redshift client to latest version * api-change:``batch``: Update batch client to latest version * api-change:``ecs``: Update ecs client to latest version ``` ### 1.14.4 ``` ====== * api-change:``ec2``: Update ec2 client to latest version * api-change:``sagemaker``: Update sagemaker client to latest version * api-change:``ds``: Update ds client to latest version ``` ### 1.14.3 ``` ====== * api-change:``securityhub``: Update securityhub client to latest version * api-change:``ssm``: Update ssm client to latest version * api-change:``ec2``: Update ec2 client to latest version * api-change:``organizations``: Update organizations client to latest version ``` ### 1.14.2 ``` ====== * api-change:``ec2``: Update ec2 client to latest version ``` ### 1.14.1 ``` ====== * api-change:``efs``: Update efs client to latest version * api-change:``ec2``: Update ec2 client to latest version * api-change:``backup``: Update backup client to latest version ``` ### 1.14.0 ``` ====== * api-change:``sagemaker``: Update sagemaker client to latest version * api-change:``chime``: Update chime client to latest version * api-change:``transfer``: Update transfer client to latest version * api-change:``ec2``: Update ec2 client to latest version * feature:Python: Dropped support for Python 2.6 and 3.3. * api-change:``workspaces``: Update workspaces client to latest version * api-change:``rds``: Update rds client to latest version ``` ### 1.13.50 ``` ======= * api-change:``logs``: Update logs client to latest version ``` ### 1.13.49 ``` ======= * api-change:``fms``: Update fms client to latest version * api-change:``translate``: Update translate client to latest version * api-change:``ce``: Update ce client to latest version ``` ### 1.13.48 ``` ======= * api-change:``codebuild``: Update codebuild client to latest version * api-change:``mgh``: Update mgh client to latest version * api-change:``xray``: Update xray client to latest version ``` ### 1.13.47 ``` ======= * api-change:``comprehend``: Update comprehend client to latest version * api-change:``mediapackage``: Update mediapackage client to latest version * api-change:``ec2``: Update ec2 client to latest version ``` ### 1.13.46 ``` ======= * api-change:``lex-models``: Update lex-models client to latest version * api-change:``ecr``: Update ecr client to latest version * api-change:``lightsail``: Update lightsail client to latest version * api-change:``ce``: Update ce client to latest version ``` ### 1.13.45 ``` ======= * api-change:``fsx``: Update fsx client to latest version * api-change:``health``: Update health client to latest version * api-change:``detective``: Update detective client to latest version ``` ### 1.13.44 ``` ======= * api-change:``transcribe``: Update transcribe client to latest version * api-change:``eks``: Update eks client to latest version * api-change:``ec2``: Update ec2 client to latest version * api-change:``rds``: Update rds client to latest version * api-change:``ssm``: Update ssm client to latest version * api-change:``redshift``: Update redshift client to latest version * api-change:``pinpoint``: Update pinpoint client to latest version * api-change:``securityhub``: Update securityhub client to latest version * api-change:``devicefarm``: Update devicefarm client to latest version ``` ### 1.13.43 ``` ======= * api-change:``transcribe``: Update transcribe client to latest version * api-change:``dlm``: Update dlm client to latest version * api-change:``lex-models``: Update lex-models client to latest version * api-change:``personalize-runtime``: Update personalize-runtime client to latest version * api-change:``ssm``: Update ssm client to latest version * api-change:``codestar-connections``: Update codestar-connections client to latest version * api-change:``gamelift``: Update gamelift client to latest version * api-change:``ec2``: Update ec2 client to latest version ``` ### 1.13.42 ``` ======= * api-change:``ec2``: Update ec2 client to latest version * api-change:``s3``: Update s3 client to latest version * api-change:``resourcegroupstaggingapi``: Update resourcegroupstaggingapi client to latest version * api-change:``cloudfront``: Update cloudfront client to latest version * enhancement:``s3``: Add support for opting into using the us-east-1 regional endpoint. * api-change:``opsworkscm``: Update opsworkscm client to latest version ``` ### 1.13.41 ``` ======= * api-change:``kinesisanalyticsv2``: Update kinesisanalyticsv2 client to latest version * api-change:``ssm``: Update ssm client to latest version * api-change:``medialive``: Update medialive client to latest version * api-change:``iot``: Update iot client to latest version * api-change:``ecs``: Update ecs client to latest version * api-change:``ec2``: Update ec2 client to latest version ``` ### 1.13.40 ``` ======= * api-change:``mq``: Update mq client to latest version * api-change:``comprehendmedical``: Update comprehendmedical client to latest version * api-change:``ec2``: Update ec2 client to latest version ``` ### 1.13.39 ``` ======= * api-change:``codebuild``: Update codebuild client to latest version * api-change:``detective``: Update detective client to latest version * api-change:``sesv2``: Update sesv2 client to latest version ``` ### 1.13.38 ``` ======= * api-change:``accessanalyzer``: Update accessanalyzer client to latest version ```Links
- PyPI: https://pypi.org/project/botocore - Changelog: https://pyup.io/changelogs/botocore/ - Repo: https://github.com/boto/botocoreUpdate django-prometheus from 1.1.0 to 2.0.0.
Changelog
### 2.0.0 ``` * Added support for newer Django and Python versions * Added an extensibility that applications to add their own labels to middleware (request/response) metrics * Allow overriding and setting custom bucket values for request/response latency histogram metric * Internal improvements: * use tox * Use pytest * use Black * Automate pre-releases on every commit ot master * Fix flaky tests. ```Links
- PyPI: https://pypi.org/project/django-prometheus - Changelog: https://pyup.io/changelogs/django-prometheus/ - Repo: http://github.com/korfuri/django-prometheusUpdate django from 2.2.8 to 3.0.2.
Changelog
### 3.0.2 ``` ========================== *January 2, 2020* Django 3.0.2 fixes several bugs in 3.0.1. Bugfixes ======== * Fixed a regression in Django 3.0 that didn't include columns referenced by a ``Subquery()`` in the ``GROUP BY`` clause (:ticket:`31094`). * Fixed a regression in Django 3.0 where ``QuerySet.exists()`` crashed if a queryset contained an aggregation over a ``Subquery()`` (:ticket:`31109`). * Fixed a regression in Django 3.0 that caused a migration crash on PostgreSQL 10+ when adding a foreign key and changing data in the same migration (:ticket:`31106`). * Fixed a regression in Django 3.0 where loading fixtures crashed for models defining a :attr:`~django.db.models.Field.default` for the primary key (:ticket:`31071`). ========================== ``` ### 3.0.1 ``` ========================== *December 18, 2019* Django 3.0.1 fixes a security issue and several bugs in 3.0. CVE-2019-19844: Potential account hijack via password reset form ================================================================ By submitting a suitably crafted email address making use of Unicode characters, that compared equal to an existing user email when lower-cased for comparison, an attacker could be sent a password reset token for the matched account. In order to avoid this vulnerability, password reset requests now compare the submitted email using the stricter, recommended algorithm for case-insensitive comparison of two identifiers from `Unicode Technical Report 36, section 2.11.2(B)(2)`__. Upon a match, the email containing the reset token will be sent to the email address on record rather than the submitted address. .. __: https://www.unicode.org/reports/tr36/Recommendations_General Bugfixes ======== * Fixed a regression in Django 3.0 by restoring the ability to use Django inside Jupyter and other environments that force an async context, by adding an option to disable :ref:`async-safety` mechanism with ``DJANGO_ALLOW_ASYNC_UNSAFE`` environment variable (:ticket:`31056`). * Fixed a regression in Django 3.0 where ``RegexPattern``, used by :func:`~django.urls.re_path`, returned positional arguments to be passed to the view when all optional named groups were missing (:ticket:`31061`). * Reallowed, following a regression in Django 3.0, :class:`~django.db.models.expressions.Window` expressions to be used in conditions outside of queryset filters, e.g. in :class:`~django.db.models.expressions.When` conditions (:ticket:`31060`). * Fixed a data loss possibility in :class:`~django.contrib.postgres.forms.SplitArrayField`. When using with ``ArrayField(BooleanField())``, all values after the first ``True`` value were marked as checked instead of preserving passed values (:ticket:`31073`). ======================== ``` ### 3.0 ``` ======================== *December 2, 2019* Welcome to Django 3.0! These release notes cover the :ref:`new features <whats-new-3.0>`, as well as some :ref:`backwards incompatible changes <backwards-incompatible-3.0>` you'll want to be aware of when upgrading from Django 2.2 or earlier. We've :ref:`dropped some features<removed-features-3.0>` that have reached the end of their deprecation cycle, and we've :ref:`begun the deprecation process for some features <deprecated-features-3.0>`. See the :doc:`/howto/upgrade-version` guide if you're updating an existing project. Python compatibility ==================== Django 3.0 supports Python 3.6, 3.7, and 3.8. We **highly recommend** and only officially support the latest release of each series. The Django 2.2.x series is the last to support Python 3.5. Third-party library support for older version of Django ======================================================= Following the release of Django 3.0, we suggest that third-party app authors drop support for all versions of Django prior to 2.2. At that time, you should be able to run your package's tests using ``python -Wd`` so that deprecation warnings appear. After making the deprecation warning fixes, your app should be compatible with Django 3.0. .. _whats-new-3.0: What's new in Django 3.0 ======================== MariaDB support --------------- Django now officially supports `MariaDB <https://mariadb.org/>`_ 10.1 and higher. See :ref:`MariaDB notes <mariadb-notes>` for more details. ASGI support ------------ Django 3.0 begins our journey to making Django fully async-capable by providing support for running as an `ASGI <https://asgi.readthedocs.io/>`_ application. This is in addition to our existing WSGI support. Django intends to support both for the foreseeable future. Async features will only be available to applications that run under ASGI, however. There is no need to switch your applications over unless you want to start experimenting with asynchronous code, but we have :doc:`documentation on deploying with ASGI </howto/deployment/asgi/index>` if you want to learn more. Note that as a side-effect of this change, Django is now aware of asynchronous event loops and will block you calling code marked as "async unsafe" - such as ORM operations - from an asynchronous context. If you were using Django from async code before, this may trigger if you were doing it incorrectly. If you see a ``SynchronousOnlyOperation`` error, then closely examine your code and move any database operations to be in a synchronous child thread. Exclusion constraints on PostgreSQL ----------------------------------- The new :class:`~django.contrib.postgres.constraints.ExclusionConstraint` class enable adding exclusion constraints on PostgreSQL. Constraints are added to models using the :attr:`Meta.constraints <django.db.models.Options.constraints>` option. Filter expressions ------------------ Expressions that output :class:`~django.db.models.BooleanField` may now be used directly in ``QuerySet`` filters, without having to first annotate and then filter against the annotation. Enumerations for model field choices ------------------------------------ Custom enumeration types ``TextChoices``, ``IntegerChoices``, and ``Choices`` are now available as a way to define :attr:`.Field.choices`. ``TextChoices`` and ``IntegerChoices`` types are provided for text and integer fields. The ``Choices`` class allows defining a compatible enumeration for other concrete data types. These custom enumeration types support human-readable labels that can be translated and accessed via a property on the enumeration or its members. See :ref:`Enumeration types <field-choices-enum-types>` for more details and examples. Minor features -------------- :mod:`django.contrib.admin` ~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Added support for the ``admin_order_field`` attribute on properties in :attr:`.ModelAdmin.list_display`. * The new :meth:`ModelAdmin.get_inlines() <django.contrib.admin.ModelAdmin.get_inlines>` method allows specifying the inlines based on the request or model instance. * Select2 library is upgraded from version 4.0.3 to 4.0.7. * jQuery is upgraded from version 3.3.1 to 3.4.1. :mod:`django.contrib.auth` ~~~~~~~~~~~~~~~~~~~~~~~~~~ * The new ``reset_url_token`` attribute in :class:`~django.contrib.auth.views.PasswordResetConfirmView` allows specifying a token parameter displayed as a component of password reset URLs. * Added :class:`~django.contrib.auth.backends.BaseBackend` class to ease customization of authentication backends. * Added :meth:`~django.contrib.auth.models.User.get_user_permissions()` method to mirror the existing :meth:`~django.contrib.auth.models.User.get_group_permissions()` method. * Added HTML ``autocomplete`` attribute to widgets of username, email, and password fields in :mod:`django.contrib.auth.forms` for better interaction with browser password managers. * :djadmin:`createsuperuser` now falls back to environment variables for password and required fields, when a corresponding command line argument isn't provided in non-interactive mode. * :attr:`~django.contrib.auth.models.CustomUser.REQUIRED_FIELDS` now supports :class:`~django.db.models.ManyToManyField`\s. * The new :meth:`.UserManager.with_perm` method returns users that have the specified permission. * The default iteration count for the PBKDF2 password hasher is increased from 150,000 to 180,000. :mod:`django.contrib.gis` ~~~~~~~~~~~~~~~~~~~~~~~~~ * Allowed MySQL spatial lookup functions to operate on real geometries. Previous support was limited to bounding boxes. * Added the :class:`~django.contrib.gis.db.models.functions.GeometryDistance` function, supported on PostGIS. * Added support for the ``furlong`` unit in :class:`~django.contrib.gis.measure.Distance`. * The :setting:`GEOIP_PATH` setting now supports :class:`pathlib.Path`. * The :class:`~django.contrib.gis.geoip2.GeoIP2` class now accepts :class:`pathlib.Path` ``path``. :mod:`django.contrib.postgres` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * The new :class:`~django.contrib.postgres.fields.RangeOperators` helps to avoid typos in SQL operators that can be used together with :class:`~django.contrib.postgres.fields.RangeField`. * The new :class:`~django.contrib.postgres.fields.RangeBoundary` expression represents the range boundaries. * The new :class:`~django.contrib.postgres.operations.AddIndexConcurrently` and :class:`~django.contrib.postgres.operations.RemoveIndexConcurrently` classes allow creating and dropping indexes ``CONCURRENTLY`` on PostgreSQL. :mod:`django.contrib.sessions` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * The new :meth:`~django.contrib.sessions.backends.base.SessionBase.get_session_cookie_age()` method allows dynamically specifying the session cookie age. :mod:`django.contrib.syndication` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Added the ``language`` class attribute to the :class:`django.contrib.syndication.views.Feed` to customize a feed language. The default value is :func:`~django.utils.translation.get_language()` instead of :setting:`LANGUAGE_CODE`. Cache ~~~~~ * :func:`~django.utils.cache.add_never_cache_headers` and :func:`~django.views.decorators.cache.never_cache` now add the ``private`` directive to ``Cache-Control`` headers. File Storage ~~~~~~~~~~~~ * The new :meth:`.Storage.get_alternative_name` method allows customizing the algorithm for generating filenames if a file with the uploaded name already exists. Forms ~~~~~ * Formsets may control the widget used when ordering forms via :attr:`~django.forms.formsets.BaseFormSet.can_order` by setting the :attr:`~django.forms.formsets.BaseFormSet.ordering_widget` attribute or overriding :attr:`~django.forms.formsets.BaseFormSet.get_ordering_widget()`. Internationalization ~~~~~~~~~~~~~~~~~~~~ * Added the :setting:`LANGUAGE_COOKIE_HTTPONLY`, :setting:`LANGUAGE_COOKIE_SAMESITE`, and :setting:`LANGUAGE_COOKIE_SECURE` settings to set the ``HttpOnly``, ``SameSite``, and ``Secure`` flags on language cookies. The default values of these settings preserve the previous behavior. * Added support and translations for the Uzbek language. Logging ~~~~~~~ * The new ``reporter_class`` parameter of :class:`~django.utils.log.AdminEmailHandler` allows providing an ``django.views.debug.ExceptionReporter`` subclass to customize the traceback text sent to site :setting:`ADMINS` when :setting:`DEBUG` is ``False``. Management Commands ~~~~~~~~~~~~~~~~~~~ * The new :option:`compilemessages --ignore` option allows ignoring specific directories when searching for ``.po`` files to compile. * :option:`showmigrations --list` now shows the applied datetimes when ``--verbosity`` is 2 and above. * On PostgreSQL, :djadmin:`dbshell` now supports client-side TLS certificates. * :djadmin:`inspectdb` now introspects :class:`~django.db.models.OneToOneField` when a foreign key has a unique or primary key constraint. * The new :option:`--skip-checks` option skips running system checks prior to running the command. * The :option:`startapp --template` and :option:`startproject --template` options now support templates stored in XZ archives (``.tar.xz``, ``.txz``) and LZMA archives (``.tar.lzma``, ``.tlz``). Models ~~~~~~ * Added hash database functions :class:`~django.db.models.functions.MD5`, :class:`~django.db.models.functions.SHA1`, :class:`~django.db.models.functions.SHA224`, :class:`~django.db.models.functions.SHA256`, :class:`~django.db.models.functions.SHA384`, and :class:`~django.db.models.functions.SHA512`. * Added the :class:`~django.db.models.functions.Sign` database function. * The new ``is_dst`` parameter of the :class:`~django.db.models.functions.Trunc` database functions determines the treatment of nonexistent and ambiguous datetimes. * ``connection.queries`` now shows ``COPY … TO`` statements on PostgreSQL. * :class:`~django.db.models.FilePathField` now accepts a callable for ``path``. * Allowed symmetrical intermediate table for self-referential :class:`~django.db.models.ManyToManyField`. * The ``name`` attributes of :class:`~django.db.models.CheckConstraint`, :class:`~django.db.models.UniqueConstraint`, and :class:`~django.db.models.Index` now support app label and class interpolation using the ``'%(app_label)s'`` and ``'%(class)s'`` placeholders. * The new :attr:`.Field.descriptor_class` attribute allows model fields to customize the get and set behavior by overriding their :py:ref:`descriptors <descriptors>`. * :class:`~django.db.models.Avg` and :class:`~django.db.models.Sum` now support the ``distinct`` argument. * Added :class:`~django.db.models.SmallAutoField` which acts much like an :class:`~django.db.models.AutoField` except that it only allows values under a certain (database-dependent) limit. Values from ``1`` to ``32767`` are safe in all databases supported by Django. * :class:`~django.db.models.AutoField`, :class:`~django.db.models.BigAutoField`, and :class:`~django.db.models.SmallAutoField` now inherit from ``IntegerField``, ``BigIntegerField`` and ``SmallIntegerField`` respectively. System checks and validators are now also properly inherited. * :attr:`.FileField.upload_to` now supports :class:`pathlib.Path`. * :class:`~django.db.models.CheckConstraint` is now supported on MySQL 8.0.16+. * The new ``allows_group_by_selected_pks_on_model()`` method of ``django.db.backends.base.BaseDatabaseFeatures`` allows optimization of ``GROUP BY`` clauses to require only the selected models' primary keys. By default, it's supported only for managed models on PostgreSQL. To enable the ``GROUP BY`` primary key-only optimization for unmanaged models, you have to subclass the PostgreSQL database engine, overriding the features class ``allows_group_by_selected_pks_on_model()`` method as you require. See :ref:`Subclassing the built-in database backends <subclassing-database-backends>` for an example. Requests and Responses ~~~~~~~~~~~~~~~~~~~~~~ * Allowed :class:`~django.http.HttpResponse` to be initialized with :class:`memoryview` content. * For use in, for example, Django templates, :attr:`.HttpRequest.headers` now allows lookups using underscores (e.g. ``user_agent``) in place of hyphens. .. _whats-new-security-3.0: Security ~~~~~~~~ * :setting:`X_FRAME_OPTIONS` now defaults to ``'DENY'``. In older versions, the :setting:`X_FRAME_OPTIONS` setting defaults to ``'SAMEORIGIN'``. If your site uses frames of itself, you will need to explicitly set ``X_FRAME_OPTIONS = 'SAMEORIGIN'`` for them to continue working. * :setting:`SECURE_CONTENT_TYPE_NOSNIFF` setting now defaults to ``True``. With the enabled :setting:`SECURE_CONTENT_TYPE_NOSNIFF`, the :class:`~django.middleware.security.SecurityMiddleware` sets the :ref:`x-content-type-options` header on all responses that do not already have it. * :class:`~django.middleware.security.SecurityMiddleware` can now send the :ref:`Referrer-Policy <referrer-policy>` header. Tests ~~~~~ * The new test :class:`~django.test.Client` argument ``raise_request_exception`` allows controlling whether or not exceptions raised during the request should also be raised in the test. The value defaults to ``True`` for backwards compatibility. If it is ``False`` and an exception occurs, the test client will return a 500 response with the attribute :attr:`~django.test.Response.exc_info`, a tuple providing information of the exception that occurred. * Tests and test cases to run can be selected by test name pattern using the new :option:`test -k` option. * HTML comparison, as used by :meth:`~django.test.SimpleTestCase.assertHTMLEqual`, now treats text, character references, and entity references that refer to the same character as equivalent. * Django test runner now supports headless mode for selenium tests on supported browsers. Add the ``--headless`` option to enable this mode. * Django test runner now supports ``--start-at`` and ``--start-after`` options to run tests starting from a specific top-level module. * Django test runner now supports a ``--pdb`` option to spawn a debugger at each error or failure. .. _backwards-incompatible-3.0: Backwards incompatible changes in 3.0 ===================================== ``Model.save()`` when providing a default for the primary key ------------------------------------------------------------- :meth:`.Model.save` no longer attempts to find a row when saving a new ``Model`` instance and a default value for the primary key is provided, and always performs a single ``INSERT`` query. In older Django versions, ``Model.save()`` performed either an ``INSERT`` or an ``UPDATE`` based on whether or not the row exists. This makes calling ``Model.save()`` while providing a default primary key value equivalent to passing :ref:`force_insert=True <ref-models-force-insert>` to model's ``save()``. Attempts to use a new ``Model`` instance to update an existing row will result in an ``IntegrityError``. In order to update an existing model for a specific primary key value, use the :meth:`~django.db.models.query.QuerySet.update_or_create` method or ``QuerySet.filter(pk=…).update(…)`` instead. For example:: >>> MyModel.objects.update_or_create(pk=existing_pk, defaults={'name': 'new name'}) >>> MyModel.objects.filter(pk=existing_pk).update(name='new name') Database backend API -------------------- This section describes changes that may be needed in third-party database backends. * The second argument of ``DatabaseIntrospection.get_geometry_type()`` is now the row description instead of the column name. * ``DatabaseIntrospection.get_field_type()`` may no longer return tuples. * If the database can create foreign keys in the same SQL statement that adds a field, add ``SchemaEditor.sql_create_column_inline_fk`` with the appropriate SQL; otherwise, set ``DatabaseFeatures.can_create_inline_fk = False``. * ``DatabaseFeatures.can_return_id_from_insert`` and ``can_return_ids_from_bulk_insert`` are renamed to ``can_return_columns_from_insert`` and ``can_return_rows_from_bulk_insert``. * Database functions now handle :class:`datetime.timezone` formats when created using :class:`datetime.timedelta` instances (e.g. ``timezone(timedelta(hours=5))``, which would output ``'UTC+05:00'``). Third-party backends should handle this format when preparing :class:`~django.db.models.DateTimeField` in ``datetime_cast_date_sql()``, ``datetime_extract_sql()``, etc. * Entries for ``AutoField``, ``BigAutoField``, and ``SmallAutoField`` are added to ``DatabaseOperations.integer_field_ranges`` to support the integer range validators on these field types. Third-party backends may need to customize the default entries. * ``DatabaseOperations.fetch_returned_insert_id()`` is replaced by ``fetch_returned_insert_columns()`` which returns a list of values returned by the ``INSERT … RETURNING`` statement, instead of a single value. * ``DatabaseOperations.return_insert_id()`` is replaced by ``return_insert_columns()`` that accepts a ``fields`` argument, which is an iterable of fields to be returned after insert. Usually this is only the auto-generated primary key. :mod:`django.contrib.admin` --------------------------- * Admin's model history change messages now prefers more readable field labels instead of field names. :mod:`django.contrib.gis` ------------------------- * Support for PostGIS 2.1 is removed. * Support for SpatiaLite 4.1 and 4.2 is removed. * Support for GDAL 1.11 and GEOS 3.4 is removed. Dropped support for PostgreSQL 9.4 ---------------------------------- Upstream support for PostgreSQL 9.4 ends in December 2019. Django 3.0 supports PostgreSQL 9.5 and higher. Dropped support for Oracle 12.1 ------------------------------- Upstream support for Oracle 12.1 ends in July 2021. Django 2.2 will be supported until April 2022. Django 3.0 officially supports Oracle 12.2 and 18c. Removed private Python 2 compatibility APIs ------------------------------------------- While Python 2 support was removed in Django 2.0, some private APIs weren't removed from Django so that third party apps could continue using them until the Python 2 end-of-life. Since we expect apps to drop Python 2 compatibility when adding support for Django 3.0, we're removing these APIs at this time. * ``django.test.utils.str_prefix()`` - Strings don't have 'u' prefixes in Python 3. * ``django.test.utils.patch_logger()`` - Use :meth:`unittest.TestCase.assertLogs` instead. * ``django.utils.lru_cache.lru_cache()`` - Alias of :func:`functools.lru_cache`. * ``django.utils.decorators.available_attrs()`` - This function returns ``functools.WRAPPER_ASSIGNMENTS``. * ``django.utils.decorators.ContextDecorator`` - Alias of :class:`contextlib.ContextDecorator`. * ``django.utils._os.abspathu()`` - Alias of :func:`os.path.abspath`. * ``django.utils._os.upath()`` and ``npath()`` - These functions do nothing on Python 3. * ``django.utils.six`` - Remove usage of this vendored library or switch to `six <https://pypi.org/project/six/>`_. * ``django.utils.encoding.python_2_unicode_compatible()`` - Alias of ``six.python_2_unicode_compatible()``. * ``django.utils.functional.curry()`` - Use :func:`functools.partial` or :class:`functools.partialmethod`. See :commit:`5b1c389603a353625ae1603`. * ``django.utils.safestring.SafeBytes`` - Unused since Django 2.0. New default value for the ``FILE_UPLOAD_PERMISSIONS`` setting ------------------------------------------------------------- In older versions, the :setting:`FILE_UPLOAD_PERMISSIONS` setting defaults to ``None``. With the default :setting:`FILE_UPLOAD_HANDLERS`, this results in uploaded files having different permissions depending on their size and which upload handler is used. ``FILE_UPLOAD_PERMISSION`` now defaults to ``0o644`` to avoid this inconsistency. New default values for security settings ---------------------------------------- To make Django projects more secure by default, some security settings now have more secure default values: * :setting:`X_FRAME_OPTIONS` now defaults to ``'DENY'``. * :setting:`SECURE_CONTENT_TYPE_NOSNIFF` now defaults to ``True``. See the *What's New* :ref:`Security section <whats-new-security-3.0>` above for more details on these changes. Miscellaneous ------------- * ``ContentType.__str__()`` now includes the model's ``app_label`` to disambiguate models with the same name in different apps. * Because accessing the language in the session rather than in the cookie is deprecated, ``LocaleMiddleware`` no longer looks for the user's language in the session and :func:`django.contrib.auth.logout` no longer preserves the session's language after logout. * :func:`django.utils.html.escape` now uses :func:`html.escape` to escape HTML. This converts ``'`` to ``&x27;`` instead of the previous equivalent decimal code ``&39;``. * The ``django-admin test -k`` option now works as the :option:`unittest -k<unittest.-k>` option rather than as a shortcut for ``--keepdb``. * Support for ``pywatchman`` < 1.2.0 is removed. * :func:`~django.utils.http.urlencode` now encodes iterable values as they are when ``doseq=False``, rather than iterating them, bringing it into line with the standard library :func:`urllib.parse.urlencode` function. * ``intword`` template filter now translates ``1.0`` as a singular phrase and all other numeric values as plural. This may be incorrect for some languages. * Assigning a value to a model's :class:`~django.db.models.ForeignKey` or :class:`~django.db.models.OneToOneField` ``'_id'`` attribute now unsets the corresponding field. Accessing the field afterwards will result in a query. * :func:`~django.utils.cache.patch_vary_headers` now handles an asterisk ``'*'`` according to :rfc:`7231section-7.1.4`, i.e. if a list of header field names contains an asterisk, then the ``Vary`` header will consist of a single asterisk ``'*'``. * On MySQL 8.0.16+, ``PositiveIntegerField`` and ``PositiveSmallIntegerField`` now include a check constraint to prevent negative values in the database. * ``alias=None`` is added to the signature of :meth:`.Expression.get_group_by_cols`. * Support for ``sqlparse`` < 0.2.2 is removed. * ``RegexPattern``, used by :func:`~django.urls.re_path`, no longer returns keyword arguments with ``None`` values to be passed to the view for the optional named groups that are missing. .. _deprecated-features-3.0: Features deprecated in 3.0 ========================== ``django.utils.encoding.force_text()`` and ``smart_text()`` ----------------------------------------------------------- The ``smart_text()`` and ``force_text()`` aliases (since Django 2.0) of ``smart_str()`` and ``force_str()`` are deprecated. Ignore this deprecation if your code supports Python 2 as the behavior of ``smart_str()`` and ``force_str()`` is different there. Miscellaneous ------------- * ``django.utils.http.urlquote()``, ``urlquote_plus()``, ``urlunquote()``, and ``urlunquote_plus()`` are deprecated in favor of the functions that they're aliases for: :func:`urllib.parse.quote`, :func:`~urllib.parse.quote_plus`, :func:`~urllib.parse.unquote`, and :func:`~urllib.parse.unquote_plus`. * ``django.utils.translation.ugettext()``, ``ugettext_lazy()``, ``ugettext_noop()``, ``ungettext()``, and ``ungettext_lazy()`` are deprecated in favor of the functions that they're aliases for: :func:`django.utils.translation.gettext`, :func:`~django.utils.translation.gettext_lazy`, :func:`~django.utils.translation.gettext_noop`, :func:`~django.utils.translation.ngettext`, and :func:`~django.utils.translation.ngettext_lazy`. * To limit creation of sessions and hence favor some caching strategies, :func:`django.views.i18n.set_language` will stop setting the user's language in the session in Django 4.0. Since Django 2.1, the language is always stored in the :setting:`LANGUAGE_COOKIE_NAME` cookie. * ``django.utils.text.unescape_entities()`` is deprecated in favor of :func:`html.unescape`. Note that unlike ``unescape_entities()``, ``html.unescape()`` evaluates lazy strings immediately. * To avoid possible confusion as to effective scope, the private internal utility ``is_safe_url()`` is renamed to ``url_has_allowed_host_and_scheme()``. That a URL has an allowed host and scheme doesn't in general imply that it's "safe". It may still be quoted incorrectly, for example. Ensure to also use :func:`~django.utils.encoding.iri_to_uri` on the path component of untrusted URLs. .. _removed-features-3.0: Features removed in 3.0 ======================= These features have reached the end of their deprecation cycle and are removed in Django 3.0. See :ref:`deprecated-features-2.0` for details on these changes, including how to remove usage of these features. * The ``django.db.backends.postgresql_psycopg2`` module is removed. * ``django.shortcuts.render_to_response()`` is removed. * The ``DEFAULT_CONTENT_TYPE`` setting is removed. * ``HttpRequest.xreadlines()`` is removed. * Support for the ``context`` argument of ``Field.from_db_value()`` and ``Expression.convert_value()`` is removed. * The ``field_name`` keyword argument of ``QuerySet.earliest()`` and ``latest()`` is removed. See :ref:`deprecated-features-2.1` for details on these changes, including how to remove usage of these features. * The ``ForceRHR`` GIS function is removed. * ``django.utils.http.cookie_date()`` is removed. * The ``staticfiles`` and ``admin_static`` template tag libraries are removed. * ``django.contrib.staticfiles.templatetags.staticfiles.static()`` is removed. ========================== ``` ### 2.2.9 ``` ========================== *December 18, 2019* Django 2.2.9 fixes a security issue and a data loss bug in 2.2.8. CVE-2019-19844: Potential account hijack via password reset form ================================================================ By submitting a suitably crafted email address making use of Unicode characters, that compared equal to an existing user email when lower-cased for comparison, an attacker could be sent a password reset token for the matched account. In order to avoid this vulnerability, password reset requests now compare the submitted email using the stricter, recommended algorithm for case-insensitive comparison of two identifiers from `Unicode Technical Report 36, section 2.11.2(B)(2)`__. Upon a match, the email containing the reset token will be sent to the email address on record rather than the submitted address. .. __: https://www.unicode.org/reports/tr36/Recommendations_General Bugfixes ======== * Fixed a data loss possibility in :class:`~django.contrib.postgres.forms.SplitArrayField`. When using with ``ArrayField(BooleanField())``, all values after the first ``True`` value were marked as checked instead of preserving passed values (:ticket:`31073`). ========================== ```Links
- PyPI: https://pypi.org/project/django - Changelog: https://pyup.io/changelogs/django/ - Homepage: https://www.djangoproject.com/Update djangorestframework from 3.10.3 to 3.11.0.
The bot wasn't able to find a changelog for this release. Got an idea?
Links
- PyPI: https://pypi.org/project/djangorestframework - Changelog: https://pyup.io/changelogs/djangorestframework/ - Homepage: https://www.django-rest-framework.org/Update docutils from 0.15.2 to 0.16.
Changelog
### 0.16 ``` ========================= .. Note:: Docutils 0.15.x is the last version supporting Python 2.6, 3.3 and 3.4. Docutils 0.16.x supports Python 2.7 and Python >= 3.5 natively, without the use of the ``2to3`` tool. * reStructuredText: - Keep `backslash escapes`__ in the document tree. This allows, e.g., escaping of author-separators in `bibliographic fields`__. __ http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.htmlescaping-mechanism __ docs/ref/rst/restructuredtext.htmlbibliographic-fields * LaTeX writer: - Informal titles of type "rubric" default to bold-italic and left aligned. - Deprecate ``\docutilsrole`` prefix for styling commands: use ``\DUrole`` instead. - Fix topic subtitle. - Add "latex writers" to the `config_section_dependencies`. - Ignore classes for `rubric` elements (class wrapper interferes with LaTeX formatting). * tools/buildhtml.py - New option "--html-writer" allows to select "html__" (default), "html4" or "html5". __ html: docs/user/html.htmlhtml * docutils/io.py - Remove the `handle_io_errors` option from io.FileInput/Output. * docutils/nodes.py - If `auto_id_prefix`_ ends with "%", this is replaced with the tag name. .. _auto_id_prefix: docs/user/config.htmlauto-id-prefix * Various bugfixes and improvements (see HISTORY_). ```Links
- PyPI: https://pypi.org/project/docutils - Changelog: https://pyup.io/changelogs/docutils/ - Homepage: http://docutils.sourceforge.net/Update kafka-python from 1.4.6 to 1.4.7.
Changelog
### 1.4.7 ``` This is a minor release focused on KafkaConsumer performance, Admin Client improvements, and Client concurrency. The KafkaConsumer iterator implementation has been greatly simplified so that it just wraps consumer.poll(). The prior implementation will remain available for a few more releases using the optional KafkaConsumer config: `legacy_iterator=True` . This is expected to improve consumer throughput substantially and help reduce heartbeat failures / group rebalancing. Client * Send socket data via non-blocking IO with send buffer (dpkp / PR 1912) * Rely on socket selector to detect completed connection attempts (dpkp / PR 1909) * Improve connection lock handling; always use context manager (melor,dpkp / PR 1895) * Reduce client poll timeout when there are no in-flight requests (dpkp / PR 1823) KafkaConsumer * Do not use wakeup when sending fetch requests from consumer (dpkp / PR 1911) * Wrap `consumer.poll()` for KafkaConsumer iteration (dpkp / PR 1902) * Allow the coordinator to auto-commit on old brokers (justecorruptio / PR 1832) * Reduce internal client poll timeout for (legacy) consumer iterator interface (dpkp / PR 1824) * Use dedicated connection for group coordinator (dpkp / PR 1822) * Change coordinator lock acquisition order (dpkp / PR 1821) * Make `partitions_for_topic` a read-through cache (Baisang / PR 1781,1809) * Fix consumer hanging indefinitely on topic deletion while rebalancing (commanderdishwasher / PR 1782) Miscellaneous Bugfixes / Improvements * Fix crc32c avilability on non-intel architectures (ossdev07 / PR 1904) * Load system default SSL CAs if `ssl_cafile` is not provided (iAnomaly / PR 1883) * Catch py3 TimeoutError in BrokerConnection send/recv (dpkp / PR 1820) * Added a function to determine if bootstrap is successfully connected (Wayde2014 / PR 1876) Admin Client * Add ACL api support to KafkaAdminClient (ulrikjohansson / PR 1833) * Add `sasl_kerberos_domain_name` config to KafkaAdminClient (jeffwidman / PR 1852) * Update `security_protocol` config documentation for KafkaAdminClient (cardy31 / PR 1849) * Break FindCoordinator into request/response methods in KafkaAdminClient (jeffwidman / PR 1871) * Break consumer operations into request / response methods in KafkaAdminClient (jeffwidman / PR 1845) * Parallelize calls to `_send_request_to_node()` in KafkaAdminClient (davidheitman / PR 1807) Test Infrastructure / Documentation / Maintenance * Add Kafka 2.3.0 to test matrix and compatibility docs (dpkp / PR 1915) * Convert remaining `KafkaConsumer` tests to `pytest` (jeffwidman / PR 1886) * Bump integration tests to 0.10.2.2 and 0.11.0.3 (jeffwidman / 1890) * Cleanup handling of `KAFKA_VERSION` env var in tests (jeffwidman / PR 1887) * Minor test cleanup (jeffwidman / PR 1885) * Use `socket.SOCK_STREAM` in test assertions (iv-m / PR 1879) * Sanity test for `consumer.topics()` and `consumer.partitions_for_topic()` (Baisang / PR 1829) * Cleanup seconds conversion in client poll timeout calculation (jeffwidman / PR 1825) * Remove unused imports (jeffwidman / PR 1808) * Cleanup python nits in RangePartitionAssignor (jeffwidman / PR 1805) * Update links to kafka consumer config docs (jeffwidman) * Fix minor documentation typos (carsonip / PR 1865) * Remove unused/weird comment line (jeffwidman / PR 1813) * Update docs for `api_version_auto_timeout_ms` (jeffwidman / PR 1812) ```Links
- PyPI: https://pypi.org/project/kafka-python - Changelog: https://pyup.io/changelogs/kafka-python/ - Repo: https://github.com/dpkp/kafka-pythonUpdate python-dateutil from 2.8.0 to 2.8.1.
Changelog
### 2.8.1 ``` ========================== Data updates ------------ - Updated tzdata version to 2019c. Bugfixes -------- - Fixed a race condition in the ``tzoffset`` and ``tzstr`` "strong" caches on Python 2.7. Reported by kainjow (gh issue 901). - Parsing errors will now raise ``ParserError``, a subclass of ``ValueError``, which has a nicer string representation. Patch by gfyoung (gh pr 881). - ``parser.parse`` will now raise ``TypeError`` when ``tzinfos`` is passed a type that cannot be interpreted as a time zone. Prior to this change, it would raise an ``UnboundLocalError`` instead. Patch by jbrockmendel (gh pr 891). - Changed error message raised when when passing a ``bytes`` object as the time zone name to gettz in Python 3. Reported and fixed by labrys () (gh issue 927, gh pr 935). - Changed compatibility logic to support a potential Python 4.0 release. Patch by Hugo van Kemenade (gh pr 950). - Updated many modules to use ``tz.UTC`` in favor of ``tz.tzutc()`` internally, to avoid an unnecessary function call. (gh pr 910). - Fixed issue where ``dateutil.tz`` was using a backported version of ``contextlib.nullcontext`` even in Python 3.7 due to a malformed import statement. (gh pr 963). Tests ----- - Switched from using assertWarns to using pytest.warns in the test suite. (gh pr 969). - Fix typo in setup.cfg causing PendingDeprecationWarning to not be explicitly specified as an error in the warnings filter. (gh pr 966) - Fixed issue where ``test_tzlocal_offset_equal`` would fail in certain environments (such as FreeBSD) due to an invalid assumption about what time zone names are provided. Reported and fixed by Kubilay Kocak (gh issue 918, pr 928). - Fixed a minor bug in ``test_isoparser`` related to ``bytes``/``str`` handling. Fixed by fhuang5 (gh issue 776, gh pr 879). - Explicitly listed all markers used in the pytest configuration. (gh pr 915) - Extensive improvements to the parser test suite, including the adoption of ``pytest``-style tests and the addition of parametrization of several test cases. Patches by jbrockmendel (gh prs 735, 890, 892, 894). - Added tests for tzinfos input types. Patch by jbrockmendel (gh pr 891). - Fixed failure of test suite when changing the TZ variable is forbidden. Patch by shadchin (gh pr 893). - Pinned all test dependencies on Python 3.3. (gh prs 934, 962) Documentation changes --------------------- - Fixed many misspellings, typos and styling errors in the comments and documentation. Patch by Hugo van Kemenade (gh pr 952). Misc ---- - Added Python 3.8 to the trove classifiers. (gh pr 970) - Moved as many keys from ``setup.py`` to ``setup.cfg`` as possible. Fixed by FakeNameSE, aquinlan82, jachen20, and gurgenz221 (gh issue 871, gh pr 880). - Reorganized ``parser`` methods by functionality. Patch by jbrockmendel (gh pr 882). - Switched ``release.py`` over to using ``pep517.build`` for creating releases, rather than direct invocations of ``setup.py``. Fixed by smeng10 (gh issue 869, gh pr 875). - Added a "build" environment into the tox configuration, to handle dependency management when making releases. Fixed by smeng10 (gh issue 870,r gh pr 876). - GH 916, GH 971 ```Links
- PyPI: https://pypi.org/project/python-dateutil - Changelog: https://pyup.io/changelogs/python-dateutil/ - Docs: https://dateutil.readthedocs.ioUpdate s3transfer from 0.2.1 to 0.3.2.
Changelog
### 0.3.2 ``` ===== * bugfix:s3: Fixes boto/botocore`1916 <https://github.com/boto/botocore/issues/1916>`__ ``` ### 0.3.1 ``` ===== * enhancement:``TransferManager``: Expose ``client`` and ``config`` properties * enhancement:Tags: Add support for ``Tagging`` and ``TaggingDirective`` ``` ### 0.3.0 ``` ===== * feature:Python: Dropped support for Python 2.6 and 3.3. ```Links
- PyPI: https://pypi.org/project/s3transfer - Changelog: https://pyup.io/changelogs/s3transfer/ - Repo: https://github.com/boto/s3transferUpdate six from 1.13.0 to 1.14.0.
Changelog
### 1.14.0 ``` ------ - Issue 288, pull request 289: Add `six.assertNotRegex`. - Issue 317: `six.moves._dummy_thread` now points to the `_thread` module on Python 3.9+. Python 3.7 and later requires threading and deprecated the `_dummy_thread` module. - Issue 308, pull request 314: Remove support for Python 2.6 and Python 3.2. - Issue 250, issue 165, pull request 251: `six.wraps` now ignores missing attributes. This follows the Python 3.2+ standard library behavior. ```Links
- PyPI: https://pypi.org/project/six - Changelog: https://pyup.io/changelogs/six/ - Repo: https://github.com/benjaminp/sixUpdate urllib3 from 1.25.7 to 1.25.8.
Changelog
### 1.25.8 ``` ------------------- * Drop support for EOL Python 3.4 (Pull 1774) * Optimize _encode_invalid_chars (Pull 1787) ```Links
- PyPI: https://pypi.org/project/urllib3 - Changelog: https://pyup.io/changelogs/urllib3/ - Docs: https://urllib3.readthedocs.io/Update whitenoise from 4.1.4 to 5.0.1.
Changelog
### 5.0.1 ``` ------ * Fix packaging to indicate only Python 3.5+ compatibiity (thanks `mdalp <https://github.com/mdalp>`_). ``` ### 5.0 ``` ---- .. note:: This is a major version bump, but only because it removes Python 2 compatibility. If you were already running under Python 3 then there should be no breaking changes. WhiteNoise is now tested on Python 3.5--3.8 and Django 2.0--3.0. Other changes include: * Fix incompatibility with Django 3.0 which caused problems with Safari (details `here <https://github.com/evansd/whitenoise/issues/240>`_). Thanks `paltman <https://github.com/paltman>`_ and `giilby <https://github.com/giilby>`_ for diagnosing. * Lots of improvements to the test suite (including switching to py.test). Thanks `NDevox <https://github.com/ndevox>`_ and `Djailla <https://github.com/djailla>`_. ```Links
- PyPI: https://pypi.org/project/whitenoise - Changelog: https://pyup.io/changelogs/whitenoise/ - Homepage: http://whitenoise.evans.ioUpdate autopep8 from 1.4.4 to 1.5.
Changelog
### 1.5 ``` * Support Python3.8 * Support `pyproject.toml` with `[tool.autopep8]` section. * fix bugs * 503, 511 : related code W503 * 489, 498 : related code E711/E712 * 449, 514 : related code W605 ```Links
- PyPI: https://pypi.org/project/autopep8 - Changelog: https://pyup.io/changelogs/autopep8/ - Repo: https://github.com/hhatto/autopep8Update coverage from 4.5.4 to 5.0.3.
Changelog
### 5.0.3 ``` ---------------------------- - A performance improvement in 5.0.2 didn't work for test suites that changed directory before combining data, causing "Couldn't use data file: no such table: meta" errors (`issue 916`_). This is now fixed. - Coverage could fail to run your program with some form of "ModuleNotFound" or "ImportError" trying to import from the current directory. This would happen if coverage had been packaged into a zip file (for example, on Windows), or was found indirectly (for example, by pyenv-virtualenv). A number of different scenarios were described in `issue 862`_ which is now fixed. Huge thanks to Agbonze O. Jeremiah for reporting it, and Alexander Waters and George-Cristian Bîrzan for protracted debugging sessions. - Added the "premain" debug option. - Added SQLite compile-time options to the "debug sys" output. .. _issue 862: https://github.com/nedbat/coveragepy/issues/862 .. _issue 916: https://github.com/nedbat/coveragepy/issues/916 .. _changes_502: ``` ### 5.0.2 ``` ---------------------------- - Programs that used multiprocessing and changed directories would fail under coverage. This is now fixed (`issue 890`_). A side effect is that debug information about the config files read now shows absolute paths to the files. - When running programs as modules (``coverage run -m``) with ``--source``, some measured modules were imported before coverage starts. This resulted in unwanted warnings ("Already imported a file that will be measured") and a reduction in coverage totals (`issue 909`_). This is now fixed. - If no data was collected, an exception about "No data to report" could happen instead of a 0% report being created (`issue 884`_). This is now fixed. - The handling of source files with non-encodable file names has changed. Previously, if a file name could not be encoded as UTF-8, an error occurred, as described in `issue 891`_. Now, those files will not be measured, since their data would not be recordable. - A new warning ("dynamic-conflict") is issued if two mechanisms are trying to change the dynamic context. Closes `issue 901`_. - ``coverage run --debug=sys`` would fail with an Attribute