During my investigation for MEP29 I have noticed in the docs (of
figure.py) that:
> (For backward compatibility, ``polar=True`` may also be provided,
which is equivalent to ``projection='polar'``).
But all the polar examples use ``polar=True``, so perhaps we should
change the examples to match our current preference (aka
``projection='polar'``)? I say perhaps, because I do feel torn about
this, because I *may* want to change this again with MEP29 assuming it
gets accepted once I have finished writing it.
I guess I err on updating the examples now because it doesn't hurt, and
updating them again later if/when we change stuff.
Shall I just make a PR of this now? Can it still make 1.5? Would we
have to backport it, or will it go straight it?
Best,
OceanWolf
Docs can always be updated. +1
ยทยทยท
On Fri, Sep 18, 2015 at 6:58 PM, OceanWolf <juichenieder-nabb at yahoo.co.uk> wrote:
During my investigation for MEP29 I have noticed in the docs (of
figure.py) that:
> (For backward compatibility, ``polar=True`` may also be provided, which
is equivalent to ``projection='polar'``).
But all the polar examples use ``polar=True``, so perhaps we should change
the examples to match our current preference (aka ``projection='polar'``)?
I say perhaps, because I do feel torn about this, because I *may* want to
change this again with MEP29 assuming it gets accepted once I have finished
writing it.
I guess I err on updating the examples now because it doesn't hurt, and
updating them again later if/when we change stuff.
Shall I just make a PR of this now? Can it still make 1.5? Would we have
to backport it, or will it go straight it?
Best,
OceanWolf
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
Matplotlib-devel Info Page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20150921/8707c4a6/attachment.html>