A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-August/016778.html below:

[Python-Dev] PEP comments, bugs, and patches

[Python-Dev] PEP comments, bugs, and patchesMartin von Loewis loewis@informatik.hu-berlin.de
Wed, 8 Aug 2001 09:13:32 +0200 (MEST)
I just found that PEP 1 is confusing in its instructions of how to
submit feedback on a PEP. In one place, it says

#  A better strategy is to encourage public feedback directly to the
#  PEP author, who collects and integrates the comments back into the
#  PEP.

which suggest that proposed amendments to a PEP should be sent to the
author. Later, it says

# Please use the SourceForge bug manager[6] if you want to report
# problems with PEPs, or better yet, the SourceForge patch manager[2]
# for submitting patches to PEPs.

which suggest that proposed amendments should be sent as patches to
SF. Now, which of these procedures is preferred? Does the second mean
that every PEP author needs permission to modify the patch database?
Should every such patch be assigned to the PEP editor (i.e. Barry)?

In case you wonder, the specific patch in question is #448841.

Regards,
Martin




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4