[Numpy-discussion] arrayobject.h (and friends) install location
strawman at astraw.com
Tue Jan 17 09:30:14 CST 2006
The main advantage of the current situation for me is that it's easy to
use with .eggs (for the reasons given). The symlink idea won't break
this, but the "let's make it like it was" solution would break it (which
was why it was changed). Can anyone think of a solution that would
please both the old-way-preferers and the .egg users?
Also, as for as I know, the only packages that install things into
/usr/include/python2.x/packagename are Numeric and numarray, so I would
argue it's not "standard", (although it may have lots of history).
>My main concern is not with the non-standard default location, but
>with the way distutils are tricked into placing headers into that
>location. Currently this is done by mislabeling the header files as
>"data files" in setup.py as follows:
>This looks like a hack that just happens to work on platforms where
>headers do not require any special treatement such as end-of-line
>conversion or pre-compilation. This is not guaranteed to work on every
>python platform now and may certainly break in the future.
>On 1/17/06, Robert Hetland <hetland at tamu.edu> wrote:
>>On Jan 17, 2006, at 9:08 AM, konrad.hinsen at laposte.net wrote:
>>What good is that symlink if no one can rely on its presence?
>>I think putting the include files in a non-standard place should be the
>>exception, rather than the rule. The standard install should behave itself,
>>and put things in the right place.
>>Rob Hetland, Assistant Professor
>>Dept of Oceanography, Texas A&M University
>>p: 979-458-0096, f: 979-845-6331
>>e: hetland at tamu.edu, w: http://pong.tamu.edu
>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!
>Numpy-discussion mailing list
>Numpy-discussion at lists.sourceforge.net
More information about the Numpy-discussion