From: Phil E. <pel...@gm...> - 2013-01-17 09:43:32
|
Hi Todd, I agree with the principle of properties - it will make much of the mpl codebase (and user code) more pythonic, so thanks for proposing this. Would you be able to give an example of how you propose setters such as Axes.set_xlim might make use of properties. The particular example I have picked uses keywords to determine the behaviours of the method itself: def set_xlim(self, left=None, right=None, emit=True, auto=False, **kw): ... For me, the backwards compatibility issue is the key blocker to this MEP. Would you mind providing some concrete examples (perhaps using the set_xlim method as a focus point)? Cheers, Phil On 16 January 2013 21:00, Todd <tod...@gm...> wrote: > I have created a very preliminary MEP for the possible move to properties: > > https://github.com/matplotlib/matplotlib/wiki/MEP13 > > Please take a look at it and discuss. As I said, this is very > preliminary. Everything is subject to change. > > > ------------------------------------------------------------------------------ > Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery > and much more. Keep your Java skills current with LearnJavaNow - > 200+ hours of step-by-step video tutorials by Java experts. > SALE $49.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122612 > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > |