Re: [Python-Dev] [PATCH] unicode subtypes broken in latest py3k debug builds
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() copies the buffer of the unicode object it just created, instead of just stealing it? Good question. We can maybe optimize this function. Victor ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP397 no command line options to python?
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 significant complexity in the launcher, and if you want to add > additional arguments like -m, -c, or -i you can do it by running > '--which' and switching to invoking that interpreter directly. Perhaps even simpler would be for the -h option to print the interpreter paths which would be returned for -2 and -3, on separate lines, even without the --which, e.g. Currently configured: -2: c:\Python27\python.exe -3: c:\Python32\python.exe Regards, Vinay Sajip ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP397 no command line options to python?
(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 --which >> C:\Python27\python.exe >> >> C:\> py -3 --which >> C:\Python32\python.exe >> >> No significant complexity in the launcher, and if you want to add >> additional arguments like -m, -c, or -i you can do it by running >> '--which' and switching to invoking that interpreter directly. > > Perhaps even simpler would be for the -h option to print the interpreter paths > which would be returned for -2 and -3, on separate lines, even without the > --which, e.g. > > Currently configured: > -2: c:\Python27\python.exe > -3: c:\Python32\python.exe --which is nice for people who can use Unix-style $() or Powershell & to directly execute the output as a command. & (py -3 --which) Paul > ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Buildbot failures
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 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 broke the build? 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? ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Buildbot failures
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 > broke the build? Some of us do the notifying manually, but it's quite boring and bothersome. Automating it is a bit tricky, since some of our tests (as well as some of the buildslaves themselves) are a bit flaky and will produce intermittent failures. But I think it's indeed the good direction. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Buildbot failures
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 eventually, but at the moment, even the "stable" buildbots are a bit too flaky for us to turn that on (essentially, the buildbots end up spamming the alerts, so people start assuming they're *all* false alarms and the notifications become ineffective). We're getting closer though - since the buildbots were put in place, many of the flakier tests have been redesigned to be significantly more reliable. In the meantime, we rely on committers to check the buildbot pages for a day or two after they make commits to confirm there aren't any lurking cross-platforms problems or other issues with their changes. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
