-
-
Notifications
You must be signed in to change notification settings - Fork 611
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
Always obey --upgrade-package, and allow it together with --upgrade #831
Conversation
As an external contributor, I can't request a reviewer or assign to a milestone 🙊 |
Thanks for the contribution! I would suggest to split it to two PR, since #830 needs to be discussed. |
I will split if anyone finds the proposal offensive but I think it's quite an easy win |
At least it would be much easier to review for maintainers. |
Fixes jazzband#829. Fixes jazzband#830. Allow the two options together, essentially making `--upgrade-package` a way of passing an extra constraint. Always parse `--upgrade-package`, regardless of whether the output file exists.
7cf6873
to
1a78dd2
Compare
This comment has been minimized.
This comment has been minimized.
Codecov Report
@@ Coverage Diff @@
## master #831 +/- ##
==========================================
- Coverage 98.8% 98.69% -0.12%
==========================================
Files 36 36
Lines 2184 2139 -45
Branches 280 279 -1
==========================================
- Hits 2158 2111 -47
- Misses 15 16 +1
- Partials 11 12 +1
Continue to review full report at Codecov.
|
It would be better if this two issues depended on each other. But they look like not depended and can be fixed(implemented) separately. I must emphasise it's not mandatory, just a simple recommendation :) Have you researched why the options |
Oh, sorry, they should be fixed by one shot of course. |
It doesn't seem there was too much deliberation in #409 which added |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for review! I decided to un-parameterize the tests since the branching was reducing readability :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!
Thanks @atugushev ! 🎉 |
@adamchainz thanks for great work! I'll prepare a release within 24h. |
* Move and duplicate note about running under multiple Python versions to the start of each command's section. * Add note about using `--upgrade` and `--upgrade-package` together following jazzband#831. * Document `--output-file`.
|
* Move and duplicate note about running under multiple Python versions to the start of each command's section. * Add note about using `--upgrade` and `--upgrade-package` together following #831. * Document `--output-file`.
Fixes #829. Closes #830.
Allow the two options together, essentially making
--upgrade-package
a way of passing an extra constraint. Always parse--upgrade-package
, regardless of whether the output file exists.Changelog-friendly one-liner:
--upgrade
and--upgrade-package
are no longer mutually exclusive.--upgrade-package
now works even if the output file doesn't exist.Contributor checklist