[Numpy-discussion] numpy install script changes permissions?
Charles R Harris
Fri Sep 25 11:10:28 CDT 2009
On Fri, Sep 25, 2009 at 10:09 AM, Charles R Harris <
> On Fri, Sep 25, 2009 at 9:59 AM, Chris Colbert <email@example.com>wrote:
>> for numpy and scipy, only the tests have executable permissions. It's
>> as if the tests were specifically targeted and had their permissions
>> And these are the only two python packages i've built from source and
>> installed in this manner, other i've gotten via easy_install, or in
>> the case of the enthought tool suite, I have as an svn install in my
>> home folder. The ETS install doesnt have these problems, but many of
>> the easy_installed packages are marked as executable, though they
>> could have come that way from the source....
>> On Fri, Sep 25, 2009 at 10:37 AM, Mark Sienkiewicz <firstname.lastname@example.org>
>> >> In the source build folder, all numpy test scripts have the correct
>> >> permissions and are not marked as executable,
>> >> but in the install directory
>> >> (/usr/local/lib/python2.6/dist-packages/numpy/), the test test scripts
>> >> have completely different permissions, and are all marked as
>> >> executable. Thus, nose wont run the tests.
>> > It works ok for me with python 2.5.1 on a mac and python 2.6.1 on
>> > linux. That doesn't help you, but it may be a clue at some point.
>> > Is it only the test scripts that are executable, or is it everything
>> > that gets installed?
>> > Does it affect packages other than numpy / scipy? If so, we can suspect
>> > distutils and/or ubuntu, rather than numpy.
>> > Mark S.
> What do the permissions look like in the source? In the build directory?
> What happens if you just copy a test script into the directory?
Oh, and what happens if you delete the site-packages/numpy directory first?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion