On Wed, Feb 2, 2011 at 06:50, anatoly techtonik wrote:
> On Wed, Feb 2, 2011 at 12:27 PM, Nick Coghlan wrote:
> > On Wed, Feb 2, 2011 at 6:33 PM, anatoly techtonik
> wrote:
> >> Making and testing a patch from Python checkout requires compiling
> >> Python, which is not possible for Windows use
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
On Wed, Feb 2, 2011 at 10:33 AM, anatoly techtonik wrote:
> How about patches sent by users who track and fix bugs directly in
> codebase of their Python installation?
While I don't personally endorse the above approach, if you're going
to develop inside your installed site-packages folder it see
On Wed, Feb 2, 2011 at 12:27 PM, Nick Coghlan wrote:
> On Wed, Feb 2, 2011 at 6:33 PM, anatoly techtonik wrote:
>> Making and testing a patch from Python checkout requires compiling
>> Python, which is not possible for Windows users.
>
> That latter comment hasn't been true since Microsoft starte
On Wed, Feb 2, 2011 at 6:33 PM, anatoly techtonik wrote:
> Making and testing a patch from Python checkout requires compiling
> Python, which is not possible for Windows users.
That latter comment hasn't been true since Microsoft started releasing
the Visual Studio Express editions.
> We should
On Tue, Jan 18, 2011 at 2:35 PM, Antoine Pitrou wrote:
> On Tue, 18 Jan 2011 07:14:51 +0100
> Ezio Melotti wrote:
>> > +
>> > +Committing Patches
>> > +==
> [...]
>> > +
>> > + svnmerge.py merge -r 42
>> > +
>> > +This will try to apply the patch to the current patch and genera
