Title: Porting section of 3.5 "What's New" doc does not mention bytecode changes.
Type: enhancement Stage: resolved
Components: Documentation Versions: Python 3.8, Python 3.7, Python 3.6, Python 3.5
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, eric.snow, serhiy.storchaka
Priority: low Keywords:

Created on 2018-08-16 15:46 by eric.snow, last changed 2018-08-17 20:40 by eric.snow. This issue is now closed.

Messages (3)
msg323605 - (view) Author: Eric Snow (eric.snow) * (Python committer) 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.

[2] bpo-33216
msg323637 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) 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) * (Python committer) Date: 2018-08-17 20:40
Fair enough.  Having the note in the 3.5 docs should be fine. :)
Date User Action Args
2018-08-17 20:40:47eric.snowsetstatus: open -> closed
resolution: rejected
messages: + msg323668

stage: needs patch -> resolved
2018-08-17 06:08:18serhiy.storchakasetmessages: + msg323637
2018-08-16 15:46:13eric.snowcreate