matplotlib-devel Mailing List for matplotlib

Hi all,

I wanted to let the community know that we are currently hiring 3 full time
software engineers to work full time on Project Jupyter/IPython. These
positions will be in my group at Cal Poly in San Luis Obispo, CA. We are
looking for frontend and backend software engineers with lots of
Python/JavaScript experience and a passion for open source software. The
details can be found here:

https://www.calpolycorporationjobs.org/postings/736

This is an unusual opportunity in a couple of respects:

* These positions will allow you to work on open source software full time
- not as a X% side project (aka weekends and evenings).
* These are fully benefited positions (CA state retirement, health care,
etc.)
* You will get to work and live in San Luis Obispo, one of the nicest
places on earth. We are minutes from the beach, have perfect year-round
weather and are close to both the Bay Area and So Cal.

I am more than willing to talk to any who interested in these positions.

Cheers,

Brian

-- 
Brian E. Granger
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgr...@ca... and ell...@gm...

I think that so long as you maintain the mapping of 'manager' to be 'gui
element holding the Figure' (rather than 'gui window holding figure')
numbering the managers should be ok.   That is, the tabs are the managers
and the multi-figure windows are a layer above the managers.

The notion of 'figure number' is very thoroughly a pyplot/figure manager
idea I am -1 on pushing that logic down in to the Figure class.

Tom

On Wed, May 6, 2015 at 4:42 PM Eric Firing <ef...@ha...> wrote:

> On 2015/05/06 9:19 AM, Federico Ariza wrote:
> > Hello
> >
> > Is there any reason why the "num" property is assigned to the manager
> > and not to the figure?
>
> I think this is because the figure is at the object-oriented API level.
>   The manager is in the pyplot state-machine level.
>
> > Pyplot.gcf is to get the "current figure" not the "current manager".
>
> It is really "get current managed figure", combined with the original
> idea that the manager is the pyplot layer on top of the figure, with one
> manager per figure.  The "current" concept comes from the state machine.
>
> >
> > In general this is not a problem. But I'm working on MEP23 where one
> > manager can contain several figures. And it would be pretty nice if I
> > could reference the figures by that number not the managers.
> >
> > A priori, do you see any problem with a PR changing that?
>
> It seems like it could work--but what will it do to existing user code?
>
> Eric
>
> >
> > Thanks
> > Federico
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > One dashboard for servers and applications across Physical-Virtual-Cloud
> > Widest out-of-the-box monitoring support with 50+ applications
> > Performance metrics, stats and reports that give you Actionable Insights
> > Deep dive visibility with transaction tracing using APM Insight.
> > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> >
> >
> >
> > _______________________________________________
> > Matplotlib-devel mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>