Hi,
It looks like the matplotlib-py3 branch is worknig well both with python2.X and python3.X.
Is there a plan to merge the changes from matplotlib-py3 into the default trunk anytime soon?
Xavier
This was recently discussed in the thread "v1.0.x branch seems confused."
I (believe) the consensus was to get out another v1.0.x maintenance release out in the near future (which would not support py3k, but would still support Python 2.4), and then merge the py3 branch into master so it starts to get some more testing before making the next major release.
I'm just today merging master into py3 so that when we are ready to do the merge the other way most of the hard work will have already been done.
Mike
···
On 06/13/2011 10:39 AM, Xavier Gnata wrote:
Hi,
It looks like the matplotlib-py3 branch is worknig well both with
python2.X and python3.X.
Is there a plan to merge the changes from matplotlib-py3 into the
default trunk anytime soon?Xavier
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
matplotlib-users List Signup and Options
--
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA
Are there features already in master that should be supported by
<python-2.6? If so, I think we should consider releasing 1.1.0 and
making a 1.1.x maintenance branch before merging the py3 stuff back
into master. Then mpl-1.2 could be the first to support py3.
Should we move this discussion to the mpl-dev mailing list?
Darren
···
On Mon, Jun 13, 2011 at 12:25 PM, Michael Droettboom <mdroe@...86...> wrote:
This was recently discussed in the thread "v1.0.x branch seems confused."
I (believe) the consensus was to get out another v1.0.x maintenance
release out in the near future (which would not support py3k, but would
still support Python 2.4), and then merge the py3 branch into master so
it starts to get some more testing before making the next major release.I'm just today merging master into py3 so that when we are ready to do
the merge the other way most of the hard work will have already been done.
Ho I wasn't aware of an mpl-dev mailing list. Sorry.
py3 is already ok with python3 *and* python2 isn't it?
Maybe the website should advertise a bit on the needs to test the py3 branch.
Users used to compile mpl from git should be able to produce valuable technical feedback, shoudn't they?
Xavier
···
On 06/13/2011 07:38 PM, Darren Dale wrote:
On Mon, Jun 13, 2011 at 12:25 PM, Michael Droettboom<mdroe@...86...> wrote:
This was recently discussed in the thread "v1.0.x branch seems confused."
I (believe) the consensus was to get out another v1.0.x maintenance
release out in the near future (which would not support py3k, but would
still support Python 2.4), and then merge the py3 branch into master so
it starts to get some more testing before making the next major release.I'm just today merging master into py3 so that when we are ready to do
the merge the other way most of the hard work will have already been done.Are there features already in master that should be supported by
<python-2.6? If so, I think we should consider releasing 1.1.0 and
making a 1.1.x maintenance branch before merging the py3 stuff back
into master. Then mpl-1.2 could be the first to support py3.Should we move this discussion to the mpl-dev mailing list?
Darren