Hi, Is there going to be a scipy release anytime soon? I'm using numpy 1.0.3 with scipy 0.5.2 and I get these ugly warnings all the time: c:\apps\python25\lib\site-packages\scipy\misc\__init__.py:25: DeprecationWarning: ScipyTest is now called NumpyTest; please update your code test = ScipyTest().test These are the latest downloadable versions right? I'm beginning to wonder whether I shouldn't start building scipy myself. Thanks, John.
On Wed, Jul 04, 2007 at 11:15:58AM +0100, John Reid wrote:
Hi,
Is there going to be a scipy release anytime soon?
I'm using numpy 1.0.3 with scipy 0.5.2 and I get these ugly warnings all the time:
c:\apps\python25\lib\site-packages\scipy\misc\__init__.py:25: DeprecationWarning: ScipyTest is now called NumpyTest; please update your code test = ScipyTest().test
These are the latest downloadable versions right? I'm beginning to wonder whether I shouldn't start building scipy myself.
If these do really drive you mad, why not use the -W option to python ? Running you script with python -W ignore myscript.py -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science Reprise et maintenance de sites CPS: http://www.migration-cms.com/
Ok I'll try that although I guess that it turns off all warnings. that I'm concerned as well that scipy's release cycle isn't as quick as it could be. John. Alexandre Fayolle wrote:
On Wed, Jul 04, 2007 at 11:15:58AM +0100, John Reid wrote:
Hi,
Is there going to be a scipy release anytime soon?
I'm using numpy 1.0.3 with scipy 0.5.2 and I get these ugly warnings all the time:
c:\apps\python25\lib\site-packages\scipy\misc\__init__.py:25: DeprecationWarning: ScipyTest is now called NumpyTest; please update your code test = ScipyTest().test
These are the latest downloadable versions right? I'm beginning to wonder whether I shouldn't start building scipy myself.
If these do really drive you mad, why not use the -W option to python ?
Running you script with
python -W ignore myscript.py
------------------------------------------------------------------------
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
John Reid wrote:
Ok I'll try that although I guess that it turns off all warnings. that I'm concerned as well that scipy's release cycle isn't as quick as it could be.
Well, quite the contrary, it is as quick as it can be. If you think it is too slow, don't hesitate to help :) David
David Cournapeau wrote:
John Reid wrote:
Ok I'll try that although I guess that it turns off all warnings. that I'm concerned as well that scipy's release cycle isn't as quick as it could be.
Well, quite the contrary, it is as quick as it can be. If you think it is too slow, don't hesitate to help :)
Well I don't really want to get into an argument about the definition of 'quick as it can be'. I'm just trying to say that when people try the latest stable versions of 2 libraries that are closely coupled, they can be put off by warnings that appear out of the box. I'm pretty sure these warnings aren't important but seeing as I don't work on the internals of the libraries I don't know for sure. It looks like something that a quicker release schedule would fix and improve confidence amongst novice users of scipy. That said I'm not the one building the releases, I was just curious how the releases are managed and whether people who work on scipy are aware of this. Probably most scipy developers aren't using the 0.5.2 version with these warnings. John.
John Reid wrote:
Well I don't really want to get into an argument about the definition of 'quick as it can be'.
I'm just trying to say that when people try the latest stable versions of 2 libraries that are closely coupled, they can be put off by warnings that appear out of the box. I'm pretty sure these warnings aren't important but seeing as I don't work on the internals of the libraries I don't know for sure. It looks like something that a quicker release schedule would fix and improve confidence amongst novice users of scipy.
I think most scipy developers are aware that releases are always too late for users. But the problem really is a lack of manpower, not a lack of love for users.
That said I'm not the one building the releases, I was just curious how the releases are managed and whether people who work on scipy are aware of this. Probably most scipy developers aren't using the 0.5.2 version with these warnings.
I think most developers use subversion, indeed. It is not enforced, but my impression is that people try pretty hard to avoid breaking the main trunk (that is using the last subversion is not more buggy than a release). At least, I myself try to do so, and the fact that most scipy dev use subversion help. I always do a full run of the tests when I deploy a new version, though. David
David Cournapeau wrote:
John Reid wrote: I think most developers use subversion, indeed. It is not enforced, but my impression is that people try pretty hard to avoid breaking the main trunk (that is using the last subversion is not more buggy than a release). At least, I myself try to do so, and the fact that most scipy dev use subversion help.
I always do a full run of the tests when I deploy a new version, though.
David Thanks for the heads up, John.
David Cournapeau wrote:
John Reid wrote:
Ok I'll try that although I guess that it turns off all warnings. that I'm concerned as well that scipy's release cycle isn't as quick as it could be.
Well, quite the contrary, it is as quick as it can be. If you think it is too slow, don't hesitate to help :)
David _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
David, Can you close ticket #420 ? AFAIK, it is fixed in svn. http://projects.scipy.org/scipy/scipy/ticket/420 Nils
On Wed, Jul 04, 2007 at 11:59:28AM +0100, John Reid wrote:
Ok I'll try that although I guess that it turns off all warnings. that
It does. See the documentation of the warnings module for the full syntax and fine grained control. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science Reprise et maintenance de sites CPS: http://www.migration-cms.com/
participants (4)
-
Alexandre Fayolle -
David Cournapeau -
John Reid -
Nils Wagner