-
Notifications
You must be signed in to change notification settings - Fork 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
freeze: make --all the default & deprecate it #9068
Conversation
c8e3dcb
to
b54820a
Compare
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.
Do we not want a transitory step, where we present a warning before making such a change, as per our https://pip.pypa.io/en/stable/development/release-process/#deprecation-policy?
I hesitated and I agree that this PR doesn't follow our deprecation policy. But following it would mean to:
which would be bothersome for users who will want an option to disable the warning. I guess a |
b54820a
to
c178119
Compare
An alternative plan could be #4256 (comment) |
Hello! I am an automated bot and I have noticed that this pull request is not currently able to be merged. If you are able to either merge the |
@xavfernandez Nudge to update this. |
c178119
to
ac51fa4
Compare
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.
@xavfernandez Could you update this PR?
deprecated( | ||
"--all is now the default behavior and does nothing", | ||
None, | ||
gone_in="23.3", |
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.
gone_in="23.3", | |
gone_in="23.0", |
Let's keep this for as little time as possible?
Closing this out given the lack of activity. |
Close #4256
And small step towards #7157