Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19822
___
___
Python-bugs-list mailing list
Roundup Robot added the comment:
New changeset 34cb64cdbf7b by Guido van Rossum in branch 'default':
Add brief explanation and web pointers to README.txt. Fixes issue 19822.
http://hg.python.org/peps/rev/34cb64cdbf7b
--
nosy: +python-dev
___
Python
Changes by Guido van Rossum gu...@python.org:
--
resolution: rejected - fixed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19822
___
___
New submission from anatoly techtonik:
https://bitbucket.org/rirror/peps
PEP repository readme lacks information about how to send Python Enhancement
Proposal step-by-step.
1. hg clone https://bitbucket.org/rirror/peps
2. cd peps
3. # choose number
4. cp ??? pep-{{number}}.txt
5. # commit
6.
Christian Heimes added the comment:
The process is well explained in the PEP templates right at the top of the PEP
list:
http://www.python.org/dev/peps/pep-0009/
http://www.python.org/dev/peps/pep-0012/
New PEP authors should get in touch with experienced core developers or mentors
in order
STINNER Victor added the comment:
PEP process entrypoint
Do you work with developers of the distutils-* objects? It looks like Daniel
Holth works on such PEP for example:
https://mail.python.org/pipermail/distutils-sig/2013-July/021854.html
You may join this mailing list:
anatoly techtonik added the comment:
The entrypoint here means the point of entry for new Python Enhancement
Proposals. Christian, what you propose is a 4th order link for someone who
knows what PEPs are, and clones PEP repository to submit own proposal.
What I propose it to make PEP
Marc-Andre Lemburg added the comment:
Anatoly, please read http://www.python.org/dev/peps/pep-0012/
The process you are describing is not correct. In particular, the discussion
happens before sending in a pull request.
As for discussion of the PEP process: that should happen on python-dev,
anatoly techtonik added the comment:
The process you are describing is not correct. In particular, the discussion
happens before sending in a pull request.
Post the link to correct process into README.rst and then this issue can be
closed.
As for python-dev, I thought it is too obvious and
Christian Heimes added the comment:
The ticket has been closed by two people. Why do you keep re-opening the ticket?
--
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19822
Marc-Andre Lemburg added the comment:
On 28.11.2013 15:45, anatoly techtonik wrote:
anatoly techtonik added the comment:
The process you are describing is not correct. In particular, the discussion
happens before sending in a pull request.
Post the link to correct process into
anatoly techtonik added the comment:
The ticket has been closed by two people. Why do you keep re-opening the
ticket?
Because you're not providing any arguments. If it is not important for you,
just ignore. If something is not clear - ask. What you do is just closing the
stuff, because you
STINNER Victor added the comment:
Anatoly, please stop reopening the issue, it's *really* annoying. Not
only you failed to understand correctly your problem (it looks like
nor Christian nor Marc-Andre nor me understood your request), but it
looks like you don't care of our answers.
PEP
Changes by Giampaolo Rodola' g.rod...@gmail.com:
--
nosy: +giampaolo.rodola
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19822
___
___
Georg Brandl added the comment:
Closing for the hopefully final time. Anatoly, if you keep reopening this
ticket you have to expect removal of tracker privileges.
--
nosy: +georg.brandl
resolution: postponed - rejected
status: open - closed
___
15 matches
Mail list logo
