fixed
On Tue, Feb 8, 2011 at 14:27, Terry Reedy wrote:
>
>> +While non-committers can use named branches without issue, as a core
>> developer
>> +you should limit their use to only those branches to be used to
>> collaborate
>
> either /their/your/
> or /as a core developer you/core developers/
On Tue, Feb 8, 2011 at 05:26, Antoine Pitrou wrote:
> On Sun, 6 Feb 2011 12:13:08 -0800
> Brett Cannon wrote:
>> >
>> > We could perhaps present SVN-like "work in the working copy" workflow
>> > (without local commits), and let seasoned hg users choose other
>> > workflows they like more (they do
As a late follow-up to this thread, I still get a bunch of hits a day
on this URL (and also on www.pythonlabs.com/talks.html -- I have no
idea what popular page *that* is still linked from).
I don't suppose we can *ever* delete that link from the LICENSE file?
On Sun, Oct 11, 2009 at 1:46 PM, Geo
On Tue, Feb 8, 2011 at 11:00 AM, R. David Murray wrote:
> There are some ResourceWarnings we haven't cured yet (the ResourceWarning is
> a fairly new innovation). I'm not sure why they don't show up when
> you run the tests individually.
Almost certainly the missing "-uall" meant the relevant te
On Sun, 6 Feb 2011 12:13:08 -0800
Brett Cannon wrote:
> >
> > We could perhaps present SVN-like "work in the working copy" workflow
> > (without local commits), and let seasoned hg users choose other
> > workflows they like more (they don't need our help anyway).
>
> I would rather give people so
Wesley Mesquita wrote:
> Hi all,
>
> I starting to explore python 3k core development environment. So, sorry in
> advance for any mistakes, but I really don't know what is the best list to
> post this, since it not a "use of python" issue, and probably is not a dev
> issue, it is more like a "dev