➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2020-11-04 21:35 by platonoff-dev, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Messages (4) | |||
|---|---|---|---|
| msg380365 - (view) | Author: Anatoliy Platonov (platonoff-dev) * | Date: 2020-11-04 21:35 | |
https://www.python.org/dev/peps/pep-0594/#id163 |
|||
| msg380368 - (view) | Author: Eric V. Smith (eric.smith) *  |
Date: 2020-11-04 21:44 | |
PEP 594 hasn't been accepted yet. |
|||
| msg380395 - (view) | Author: Steven D'Aprano (steven.daprano) * |
Date: 2020-11-05 07:43 | |
PEP 594 is a draft, it has not been accepted. It is premature to start cancelling perfectly good modules and breaking people's code. https://conroy.org/breaking-python-packages If you have some concrete reason for removing the binhex module, other than just PEP 594, then we can consider depreciating it in 3.10 or 3.11, and removing it in 3.12 or 3.13, or possibly later. |
|||
| msg380402 - (view) | Author: Anatoliy Platonov (platonoff-dev) * | Date: 2020-11-05 10:03 | |
Yeah, this was my mistake. I hurried a little with this issue and didn't notice that PEP is in draft state. Binhex module already marked as deprecated, since 3.9 I think. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:37 | admin | set | github: 86431 |
| 2020-11-05 10:03:39 | platonoff-dev | set | messages: + msg380402 |
| 2020-11-05 07:43:10 | steven.daprano | set | status: open -> closed nosy: + steven.daprano messages: + msg380395 resolution: rejected stage: resolved |
| 2020-11-04 21:44:40 | eric.smith | set | nosy:
+ eric.smith messages: + msg380368 |
| 2020-11-04 21:35:07 | platonoff-dev | create | |