RetroSearch Browse

Fri Jul 29 17:42:45 CEST 2011 · https://mail.python.org/pipermail/python-dev/2011-July/112641.html

Barry Warsaw wrote:
> On Jul 29, 2011, at 02:07 PM, Eli Bendersky wrote:
>> I think the unlink&rmtree functions are just a symptom. The real issue here
>> is - what is the devguide for, and how is it different from Python's
>> existing documentation? What should go into the official docs, and what
>> should go into the devguide? Once we agree on these question, I think the
>> test.support dilemma will solve itself.
> 
> Let's see!
> 
> I think the devguide should document things like "how to submit bugs", "how to
> use Mercurial", "how to propose changes to Python", "how to ensure code works
> across all existing interpreter implementations", "where to find continuous
> integration results and how to interpret them", "what's the right forum to
> discuss Python", etc.  I.e. processes, workflows, and conventions that are
> important cultural artifacts we've built up over 20 years.
> 
> I don't think the devguide should document the actual code we ship.

+1

~Ethan~

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

Showing content from https://mail.python.org/pipermail/python-dev/2011-July/112641.html below:

[Python-Dev] Convention on functions that shadow existing stdlib functions