GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — PEP 675: Add link to official discussion thread by CAM-Gerlach · Pull Request #2333 · python/peps

Conversation

@CAM-Gerlach

@CAM-Gerlach CAM-Gerlach commented Feb 16, 2022

Copy link
Copy Markdown
Member

It looks like PEP 675 hasn't yet been updated with the link to the latest official discussion thread (potentially contributing to the uncertainty of the community member on #2282 as to where to submit substantive feedback), which I believe I found after a fair amount of digging and a bit of guesswork. As such, this PR does just that.

CC: @pradeep90

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@CAM-Gerlach
PEP 675: Add link to official discussion thread
a333c81
@CAM-Gerlach
CAM-Gerlach requested a review from JelleZijlstra as a code owner February 16, 2022 17:24
@CAM-Gerlach CAM-Gerlach self-assigned this Feb 16, 2022
@the-knights-who-say-ni the-knights-who-say-ni added the CLA signed label Feb 16, 2022
JelleZijlstra
JelleZijlstra approved these changes Feb 17, 2022
View reviewed changes

@JelleZijlstra JelleZijlstra left a comment

Copy link
Copy Markdown
Member

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Existing PEPs are inconsistent, but this does seem more informative:

% grep 'Discussions-To.*yping' *.rst
pep-0585.rst:Discussions-To: Typing-Sig <[email protected]>
pep-0586.rst:Discussions-To: Typing-Sig <[email protected]>
pep-0589.rst:Discussions-To: [email protected]
pep-0591.rst:Discussions-To: [email protected]
pep-0593.rst:Discussions-To: [email protected]
pep-0604.rst:Discussions-To: [email protected]
pep-0612.rst:Discussions-To: Typing-Sig <[email protected]>
pep-0613.rst:Discussions-To: https://mail.python.org/archives/list/[email protected]/thread/MWRJOBEEEMFVXE7CAKO7B4P46IPM4AN3/
pep-0647.rst:Discussions-To: Typing-Sig <[email protected]>
pep-0655.rst:Discussions-To: typing-sig at python.org
pep-0673.rst:Discussions-To: Typing-Sig <[email protected]>
pep-0675.rst:Discussions-To: Typing-Sig <[email protected]>
pep-0681.rst:Discussions-To: https://mail.python.org/archives/list/[email protected]/thread/EAALIHA3XEDFDNG2NRXTI3ERFPAD65Z4/

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@CAM-Gerlach

CAM-Gerlach commented Feb 17, 2022

Copy link
Copy Markdown
Member Author

@JelleZijlstra Just FYI, as discussed and agreed in #2266 , PEP 1 will be formally revised to clarify that direct links to the actual discussion thread should be preferred whenever possible over a generic, relatively unhelpful email address; its just pending merge of #2302 to avoid any merge conflicts before I go ahead and implement what we talked about. That won't necessarily involve mass-updating all old PEPs (though there would be tangible benefits to doing so), but will at least apply to any new PEPs and when current draft, active, etc. PEPs are updated.

As an aside, speaking from personal experience, this is one of the single biggest consistent usability barriers that I've experienced as a PEP reader and contributor, as well as likely contributed to the community member's uncertainty about where to post feedback on the PEP that we saw on #2282 .

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@AA-Turner
AA-Turner merged commit 185aedc into python:main Feb 21, 2022
@erlend-aasland erlend-aasland mentioned this pull request May 13, 2022
pep8/greppable exception messages erlend-aasland/peps#1
Closed
@erlend-aasland erlend-aasland mentioned this pull request Jun 27, 2022
pep 687/mark as accepted erlend-aasland/peps#2
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@JelleZijlstra JelleZijlstra JelleZijlstra approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

@CAM-Gerlach CAM-Gerlach

Labels

CLA signed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

4 participants

@CAM-Gerlach @JelleZijlstra @AA-Turner @the-knights-who-say-ni
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.