matplotlib v2.0.0b1

Folks,

We tagged the first beta for v2.0.0 tonight. Please check out the new
defaults!

This is tagged as a beta because we anticipate a longer than normal release
cycle. The style changes are substantial and we want to make sure that we
have not crippled any common use cases. The target for the final release
around scipy.

A build of the docs is available at http://matplotlib.org/2.0.0b1

Preview conda packages are available via

conda install -c conda-forge/label/rc -c conda-forge matplotlib

pre-release packages should be on pypi tomorrow.

Brief release notes:

This previews the new default style and many bug-fixes. A full list of
the style changes will be collected for the final release.

In addition to the style change this release includes:
- overhaul of font handling/text rendering to be faster and clearer
- many new rcParams
- Agg based OSX backend
- optionally deterministic SVGs
- complete re-write of image handling code
- simplified color conversion
- specify colors in the global property cycle via `'C0'`,
   `'C1'`... `'C9'`
- use the global property cycle more places (bar, stem, scatter)

There is a 'classic' style sheet which reproduces the 1.Y defaults:

   import matplotlib.style as mstyle
   mstyle.use('classic')

A big thank you to everyone who worked on this release.

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160531/acff5c0b/attachment.html>

Thomas Caswell wrote:

conda install -c conda-forge/label/rc -c conda-forge matplotlib

seems to work.

Where can I find info on new features/changelog?
http://matplotlib.org/2.0.0b1/users/whats_new.html
Does not seem to be updated

The full release notes have not been compiled yet.

https://github.com/matplotlib/matplotlib/tree/v2.x/doc/users/whats_new is
the components that will go into it.

For the style changes, look a a diff of rcsetup.py from 1.5.1 -> 2.0.0b1

Tom

···

On Tue, May 31, 2016 at 7:13 AM Neal Becker <ndbecker2 at gmail.com> wrote:

Thomas Caswell wrote:

> conda install -c conda-forge/label/rc -c conda-forge matplotlib

seems to work.

Where can I find info on new features/changelog?
http://matplotlib.org/2.0.0b1/users/whats_new.html
Does not seem to be updated

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160531/d21d2187/attachment-0001.html>

You should now be able to get this release on OSX or Linux with:

python -m pip install --upgrade pip # upgrade pip to latest
pip install --pre matplotlib

Cheers,

Matthew

···

On Mon, May 30, 2016 at 9:01 PM, Thomas Caswell <tcaswell at gmail.com> wrote:

Folks,

We tagged the first beta for v2.0.0 tonight. Please check out the new
defaults!

This is tagged as a beta because we anticipate a longer than normal release
cycle. The style changes are substantial and we want to make sure that we
have not crippled any common use cases. The target for the final release
around scipy.

python -m pip install --upgrade pip # upgrade pip to latest
pip install --pre matplotlib

Should now work on all platforms.

Tom

···

On Tue, May 31, 2016 at 6:31 PM Skip Montanaro <skip at pobox.com> wrote:

> A build of the docs is available at http://matplotlib.org/2.0.0b1

Thanks. Is there a "What's New" page in the docs? Or maybe an upgrade
guide which identifies incompatibilities with 1.5?

Skip Montanaro
who still remembers John Hunter's interview presentation at TradeLink,
lo these many years ago...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160531/03810045/attachment.html>

Nice! sorry to arrive late at the party, but do you already have an
idea of how the distributions should handle the migration to the new
version? should we keep both 1.x and 2.x available or migrate to 2.x
as if it was "just" a new version (the latter is my preferred
solution)?

As for Debian, for now I will plan to keep 1.5.x in unstable, and
upload 2.x to experimental, but targetting to include 2.x in the next
stable release (we are still months away from the freeze, but time
flies :slight_smile: )

let me know of any suggestions/concerns

Cheers,

···

On Tue, May 31, 2016 at 5:01 AM, Thomas Caswell <tcaswell at gmail.com> wrote:

We tagged the first beta for v2.0.0 tonight. Please check out the new
defaults!

--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

I think that distributions should just adopt 2.0 as the next version.
There are no more functionality breaks than in a typical minor release.

Tom

···

On Sat, Jun 11, 2016, 15:12 Sandro Tosi <morph at debian.org> wrote:

On Tue, May 31, 2016 at 5:01 AM, Thomas Caswell <tcaswell at gmail.com> > wrote:
> We tagged the first beta for v2.0.0 tonight. Please check out the new
> defaults!

Nice! sorry to arrive late at the party, but do you already have an
idea of how the distributions should handle the migration to the new
version? should we keep both 1.x and 2.x available or migrate to 2.x
as if it was "just" a new version (the latter is my preferred
solution)?

As for Debian, for now I will plan to keep 1.5.x in unstable, and
upload 2.x to experimental, but targetting to include 2.x in the next
stable release (we are still months away from the freeze, but time
flies :slight_smile: )

let me know of any suggestions/concerns

Cheers,
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160612/ad0ffa70/attachment.html>