On Sun, Oct 23, 2011 at 5:30 AM, Andrea Crotti
wrote:
> If one is not clearly defined, maybe notifying the last N developers that
> committed
> between the last successful builds and the failing build, would it be
> possible and make sense?
Yeah, as Antoine noted, that's where we want to get to e
On Sat, 22 Oct 2011 20:30:34 +0100
Andrea Crotti wrote:
>
> In my previous workplace if someone broke a build committing something
> wrong he/she
> had to bring cake for everyone next meeting.
>
> The cake is not really feasible I guess, but isn't it possible to notify
> the developer that
>
On 10/21/2011 10:08 PM, Antoine Pitrou wrote:
Hello,
There are currently a bunch of various buildbot failures on all 3
branches. I would remind committers to regularly take a look at the
buildbots, so that these failures get solved reasonably fast.
Regards
Antoine.
In my previous workplace i
(Sorry, should have gone to the list...)
On 22 October 2011 13:15, Vinay Sajip wrote:
> Nick Coghlan gmail.com> writes:
>
>> As a simpler alternative, I suggest the launcher just gain a "--which"
>> long option that displays the full path to the interpreter it found.
>>
>> So:
>>
>> C:\> py -2 -
Nick Coghlan gmail.com> writes:
> As a simpler alternative, I suggest the launcher just gain a "--which"
> long option that displays the full path to the interpreter it found.
>
> So:
>
> C:\> py -2 --which
> C:\Python27\python.exe
>
> C:\> py -3 --which
> C:\Python32\python.exe
>
> No signif
the py3k debug build has been broken in Cython's integration tests for a
couple of weeks now due to a use-after-decref bug. Here's the fix,
please apply.
Oops, I introduced this bug when I added "check_content" option to
_PyUnicode_CheckUnicode().
BTW, is there a reason unicode_subtype_new()
