-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Revert legacy path removals #12087
Revert legacy path removals #12087
Conversation
7594649
to
29b9b6e
Compare
29b9b6e
to
2210975
Compare
Thanks for picking this up, I'm very grateful this is landing |
I know that the py.path hook arguments deprecation didn't work (for implementers, it did work for callers). But are we sure that the py.path node constructor arguments deprecation didn't work? I don't remember seeing any complaints about that one but maybe I missed it. |
Good question, I decided to revert both py.path deprecations to avoid confusion -- better to deprecate the py.path arguments (hooks + nodes) in one fell swoop I think. |
I think it's better to keep the removal if it was properly deprecated, this way we don't hold up progress in this area until 9.1. But it's OK if you think otherwise. This PR just undoes the removal, doesn't fix the silent deprecation right? |
No it doesn't, we should create a new issue for that. From #12069 (comment):
@RonnyPfannschmidt do we know exactly for which hooks we were not showing the warnings?
I think it will be less confusing for users, also as I see it the benefit we want is to remove the |
This reverts commits 6c89f92 and a98f02d (as usual, thanks @bluetech for care with the git commit history), bringing back the legacy path arguments to hooks and
Node
constructors.We will need to manually fix the changelog for
8.1.1
at the time of release.Fix #12069