Re: [Numpy-discussion] nose changes checked in
On Tue, Jun 17, 2008 at 22:44, Alan McIntyre <[EMAIL PROTECTED]> wrote: > I'm assuming this experience should tell me that any item "bar" that I > can get by issuing "from numpy.foo import bar" should be considered > the public API and therefore deprecated instead of removed? ;) It's usually a good guess. But asking is usually better than guessing. -- 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://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] nose changes checked in
On Mon, Jun 16, 2008 at 8:39 PM, Robert Kern <[EMAIL PROTECTED]> wrote: > Please port over the changes I made to scipy.testing in scipy's r4424 > in order to avoid importing nose until the actual execution of tests. By the way, I notice that making those changes broke the ability to run a single test module with the command "python numpy/numpy/foo/tests/test_bar.py". So for both NumPy and SciPy, the boilerplate "if __name__ == '__main__'" stuff needs to be changed if we're going to retain that capability. I think I'd prefer to see a convenience function in numpy.testing that could be used to run the module instead of sprinkling "import nose" in all that boilerplate, especially since most of the test modules are already doing a "from numpy.testing import *" anyway. ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] nose changes checked in
On Tue, Jun 17, 2008 at 8:26 PM, Robert Kern <[EMAIL PROTECTED]> wrote: > On Tue, Jun 17, 2008 at 09:53, Alan McIntyre <[EMAIL PROTECTED]> wrote: >> If there's a consensus that they need to go back in and get marked as >> deprecated, I'll put them back. > > Yes, please do this. Using numpy.deprecate on __init__ seems to work for deprecating a class, although it says that __init__ is deprecated instead of the class. Is there a better way to deprecate a class? ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] nose changes checked in
On Tue, Jun 17, 2008 at 8:15 PM, Anne Archibald <[EMAIL PROTECTED]> wrote: > Uh, I assumed NumpyTestCase was public and used it. I'm presumably not > alone, so perhaps a deprecation warning would be good. What > backward-compatible class should I use? unittest.TestCase? Yes, unittest.TestCase seemed to be completely adequate for all the existing tests in NumPy. Unless you need some functionality explicitly implemented in NumpyTestCase (like the 'measure' or 'rundocs' methods), you can just replace it with TestCase. TestCase can be imported from numpy.testing, although (now that I think about it) it's probably less cryptic to just import it from unittest. For module-level doctests, you can place something like this in the module: from numpy.testing import * def test(): return rundocs() You can replace ParametricTest with generators, as described here: http://scipy.org/scipy/scipy/wiki/TestingGuidelines I will document all this more completely once the test setup isn't changing on a daily basis, honest. I'm assuming this experience should tell me that any item "bar" that I can get by issuing "from numpy.foo import bar" should be considered the public API and therefore deprecated instead of removed? ;) Cheers, Alan ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] building 1.1.0 on 64bit, seems to be stuck on infinite loop or something
Charles Doutriaux wrote: > Hello, > > I'm trying to build 1.1.0 on a: > Linux thunder0 2.6.9-74chaos #1 SMP Wed Oct 24 08:41:12 PDT 2007 ia64 > ia64 ia64 GNU/Linux > > using python 2.5 (latest stable) > > It seems to be stuck forever at the end of that output: > Is it stuck with 100 % Cpu usage ? May well be a compiler bug ? Did you check gcc buglist for your gcc version ? cheers, David ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Array and vector initialization good practice
Say, there are two initialized numpy arrays: A = numpy.blah B = numpy.blah.blah With, C = A*d + B*e which doesn't have to be initialized beforehand (as A and B are and so are d and e) Now, place this in a function ie. def havingFun(d, e) C = A*d + B*e return C The main program calls havingFun(d, e) continuously with new vectors d and e each time (A and B do not change). Assume that A, B, C, d, e are all very large (>100,000 rows and/or columns). In the first call to havingFun, C is created. In the next call, does Python/Numpy/Scipy have C available to overwrite it or does it create a new C (having deleted the previous C)? Wrt to efficiency and performance does it matter if C is initialized beforehand or not? Cheers! Dinesh ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] nose changes checked in
2008/6/17 Anne Archibald <[EMAIL PROTECTED]>: > 2008/6/17 Alan McIntyre <[EMAIL PROTECTED]>: > > On Tue, Jun 17, 2008 at 9:26 AM, David Huard <[EMAIL PROTECTED]> > wrote: > >> I noticed that NumpyTest and NumpyTestCase disappeared, and now I am > >> wondering whether these classes part of the public interface or were > they > >> reserved for internal usage ? > >> > >> In the former, it might be well to deprecate them before removing them. > > > > ParametricTestCase is gone too. There was at least one person using > > it that said he didn't mind porting to the nose equivalent, but I > > expect that's an indication there's more people out there using them. > > If there's a consensus that they need to go back in and get marked as > > deprecated, I'll put them back. > > Uh, I assumed NumpyTestCase was public and used it. I'm presumably not > alone, so perhaps a deprecation warning would be good. What > backward-compatible class should I use? unittest.TestCase? > Yes. You'll also have to replace the NumpyTest().run() by something else. Either the new nose method or the old fashioned if __name__ == '__main__': unittest.main() Also, note that unittest.TestCase is more restrictive than NumpyTestCase regarding the method names that are considered tests. While NumpyTestCase accepted method names starting with check_, TestCase won't recognize those as tests. David > Thanks, > Anne > ___ > Numpy-discussion mailing list > Numpy-discussion@scipy.org > http://projects.scipy.org/mailman/listinfo/numpy-discussion > ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] nose changes checked in
On Tue, Jun 17, 2008 at 09:53, Alan McIntyre <[EMAIL PROTECTED]> wrote: > On Tue, Jun 17, 2008 at 9:26 AM, David Huard <[EMAIL PROTECTED]> wrote: >> I noticed that NumpyTest and NumpyTestCase disappeared, and now I am >> wondering whether these classes part of the public interface or were they >> reserved for internal usage ? >> >> In the former, it might be well to deprecate them before removing them. > > ParametricTestCase is gone too. There was at least one person using > it that said he didn't mind porting to the nose equivalent, but I > expect that's an indication there's more people out there using them. > If there's a consensus that they need to go back in and get marked as > deprecated, I'll put them back. Yes, please do this. -- 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://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] nose changes checked in
2008/6/17 Alan McIntyre <[EMAIL PROTECTED]>: > On Tue, Jun 17, 2008 at 9:26 AM, David Huard <[EMAIL PROTECTED]> wrote: >> I noticed that NumpyTest and NumpyTestCase disappeared, and now I am >> wondering whether these classes part of the public interface or were they >> reserved for internal usage ? >> >> In the former, it might be well to deprecate them before removing them. > > ParametricTestCase is gone too. There was at least one person using > it that said he didn't mind porting to the nose equivalent, but I > expect that's an indication there's more people out there using them. > If there's a consensus that they need to go back in and get marked as > deprecated, I'll put them back. Uh, I assumed NumpyTestCase was public and used it. I'm presumably not alone, so perhaps a deprecation warning would be good. What backward-compatible class should I use? unittest.TestCase? Thanks, Anne ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] building 1.1.0 on 64bit, seems to be stuck on infinite loop or something
On Tue, Jun 17, 2008 at 3:40 PM, Charles Doutriaux <[EMAIL PROTECTED]> wrote: > Hello, > > I'm trying to build 1.1.0 on a: > Linux thunder0 2.6.9-74chaos #1 SMP Wed Oct 24 08:41:12 PDT 2007 ia64 > ia64 ia64 GNU/Linux > > using python 2.5 (latest stable) > > It seems to be stuck forever at the end of that output: > > anybody ran into this? > > ~/CDAT/5.0.0.beta1/bin/python setup.py install > Running from numpy source directory. > F2PY Version 2_5237 > blas_opt_info: > blas_mkl_info: > libraries mkl,vml,guide not found in /g/g90/cdoutrix/CDAT/Externals/lib > NOT AVAILABLE > I've had mixed success trying to set up CDAT5.0.0.beta1 and wasn't motivated to pursue it. I'll give it another shot, but probably not until the weekend. Chuck ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] building 1.1.0 on 64bit, seems to be stuck on infinite loop or something
Just so it might help debuging, when i kill it i get: _exec_command_posix failed (status=2) C. Charles Doutriaux wrote: > Hello, > > I'm trying to build 1.1.0 on a: > Linux thunder0 2.6.9-74chaos #1 SMP Wed Oct 24 08:41:12 PDT 2007 ia64 > ia64 ia64 GNU/Linux > > using python 2.5 (latest stable) > > It seems to be stuck forever at the end of that output: > > anybody ran into this? > > ~/CDAT/5.0.0.beta1/bin/python setup.py install > Running from numpy source directory. > F2PY Version 2_5237 > blas_opt_info: > blas_mkl_info: > libraries mkl,vml,guide not found in /g/g90/cdoutrix/CDAT/Externals/lib > NOT AVAILABLE > > atlas_blas_threads_info: > Setting PTATLAS=ATLAS > libraries ptf77blas,ptcblas,atlas not found in > /g/g90/cdoutrix/CDAT/Externals/lib > NOT AVAILABLE > > atlas_blas_info: > libraries f77blas,cblas,atlas not found in > /g/g90/cdoutrix/CDAT/Externals/lib > NOT AVAILABLE > > /g/g90/cdoutrix/svn/cdat/branches/devel/build/numpy-1.1.0/numpy/distutils/system_info.py:1340: > > UserWarning: > Atlas (http://math-atlas.sourceforge.net/) libraries not found. > Directories to search for the libraries can be specified in the > numpy/distutils/site.cfg file (section [atlas]) or by setting > the ATLAS environment variable. > warnings.warn(AtlasNotFoundError.__doc__) > blas_info: > libraries blas not found in /g/g90/cdoutrix/CDAT/Externals/lib > NOT AVAILABLE > > /g/g90/cdoutrix/svn/cdat/branches/devel/build/numpy-1.1.0/numpy/distutils/system_info.py:1349: > > UserWarning: > Blas (http://www.netlib.org/blas/) libraries not found. > Directories to search for the libraries can be specified in the > numpy/distutils/site.cfg file (section [blas]) or by setting > the BLAS environment variable. > warnings.warn(BlasNotFoundError.__doc__) > blas_src_info: > NOT AVAILABLE > > /g/g90/cdoutrix/svn/cdat/branches/devel/build/numpy-1.1.0/numpy/distutils/system_info.py:1352: > > UserWarning: > Blas (http://www.netlib.org/blas/) sources not found. > Directories to search for the sources can be specified in the > numpy/distutils/site.cfg file (section [blas_src]) or by setting > the BLAS_SRC environment variable. > warnings.warn(BlasSrcNotFoundError.__doc__) > NOT AVAILABLE > > lapack_opt_info: > lapack_mkl_info: > mkl_info: > libraries mkl,vml,guide not found in /g/g90/cdoutrix/CDAT/Externals/lib > NOT AVAILABLE > > NOT AVAILABLE > > atlas_threads_info: > Setting PTATLAS=ATLAS > libraries ptf77blas,ptcblas,atlas not found in > /g/g90/cdoutrix/CDAT/Externals/lib > libraries lapack_atlas not found in /g/g90/cdoutrix/CDAT/Externals/lib > numpy.distutils.system_info.atlas_threads_info > NOT AVAILABLE > > atlas_info: > libraries f77blas,cblas,atlas not found in > /g/g90/cdoutrix/CDAT/Externals/lib > libraries lapack_atlas not found in /g/g90/cdoutrix/CDAT/Externals/lib > numpy.distutils.system_info.atlas_info > NOT AVAILABLE > > /g/g90/cdoutrix/svn/cdat/branches/devel/build/numpy-1.1.0/numpy/distutils/system_info.py:1247: > > UserWarning: > Atlas (http://math-atlas.sourceforge.net/) libraries not found. > Directories to search for the libraries can be specified in the > numpy/distutils/site.cfg file (section [atlas]) or by setting > the ATLAS environment variable. > warnings.warn(AtlasNotFoundError.__doc__) > lapack_info: > libraries lapack not found in /g/g90/cdoutrix/CDAT/Externals/lib > NOT AVAILABLE > > /g/g90/cdoutrix/svn/cdat/branches/devel/build/numpy-1.1.0/numpy/distutils/system_info.py:1258: > > UserWarning: > Lapack (http://www.netlib.org/lapack/) libraries not found. > Directories to search for the libraries can be specified in the > numpy/distutils/site.cfg file (section [lapack]) or by setting > the LAPACK environment variable. > warnings.warn(LapackNotFoundError.__doc__) > lapack_src_info: > NOT AVAILABLE > > /g/g90/cdoutrix/svn/cdat/branches/devel/build/numpy-1.1.0/numpy/distutils/system_info.py:1261: > > UserWarning: > Lapack (http://www.netlib.org/lapack/) sources not found. > Directories to search for the sources can be specified in the > numpy/distutils/site.cfg file (section [lapack_src]) or by setting > the LAPACK_SRC environment variable. > warnings.warn(LapackSrcNotFoundError.__doc__) > NOT AVAILABLE > > running install > running build > running scons > customize UnixCCompiler > Found executable /usr/local/bin/gcc > customize GnuFCompiler > Found executable /usr/local/bin/g77 > gnu: no Fortran 90 compiler found > gnu: no Fortran 90 compiler found > customize GnuFCompiler > gnu: no Fortran 90 compiler found > gnu: no Fortran 90 compiler found > customize UnixCCompiler > customize UnixCCompiler using scons > running config_cc > unifing config_cc, config, build_clib, build_ext, build commands > --compiler options > running config_fc > unifing config_fc, config, build_clib, build_ext, build commands > --fcompiler options > running build_src
[Numpy-discussion] building 1.1.0 on 64bit, seems to be stuck on infinite loop or something
Hello, I'm trying to build 1.1.0 on a: Linux thunder0 2.6.9-74chaos #1 SMP Wed Oct 24 08:41:12 PDT 2007 ia64 ia64 ia64 GNU/Linux using python 2.5 (latest stable) It seems to be stuck forever at the end of that output: anybody ran into this? ~/CDAT/5.0.0.beta1/bin/python setup.py install Running from numpy source directory. F2PY Version 2_5237 blas_opt_info: blas_mkl_info: libraries mkl,vml,guide not found in /g/g90/cdoutrix/CDAT/Externals/lib NOT AVAILABLE atlas_blas_threads_info: Setting PTATLAS=ATLAS libraries ptf77blas,ptcblas,atlas not found in /g/g90/cdoutrix/CDAT/Externals/lib NOT AVAILABLE atlas_blas_info: libraries f77blas,cblas,atlas not found in /g/g90/cdoutrix/CDAT/Externals/lib NOT AVAILABLE /g/g90/cdoutrix/svn/cdat/branches/devel/build/numpy-1.1.0/numpy/distutils/system_info.py:1340: UserWarning: Atlas (http://math-atlas.sourceforge.net/) libraries not found. Directories to search for the libraries can be specified in the numpy/distutils/site.cfg file (section [atlas]) or by setting the ATLAS environment variable. warnings.warn(AtlasNotFoundError.__doc__) blas_info: libraries blas not found in /g/g90/cdoutrix/CDAT/Externals/lib NOT AVAILABLE /g/g90/cdoutrix/svn/cdat/branches/devel/build/numpy-1.1.0/numpy/distutils/system_info.py:1349: UserWarning: Blas (http://www.netlib.org/blas/) libraries not found. Directories to search for the libraries can be specified in the numpy/distutils/site.cfg file (section [blas]) or by setting the BLAS environment variable. warnings.warn(BlasNotFoundError.__doc__) blas_src_info: NOT AVAILABLE /g/g90/cdoutrix/svn/cdat/branches/devel/build/numpy-1.1.0/numpy/distutils/system_info.py:1352: UserWarning: Blas (http://www.netlib.org/blas/) sources not found. Directories to search for the sources can be specified in the numpy/distutils/site.cfg file (section [blas_src]) or by setting the BLAS_SRC environment variable. warnings.warn(BlasSrcNotFoundError.__doc__) NOT AVAILABLE lapack_opt_info: lapack_mkl_info: mkl_info: libraries mkl,vml,guide not found in /g/g90/cdoutrix/CDAT/Externals/lib NOT AVAILABLE NOT AVAILABLE atlas_threads_info: Setting PTATLAS=ATLAS libraries ptf77blas,ptcblas,atlas not found in /g/g90/cdoutrix/CDAT/Externals/lib libraries lapack_atlas not found in /g/g90/cdoutrix/CDAT/Externals/lib numpy.distutils.system_info.atlas_threads_info NOT AVAILABLE atlas_info: libraries f77blas,cblas,atlas not found in /g/g90/cdoutrix/CDAT/Externals/lib libraries lapack_atlas not found in /g/g90/cdoutrix/CDAT/Externals/lib numpy.distutils.system_info.atlas_info NOT AVAILABLE /g/g90/cdoutrix/svn/cdat/branches/devel/build/numpy-1.1.0/numpy/distutils/system_info.py:1247: UserWarning: Atlas (http://math-atlas.sourceforge.net/) libraries not found. Directories to search for the libraries can be specified in the numpy/distutils/site.cfg file (section [atlas]) or by setting the ATLAS environment variable. warnings.warn(AtlasNotFoundError.__doc__) lapack_info: libraries lapack not found in /g/g90/cdoutrix/CDAT/Externals/lib NOT AVAILABLE /g/g90/cdoutrix/svn/cdat/branches/devel/build/numpy-1.1.0/numpy/distutils/system_info.py:1258: UserWarning: Lapack (http://www.netlib.org/lapack/) libraries not found. Directories to search for the libraries can be specified in the numpy/distutils/site.cfg file (section [lapack]) or by setting the LAPACK environment variable. warnings.warn(LapackNotFoundError.__doc__) lapack_src_info: NOT AVAILABLE /g/g90/cdoutrix/svn/cdat/branches/devel/build/numpy-1.1.0/numpy/distutils/system_info.py:1261: UserWarning: Lapack (http://www.netlib.org/lapack/) sources not found. Directories to search for the sources can be specified in the numpy/distutils/site.cfg file (section [lapack_src]) or by setting the LAPACK_SRC environment variable. warnings.warn(LapackSrcNotFoundError.__doc__) NOT AVAILABLE running install running build running scons customize UnixCCompiler Found executable /usr/local/bin/gcc customize GnuFCompiler Found executable /usr/local/bin/g77 gnu: no Fortran 90 compiler found gnu: no Fortran 90 compiler found customize GnuFCompiler gnu: no Fortran 90 compiler found gnu: no Fortran 90 compiler found customize UnixCCompiler customize UnixCCompiler using scons running config_cc unifing config_cc, config, build_clib, build_ext, build commands --compiler options running config_fc unifing config_fc, config, build_clib, build_ext, build commands --fcompiler options running build_src building py_modules sources building extension "numpy.core.multiarray" sources adding 'build/src.linux-ia64-2.5/numpy/core/config.h' to sources. adding 'build/src.linux-ia64-2.5/numpy/core/numpyconfig.h' to sources. executing numpy/core/code_generators/generate_array_api.py adding 'build/src.linux-ia64-2.5/numpy/core/__multiarray_api.h' to sources. adding 'build/src.linux-ia
Re: [Numpy-discussion] ImportError: No module named numpy.distutils.core
On Tue, Jun 17, 2008 at 11:04, Nils Wagner <[EMAIL PROTECTED]> wrote:
> On Tue, 17 Jun 2008 17:53:53 +0200
> "Nils Wagner" <[EMAIL PROTECTED]> wrote:
> Anyway, numpy.test() now results in
>
> ==
> FAIL:
> test_format.test_memmap_roundtrip('\x93NUMPY\x01\x00F\x00{\'shape\':
> (3, 3), \'descr\': \'>c16\', \'fortran_order\': False}
> '\x93NUMPY\x01\x00F\x00{\'shape\': (3, 3),
> \'fortran_order\': False, \'descr\': \'>c16\'}
Okay, it looks like pprint.pformat() doesn't sort the keys reliably
like I thought it did. Your installation is fine; the testis buggy as
it relies on something it (apparently) shouldn't rely on.
--
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://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ImportError: No module named numpy.distutils.core
On Tue, 17 Jun 2008 18:31:31 +0200
"Nils Wagner" <[EMAIL PROTECTED]> wrote:
> On Tue, 17 Jun 2008 10:13:31 -0600
> "Charles R Harris" <[EMAIL PROTECTED]> wrote:
>> On Tue, Jun 17, 2008 at 10:04 AM, Nils Wagner
>><[EMAIL PROTECTED]>
>> wrote:
>>
>>> On Tue, 17 Jun 2008 17:53:53 +0200
>>> "Nils Wagner" <[EMAIL PROTECTED]> wrote:
>>> > Hi all,
>>> >
>>> > How do I install numpy from svn ?
>>> >
>>> > With latest svn I get
>>> >
>>> > /usr/bin/python setup.py install
>>> > Traceback (most recent call last):
>>> > File "setup.py", line 96, in ?
>>> > setup_package()
>>> > File "setup.py", line 68, in setup_package
>>> > from numpy.distutils.core import setup
>>> > ImportError: No module named numpy.distutils.core
>>> >
>>> > Cheers,
>>> >
>>> >Nils
>>> >
>>>
>>> Please ignore the message. I have removed my numpy
>>> directory by accident.
>>>
>>> Sorry for the noise.
>>>
>>>
>>> Anyway, numpy.test() now results in
>>>
>>> ==
>>> FAIL:
>>> test_format.test_memmap_roundtrip('\x93NUMPY\x01\x00F\x00{\'shape\':
>>> (3, 3), \'descr\': \'>c16\', \'fortran_order\': False}
>>> [EMAIL PROTECTED]@
>>> (\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>>> ,\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>>> \x14\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>>> \x1c\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>>> "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>>> \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>>> \x10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
>>> '\x93NUMPY\x01\x00F\x00{\'shape\': (3, 3),
>>> \'fortran_order\': False, \'descr\': \'>c16\'}
>>> [EMAIL PROTECTED]@
>>> (\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>>> ,\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>>> \x14\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>>> \x1c\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>>> "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>>> \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>>> \x10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00')
>>> --
>>> Traceback (most recent call last):
>>>File "/usr/lib/python2.4/site-packages/nose/case.py",
>>> line 203, in runTest
>>> self.test(*self.arg)
>>> File
>>> "/usr/lib/python2.4/site-packages/numpy/lib/tests/test_format.py",
>>> line 414, in assert_equal
>>> assert o1 == o2
>>> AssertionError
>>>
>>> --
>>> Ran 1655 tests in 29.608s
>>>
>>> FAILED (failures=144)
>>>
>>
>> OS? Architecture? Compiler? Nose version?
>>
nose.__version__
> '0.10.1'
> uname -a
> Linux linux 2.6.11.4-21.17-default #1 Fri Apr 6 08:42:34
> UTC 2007 i686 athlon i386 GNU/Linux
> Python 2.4 (#1, Oct 13 2006, 17:13:31)
> [GCC 3.3.5 20050117 (prerelease) (SUSE Linux)] on linux2
> Type "help", "copyright", "credits" or "license" for
>more
> information.
>
> Nils
BTW, the failures persist after an upgrade of nose.
>>> import nose
>>> nose.__version__
'0.10.3'
Cheers,
Nils
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ImportError: No module named numpy.distutils.core
On Tue, 17 Jun 2008 10:13:31 -0600
"Charles R Harris" <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 17, 2008 at 10:04 AM, Nils Wagner
><[EMAIL PROTECTED]>
> wrote:
>
>> On Tue, 17 Jun 2008 17:53:53 +0200
>> "Nils Wagner" <[EMAIL PROTECTED]> wrote:
>> > Hi all,
>> >
>> > How do I install numpy from svn ?
>> >
>> > With latest svn I get
>> >
>> > /usr/bin/python setup.py install
>> > Traceback (most recent call last):
>> > File "setup.py", line 96, in ?
>> > setup_package()
>> > File "setup.py", line 68, in setup_package
>> > from numpy.distutils.core import setup
>> > ImportError: No module named numpy.distutils.core
>> >
>> > Cheers,
>> >
>> >Nils
>> >
>>
>> Please ignore the message. I have removed my numpy
>> directory by accident.
>>
>> Sorry for the noise.
>>
>>
>> Anyway, numpy.test() now results in
>>
>> ==
>> FAIL:
>> test_format.test_memmap_roundtrip('\x93NUMPY\x01\x00F\x00{\'shape\':
>> (3, 3), \'descr\': \'>c16\', \'fortran_order\': False}
>> [EMAIL PROTECTED]@
>> (\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>> ,\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>> \x14\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>> \x1c\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>> "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>> \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>> \x10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
>> '\x93NUMPY\x01\x00F\x00{\'shape\': (3, 3),
>> \'fortran_order\': False, \'descr\': \'>c16\'}
>> [EMAIL PROTECTED]@
>> (\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>> ,\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>> \x14\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>> \x1c\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>> "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>> \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
>> \x10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00')
>> --
>> Traceback (most recent call last):
>>File "/usr/lib/python2.4/site-packages/nose/case.py",
>> line 203, in runTest
>> self.test(*self.arg)
>> File
>> "/usr/lib/python2.4/site-packages/numpy/lib/tests/test_format.py",
>> line 414, in assert_equal
>> assert o1 == o2
>> AssertionError
>>
>> --
>> Ran 1655 tests in 29.608s
>>
>> FAILED (failures=144)
>>
>
> OS? Architecture? Compiler? Nose version?
>
>>> nose.__version__
'0.10.1'
uname -a
Linux linux 2.6.11.4-21.17-default #1 Fri Apr 6 08:42:34
UTC 2007 i686 athlon i386 GNU/Linux
Python 2.4 (#1, Oct 13 2006, 17:13:31)
[GCC 3.3.5 20050117 (prerelease) (SUSE Linux)] on linux2
Type "help", "copyright", "credits" or "license" for more
information.
Nils
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ImportError: No module named numpy.distutils.core
On Tue, Jun 17, 2008 at 10:04 AM, Nils Wagner <[EMAIL PROTECTED]>
wrote:
> On Tue, 17 Jun 2008 17:53:53 +0200
> "Nils Wagner" <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > How do I install numpy from svn ?
> >
> > With latest svn I get
> >
> > /usr/bin/python setup.py install
> > Traceback (most recent call last):
> > File "setup.py", line 96, in ?
> > setup_package()
> > File "setup.py", line 68, in setup_package
> > from numpy.distutils.core import setup
> > ImportError: No module named numpy.distutils.core
> >
> > Cheers,
> >
> >Nils
> >
>
> Please ignore the message. I have removed my numpy
> directory by accident.
>
> Sorry for the noise.
>
>
> Anyway, numpy.test() now results in
>
> ==
> FAIL:
> test_format.test_memmap_roundtrip('\x93NUMPY\x01\x00F\x00{\'shape\':
> (3, 3), \'descr\': \'>c16\', \'fortran_order\': False}
> [EMAIL PROTECTED]@
> (\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
> ,\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
> \x14\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
> \x1c\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
> "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
> \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
> \x10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
> '\x93NUMPY\x01\x00F\x00{\'shape\': (3, 3),
> \'fortran_order\': False, \'descr\': \'>c16\'}
> [EMAIL PROTECTED]@
> (\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
> ,\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
> \x14\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
> \x1c\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
> "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
> \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@
> \x10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00')
> --
> Traceback (most recent call last):
>File "/usr/lib/python2.4/site-packages/nose/case.py",
> line 203, in runTest
> self.test(*self.arg)
> File
> "/usr/lib/python2.4/site-packages/numpy/lib/tests/test_format.py",
> line 414, in assert_equal
> assert o1 == o2
> AssertionError
>
> --
> Ran 1655 tests in 29.608s
>
> FAILED (failures=144)
>
OS? Architecture? Compiler? Nose version?
Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ImportError: No module named numpy.distutils.core
On Tue, 17 Jun 2008 17:53:53 +0200
"Nils Wagner" <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> How do I install numpy from svn ?
>
> With latest svn I get
>
> /usr/bin/python setup.py install
> Traceback (most recent call last):
> File "setup.py", line 96, in ?
> setup_package()
> File "setup.py", line 68, in setup_package
> from numpy.distutils.core import setup
> ImportError: No module named numpy.distutils.core
>
> Cheers,
>
>Nils
>
Please ignore the message. I have removed my numpy
directory by accident.
Sorry for the noise.
Anyway, numpy.test() now results in
==
FAIL:
test_format.test_memmap_roundtrip('\x93NUMPY\x01\x00F\x00{\'shape\':
(3, 3), \'descr\': \'>c16\', \'fortran_order\': False}
[EMAIL
PROTECTED]@(\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@,[EMAIL
PROTECTED]@\x1c\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@"[EMAIL
PROTECTED]@\x10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
'\x93NUMPY\x01\x00F\x00{\'shape\': (3, 3),
\'fortran_order\': False, \'descr\': \'>c16\'}
[EMAIL
PROTECTED]@(\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@,[EMAIL
PROTECTED]@\x1c\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00@"[EMAIL
PROTECTED]@\x10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00')
--
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/nose/case.py",
line 203, in runTest
self.test(*self.arg)
File
"/usr/lib/python2.4/site-packages/numpy/lib/tests/test_format.py",
line 414, in assert_equal
assert o1 == o2
AssertionError
--
Ran 1655 tests in 29.608s
FAILED (failures=144)
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ImportError: No module named numpy.distutils.core
On Tue, Jun 17, 2008 at 9:53 AM, Nils Wagner <[EMAIL PROTECTED]> wrote: > Hi all, > > How do I install numpy from svn ? > > With latest svn I get > > /usr/bin/python setup.py install > Traceback (most recent call last): > File "setup.py", line 96, in ? > setup_package() > File "setup.py", line 68, in setup_package > from numpy.distutils.core import setup > ImportError: No module named numpy.distutils.core > I don't have that problem. What happens if you delete the build directory? What if you build separately from install? Chuck ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] ImportError: No module named numpy.distutils.core
Hi all, How do I install numpy from svn ? With latest svn I get /usr/bin/python setup.py install Traceback (most recent call last): File "setup.py", line 96, in ? setup_package() File "setup.py", line 68, in setup_package from numpy.distutils.core import setup ImportError: No module named numpy.distutils.core Cheers, Nils ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] nose changes checked in
On Tue, June 17, 2008 6:17 am, Robert Kern wrote: > On Mon, Jun 16, 2008 at 21:18, Alan McIntyre <[EMAIL PROTECTED]> > wrote: >> On Mon, Jun 16, 2008 at 9:04 PM, Charles R Harris >> <[EMAIL PROTECTED]> wrote: > >>> In [1]: numpy.test() >>> Not implemented: Defined_Binary_Op >>> Not implemented: Defined_Binary_Op >>> Defined_Operator not defined used by Generic_Spec >>> Needs match implementation: Allocate_Stmt >>> Needs match implementation: Associate_Construct >> >> >> That stream of "Not implemented" and "Needs match implementation" >> stuff comes from numpy/f2py/lib/parser/test_Fortran2003.py and >> Fortran2003.py. I can silence most of that output by disabling those >> module-level "if 1:" blocks in those two files, but there's still >> complaints about Defined_Binary_Op not being implemented. If someone >> more knowledgeable about that module could comment on that I'd >> appreciate it. > > These files were for the in-development g3 version of f2py. That > development has moved outside of numpy, so I think they can be removed > wholesale. Some of them seem to require a Fortran 90 compiler, so I > have had them fail for me. Removing these is a high priority. > > Pearu, can you confirm? Can we give you the task of removing the > unused g3 portions of f2py for the 1.2 release? Yes, I have created the corresponding ticket some time ago: http://projects.scipy.org/scipy/numpy/ticket/758 Pearu ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] nose changes checked in
On Tue, Jun 17, 2008 at 9:26 AM, David Huard <[EMAIL PROTECTED]> wrote: > I noticed that NumpyTest and NumpyTestCase disappeared, and now I am > wondering whether these classes part of the public interface or were they > reserved for internal usage ? > > In the former, it might be well to deprecate them before removing them. ParametricTestCase is gone too. There was at least one person using it that said he didn't mind porting to the nose equivalent, but I expect that's an indication there's more people out there using them. If there's a consensus that they need to go back in and get marked as deprecated, I'll put them back. Alan ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] nose changes checked in
On Mon, Jun 16, 2008 at 11:17 PM, Robert Kern <[EMAIL PROTECTED]> wrote: > These files were for the in-development g3 version of f2py. That > development has moved outside of numpy, so I think they can be removed > wholesale. Some of them seem to require a Fortran 90 compiler, so I > have had them fail for me. Removing these is a high priority. Nice, thanks. For what it's worth, removing both of those files doesn't seem to cause any problems for me locally with NumPy or SciPy. ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Numpy 1.1.0 on Python 2.3?
D.Hendriks (Dennis) wrote: > > I could not find anything about Python 2.3 no longer being supported by > Numpy. Did I miss anything? > If you're right (the operation not being possible under python 2.3), then this is a bug. Numpy 1.1.* still supports python 2.3. Starting from 1.2, we will only support 2.4 (and above). May I suggest you to report this bug to our bug tracking system ? http://projects.scipy.org/scipy/numpy cheers, David ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] nose changes checked in
I noticed that NumpyTest and NumpyTestCase disappeared, and now I am wondering whether these classes part of the public interface or were they reserved for internal usage ? In the former, it might be well to deprecate them before removing them. Cheers, David 2008/6/17 David Cournapeau <[EMAIL PROTECTED]>: > David Cournapeau wrote: > > It does not work with python2.6a3, but it is a nose problem, apparently > > (I have the exact same error) > > > > Sorry, it is a python26 problem, not nose. > > cheers, > > David > ___ > Numpy-discussion mailing list > Numpy-discussion@scipy.org > http://projects.scipy.org/mailman/listinfo/numpy-discussion > ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Numpy 1.1.0 on Python 2.3?
Hello, After I just upgraded my Numpy from 1.0.3.1 to 1.1.0 and executed (using Python 2.3.4): python -c 'import numpy; numpy.test()' I got: Traceback (most recent call last): File "", line 1, in ? File "###/lib/python2.3/site-packages/numpy/__init__.py", line 107, in ? import ma File "###/lib/python2.3/site-packages/numpy/ma/__init__.py", line 14, in ? import core File "###/lib/python2.3/site-packages/numpy/ma/core.py", line 114, in ? max_filler.update([(k,-numpy.inf) for k in [numpy.float32, numpy.float64]]) AttributeError: keys It seems Python 2.3 doesn't allow updating dictionaries using a list of key-value-pair tuples; it only allows a dictionary as parameter to update(). I could not find anything about Python 2.3 no longer being supported by Numpy. Did I miss anything? Dennis ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Buildbot config
To whomever knows, Where do we keep the buildbot configuration? The arguments for numpy.test have changed with the switch to nose, so the test step fails. It also appears nose needs to be installed/updated on the build slaves. Thanks, Alan ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] nose changes checked in
David Cournapeau wrote: > It does not work with python2.6a3, but it is a nose problem, apparently > (I have the exact same error) > Sorry, it is a python26 problem, not nose. cheers, David ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] nose changes checked in
Alan McIntyre wrote: > Hi all, > > I just checked in the switch to use nose to run unit tests. Please > let me know if you experience any difficulties as a result. > It does not work with python2.6a3, but it is a nose problem, apparently (I have the exact same error) http://bzimmer.ziclix.com/2008/05/16/pysmug-on-python26a3/ Just thought I would mention it if other people try things with python2.6 cheers, David ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
