head	1.8;
access;
symbols
	pkgsrc-2026Q3:1.8.0.2
	pkgsrc-2026Q3-base:1.8
	pkgsrc-2026Q2:1.7.0.10
	pkgsrc-2026Q2-base:1.7
	pkgsrc-2026Q1:1.7.0.8
	pkgsrc-2026Q1-base:1.7
	pkgsrc-2025Q4:1.7.0.6
	pkgsrc-2025Q4-base:1.7
	pkgsrc-2025Q3:1.7.0.4
	pkgsrc-2025Q3-base:1.7
	pkgsrc-2025Q2:1.7.0.2
	pkgsrc-2025Q2-base:1.7
	pkgsrc-2025Q1:1.6.0.12
	pkgsrc-2025Q1-base:1.6
	pkgsrc-2024Q4:1.6.0.10
	pkgsrc-2024Q4-base:1.6
	pkgsrc-2024Q3:1.6.0.8
	pkgsrc-2024Q3-base:1.6
	pkgsrc-2024Q2:1.6.0.6
	pkgsrc-2024Q2-base:1.6
	pkgsrc-2024Q1:1.6.0.4
	pkgsrc-2024Q1-base:1.6
	pkgsrc-2023Q4:1.6.0.2
	pkgsrc-2023Q4-base:1.6
	pkgsrc-2023Q3:1.5.0.2
	pkgsrc-2023Q3-base:1.5
	pkgsrc-2023Q2:1.4.0.28
	pkgsrc-2023Q2-base:1.4
	pkgsrc-2023Q1:1.4.0.26
	pkgsrc-2023Q1-base:1.4
	pkgsrc-2022Q4:1.4.0.24
	pkgsrc-2022Q4-base:1.4
	pkgsrc-2022Q3:1.4.0.22
	pkgsrc-2022Q3-base:1.4
	pkgsrc-2022Q2:1.4.0.20
	pkgsrc-2022Q2-base:1.4
	pkgsrc-2022Q1:1.4.0.18
	pkgsrc-2022Q1-base:1.4
	pkgsrc-2021Q4:1.4.0.16
	pkgsrc-2021Q4-base:1.4
	pkgsrc-2021Q3:1.4.0.14
	pkgsrc-2021Q3-base:1.4
	pkgsrc-2021Q2:1.4.0.12
	pkgsrc-2021Q2-base:1.4
	pkgsrc-2021Q1:1.4.0.10
	pkgsrc-2021Q1-base:1.4
	pkgsrc-2020Q4:1.4.0.8
	pkgsrc-2020Q4-base:1.4
	pkgsrc-2020Q3:1.4.0.6
	pkgsrc-2020Q3-base:1.4
	pkgsrc-2020Q2:1.4.0.4
	pkgsrc-2020Q2-base:1.4
	pkgsrc-2020Q1:1.4.0.2
	pkgsrc-2020Q1-base:1.4
	pkgsrc-2019Q4:1.3.0.10
	pkgsrc-2019Q4-base:1.3
	pkgsrc-2019Q3:1.3.0.6
	pkgsrc-2019Q3-base:1.3
	pkgsrc-2019Q2:1.3.0.4
	pkgsrc-2019Q2-base:1.3
	pkgsrc-2019Q1:1.3.0.2
	pkgsrc-2019Q1-base:1.3
	pkgsrc-2018Q4:1.2.0.6
	pkgsrc-2018Q4-base:1.2
	pkgsrc-2018Q3:1.2.0.4
	pkgsrc-2018Q3-base:1.2
	pkgsrc-2018Q2:1.2.0.2
	pkgsrc-2018Q2-base:1.2
	pkgsrc-2018Q1:1.1.0.2
	pkgsrc-2018Q1-base:1.1;
locks; strict;
comment	@# @;


1.8
date	2026.08.12.07.57.25;	author adam;	state Exp;
branches;
next	1.7;
commitid	5JMBAOn0Vagv0kRG;

1.7
date	2025.04.15.04.52.02;	author adam;	state Exp;
branches;
next	1.6;
commitid	JQvhcojVEbTix6RF;

1.6
date	2023.11.03.08.21.59;	author adam;	state Exp;
branches;
next	1.5;
commitid	fqBZB4vrXdrJH8LE;

1.5
date	2023.09.06.20.17.50;	author adam;	state Exp;
branches;
next	1.4;
commitid	MH8BL4yP8fVFwKDE;

1.4
date	2020.01.14.16.05.04;	author adam;	state Exp;
branches;
next	1.3;
commitid	kRfWasKFs4sHUFSB;

1.3
date	2019.02.27.12.07.14;	author adam;	state Exp;
branches;
next	1.2;
commitid	nExnjr02FJqTUodB;

1.2
date	2018.06.24.11.19.33;	author adam;	state Exp;
branches;
next	1.1;
commitid	jVgqJdu4JkLFCwHA;

1.1
date	2018.01.11.14.07.11;	author adam;	state Exp;
branches;
next	;
commitid	Y3CYzJZBI3k3PsmA;


desc
@@


1.8
log
@py-test-django: updated to 4.14.0

4.14.0 (2026-08-10)

Compatibility

* Restored (unofficial) support for Django 5.0 and Django 5.1.

Improvements

* Added a ``django`` extra to the package. By depending on this extra
  (e.g. ``pip install pytest-django[django]``), the dependency resolver
  will ensure you get a version of pytest-django that is compatible with
  your version of Django (lower bound only). At least from now on...
@
text
@@@comment $NetBSD: PLIST,v 1.7 2025/04/15 04:52:02 adam Exp $
${PYSITELIB}/${WHEEL_INFODIR}/METADATA
${PYSITELIB}/${WHEEL_INFODIR}/RECORD
${PYSITELIB}/${WHEEL_INFODIR}/WHEEL
${PYSITELIB}/${WHEEL_INFODIR}/entry_points.txt
${PYSITELIB}/${WHEEL_INFODIR}/licenses/AUTHORS
${PYSITELIB}/${WHEEL_INFODIR}/licenses/LICENSE
${PYSITELIB}/${WHEEL_INFODIR}/top_level.txt
${PYSITELIB}/pytest_django/__init__.py
${PYSITELIB}/pytest_django/__init__.pyc
${PYSITELIB}/pytest_django/__init__.pyo
${PYSITELIB}/pytest_django/_version.py
${PYSITELIB}/pytest_django/_version.pyc
${PYSITELIB}/pytest_django/_version.pyo
${PYSITELIB}/pytest_django/asserts.py
${PYSITELIB}/pytest_django/asserts.pyc
${PYSITELIB}/pytest_django/asserts.pyi
${PYSITELIB}/pytest_django/asserts.pyo
${PYSITELIB}/pytest_django/django_compat.py
${PYSITELIB}/pytest_django/django_compat.pyc
${PYSITELIB}/pytest_django/django_compat.pyo
${PYSITELIB}/pytest_django/fixtures.py
${PYSITELIB}/pytest_django/fixtures.pyc
${PYSITELIB}/pytest_django/fixtures.pyo
${PYSITELIB}/pytest_django/lazy_django.py
${PYSITELIB}/pytest_django/lazy_django.pyc
${PYSITELIB}/pytest_django/lazy_django.pyo
${PYSITELIB}/pytest_django/live_server_helper.py
${PYSITELIB}/pytest_django/live_server_helper.pyc
${PYSITELIB}/pytest_django/live_server_helper.pyo
${PYSITELIB}/pytest_django/plugin.py
${PYSITELIB}/pytest_django/plugin.pyc
${PYSITELIB}/pytest_django/plugin.pyo
${PYSITELIB}/pytest_django/py.typed
${PYSITELIB}/pytest_django/runner.py
${PYSITELIB}/pytest_django/runner.pyc
${PYSITELIB}/pytest_django/runner.pyo
@


1.7
log
@py-test-django: updated to 4.11.1

v4.11.1 (2025-04-03)

Bugfixes

* Fixed a regression in v4.11.0 for Django ``TestCase`` tests using the ``databases`` class variable

v4.11.0 (2025-04-01)

Compatibility

* Added official support for Django 5.2
* Dropped testing on MySQL’s MyISAM storage engine

Bugfixes

* Stopped setting up and serializing databases on test session setup when not needed (the database is not requested / ``serialized_rollback`` is not used).
  On test databases with large amounts of pre-seeded data, this may remove a delay of a few seconds when running ``pytest --reuse-db``.

  The determination of which databases to setup is done by static inspection of the test suite.
  Using pytest's dynamic features to request db access, such as :meth:`request.getfixturevalue("db") <pytest.FixtureRequest.getfixturevalue>`, may throw off this analysis.
  If you start seeing ``DatabaseOperationForbidden`` or "unable to open database" errors, this is likely the cause.
  To fix this, decorate at least one test with the :func:`django_db <pytest.mark.django_db>` marker with appropriate ``databases`` and ``serialized_rollback`` settings.
@
text
@d1 1
a1 1
@@comment $NetBSD: PLIST,v 1.6 2023/11/03 08:21:59 adam Exp $
d17 1
@


1.6
log
@py-test-django: updated to 4.6.0

v4.6.0 (2023-10-30)
-------------------

Compatibility

* Official Django 4.1 & 4.2 support.

* Official Python 3.11 support.

* Drop support for Python version 3.5, 3.6 & 3.7.

* Drop official support for Django 4.0.

* Drop support for pytest < 7.

Improvements

* Add support for setting :py:attr:`available_apps
  <django.test.TransactionTestCase.available_apps>` in the :func:`django_db
  <pytest.mark.django_db>` marker.

* Convert Django :ref:`test tags <django:topics-tagging-tests>` to :ref:`Pytest
  markers <pytest:mark examples>`.

* Show Django's version in the pytest ``django`` report header.

* Add precise ``pytest_django.asserts.assertQuerySetEqual`` typing.

Bugfixes

* Fix bug where the effect of :func:`@@pytest.mark.ignore_template_errors
  <pytest.mark.ignore_template_errors>` was not reset when using
  ``--fail-on-template-vars``.
@
text
@d1 1
a1 3
@@comment $NetBSD: PLIST,v 1.5 2023/09/06 20:17:50 adam Exp $
${PYSITELIB}/${WHEEL_INFODIR}/AUTHORS
${PYSITELIB}/${WHEEL_INFODIR}/LICENSE
d6 2
d34 3
@


1.5
log
@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
@
text
@d1 8
a8 8
@@comment $NetBSD: PLIST,v 1.4 2020/01/14 16:05:04 adam Exp $
${PYSITELIB}/${EGG_INFODIR}/PKG-INFO
${PYSITELIB}/${EGG_INFODIR}/SOURCES.txt
${PYSITELIB}/${EGG_INFODIR}/dependency_links.txt
${PYSITELIB}/${EGG_INFODIR}/entry_points.txt
${PYSITELIB}/${EGG_INFODIR}/not-zip-safe
${PYSITELIB}/${EGG_INFODIR}/requires.txt
${PYSITELIB}/${EGG_INFODIR}/top_level.txt
@


1.4
log
@py-test-django: updated to 3.8.0

3.8.0:
* Make Django's assertion helpers available in pytest_django.asserts.
* Report django-configurations setting
@
text
@d1 1
a1 1
@@comment $NetBSD: PLIST,v 1.3 2019/02/27 12:07:14 adam Exp $
d6 1
d12 3
a17 3
${PYSITELIB}/pytest_django/compat.py
${PYSITELIB}/pytest_django/compat.pyc
${PYSITELIB}/pytest_django/compat.pyo
a29 3
${PYSITELIB}/pytest_django/migrations.py
${PYSITELIB}/pytest_django/migrations.pyc
${PYSITELIB}/pytest_django/migrations.pyo
d33 1
@


1.3
log
@py-test-django: updated to 3.4.8

3.4.8:
Fix DB renaming fixture for Multi-DB environment with SQLite
@
text
@d1 1
a1 1
@@comment $NetBSD: PLIST,v 1.2 2018/06/24 11:19:33 adam Exp $
d11 3
@


1.2
log
@py-test-django: updated to 3.3.2

3.3.2:
Unknown changes

3.3.1:
Bug fixes
* Fixed test for classmethod with Django TestCases again
Compatibility
* Support Django 2.1 (no changes necessary)
@
text
@d1 1
a1 1
@@comment $NetBSD: PLIST,v 1.1 2018/01/11 14:07:11 adam Exp $
a13 3
${PYSITELIB}/pytest_django/db_reuse.py
${PYSITELIB}/pytest_django/db_reuse.pyc
${PYSITELIB}/pytest_django/db_reuse.pyo
@


1.1
log
@py-test-django: added version 3.1.2

pytest-django allows you to test your Django project/applications with the
pytest testing tool.

Running your test suite with pytest-django allows you to tap into the features
that are already present in pytest. Here are some advantages:
* Manage test dependencies with pytest fixtures.
* Less boilerplate tests: no need to import unittest, create a subclass with
  methods. Write tests as regular functions.
* Database re-use: no need to re-create the test database for every test run.
* Run tests in multiple processes for increased speed (with the pytest-xdist
  plugin).
* Make use of other pytest plugins.
* Works with both worlds: Existing unittest-style TestCase's still work
  without any modifications.
@
text
@d1 1
a1 1
@@comment $NetBSD$
a34 3
${PYSITELIB}/pytest_django/pytest_compat.py
${PYSITELIB}/pytest_django/pytest_compat.pyc
${PYSITELIB}/pytest_django/pytest_compat.pyo
@

