Conversation
| * A 3 year deprecating for the processing of ``import`` lines in ``.pth`` | ||
| files, after which, ``import`` lines in ``.pth`` files will be silently | ||
| ignored. | ||
| * A 5 year period after which a warning will be produced for the existence of |
There was a problem hiding this comment.
Wait, they're deprecated after 3 years, and then after 5 years we produce a warning?
There was a problem hiding this comment.
The thinking behind this is that there's a strong desire to stop processing import lines asap (3 years) but not to annoy people with warnings until the last active Python that doesn't support 829 is EOL (5 years). Without this, you can't "roman ride" with both a legacy .pth file for older Pythons and a .start file for newer Pythons without warnings.
There was a problem hiding this comment.
So the earlier deprecation is silent? I know this has been decided on already, just want to make sure it's presented clearly. Perhaps something like this:
Support for import lines in .pth files will be gradually removed:
- For the first three years (expected to be Python 3.15, 3.16, and 3.17) the behavior will remain as it is now.
- For the next two years (expected to be Python 3.18 and 3.19),
importlines will be silently ignored. - Afterwards (expected to be Python 3.20 and higher), a warning will be produced for the existence of
importlines in.pthfiles.
There was a problem hiding this comment.
Yes, that's much clearer, thanks! Let me push an update.
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
3 participants
Also, updates based on SC acceptance feedback
📚 Documentation preview 📚: https://pep-previews--4937.org.readthedocs.build/