Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

python27Packages.pytestpep8: remove due to pytest v6 incompatibility #106579

Merged
merged 7 commits into from Dec 13, 2020

Conversation

drewrisinger
Copy link
Contributor

@drewrisinger drewrisinger commented Dec 10, 2020

Motivation for this change

Remove pythonPackages.pytestpep8 because:

Removing it will make it clear that it is no longer working, instead of chasing down pytest collection errors when the plugin doesn't work.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

Remove ``pythonPackages.pytestpep8`` because:
* It has been abandoned upstream: no PyPi release since 2014
* It is no longer compatible with pytest v6+: I get an error pointing to
  https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent
  when I try to use it with ``pytestCheckHook`` (i.e. pytest v6.0+)
* It doesn't have a maintainer
@drewrisinger
Copy link
Contributor Author

Converting to a draft b/c I didn't realize how widespread its usage is in the tree. It looks like pythonPackages.pytestpep8 only produces a pytest error when pytest is called as pytest --pep8, so maybe it's OK to leave in tree?

E.g. python3Packages.mwclient builds on master, but adding --pep8 to its checkPhase fails the build.

@jonringer
Copy link
Contributor

these could be dated references

most check phases are most likely not making use of it

@drewrisinger
Copy link
Contributor Author

@jonringer is it worth removing it then if the check phase isn't making use of it?

Just asking before I put in the time going through ~20 packages.

@drewrisinger drewrisinger reopened this Dec 11, 2020
pytestpep8 was removed in 25c9946.
This removes pytestpep8 in the rest of the tree, where it was hardly
used.
Build was failing due to line continuation between disabled tests in
checkPhase.
Fixed by converting to easier syntax of ``pytestCheckHook``.
@gebner
Copy link
Member

gebner commented Dec 13, 2020

All of the issues seem to have been addressed. I'm merging this now because the PR unbreaks cura. Please open a new PR for further improvements.

@gebner gebner merged commit 92cbe95 into NixOS:master Dec 13, 2020
@drewrisinger
Copy link
Contributor Author

I hadn't finished going through & building everything, so I didn't want to unmark it as a draft quite yet. I'll finish this project sometime later today, probably.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants