Re: [matplotlib-devel] MPL w/package_data

[Andrew S. <str...@as...>]

Charlie Moad wrote:

>On 1/26/06, Charlie Moad <cw...@gm...> wrote:
>  
>
>>On 1/26/06, Nadezhda Dencheva <den...@st...> wrote:
>>    
>>
>>>What's wrong with Pete Shinners's smart_istall_data?
>>>I am thinking of using it in all our packages, so
>>>if someone knows of any drawbacks I'd like to hear
>>>about this.
>>>      
>>>
>>Um wow, absolutely no problems as far as I can tell.  We don't even
>>have to shuffle around folders in cvs.  Thanks for forcing me to try
>>this! ;)
>>
>>After some more testing I will commit this simple fix.
>>    
>>
>
>Committed.  Please test.  This REALLY cleans up the setup.py file. 
>Should hopefully address the building non-eggs with setuptools issue.
>
>  
>
Charlie, it works for me. Here's an idea which will mean setuptools
isn't imported by setup.py, even for those who have setuptools installed
but don't want to use it. (I guess there might be some.)

The downside is that to use setuptools, you'd have to do some thing like:

python -c "import setuptools; execfile('setup.py')" bdist_egg
or
python -c "import setuptools; execfile('setup.py')" install

(I think "easy_install ." is also supposed to work, but it looks I've
got a few poorly-behaving modules installed...)

I'm myself not 100% sure we want to use this patch, but I think perhaps
it's better -- people who happen to have setuptools installed don't get
setuptools-built packages unless they ask for them.

Thanks for your work on this,
Andrew