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

pythonPackages.zeep: Enable test suite for Python 3 #58154

Closed
wants to merge 2 commits into from

Conversation

rvl
Copy link
Contributor

@rvl rvl commented Mar 23, 2019

Motivation for this change

Using pytest with Python 3 is possible now.

See also #57469.

Things done
  • Enabled tests for the zeep package.

  • Added the airoresponses package which was a dependency of the test suite.

  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)

  • 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 nix-review --run "nix-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)

  • Assured whether relevant documentation is up to date

  • Fits CONTRIBUTING.md.

pkgs/development/python-modules/aioresponses/default.nix Outdated Show resolved Hide resolved
pkgs/development/python-modules/aioresponses/default.nix Outdated Show resolved Hide resolved
pkgs/development/python-modules/aioresponses/default.nix Outdated Show resolved Hide resolved
buildInputs = if isPy3k then [] else [
buildInputs = [
aiohttp
aioresponses
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest conditionally adding these to propagatedBuildInputs:

++ lib.optionals isPy3k [ aiohttp aioresponses ]

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you mark this as resolved? Zeep still doesn't work on Python 2 with your proposal.

@rvl rvl force-pushed the python-zeep-docheck branch 3 times, most recently from eb34f83 to 9f55a30 Compare March 23, 2019 22:45
@rvl
Copy link
Contributor Author

rvl commented Mar 24, 2019

I have better things to do than waste my time talking to you @dotlambda.

@rvl rvl closed this Mar 24, 2019
@dotlambda
Copy link
Member

@rvl I'm sorry if it felt like that. Did

You're not the only being on this planet.

offend you? If so, I'm sorry. I just meant to express "other people might be interested in Python 2 support" in a non-standard non-boring way. I'm genuinely interested to learn what you think I did wrong.

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

4 participants