Message335926
| Author |
vstinner |
| Recipients |
Anthony Sottile, Chris Billington, Ivan.Pozdeev, SilentGhost, __Vano, barry, brett.cannon, cheryl.sabella, christian.heimes, eric.smith, eric.snow, ethan smith, ionelmc, jaraco, mhammond, ncoghlan, pitrou, takluyver, terry.reedy, veky, vstinner |
| Date |
2019年02月19日.11:30:14 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1550575814.73.0.127450509758.issue33944@roundup.psfhosted.org> |
| In-reply-to |
| Content |
> 3. I realize that PEPs are needed for any change and even to define what that change might look like, but is there any value in adding PendingDeprecationWarnings for 3.8 if that's a possible action that will happen? As I understand it, it would be easier to remove that warning later instead of delaying any actions from it.
We cannot modify Python before a PEP is approved. It's too early to see that a PEP removing support for .pth file will be approved or not. There are too many constraints and use cases. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2019年02月19日 11:30:14 | vstinner | set | recipients:
+ vstinner, mhammond, barry, brett.cannon, terry.reedy, jaraco, ncoghlan, pitrou, eric.smith, christian.heimes, ionelmc, SilentGhost, __Vano, eric.snow, takluyver, veky, Ivan.Pozdeev, Anthony Sottile, ethan smith, cheryl.sabella, Chris Billington |
| 2019年02月19日 11:30:14 | vstinner | set | messageid: <1550575814.73.0.127450509758.issue33944@roundup.psfhosted.org> |
| 2019年02月19日 11:30:14 | vstinner | link | issue33944 messages |
| 2019年02月19日 11:30:14 | vstinner | create |
|