On Mon, Mar 30, 2009 at 2:13 AM, Reinier Heeres <rein...@heeres.eu> wrote:
>
> That sounds good. I assume you mean adding it to lib/mpl_toolkits in
> the matplotlib source? It would be great to do this soon.
>
> I also tried to create a separate mpl_toolkit installer with
> setuptools, but can't get that to work properly:
>
> In [2]: import mpl_toolkits.mplot3d
> /usr/lib/python2.5/site-packages/mpl_toolkits/__init__.py:2:
> UserWarning: Module mpl_toolkits was already imported from
> /usr/lib/python2.5/site-packages/mpl_toolkits/__init__.pyc, but
> /usr/lib/python2.5/site-packages/mplot3d-0.1-py2.5.egg is being added
> to sys.path
> __import__('pkg_resources').declare_namespace(__name__)
>
> This can probably be fixed, but I would prefer things to live in the
> matplotlib tree, and I'm willing to volunteer to support it.
>
Since this is pure python, my plan was to put it in the mpl source tree in
mpl_toolkits so that it gets included in all mpl installs, rather than
distribute it separately. This might put some additional burden on you
since we still use svn, but we have some notes on developing mpl via git
with a git/svn gateway
http://matplotlib.sourceforge.net/devel/coding_guide.html#id3
Have you done any work on bringing it up to compatibility with svn HEAD?
I'd like at least the basic demos to work with svn HEAD before I do the
import. I think the major missing piece there is the missing TextWithDash.
Thanks,
JDH
------------------------------------------------------------------------------
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
