about summary refs log tree commit diff
path: root/pkgs/development/python-modules/pytest
AgeCommit message (Collapse)AuthorFilesLines
2022-01-16python3Packages.pytest_5: removeFrederik Rietdijk1-95/+0
no longer needed
2022-01-16python2.pkgs: move expressions into python2-modules/ folderFrederik Rietdijk1-68/+0
Another step in further separating python2 from python3.
2021-12-26python310Packages.pytest: fix testsMartin Weinelt1-4/+8
2021-11-14Merge master into staging-nextgithub-actions[bot]1-3/+0
2021-11-13pkgs.development.python-modules: remove unused argsMarkus S. Wamser1-3/+0
2021-10-30pytest: new hook to delete pytest bytecodeSergei Trofimovich3-0/+39
In https://github.com/NixOS/nixpkgs/issues/139292 we found out that pytest leaves pytest-generated bytecode in install directory (as tests are ran after install). That bytecode is: - non-deterministic (was copied from cpython before cpython got support for deterministic bytecode) - unneeded after test run The change cleans bytecode up and provides a hook variable to avoid it if needed. Tested on `python39Packages.pytest-xdist` and `python27Packages.flaky` as: $ nix build -f. python39Packages.pytest-xdist $ nix build -f. python39Packages.pytest-xdist --rebuild $ nix build -f. python27Packages.flaky $ nix build -f. python27Packages.flaky --rebuild Closes: https://github.com/NixOS/nixpkgs/issues/139292
2021-09-05python3Packages.pytest: 6.2.4 -> 6.2.5Martin Weinelt1-2/+2
2021-09-05python3Packages.pytest_5: relax pluggy constraintsMartin Weinelt1-0/+5
2021-09-05python3Packages.pytest_4: relax pluggy constraintsSandro Jäckel1-0/+5
Following 7e27631e46c8121e5b906083e1de74ec53de2730
2021-09-05python3Packages.pytest: relax pluggy constraintsMartin Weinelt1-0/+5
Apparently possible without further changes: https://github.com/pytest-dev/pytest/pull/9040
2021-09-01python3Packages.pytest: 6.2.4 -> 6.2.5Martin Weinelt1-2/+2
2021-09-01python3Packages.pytest_5: relax pluggy constraintsMartin Weinelt1-0/+5
2021-09-01python3Packages.pytest_4: relax pluggy constraintsSandro Jäckel1-0/+5
Following 7e27631e46c8121e5b906083e1de74ec53de2730
2021-09-01python3Packages.pytest: relax pluggy constraintsMartin Weinelt1-0/+5
Apparently possible without further changes: https://github.com/pytest-dev/pytest/pull/9040
2021-06-22python3Packages.pytest: 6.2.3 -> 6.2.4Martin Weinelt1-2/+2
2021-06-03treewide: setuptools_scm -> setuptools-scmSandro Jäckel2-4/+4
2021-04-04python3Packages.pytest: 6.2.2 -> 6.2.3Martin Weinelt1-2/+2
https://github.com/pytest-dev/pytest/releases/tag/6.2.3
2021-04-03python3Packages.pytest: fix testsJonathan Ringer1-1/+4
2021-03-05python3Packages.pytest: 6.1.2 -> 6.2.2Fabian Affolter1-10/+12
2021-01-25treewide: remove stdenv where not neededPavol Rusnak3-3/+3
2021-01-24pkgs/development/python-modules: stdenv.lib -> libPavol Rusnak3-4/+4
2021-01-11treewide: with stdenv.lib; in meta -> with lib;Profpatsch3-6/+6
Part of: https://github.com/NixOS/nixpkgs/issues/108938 meta = with stdenv.lib; is a widely used pattern. We want to slowly remove the `stdenv.lib` indirection and encourage people to use `lib` directly. Thus let’s start with the meta field. This used a rewriting script to mostly automatically replace all occurances of this pattern, and add the `lib` argument to the package header if it doesn’t exist yet. The script in its current form is available at https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
2020-12-28python3Packages.pytest: remove unreproducible test artifacts from outputArnout Engelen1-0/+6
Running the tests produced some unreproducible artifacts from the output directory. This cleans them up afterwards.
2020-11-06python37Packages.pytest_6: 6.1.1 -> 6.1.2R. RyanTM1-2/+2
2020-10-16python37Packages.pytest_6: 6.0.1 -> 6.1.1R. RyanTM1-2/+2
2020-08-30python3Packages.pytest: 4.6.9 -> 4.6.11Frederik Rietdijk1-2/+2
2020-08-16python3Packages.pytest_5: init at 5.4.3Jonathan Ringer1-0/+80
2020-08-16pytest: fix dependencies, refactorJonathan Ringer1-7/+20
2020-08-16python: pytest: 5.4.3 -> 6.0.1Frederik Rietdijk1-2/+2
2020-06-06python: pytest: 5.4.2 -> 5.4.3Frederik Rietdijk1-2/+2
2020-05-11python2Packages.pytest: 4.6.8 -> 4.6.9Jonathan Ringer1-2/+2
2020-05-11python3Packages.pytest: does not need mockFrederik Rietdijk1-1/+1
2020-05-11python3Packages.pytest: 5.4.1 -> 5.4.2Frederik Rietdijk1-2/+2
2020-05-11python3Packages.pytest: 5.3.5 -> 5.4.1Jonathan Ringer1-6/+22
2020-04-22Merge pull request #72091 from xwvvvvwx/reproducible-pytest4Domen Kožar1-6/+8
python3Packages.pytest4: deterministic bytecode
2020-04-10treewide: Per RFC45, remove all unquoted URLsMichael Reilly2-2/+2
2020-01-30python: pytest: 5.3.2 -> 5.3.5Frederik Rietdijk1-2/+2
2019-12-30python: pytest: 4.6.7 -> 4.6.8Frederik Rietdijk1-2/+2
2019-12-30python: pytest: 5.2.4 -> 5.3.2Frederik Rietdijk1-2/+2
2019-12-15python: pytest: 4.6.6 -> 4.6.7Frederik Rietdijk1-2/+2
2019-11-22python: pytest: 5.2.2 -> 5.2.4Frederik Rietdijk1-2/+2
2019-11-12python: pytest: 5.2.1 -> 5.2.2Frederik Rietdijk1-2/+2
2019-10-27python3Packages.pytest4: deterministic bytecodeDavid Terry1-6/+8
For reasons that are not clear to me, the pytest4 check phase produces a lot of non-deterministic bytecode files. This PR turns off bytecode generation and disables a test that force enables bytecode generation.
2019-10-18python: pytest: 4.6.5 -> 4.6.6Frederik Rietdijk1-2/+2
2019-10-18python: pytest: 5.1.0 -> 5.2.1Frederik Rietdijk1-2/+2
2019-09-15python2Packages.pytest_5: disable buildMaximilian Bosch1-1/+2
`pytest_5` only supports python3[1], however the python2 build was enabled by separating pytest_4 and pytest_5 into two different attributes. ZHF #68361 [1] https://docs.pytest.org/en/latest/py27-py34-deprecation.html
2019-09-14paperless: Use pytest_4 in django-crispy-formsDaniel Schaefer1-0/+0
Doesn't build with pytest_5
2019-09-06Split buildPythonPackage into setup hooksFrederik Rietdijk1-4/+7
This commit splits the `buildPythonPackage` into multiple setup hooks. Generally, Python packages are built from source to wheels using `setuptools`. The wheels are then installed with `pip`. Tests were often called with `python setup.py test` but this is less common nowadays. Most projects now use a different entry point for running tests, typically `pytest` or `nosetests`. Since the wheel format was introduced more tools were built to generate these, e.g. `flit`. Since PEP 517 is provisionally accepted, defining a build-system independent format (`pyproject.toml`), `pip` can now use that format to execute the correct build-system. In the past I've added support for PEP 517 (`pyproject`) to the Python builder, resulting in a now rather large builder. Furthermore, it was not possible to reuse components elsewhere. Therefore, the builder is now split into multiple setup hooks. The `setuptoolsCheckHook` is included now by default but in time it should be removed from `buildPythonPackage` to make it easier to use another hook (curently one has to pass in `dontUseSetuptoolsCheck`).
2019-08-18pythonPackages.pytest: 4.6.5 -> 5.1.0 in case of Python 3Frederik Rietdijk2-3/+52
2019-08-18pythonPackages.pytest: 4.6.3 -> 4.6.5Frederik Rietdijk1-2/+2
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-08-08 06:15:38 +0000