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.
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.
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.
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 )
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!
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 )
)