➜
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 2018-08-16 15:46 by eric.snow, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg323605 - (view) | Author: Eric Snow (eric.snow) *  |
Date: 2018-08-16 15:46 | |
In the 3.5 "What's New" doc, the porting section [1] does not mention the bytecode changes resulting from the PEP 448 implementation. [2][3] It should. I've marked this issue for the versions past 3.5 because each branch has its own "What's New" doc for 3.5. [1] https://docs.python.org/3/whatsnew/3.5.html#porting-to-python-3-5 [2] bpo-33216 [3] https://github.com/python/cpython/pull/8783#discussion_r210642202 |
|||
| msg323637 - (view) | Author: Serhiy Storchaka (serhiy.storchaka) * |
Date: 2018-08-17 06:08 | |
I don't think this needs to be exposed in What's New. This is a very low level implementation detail and isn't interested for most users. I think it would just distract attention from more significant changes. But it may be worth to document this change in the NEWS file. Changes in BUILD_MAP affected more users and also was not mentioned in the NEWS file. It was documented in the dis module documentation only in issue26213. |
|||
| msg323668 - (view) | Author: Eric Snow (eric.snow) * |
Date: 2018-08-17 20:40 | |
Fair enough. Having the note in the 3.5 docs should be fine. :) |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:04 | admin | set | github: 78594 |
| 2018-08-17 20:40:47 | eric.snow | set | status: open -> closed resolution: rejected messages: + msg323668 stage: needs patch -> resolved |
| 2018-08-17 06:08:18 | serhiy.storchaka | set | messages: + msg323637 |
| 2018-08-16 15:46:13 | eric.snow | create | |