Eggs and toolkits

Hi folks,

I recently installed setuptools, and now whenever I build mpl
(I'm using 0.86), it gets installed in site-packages as an egg.
Fine, as far as use within python is concerned it works just
as before. But I just tried to install basemap, and the
installer puts it in site-packages in a new matplotlib directory
(i.e., not in the matplotlib...egg directory). If I try
to use it, I get an import error because it's not found
in the egg (which must the first place Python finds mpl).

How can I properly install an mpl toolkit in the egg scenario;
or if there is no easy way, how can I "turn off" eggs so when
I build mpl it makes a normal install. Just deleting the
build directory (and the egg from site-packages) and rebuilding
from scratch didn't do it.

Thanks,
Tom

···

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

We haven't put support in yet, but it is very easy to do. I will add
this to cvs very soon. For now:

Edit basemap's setup.py and replace "from distutils.core import setup"
with "from setuptools import setup".

In BOTH mpl's and basemap's setup.py file add this option to the setup
method, "namespace_packages = 'matplotlib.toolkits'".

Both mpl and basemap should be installed as eggs. The namespace is
how setuptools know separate packages share... a namespace.

Let us know if you run into problems.

- Charlie

···

On 1/18/06, Tom Loredo <loredo@...477...> wrote:

Hi folks,

I recently installed setuptools, and now whenever I build mpl
(I'm using 0.86), it gets installed in site-packages as an egg.
Fine, as far as use within python is concerned it works just
as before. But I just tried to install basemap, and the
installer puts it in site-packages in a new matplotlib directory
(i.e., not in the matplotlib...egg directory). If I try
to use it, I get an import error because it's not found
in the egg (which must the first place Python finds mpl).

How can I properly install an mpl toolkit in the egg scenario;
or if there is no easy way, how can I "turn off" eggs so when
I build mpl it makes a normal install. Just deleting the
build directory (and the egg from site-packages) and rebuilding
from scratch didn't do it.

Thanks,
Tom

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

This problem was more complicated than originally thought, but it is
working in cvs now. I updated basemap and matplotlib to express the
shared namespace matplotlib.toolkits. Now you should be able to use
matplotlib and basemap as separate eggs and all should work as
expected.

···

On 1/18/06, Charlie Moad <cwmoad@...287...> wrote:

We haven't put support in yet, but it is very easy to do. I will add
this to cvs very soon. For now:

Edit basemap's setup.py and replace "from distutils.core import setup"
with "from setuptools import setup".

In BOTH mpl's and basemap's setup.py file add this option to the setup
method, "namespace_packages = 'matplotlib.toolkits'".

Both mpl and basemap should be installed as eggs. The namespace is
how setuptools know separate packages share... a namespace.

Let us know if you run into problems.

- Charlie

On 1/18/06, Tom Loredo <loredo@...477...> wrote:
>
> Hi folks,
>
> I recently installed setuptools, and now whenever I build mpl
> (I'm using 0.86), it gets installed in site-packages as an egg.
> Fine, as far as use within python is concerned it works just
> as before. But I just tried to install basemap, and the
> installer puts it in site-packages in a new matplotlib directory
> (i.e., not in the matplotlib...egg directory). If I try
> to use it, I get an import error because it's not found
> in the egg (which must the first place Python finds mpl).
>
> How can I properly install an mpl toolkit in the egg scenario;
> or if there is no easy way, how can I "turn off" eggs so when
> I build mpl it makes a normal install. Just deleting the
> build directory (and the egg from site-packages) and rebuilding
> from scratch didn't do it.
>
> Thanks,
> Tom
>
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Matplotlib-users mailing list
> Matplotlib-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>