[issue34413] Porting section of 3.5 "What's New" doc does not mention bytecode changes.

Eric Snow added the comment: Fair enough. Having the note in the 3.5 docs should be fine. :) -- resolution: -> rejected stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue34413] Porting section of 3.5 "What's New" doc does not mention bytecode changes.

Serhiy Storchaka added the comment: 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

[issue34413] Porting section of 3.5 "What's New" doc does not mention bytecode changes.

New submission from Eric Snow : 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.