Subject: CVS commit: pkgsrc/www/py-test-django
From: Adam Ciarcinski
Date: 2023-09-06 22:17:50
Message id: 20230906201751.04960FBDB@cvs.NetBSD.org

Log Message:
py-test-django: updated to 4.5.2

v4.5.2 (2021-12-07)
-------------------

Bugfixes

* Fix regression in v4.5.0 - ``pytest.mark.django_db(reset_sequence=True)`` now
  implies ``transaction=True`` again.

v4.5.1 (2021-12-02)
-------------------

Bugfixes

* Fix regression in v4.5.0 - database tests inside (non-unittest) classes were
  not ordered correctly to run before non-database tests, same for transactional
  tests before non-transactional tests.

v4.5.0 (2021-12-01)
-------------------

Improvements

* Add support for :ref:`rollback emulation/serialized rollback
  <test-case-serialized-rollback>`. The :func:`pytest.mark.django_db` marker
  has a new ``serialized_rollback`` option, and a
  :fixture:`django_db_serialized_rollback` fixture is added.

* Official Python 3.10 support.

* Official Django 4.0 support (tested against 4.0rc1 at the time of release).

* Drop official Django 3.0 support. Django 2.2 is still supported, and 3.0
  will likely keep working until 2.2 is dropped, but it's not tested.

* Added pyproject.toml file.

* Skip Django's `setUpTestData` mechanism in pytest-django tests. It is not
  used for those, and interferes with some planned features. Note that this
  does not affect ``setUpTestData`` in unittest tests (test classes which
  inherit from Django's `TestCase`).

Bugfixes

* Fix :fixture:`live_server` when using an in-memory SQLite database.

* Fix typing of ``assertTemplateUsed`` and ``assertTemplateNotUsed``.

v4.4.0 (2021-06-06)
-------------------

Improvements

* Add a fixture :fixture:`django_capture_on_commit_callbacks` to capture
  :func:`transaction.on_commit() <django.db.transaction.on_commit>` callbacks
  in tests.

v4.3.0 (2021-05-15)
-------------------

Improvements

* Add experimental :ref:`multiple databases <multi-db>` (multi db) support.

* Add type annotations. If you previously excluded ``pytest_django`` from
  your type-checker, you can remove the exclusion.

* Documentation improvements.

v4.2.0 (2021-04-10)
-------------------

Improvements

* Official Django 3.2 support.

* Documentation improvements.

Bugfixes

* Disable atomic durability check on non-transactional tests

v4.1.0 (2020-10-22)
-------------------

Improvements

* Add the :fixture:`async_client` and :fixture:`async_rf` fixtures

* Add :ref:`django_debug_mode <usage>` to configure how ``DEBUG`` is set \ 
in tests

* Documentation improvements.

Bugfixes

* Make :fixture:`admin_user` work for custom user models without an ``email`` field.

v4.0.0 (2020-10-16)
-------------------

Compatibility

This release contains no breaking changes, except dropping compatibility
with some older/unsupported versions.

* Drop support for Python versions before 3.5

  Previously 2.7 and 3.4 were supported. Running ``pip install pytest-django``
  on Python 2.7 or 3.4 would continue to install the compatible 3.x series.

* Drop support for Django versions before 2.2

  Previously Django>=1.8 was supported.

* Drop support for pytest versions before 5.4

  Previously pytest>=3.6 was supported.

Improvements

* Officially support Python 3.9.

* Add ``pytest_django.__version__``

* Minor documentation improvements

Bugfixes

* Make the ``admin_user`` and ``admin_client`` fixtures compatible with custom
  user models which don't have a ``username`` field

* Change the ``admin_user`` fixture to use ``get_by_natural_key()`` to get the
  user instead of directly using ``USERNAME_FIELD``, in case it is overridden,
  and to match Django

Misc

* Fix pytest-django's own tests failing due to some deprecation warnings

Files:
RevisionActionfile
1.24modifypkgsrc/www/py-test-django/Makefile
1.5modifypkgsrc/www/py-test-django/PLIST
1.23modifypkgsrc/www/py-test-django/distinfo