David Abrahams writes:
> At Sat, 08 May 2010 11:04:47 -0500,
> John Arbash Meinel wrote:
> > Don't you need to register the "git+file:///" url for urlparse to
> > properly split it?
>
> Yes. But the question is whether urlparse should really be so fragile
> that every hierarchical scheme
On Sun, May 09, 2010 at 03:19:40PM -0600, David Abrahams wrote:
> John Arbash Meinel wrote:
> > Don't you need to register the "git+file:///" url for urlparse to
> > properly split it?
>
> Yes. But the question is whether urlparse should really be so fragile
> that every hierarchical scheme needs
On Wed, May 5, 2010 at 8:10 AM, Antoine Pitrou wrote:
> For the record, I've added to the untabify script a patch rewriting option
> ("-p") which reindents all patch hunks for C files containing tabs. It
> should
> minimize manual reformatting work with existing patches.
>
I just tried '-p' with
On Sun, May 09, 2010 at 03:19:40PM -0600, David Abrahams wrote:
> Yes. But the question is whether urlparse should really be so fragile
> that every hierarchical scheme needs to be explicitly registered.
> Surely ending with “+file” should be sufficient to have it recognized
> as a file-based sche
At Sat, 08 May 2010 11:04:47 -0500,
John Arbash Meinel wrote:
>
> Stephen J. Turnbull wrote:
> > David Abrahams writes:
> > >
> > > This is a bug report. bugs.python.org seems to be down.
> > >
> > > >>> from urlparse import *
> > > >>> urlunsplit(urlsplit('git+file:///foo/bar/baz'))
>
* Benjamin Peterson:
> http://doc.python.org/dev/whatsnew/2.7.html or Misc/NEWS in the Python
> distribution.
Something is missing here: "* Multiple context managers in"
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/li
Hello,
The untabification of C files didn't produce any noticeable problem on
the buildbots. I've updated PEP 7 with the mention that all C files
should be 4-space indented, and removed the obsolete wording about
some files being indented with tabs.
Regards
Antoine.
_
On Thu, May 6, 2010 at 4:52 AM, Joao S. O. Bueno wrote:
> On Wed, May 5, 2010 at 9:59 PM, Eric Smith wrote:
>> That's my point. Since it's basically unreviewable, is it smart to do it
>> during a beta?
>
> Hello folks -
> I don't think these modifications are that "unreviewable": the
> generated
John Arbash Meinel writes:
> Stephen J. Turnbull wrote:
> > David Abrahams writes:
> > >
> > > This is a bug report. bugs.python.org seems to be down.
> > >
> > > >>> from urlparse import *
> > > >>> urlunsplit(urlsplit('git+file:///foo/bar/baz'))
> > > git+file:/foo/bar/baz
> FWIW I *usually* run the test suite with parallelization (it is just so
> much quicker) and these days *rarely* see spurious failures as a result.
> This is on Mac OS X, YMMV.
I may misremember the details, but IIRC, the multiprocessing tests would
fail to terminate on Solaris. This made it unsu
Le dimanche 09 mai 2010 11:08:29, Michael Foord a écrit :
> FWIW I *usually* run the test suite with parallelization (it is just so
> much quicker) and these days *rarely* see spurious failures as a result.
> This is on Mac OS X, YMMV.
I use regrtest.py -j 4 on a Intel Quad Core on Linux: 4 tests
On 09/05/2010 03:32, Nick Coghlan wrote:
Martin v. Löwis wrote:
Has anyone considered using regrtest's -j option in the buildbot
configuration to speed up the test runs?
Yes, I did. I turned it off again when the tests started failing because
of it.
Yeah, a lot of our tests w
12 matches
Mail list logo
