Re: [Python-Dev] open issues on accepted PEPs
Nick Coghlan wrote: On Fri, Feb 3, 2012 at 9:16 AM, Ethan Furman wrote: I was looking at the other Open Issues on PEP 3134, think I might try to resolve them as well, and discovered via testing that they have already been taken care of. Is there an established way to get information like that? I realize that PEPs are partly historical documents, but it would it make sense to add a note after an Open Issue (or any other section) that was refined, resolved, or whatever in a later PEP or bug or patch or ...* If that kind of thing comes up, updating the PEP directly is definitely a reasonable way to clarify things. If people want to see the *exact* state of the PEP when it was accepted, they're all under version control. What we actually do depends on the specifics of the PEP, though (and whether or not anyone feels motivated to clarify things!). Okay. I would like to put links to the updates to the Open Issues in PEP3134 -- is there an easier way to find those besides typing in 'exception' in the bug tracker? I would like to complete that task in /this/ lifetime. ;) ~Ethan~ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] open issues on accepted PEPs
On Fri, Feb 3, 2012 at 9:16 AM, Ethan Furman wrote: > I was looking at the other Open Issues on PEP 3134, think I might try to > resolve them as well, and discovered via testing that they have already been > taken care of. > > Is there an established way to get information like that? > > I realize that PEPs are partly historical documents, but it would it make > sense to add a note after an Open Issue (or any other section) that was > refined, resolved, or whatever in a later PEP or bug or patch or ...* If that kind of thing comes up, updating the PEP directly is definitely a reasonable way to clarify things. If people want to see the *exact* state of the PEP when it was accepted, they're all under version control. What we actually do depends on the specifics of the PEP, though (and whether or not anyone feels motivated to clarify things!). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] open issues on accepted PEPs
I was looking at the other Open Issues on PEP 3134, think I might try to resolve them as well, and discovered via testing that they have already been taken care of. Is there an established way to get information like that? I realize that PEPs are partly historical documents, but it would it make sense to add a note after an Open Issue (or any other section) that was refined, resolved, or whatever in a later PEP or bug or patch or ...* ~Ethan~ *Yes, I am volunteering to tackle that project. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
