when I build numpy from source via: python setup.py build sudo python setup.py install the nosetests fail because of permissions: In [5]: np.test() Running unit tests for numpy NumPy version 1.3.0 NumPy is installed in /usr/local/lib/python2.6/dist-packages/numpy Python version 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) [GCC 4.3.3] nose version 0.10.4 ---------------------------------------------------------------------- Ran 0 tests in 0.007s OK Out[5]: <nose.result.TextTestResult run=0 errors=0 failures=0> The problem I'm running into is I can't do a blanket chmod 664 *.py on the numpy directory because that breaks things. And since I don't which files are nosetests, it's very difficult to change by hand. Is there a workaround for this, or would it more appropriate for the numpy build script to set the permissions of the test file accordingly? Cheers, Chris
On Thu, Aug 20, 2009 at 13:52, Chris Colbert<sccolbert@gmail.com> wrote:
when I build numpy from source via:
python setup.py build sudo python setup.py install
the nosetests fail because of permissions:
What permissions do your files have? If they're not readable for whatever reason, you would be SOL no matter what. The only fixable issue I am aware of is that nosetests does not like to collect tests in executable files (nose 0.11 has an option to permit that). However, I don't know why such a standard installation would do either of those things. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
On Thu, Aug 20, 2009 at 1:52 PM, Chris Colbert<sccolbert@gmail.com> wrote:
when I build numpy from source via:
python setup.py build sudo python setup.py install
the nosetests fail because of permissions:
In [5]: np.test() Running unit tests for numpy NumPy version 1.3.0 NumPy is installed in /usr/local/lib/python2.6/dist-packages/numpy Python version 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) [GCC 4.3.3] nose version 0.10.4
---------------------------------------------------------------------- Ran 0 tests in 0.007s
OK Out[5]: <nose.result.TextTestResult run=0 errors=0 failures=0>
The problem I'm running into is I can't do a blanket chmod 664 *.py on the numpy directory because that breaks things. And since I don't which files are nosetests, it's very difficult to change by hand.
Is there a workaround for this, or would it more appropriate for the numpy build script to set the permissions of the test file accordingly?
Works for me. But my numpy is in the site-packages directory. Did you move it to dist-packages?
np.test() Running unit tests for numpy NumPy version 1.3.0 NumPy is installed in /usr/local/lib/python2.6/site-packages/numpy Python version 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) [GCC 4.3.3] nose version 0.11.1 [snip]
Ran 2030 tests in 5.033s OK (KNOWNFAIL=1, SKIP=11) <nose.result.TextTestResult run=2030 errors=0 failures=0>
the issue is that the files are executable. I have no idea why they are set that way either. This is numpy 1.3.0 built from source. the default install location for setup.py install is the local dist-packages. So that's where it is. On Thu, Aug 20, 2009 at 5:03 PM, Keith Goodman<kwgoodman@gmail.com> wrote:
On Thu, Aug 20, 2009 at 1:52 PM, Chris Colbert<sccolbert@gmail.com> wrote:
when I build numpy from source via:
python setup.py build sudo python setup.py install
the nosetests fail because of permissions:
In [5]: np.test() Running unit tests for numpy NumPy version 1.3.0 NumPy is installed in /usr/local/lib/python2.6/dist-packages/numpy Python version 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) [GCC 4.3.3] nose version 0.10.4
---------------------------------------------------------------------- Ran 0 tests in 0.007s
OK Out[5]: <nose.result.TextTestResult run=0 errors=0 failures=0>
The problem I'm running into is I can't do a blanket chmod 664 *.py on the numpy directory because that breaks things. And since I don't which files are nosetests, it's very difficult to change by hand.
Is there a workaround for this, or would it more appropriate for the numpy build script to set the permissions of the test file accordingly?
Works for me. But my numpy is in the site-packages directory. Did you move it to dist-packages?
np.test() Running unit tests for numpy NumPy version 1.3.0 NumPy is installed in /usr/local/lib/python2.6/site-packages/numpy Python version 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) [GCC 4.3.3] nose version 0.11.1 [snip]
Ran 2030 tests in 5.033s
OK (KNOWNFAIL=1, SKIP=11) <nose.result.TextTestResult run=2030 errors=0 failures=0> _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
this happens with scipy too... On Thu, Aug 20, 2009 at 5:06 PM, Chris Colbert<sccolbert@gmail.com> wrote:
the issue is that the files are executable. I have no idea why they are set that way either. This is numpy 1.3.0 built from source.
the default install location for setup.py install is the local dist-packages. So that's where it is.
On Thu, Aug 20, 2009 at 5:03 PM, Keith Goodman<kwgoodman@gmail.com> wrote:
On Thu, Aug 20, 2009 at 1:52 PM, Chris Colbert<sccolbert@gmail.com> wrote:
when I build numpy from source via:
python setup.py build sudo python setup.py install
the nosetests fail because of permissions:
In [5]: np.test() Running unit tests for numpy NumPy version 1.3.0 NumPy is installed in /usr/local/lib/python2.6/dist-packages/numpy Python version 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) [GCC 4.3.3] nose version 0.10.4
---------------------------------------------------------------------- Ran 0 tests in 0.007s
OK Out[5]: <nose.result.TextTestResult run=0 errors=0 failures=0>
The problem I'm running into is I can't do a blanket chmod 664 *.py on the numpy directory because that breaks things. And since I don't which files are nosetests, it's very difficult to change by hand.
Is there a workaround for this, or would it more appropriate for the numpy build script to set the permissions of the test file accordingly?
Works for me. But my numpy is in the site-packages directory. Did you move it to dist-packages?
np.test() Running unit tests for numpy NumPy version 1.3.0 NumPy is installed in /usr/local/lib/python2.6/site-packages/numpy Python version 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) [GCC 4.3.3] nose version 0.11.1 [snip]
Ran 2030 tests in 5.033s
OK (KNOWNFAIL=1, SKIP=11) <nose.result.TextTestResult run=2030 errors=0 failures=0> _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Thu, Aug 20, 2009 at 14:06, Chris Colbert<sccolbert@gmail.com> wrote:
the issue is that the files are executable. I have no idea why they are set that way either. This is numpy 1.3.0 built from source.
Are you sure that those are exactly the commands that you executed? You didn't invoke setuptools in any way? -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
nope. I build Atlas, and modified site.cfg to find those libs in /usr/local/lib/atlas/ then i did: python setup.py build sudo python setup.py install that's it. On Thu, Aug 20, 2009 at 5:09 PM, Robert Kern<robert.kern@gmail.com> wrote:
On Thu, Aug 20, 2009 at 14:06, Chris Colbert<sccolbert@gmail.com> wrote:
the issue is that the files are executable. I have no idea why they are set that way either. This is numpy 1.3.0 built from source.
Are you sure that those are exactly the commands that you executed? You didn't invoke setuptools in any way?
-- Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Thu, Aug 20, 2009 at 14:13, Chris Colbert<sccolbert@gmail.com> wrote:
nope.
I build Atlas, and modified site.cfg to find those libs in /usr/local/lib/atlas/
then i did:
python setup.py build sudo python setup.py install
that's it.
Huh. I don't know. Are the source files executable? -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
On Thu, Aug 20, 2009 at 2:06 PM, Chris Colbert<sccolbert@gmail.com> wrote:
the issue is that the files are executable. I have no idea why they are set that way either. This is numpy 1.3.0 built from source.
Which sources are you using ? The tarball on sourceforge, from svn, etc... ? cheers, David
tarball from sourceforge. On Thu, Aug 20, 2009 at 6:33 PM, David Cournapeau<cournape@gmail.com> wrote:
On Thu, Aug 20, 2009 at 2:06 PM, Chris Colbert<sccolbert@gmail.com> wrote:
the issue is that the files are executable. I have no idea why they are set that way either. This is numpy 1.3.0 built from source.
Which sources are you using ? The tarball on sourceforge, from svn, etc... ?
cheers,
David _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
participants (4)
-
Chris Colbert -
David Cournapeau -
Keith Goodman -
Robert Kern