Your message dated Fri, 13 Mar 2009 12:55:54 -0400 with message-id <[email protected]> and subject line Re: Bug#519440: python-scipy: take care about deprecation warnings from numpy has caused the Debian Bug report #519440, regarding python-scipy: take care about deprecation warnings from numpy to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 519440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519440 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: python-scipy Version: 0.6.0-12 Severity: normal Any code which uses scipy and numpy on debian sid now provokes a flood of deprecation warnings like: In [1]:import scipy /usr/lib/python2.5/site-packages/scipy/misc/__init__.py:25: DeprecationWarning: NumpyTest will be removed in the next release; please update your code to use nose or unittest test = NumpyTest().test In [4]:mimport scipy.linalg /usr/lib/python2.5/site-packages/scipy/linalg/__init__.py:32: DeprecationWarning: NumpyTest will be removed in the next release; please update your code to use nose or unittest test = NumpyTest().test and more of scipy you import more you get of those... why should I care about receiving these ones if I don't use NumpyTest per se? If you are aware of this issue I would humbly appreciate if some action is taken... my little mind finds only a cruel suggestion to wrap those test instantiations within warnings.simplefilter('ignore', DeprecationWarning) test = NumpyTest().test warnings.simplefilter('defaul', DeprecationWarning) but I hope that there is a better way, like defining a custom filter to catch those known deprecation issues -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (300, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages python-scipy depends on: ii libatlas3gf-base [libla 3.6.0-22.1~debug Automatically Tuned Linear Algebra ii libatlas3gf-sse [liblap 3.6.0-22.1~debug Automatically Tuned Linear Algebra ii libatlas3gf-sse2 [libla 3.6.0-22.1~debug Automatically Tuned Linear Algebra ii libblas3gf [libblas.so. 1.2-2 Basic Linear Algebra Subroutines 3 ii libc6 2.9-4 GNU C Library: Shared libraries ii libfftw3-3 3.1.2-3.1 library for computing Fast Fourier ii libgcc1 1:4.3.1-9 GCC support library ii libgfortran3 4.3.1-9 Runtime library for GNU Fortran ap ii liblapack3gf [liblapack 3.1.1-1 library of linear algebra routines ii libstdc++6 4.3.1-9 The GNU Standard C++ Library v3 ii libsuitesparse-3.1.0 3.1.0-3 collection of libraries for comput ii python 2.5.2-2 An interactive high-level object-o ii python-central 0.6.11 register and build utility for Pyt ii python-imaging 1.1.6-3 Python Imaging Library ii python-numpy 1:1.2.1-1 Numerical Python adds a fast array Versions of packages python-scipy recommends: ii g++ [c++-compiler] 4:4.3.1-2 The GNU C++ compiler ii g++-2.95 [c++-compiler] 1:2.95.4-27 The GNU C++ compiler ii g++-3.2 [c++-compiler] 1:3.2.3-9 The GNU C++ compiler ii g++-3.3 [c++-compiler] 1:3.3.6-15 The GNU C++ compiler ii g++-4.0 [c++-compiler] 4.0.3-7 The GNU C++ compiler ii g++-4.1 [c++-compiler] 4.1.2-25 The GNU C++ compiler ii g++-4.2 [c++-compiler] 4.2.4-6 The GNU C++ compiler ii g++-4.3 [c++-compiler] 4.3.1-9 The GNU C++ compiler Versions of packages python-scipy suggests: ii python-profiler 2.5.2-1 deterministic profiling of any Pyt -- no debconf information
--- End Message ---
--- Begin Message ---only later on I mentioned that scipy 0.7.0 is in unstable already. Thanks! and it seems that it became more compliant to numpy 1.2.1 -- all those warnings are gone. Since probably 0.7.0 will enter testing some time soon, and there will be no 1.2.1 numpy + 0.6.0 broken tandem, there is no reason to keep this bug open ;) closing it now (to take away the burden of closing it whenever scipy 0.7.0 is in testing) On Thu, 12 Mar 2009, Ondrej Certik wrote: > Thanks for the bug report, indeed, this is extremely annoying. > I am aware of this, but I don't have time to fix it. I would > appreciate if you could help us with it. We just need to patch numpy > so that it doesn't emmit those warnings. Or patch scipy. > Thanks for any work you do, > Ondrej -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-1412 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik
--- End Message ---
_______________________________________________ Python-modules-team mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
