Hello,
Can a committer check-in their own PEP directly, or do they have to go through the peps@python.org process?
Thank you
Antoine.
On Wed, Jul 21, 2010 at 11:34, Antoine Pitrou solipsis@pitrou.net wrote:
Can a committer check-in their own PEP directly, or do they have to go through the peps@python.org process?
As long as the PEP is formatted correctly and conforms to PEP 1 (PEP Purpose and Guidelines), committers are welcome to handle their PEPs directly. Less experienced PEP authors should send drafts to peps@python.org for editorial guidance. The PEP editors are there to help polish your text and avoid omissions & embarrassing errors.
IOW, as a committer you're welcome to short-circuit the PEP process, but if you do, the egg will be on your own face ;-)
Thank you all for the answers! The PEP (numbered 3151) is now discussed on python-ideas.
Regards
Antoine.
Le mercredi 21 juillet 2010 à 12:01 -0400, David Goodger a écrit :
On Wed, Jul 21, 2010 at 11:34, Antoine Pitrou solipsis@pitrou.net wrote:
Can a committer check-in their own PEP directly, or do they have to go through the peps@python.org process?
As long as the PEP is formatted correctly and conforms to PEP 1 (PEP Purpose and Guidelines), committers are welcome to handle their PEPs directly. Less experienced PEP authors should send drafts to peps@python.org for editorial guidance. The PEP editors are there to help polish your text and avoid omissions & embarrassing errors.
IOW, as a committer you're welcome to short-circuit the PEP process, but if you do, the egg will be on your own face ;-)
Le jeudi 22 juillet 2010 14:24:06, Antoine Pitrou a écrit :
The PEP (numbered 3151) is now discussed on python-ideas.
I like this PEP, great job Antoine!
You can check in directly. The peps@ list is only for PEP authors without checkin privileges, or if you're not sure you have conformed to the PEP template sufficiently well. Picking a PEP number is arbitrated by svn (soon hopefully Hg). However always to make sure that your pep runs through pep2html without warnings or errors.
--Guido
On Wed, Jul 21, 2010 at 4:34 PM, Antoine Pitrou solipsis@pitrou.net wrote:
Hello,
Can a committer check-in their own PEP directly, or do they have to go through the peps@python.org process?
Thank you
Antoine.
python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
On Thu, Jul 22, 2010 at 2:15 AM, Guido van Rossum guido@python.org wrote:
You can check in directly. The peps@ list is only for PEP authors without checkin privileges, or if you're not sure you have conformed to the PEP template sufficiently well. Picking a PEP number is arbitrated by svn (soon hopefully Hg). However always to make sure that your pep runs through pep2html without warnings or errors.
These days running genpepindex.py is also useful to make sure you don't break the generation of PEP 0 (e.g. I found an error in the way I had written the headers for PEP 3150 when I did that).
Useful commands (using PEP 3150 as my example): python genpepindex.py # ./genpepindex.py only works if Python 2.5 is installed ./pep2html.py -b 3150 # Generate the PEP and open in a new browser window ./pep2html.py 3150 # Regenerate the PEP (hit refresh in the browser to see changes)
The "-b" switch opens the wrong browser for me (Konqueror, despite Firefox being set as default) but it's handy when it works. Otherwise the HTML file is pretty easy to find manually (it is generated in the same directory as the source text file)
You won't have the relevant CSS files, so the PEP won't be as nicely formatted as it is on python.org, but you can still check that things are coming out basically the way you want them to.
Cheers, Nick.
2010/7/21 Nick Coghlan ncoghlan@gmail.com:
On Thu, Jul 22, 2010 at 2:15 AM, Guido van Rossum guido@python.org wrote:
You can check in directly. The peps@ list is only for PEP authors without checkin privileges, or if you're not sure you have conformed to the PEP template sufficiently well. Picking a PEP number is arbitrated by svn (soon hopefully Hg). However always to make sure that your pep runs through pep2html without warnings or errors.
These days running genpepindex.py is also useful to make sure you don't break the generation of PEP 0 (e.g. I found an error in the way I had written the headers for PEP 3150 when I did that).
Useful commands (using PEP 3150 as my example): python genpepindex.py # ./genpepindex.py only works if Python 2.5 is installed
You can also do "make PYTHON=python"
On Jul 22, 2010, at 08:17 AM, Nick Coghlan wrote:
Useful commands (using PEP 3150 as my example): python genpepindex.py # ./genpepindex.py only works if Python 2.5 is installed ./pep2html.py -b 3150 # Generate the PEP and open in a new browser window ./pep2html.py 3150 # Regenerate the PEP (hit refresh in the browser to see changes)
Just run 'make' in the peps checkout directory.
-Barry
On Thu, Jul 22, 2010 at 6:35 PM, Barry Warsaw barry@python.org wrote:
On Jul 22, 2010, at 08:17 AM, Nick Coghlan wrote:
Useful commands (using PEP 3150 as my example): python genpepindex.py # ./genpepindex.py only works if Python 2.5 is installed ./pep2html.py -b 3150 # Generate the PEP and open in a new browser window ./pep2html.py 3150 # Regenerate the PEP (hit refresh in the browser to see changes)
Just run 'make' in the peps checkout directory.
That doesn't work for me by default since I don't have python2.5 installed (although it does turn out it can be made to work by overriding PYTHON as Benjamin suggests). Not only that, but the makefile builds all the PEPs when I generally only care about the PEP I'm working on and PEP 0.
Basically, direct invocation of the Python scripts is simple enough in this case that going indirect through the makefile didn't really make things any easier for me.
Cheers, Nick.
2010/7/22 Nick Coghlan ncoghlan@gmail.com:
On Thu, Jul 22, 2010 at 6:35 PM, Barry Warsaw barry@python.org wrote:
On Jul 22, 2010, at 08:17 AM, Nick Coghlan wrote:
Useful commands (using PEP 3150 as my example): python genpepindex.py # ./genpepindex.py only works if Python 2.5 is installed ./pep2html.py -b 3150 # Generate the PEP and open in a new browser window ./pep2html.py 3150 # Regenerate the PEP (hit refresh in the browser to see changes)
Just run 'make' in the peps checkout directory.
That doesn't work for me by default since I don't have python2.5 installed (although it does turn out it can be made to work by overriding PYTHON as Benjamin suggests). Not only that, but the makefile builds all the PEPs when I generally only care about the PEP I'm working on and PEP 0.
Note that dinsdale's python version is now up to 2.5, so the prefix can be (and has been) removed.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 22/07/10 14:16, Nick Coghlan wrote:
Just run 'make' in the peps checkout directory.
That doesn't work for me by default since I don't have python2.5 installed (although it does turn out it can be made to work by overriding PYTHON as Benjamin suggests). Not only that, but the makefile builds all the PEPs when I generally only care about the PEP I'm working on and PEP 0.
The "make" should include dependency information to only rebuild the changed documents. :-?.
Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ . _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
Just run 'make' in the peps checkout directory.
That doesn't work for me by default since I don't have python2.5 installed (although it does turn out it can be made to work by overriding PYTHON as Benjamin suggests). Not only that, but the makefile builds all the PEPs when I generally only care about the PEP I'm working on and PEP 0.
The "make" should include dependency information to only rebuild the changed documents. :-?.
And indeed, it does.
Regards, Martin
>>>> Just run 'make' in the peps checkout directory.
>>>
>>> That doesn't work for me by default since I don't have python2.5
>>> installed (although it does turn out it can be made to work by
>>> overriding PYTHON as Benjamin suggests). Not only that, but the
>>> makefile builds all the PEPs when I generally only care about the PEP
>>> I'm working on and PEP 0.
>>
>> The "make" should include dependency information to only rebuild the
>> changed documents. :-?.
Martin> And indeed, it does.
Following up on Martin's comment, note that you are not required to make all PEP outputs. Just make the one(s) you care about at the moment:
% make pep-0008.html
pep-0008.txt (text/plain) -> pep-0008.html
Skip
On Fri, Jul 23, 2010 at 2:45 AM, Jesus Cea jcea@jcea.es wrote:
That doesn't work for me by default since I don't have python2.5 installed (although it does turn out it can be made to work by overriding PYTHON as Benjamin suggests). Not only that, but the makefile builds all the PEPs when I generally only care about the PEP I'm working on and PEP 0.
The "make" should include dependency information to only rebuild the changed documents. :-?.
I don't generally have the PEP directory completely built. I suppose I *could* do it that way but the basic commands are so simple I've never even considered the idea.
Cheers, Nick.
-
"Martin v. Löwis" -
Antoine Pitrou -
Barry Warsaw -
Benjamin Peterson -
David Goodger -
Guido van Rossum -
Jesus Cea -
Nick Coghlan -
skip＠pobox.com -
Victor Stinner