Repository navigation
PEP 684: Minor Updates - #3004
Conversation
|
Hey, so just FYI, at least the modern link form of If the update is major enough, you could consider posting a fresh "Take 2" (or 3, 4, etc) discussion thread and updating the The linter intentionally ensures that Discourse links are to the thread rather than to an individual message, per the above, and also because it is a pretty easy mistake to make by accident as if you've scrolled past the first message, the message number will be appended to the URL, leaving readers unintentionally stuck in the middle of the thread rather than at the start (which also messes with Discourse's bookmarking of where you left off reading a thread). Also, as the headers are intended to be structured data in an easily-machine-parsable format, consumed by a number of tools in this repo and many more through the PEP API, including PEP-o-tron, the Python Discord bot, and others, it's best if they are as consistant as possible. As such, I've opened PR #3005 to fix the issue. |
|
FWIW, I find it useful to identify each round of discussion. In this case I re-used the same thread, since it is the one in the |
|
Hey, thanks for taking the time to explain your reasoning and the benefits you feel it brings for authors and readers. After some thought, in light of that I think there's a relatively clean workaround in the linter that will still detect cases where a specific message was unintentionally appended (e.g. due to scrolling), but still allow intentionally linking directly to a specific post if the author is convinced that is best for their PEP. See PR #3005 for more discussion on that. |
|
Thanks for not dropping this, even though that would have been okay. 😄 |
I had forgotten to update the Post-History header back in October. There was also one minor point from that round of discussion that I had not added to the PEP yet.
PEP 123: Summary of changes)