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/2011-February/107867.html below:

[Python-Dev] devguide: Generate patches without code checkout (Was: devguide: Write a guide to committing a patch.)

[Python-Dev] devguide: Generate patches without code checkout (Was: devguide: Write a guide to committing a patch.) [Python-Dev] devguide: Generate patches without code checkout (Was: devguide: Write a guide to committing a patch.)Georg Brandl g.brandl at gmx.net
Wed Feb 2 20:29:15 CET 2011
Am 02.02.2011 13:50, schrieb anatoly techtonik:

>>> We should add less
>>> hardcore instructions how to use bundled diff.py for creating simple
>>> patches like docstring, comment fixes or generating new testcases.
>>> This will greatly reduce the barrier for starting with development.
>>
>> Given the length of Python's release cycles, diffs against released
>> versions are far too likely to be out of date. We want diffs against
>> the head of the relevant branch.
> 
> I only see that you want the contribution entry barrier to stay at the
> height of core developer.

Because only core developers are allowed to have a checkout of trunk?

Georg

More information about the Python-Dev mailing list

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