Message333645
| Author | barry |
|---|---|
| Recipients | Anthony Sottile, Chris Billington, Ivan.Pozdeev, SilentGhost, __Vano, barry, brett.cannon, christian.heimes, emma_smith, eric.smith, eric.snow, jaraco, mhammond, ncoghlan, pitrou, takluyver, terry.reedy, vstinner |
| Date | 2019-01-14.22:42:18 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <26D38932-E046-477D-8626-DB9C03A528AE@python.org> |
| In-reply-to | <CA+3bQGHaHxdrJE4vyQJvt57eNb2uSR8D8Mt3nKEg-39d3uJRGw@mail.gmail.com> |
| Content | |
|---|---|
On Jan 14, 2019, at 17:30, STINNER Victor <report@bugs.python.org> wrote: > > I don't think that you will like it, but I feel that a PEP will be needed > here to list use cases and explain what replace .pth files for each use > case. Maybe no replacement for some use cases is fine. The PEP doesn't have > to be long. > > I also expect that it's going to be a large backward incompatible change. A > PEP can summerize the rationale, schedule deprecation, etc. +1 > Any volunteer around? Barry, Nick, someone else? I will volunteer to co-author. I would definitely like at least Nick and/or Jason to help. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-01-14 22:42:19 | barry | set | recipients: + barry, mhammond, brett.cannon, terry.reedy, jaraco, ncoghlan, pitrou, vstinner, eric.smith, christian.heimes, SilentGhost, __Vano, eric.snow, takluyver, Ivan.Pozdeev, Anthony Sottile, emma_smith, Chris Billington |
| 2019-01-14 22:42:18 | barry | link | issue33944 messages |
| 2019-01-14 22:42:18 | barry | create | |