Message347288
| Author | vstinner |
|---|
| Recipients | dstufft, eric.araujo, p-ganssle, paul.moore, steve.dower, tim.golden, vstinner, zach.ware |
|---|
| Date | 2019-07-04.16:39:35 |
|---|
| SpamBayes Score | -1.0 |
|---|
| Marked as misclassified | Yes |
|---|
| Message-id | <1562258376.15.0.123922516458.issue37481@roundup.psfhosted.org> |
|---|
| In-reply-to | |
|---|
| Content |
|---|
> So consider me +1 for deprecate in 3.8 (we can still do that, right? it's just docs and a warning on use) and remove in 3.9 or 3.10 as appropriate.I modified my PR to deprecate the feature in Python 3.8. I'm not sure about scheduling the removal yet, since the Python 3.9 release schedule is under discussion:https://discuss.python.org/t/pep-596-python-3-9-release-schedule-doubling-the-release-cadence/1828I would prefer to give at least 2 years to projects to update their setup.py (how they are distributed). Even if bdist_wininst has issues, it's not too painful to maintain a few more years. The removal can be decided later. |
|