-
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
Disallow explicitly passing install-location-related arguments in --install-options #8556
Disallow explicitly passing install-location-related arguments in --install-options #8556
Conversation
The current test depends on passing `--home` to `--install-option`. Since we would like that to fail, we need to use another argument. None of the other possible arguments have a visible side-effect, so we just write the provided arguments to a file and check that in the test.
Similar to our previous test refactoring, this removes the usage of `--home` from the test command. "Overriding" in the original test meant "placed after" in the command-line arguments, which makes sense because setuptools will use the last argument passed.
Since it no longer shows a deprecation warning, the previous name doesn't fit.
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.
I recently learned that our deprecated
function automatically turns deprecation warnings into exceptions when the pip version is greater than the gone_in
version. Not sure in which case it is appropriate to use that mechanism, though.
I assumed that was to make sure we do not forget to follow through on the warning. |
Yes! The idea is that if we miss this, the release manager would be running the test suite after bumping the version and we'llccatch the missed-deprecation there. This was something I thought was documented in the release process but isn't! We should fix the docs. :) |
Thank you again for your time! Now hopefully we can clean some stuff up. |
This converts our deprecation warning into a hard failure.
Closes #7309.