-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
django-extensions: 2.1.4 -> 2.2.1 #68004
Conversation
On macos 10.13:
seems confused about its working dir etc. |
@risicle I could reproduce the issue building this on macOS. One test required localhost networking and an another issue is now reported upstream: I included the proposed upstream patch in this PR to fix the test failure. |
Neat! Afraid I can't test myself till the weekend but you seem to have it under control. |
de77fe7
to
5bfe019
Compare
The upstream patch is already merged, so I replaced the file with a |
please rebase and test again |
9c7fbd0
to
c821a6a
Compare
c821a6a
to
85b1fe3
Compare
Rebase is done. Only |
@FRidh can this be merged and cherry picked into release now? |
Closing as superseded by #72632 |
This updates
django-extensions
to version2.2.1
, which also fixes the pytest5 build failures.The
pipchecker
tests all try to executepip
inside the sandbox with either specific version requirements or agit+https
repository and are therefore removed because they fail.nix-review
shows two failed pkgs that depend ondjango-extensions
(python3.7-django-q-1.0.1
andpython3.7-HyperKitty-1.2.2
). They seem to fail due to pytest5 incompatibility.Motivation for this change
The
django-extensions
build is currently failing.Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers