On Fri, Oct 28, 2011 at 12:50 PM, Michael Droettboom <md...@stsci.edu>wrote:
> Now that we have 1.1.0 out, I was thinking maybe now is the time to
> merge the matplotlib-py3 branch into master. As a reminder, the main
> downside is losing compatibility with Python 2.5 and earlier. We would
> continue to have a 1.1.x maintenance branch for the foreseeable future
> for small-yet-critical bugfixes, and can still make a Python
> 2.5-compatible bugfix release from that.
>
> Any objections or concerns? Any reason to hold off?
>
> Mike
>
>
I guess it would be fine to start doing that. Are there any recommended
guides for preparing for the transition to py3k. I haven't begun to look
into that and have only been using 2.6 and 2.7 for a while now.
Ben Root
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
