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!
--
Victor Stinner
http://www.haypocalc.com/
___
python-committers mailing list
python-committers
On Fri, Jul 23, 2010 at 2:45 AM, Jesus Cea 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 generall
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
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
-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 Ben
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 wrote:
> > Can a committer check-in their own PEP directly, or do they
2010/7/22 Nick Coghlan :
> On Thu, Jul 22, 2010 at 6:35 PM, Barry Warsaw 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 # Ge
On Thu, Jul 22, 2010 at 6:35 PM, Barry Warsaw 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
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 (hi
2010/7/21 Nick Coghlan :
> On Thu, Jul 22, 2010 at 2:15 AM, Guido van Rossum 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
>> arbi
On Thu, Jul 22, 2010 at 2:15 AM, Guido van Rossum 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 H
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 pep2htm
On Wed, Jul 21, 2010 at 11:34, Antoine Pitrou wrote:
> Can a committer check-in their own PEP directly, or do they have to go
> through the p...@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
Hello,
Can a committer check-in their own PEP directly, or do they have to go
through the p...@python.org process?
Thank you
Antoine.
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-com
14 matches
Mail list logo
