[SciPy-dev] problems with numpy.setuptools("single_version_externally_managed")

David M. Cooke cookedm@physics.mcmaster...
Tue Sep 25 10:43:58 CDT 2007


"Pearu Peterson" <pearu@cens.ioc.ee> writes:
> On Tue, September 25, 2007 5:57 pm, David M. Cooke wrote:
>>
>> $ python setupegg.py bdist_egg
>> Running from numpy source directory.
>> ********************************************************
>> WARNING!WARNING!WARNING!WARNING!WARNING!WARNING!WARNING!
>> [etc.]
>
>
> This is a warning message. It does not break code.

When a supported method of building throws up a huge warning, I
consider that broken ;-)

>> I *think* (and I'll fix any bugs that don't correspond to this ;-)
>> that importing numpy.distutils after distutils is ok, as long as
>> you're not doing anything 'odd'.
>
> I am just trying to ensure that numpy/scipy build on all
> platforms we can support. The questions is which one is
> more important: to support setuptools or to make the build
> work on more platforms? In the given case Windows with MS Visual
> compiler.
>
> Ok, then we have a problem. Details follow below.
>
> So, if distutils is imported before numpy.distutils then
>
>   distutils.ccompiler.gen_lib_options = <our gen_lib_options>
>
> is not effective as distutils/msvccompiler.py does
>
>   from distutils.ccompiler import gen_lib_options
>
> so that the code in msvccompiler.py would still use the old
> distutils gen_lib_options function.

Fixed that for you. See r4134.

-- 
|>|\/|<
/------------------------------------------------------------------\
|David M. Cooke              http://arbutus.physics.mcmaster.ca/dmc/
|cookedm@physics.mcmaster.ca


More information about the Scipy-dev mailing list