matplotlib-devel Mailing List for matplotlib

On 2014/10/26, 4:52 AM, Thomas Caswell wrote:
> https://github.com/HamsterHuey/easyplot?utm_content=buffer48700&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer
>
> I have not looked at it carefully, but it is something we might want to
> be aware of when thinking about API re-designs.

Yes, this is well worth keeping in mind.  It looks like there are some 
very good ideas here.

Eric

>
> Tom
>
> --
> Thomas Caswell
> tca...@gm... <mailto:tca...@gm...>
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Andy,

The issue of the axes frame corners _should_ be fixed in 1.4

The user mailing list is still a going concern, the SF archives are just
broken.  They know (and the archive pages are _less_ broken than they used
to be), but have not fixed it yet.

Tom

On Sun, Oct 26, 2014 at 11:50 AM, Andy Buckley <an...@in...>
wrote:

> Hi all,
>
> I have a question/request about improving a minor aspect of plot
> cosmetics, namely that axis spines seem to be rendered as 4 individual
> lines, meaning that the corners of the axes boundary do not match up
> with a neat corner but have a "stair" appearance. I've attached a
> screenshot from a zoomed PDF showing this effect, made with MPL 1.3.1
> from Ubuntu 14.04... so apologies if it's already fixed in the latest
> 1.4.x versions. This effect is also visible in PNG output, as just a
> couple of pixels in the corners that look "ragged". Would it be possible
> to tidy this up... or point me to where in the code this rendering is
> done, if it's something easy that I could maybe help with?
>
> At the same time, I note in this zoom that the axis is showing tick
> marks at the very end(s) of the axis, where they overlap with the other
> axis/plot boundary line: is there an automatic way to elide tick marks
> in that redundant position?
>
> Apologies if this isn't a good place for these queries/requests -- I had
> a look at the matplotlib-user and -announce list archives linked from
> the web page and they seem to have gone defunct in 2012, hence coming
> here. I am happy to do a bit of development to address little cosmetic
> tweaks like this, but am not yet familiar with MPL internals.
>
> Thanks!
> Andy
>
> PS. I also have a question about how to enable old-style figures in a
> font when using the TeX/PGF rendering backed, cf.
> \usepackage[osf]{mathpazo}, but I'll wait to see if this is an
> appropriate place for such questions before troubling you with that!
>
> --
> Dr Andy Buckley, Royal Society University Research Fellow
> Particle Physics Expt Group, University of Glasgow / PH Dept, CERN
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>


-- 
Thomas Caswell
tca...@gm...

Hi all,

I have a question/request about improving a minor aspect of plot
cosmetics, namely that axis spines seem to be rendered as 4 individual
lines, meaning that the corners of the axes boundary do not match up
with a neat corner but have a "stair" appearance. I've attached a
screenshot from a zoomed PDF showing this effect, made with MPL 1.3.1
from Ubuntu 14.04... so apologies if it's already fixed in the latest
1.4.x versions. This effect is also visible in PNG output, as just a
couple of pixels in the corners that look "ragged". Would it be possible
to tidy this up... or point me to where in the code this rendering is
done, if it's something easy that I could maybe help with?

At the same time, I note in this zoom that the axis is showing tick
marks at the very end(s) of the axis, where they overlap with the other
axis/plot boundary line: is there an automatic way to elide tick marks
in that redundant position?

Apologies if this isn't a good place for these queries/requests -- I had
a look at the matplotlib-user and -announce list archives linked from
the web page and they seem to have gone defunct in 2012, hence coming
here. I am happy to do a bit of development to address little cosmetic
tweaks like this, but am not yet familiar with MPL internals.

Thanks!
Andy

PS. I also have a question about how to enable old-style figures in a
font when using the TeX/PGF rendering backed, cf.
\usepackage[osf]{mathpazo}, but I'll wait to see if this is an
appropriate place for such questions before troubling you with that!

-- 
Dr Andy Buckley, Royal Society University Research Fellow
Particle Physics Expt Group, University of Glasgow / PH Dept, CERN

https://github.com/HamsterHuey/easyplot?utm_content=buffer48700&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer

I have not looked at it carefully, but it is something we might want to be
aware of when thinking about API re-designs.

Tom

-- 
Thomas Caswell
tca...@gm...

Sorry - I accidentally sent this reply just to Nathaniel - returning
to this as it bit me again:

On 7/14/14, Nathaniel Smith <nj...@po...> wrote:
> Wouldn't a better default be to just close all figures when they're
> displayed? It can't be common that someone wants to show the same plot
> repeatedly (and if they do that could have an option)...?

Yes, I think that would be a better default.

You mean that if :context: is true, then always do something like
``plt.close('all')`` before running the relevant code and looking for
figures.

It would change the current behavior, but I agree that would be better.

Anyone disagree?

If not, I will make a pull request to change the behavior...

Cheers,

Matthew

Hot on the tails of v1.4.1, we have a v1.4.2 due to an error in the boxplot
api in pyplot.py

The only changes between 1.4.1 and 1.4.2 are:

 - corrected boxplot in pyplot.py
 - added extra paths to default search paths for freetype

Tom

-- 
Thomas Caswell
tca...@gm...