matplotlib-devel Mailing List for matplotlib

I plotted a large number of bars on a bargraph. I am not surprised memory usage 
and time to draw are bad on the initial view. But I'd expect as I zoom in more 
and more, the time to draw should improve - there's less to draw.
This does not appear to be the case.
-- 
-- Those who don't understand recursion are doomed to repeat it

Thanks again Thomas for the release !
Cheers,
N
On 17 February 2015 at 06:09, Thomas Caswell <tca...@gm...> wrote:
> Hello all,
>
> We are pleased to announce the release of matplotlib v1.4.3!
>
> Wheels, windows binaries and the source tarball are available through both
> source-forge [1] and pypi (via pip). Additionally the source is available
> tarball is available from github [2] and mac-wheels from
> http://wheels.scikit-image.org/.
>
> This is the last planned bug-fix release in the 1.4 series.
>
> Many bugs are fixed including:
>
> fixing drawing of edge-only markers in AGG
> fix run-away memory usage when using %inline or saving with a tight bounding
> box with QuadMesh artists
> improvements to wx and tk gui backends
>
> Additionally the webagg and nbagg backends were brought closer to
> feature parity with the desktop backends with the addition of keyboard
> and scroll events thanks to Steven Silvester.
>
> The next planned release will be based on the 1.4.x series but will change
> the default colors and be tagged as version v2.0. The target release date is
> in the next month or two.
>
> The next feature release will be v2.1 targeted for around SciPy in July.
>
> Tom
>
>
> [1]
> https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.4.3/
>
> [2] https://github.com/matplotlib/matplotlib/releases/tag/v1.4.3
>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

I wasn't referring to just the default colors, but the default style in
general. Things like background, line thickness, padding, ticks, etc. I
thought that there was agreement that the default matplotlib style is not
optimal, and that the point of the 2.0 release was to put all the
stylistic changes in one release so people don't have to keep changing
their unit tests.
On Feb 8, 2015 11:04 PM, "Thomas Caswell" <tca...@gm...> wrote:
>
> To overhauling all of the default colors, I think that is still in the
cards, but some one who is not me needs to drive that.
>
> The goal of pulling pyplot out of backend_bases is exactly that, to be
able to do everything using the OO interface in a convenient way.
>
> Tom
>
> On Sun Feb 08 2015 at 4:50:51 PM Todd <tod...@gm...> wrote:
>>
>>
>> On Feb 8, 2015 1:13 AM, "Thomas Caswell" <tca...@gm...> wrote:
>> >
>> > Hey all,
>> >
>> > To start with, the 2.0 release is pending a choice of new default
color map. I think that when we pick that we should cut 2.0 off of the
last release and then the next minor release turns into 2.1. If we want to
do other breaking changes we will just do a 3.0 when that happens. It
makes sense to me to bundle default color changes as one set of breaking
changes and code API changes as another.
>>
>> I thought there was going to be a complete overhaul of the default
theme? Has that idea been abandoned?
>>
>> > - making OO interface easier to use interactively (if interactive,
auto-redraw at sensible time)
>> >
>> > - pull the pyplot state machine out of backend_bases and expose the
figure_manager classes
>>
>> Do either of these mean that it will be possible to use the OO interface
without needing to go through pyplot?
>>
>>
------------------------------------------------------------------------------
>>
>> Dive into the World of Parallel Programming. The Go Parallel Website,
>> sponsored by Intel and developed in partnership with Slashdot Media, is
your
>> hub for all things parallel software development, from weekly thought
>> leadership blogs to news, videos, case studies, tutorials and more. Take
a
>> look and join the conversation now.
http://goparallel.sourceforge.net/_______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Do remember that I have a PR to add linestyle cycling, which would greatly
mitigate problems for colorblindness and non-color publications.
I also prefer it for slideshows as projectors at conferences tend to have
crappy colors anyway (was at a radar conference when the projector's red
crapped out while the presenter was building up suspense about the really,
really impressive radar image of a supercell on the next slide)
Ben Root
On Feb 16, 2015 7:24 PM, "Michael Waskom" <mw...@st...> wrote:
> See [here](http://nbviewer.ipython.org/gist/mwaskom/6a43a3b94eca4a9e2e8b)
> for a quick and dirty implementation that should get a general idea. This
> probably ins't the best way to do it -- anyone should feel free to build on
> this.
>
> On Mon, Feb 16, 2015 at 3:38 PM, Eric Firing <ef...@ha...> wrote:
>
>> On 2015年02月16日 1:29 PM, Michael Waskom wrote:
>>
>> Nathaniel's January 9 message in that thread (can't figure out how to
>>> link to it in the archives) had a suggestion that I thought was very
>>> promising, to do something similar to Parula but rotate around the hue
>>> circle the other direction so that the hues would go blue - purple - red
>>> - yellow. I don't think we've seen an example of exactly what it would
>>> look like, but I reckon it would be similar to the middle colormap here
>>> http://earthobservatory.nasa.gov/blogs/elegantfigures/
>>> files/2013/08/three_perceptual_palettes_618.png
>>> (from the elegant figures block series linked above), which I've always
>>> found quite attractive.
>>>
>>
>> Certainly it can be considered--but we have to have a real implementation.
>>
>>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Hello all,
We are pleased to announce the release of matplotlib v1.4.3!
Wheels, windows binaries and the source tarball are available through both
source-forge [1] and pypi (via pip). Additionally the source is available
tarball is available from github [2] and mac-wheels from
http://wheels.scikit-image.org/.
This is the last planned bug-fix release in the 1.4 series.
Many bugs are fixed including:
 - fixing drawing of edge-only markers in AGG
 - fix run-away memory usage when using %inline or saving with a tight
 bounding box with QuadMesh artists
 - improvements to wx and tk gui backends
Additionally the webagg and nbagg backends were brought closer to
feature parity with the desktop backends with the addition of keyboard
and scroll events thanks to Steven Silvester.
The next planned release will be based on the 1.4.x series but will change
the default colors and be tagged as version v2.0. The target release date
is in the next month or two.
The next feature release will be v2.1 targeted for around SciPy in July.
Tom
[1]
https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.4.3/
[2] https://github.com/matplotlib/matplotlib/releases/tag/v1.4.3

See [here](http://nbviewer.ipython.org/gist/mwaskom/6a43a3b94eca4a9e2e8b)
for a quick and dirty implementation that should get a general idea. This
probably ins't the best way to do it -- anyone should feel free to build on
this.
On Mon, Feb 16, 2015 at 3:38 PM, Eric Firing <ef...@ha...> wrote:
> On 2015年02月16日 1:29 PM, Michael Waskom wrote:
>
> Nathaniel's January 9 message in that thread (can't figure out how to
>> link to it in the archives) had a suggestion that I thought was very
>> promising, to do something similar to Parula but rotate around the hue
>> circle the other direction so that the hues would go blue - purple - red
>> - yellow. I don't think we've seen an example of exactly what it would
>> look like, but I reckon it would be similar to the middle colormap here
>> http://earthobservatory.nasa.gov/blogs/elegantfigures/
>> files/2013/08/three_perceptual_palettes_618.png
>> (from the elegant figures block series linked above), which I've always
>> found quite attractive.
>>
>
> Certainly it can be considered--but we have to have a real implementation.
>
>