bpo-23404: make regen-all What's New entry
#2128
Conversation
While the build changes won't affect most users, they may affect redistributors and folks building their own Python binaries from source.
|
Alternative proposal to #2127 |
|
I think this should be added also in What's New in 3.7. |
|
@serhiy-storchaka Agreed, but doing the different versions in different commits will make it easier to cherry-pick them to the applicable branches. |
|
(It's one of the few cases where I think cherry-picking forward into the development branch rather than backwards into the maintenance branches actually makes sense, as that way there can still be one combined PR to update 3.7) |
vstinner
left a comment
vstinner
left a comment
There was a problem hiding this comment.
Ah, you mean a new title, ok. I prefer your wording and formatting than me ;-) LGTM.
|
|
||
| (Contributed by Victor Stinner in :issue:`23404`.) | ||
|
|
||
| .. versionadded:: 3.6.2 |
There was a problem hiding this comment.
Hum, it's more versionchanged than versonadded, no?
There was a problem hiding this comment.
regen-all is genuinely new, and attempting to use it on 3.6.0 or 3.61 will straight-up fail, so "added" seemed appropriate. I did use a "changed" marker on ``touch`, though (since we don't have a "removed" marker).
|
Thanks @ncoghlan for the PR 🌮🎉.. I'm working now to backport this PR to: 2.7. |
|
Sorry, @ncoghlan, I could not cleanly backport this to |
6 participants
While the build changes won't affect most users,
they may affect redistributors and folks building
their own Python binaries from source.