Re: [Python-Dev] PEP 385: pruning/reorganizing branches

2009-08-03 Thread Dirkjan Ochtman
On Tue, Aug 4, 2009 at 08:06, "Martin v. Löwis" wrote: > I use that as a branch to tell build slaves to clean out their > current checkouts. So keep-clone sounds right, assuming it is possible > to target buildslaves at either clones or branches (which, IIUC, would > be necessary anyway, since we a

Re: [Python-Dev] PEP 385: pruning/reorganizing branches

2009-08-03 Thread Martin v. Löwis
> empty: keep-clone? I use that as a branch to tell build slaves to clean out their current checkouts. So keep-clone sounds right, assuming it is possible to target buildslaves at either clones or branches (which, IIUC, would be necessary anyway, since we are using a mix of branches and clones).

[Python-Dev] PEP 385: pruning/reorganizing branches

2009-08-03 Thread Dirkjan Ochtman
So PEP 385 proposes to clean up the old branches we still have lying around in SVN. This list of branch: action items is what I've come up with to do this cleanup. Legend first: - keep-clone means we'll keep that branch in a separate clone - keep-named means we'll keep that branch as a named bran

Re: [Python-Dev] PEP 385: updating the PEP

2009-08-03 Thread Brett Cannon
On Mon, Aug 3, 2009 at 04:53, Dirkjan Ochtman wrote: > The diff below should reflect changes from the discussion we had last > time. Please review. (Some comments may be more appropriate for the > other threads I just kicked off.) > > Cheers, > > Dirkjan > > Index: pep-0385.txt >

[Python-Dev] Functionality in subprocess.Popen.terminate()

2009-08-03 Thread Eric Pruitt
In my GSoC project, I have implemented asnychronous I/O in subprocess.Popen. Since the read/write operations are asynchronous, the program may have already exited by the time one calls the asyncread function I have implemented. While it returns the data just fine, I have come across an issue with t

Re: [Python-Dev] pylinting the stdlib

2009-08-03 Thread Vincent Legoll
On Sun, Aug 2, 2009 at 6:20 PM, Mark Dickinson wrote: > On Sat, Aug 1, 2009 at 11:40 PM, Vincent Legoll > wrote: >> >> I've fed parts of the stdlib to pylint and after some filtering >> there appears to be some things that looks strange, I've >> filled a few bugs to the tracker for them. >> >> Is

Re: [Python-Dev] In late this am

2009-08-03 Thread Casey Duncan
Heh, wrong dev list 8^). Sorry for the noise. -Casey On Aug 3, 2009, at 8:47 AM, Casey Duncan wrote: Going to the Dr., will be in thereafter. -Casey ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-d

[Python-Dev] In late this am

2009-08-03 Thread Casey Duncan
Going to the Dr., will be in thereafter. -Casey ___ 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] PEP 385: updating the PEP

2009-08-03 Thread Antoine Pitrou
Hello Dirkjan, Dirkjan Ochtman ochtman.nl> writes: > > +As an optional optimization technique, I have performed a reordering pass on > +the revlogs (internal Mercurial files) resulting from the conversion. In some > +cases this results in dramatic decreases in on-disk repository size. Can you

[Python-Dev] PEP 385: the eol-type issue

2009-08-03 Thread Dirkjan Ochtman
So, I've been not-working on this, which I feel bad about. Suffice it to say the day job has required more of my time then usual for the past few weeks. I want to get back into it, so let's start by re-raising this issue, which Mark Hammond conveniently summarized below. > On 4/07/2009 2:03 PM, Ma

[Python-Dev] PEP 385: updating the PEP

2009-08-03 Thread Dirkjan Ochtman
The diff below should reflect changes from the discussion we had last time. Please review. (Some comments may be more appropriate for the other threads I just kicked off.) Cheers, Dirkjan Index: pep-0385.txt === --- pep-0385.txt