[matplotlib-devel] Python 3.3 released

2012-09-29 Thread Damon McDougall
I've just read that Python 3.3 has been released and thought I would initiate a discussion oriented around adoption and possible benefits/problems. It appears that, at least for the Mac, there are issues with certain versions of ActiveTcl

Re: [matplotlib-devel] Python 3.3 released

2012-09-29 Thread Christoph Gohlke
On 9/29/2012 9:48 AM, Damon McDougall wrote: > I've just read that Python 3.3 has been > released and thought I > would initiate a discussion oriented around adoption and possible > benefits/problems. It appears that, at least for the Mac, there are > iss

Re: [matplotlib-devel] Python 3.3 released

2012-09-29 Thread Benjamin Root
On Saturday, September 29, 2012, Christoph Gohlke wrote: > On 9/29/2012 9:48 AM, Damon McDougall wrote: > > I've just read that Python 3.3 has been > > released and thought I > > would initiate a discussion oriented around adoption and possible > > benef

[matplotlib-devel] Fwd: Python 3.3 released

2012-09-29 Thread Damon McDougall
Forgot to reply all. -- Forwarded message -- From: Damon McDougall Date: Sat, Sep 29, 2012 at 8:51 PM Subject: Re: [matplotlib-devel] Python 3.3 released To: Benjamin Root On Sat, Sep 29, 2012 at 6:46 PM, Benjamin Root wrote: > > > On Saturday, September 29, 2012, Christoph G

[matplotlib-devel] branch merge strategy

2012-09-29 Thread Eric Firing
Mike, I'm getting confused about branch merge strategy. Usually, it seems that it has been to periodically merge the maintenance branch into master. Something like this: git fetch upstream git checkout master git merge --ff-only upstream/master git merge upstream/v1.2.x # test, commit changes