-
-
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
Treat --upgrade-packages
PKGSPECs as constraints (not just minimums), consistently
#1578
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
afe728c
to
6a6b4c7
Compare
--upgrade-packages PKGSPEC
s as constraints, even for yet unpinned subdependencies, or when combined with --upgrade
--upgrade-packages PKGSPEC
s as constraints, even for yet unpinned subdependencies, or when combined with --upgrade
This comment was marked as outdated.
This comment was marked as outdated.
OK I think the new parametrization for |
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 working to restore this behavior @AndydeCleyre !
90c1b6c
to
d2a8569
Compare
cd3002a
to
e248a40
Compare
583104c
to
e8fd4b0
Compare
e8fd4b0
to
6d979d5
Compare
f9b3eae
to
51bf60d
Compare
e187eaa
to
efaf7e9
Compare
06708b0
to
51d4d41
Compare
51d4d41
to
e0bf1b5
Compare
e0bf1b5
to
316052b
Compare
Ensure temporary constraints file gets cleaned up in a way that avoids Windows file handling complications
Remove leftovers of now unused existing_pins_to_upgrade set
... to cover when the subdependency is not already pinned
... to cover when the -P pkgs are only subdependencies
316052b
to
91a1c0e
Compare
--upgrade-packages
PKGSPECs as constraints (not just minimums), consistently
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.
Finally got to this PR. That looks awesome, thanks!
Fixes #1550
This aims to address two problems:
--upgrade
and--upgrade-packages PKGSPEC
are used together, andPKGSPEC
's package is not in the input file (but is a subdependency), then that package is upgraded beyondPKGSPEC
--upgrade-packages PKGSPEC
is used, andPKGSPEC
's package is in neither the input file nor a preexisting output file (but is a subdependency), then that package is upgraded beyondPKGSPEC
In other words:
Some of the current behavior was informed by discussion at #759.
However my understanding now is that it's useful, expected, and without significant cost to additionally treat
--upgrade-packages
specs as constraints, thereby resolving the above cases.Contributor checklist
Maintainer checklist
backwards incompatible
,feature
,enhancement
,deprecation
,bug
,dependency
,docs
orskip-changelog
as they determine changelog listing.