Adam Machnik | 1 Feb 17:10 2011
Picon

Vitality-potion for your rod

Portion of strength for men
   http://tpios.fapmoyhpaji.com/
Sturla Molden | 1 Feb 17:47 2011
Picon

Re: Vitality-potion for your rod

Den 01.02.2011 17:10, skrev Adam Machnik:
> Portion of strength for men
>     http://tpios.fap***hpaji.com/
Mine is strong enough...
Get the spammer off the list please?

Sturla
Aaron River | 1 Feb 20:37 2011

Re: Vitality-potion for your rod

Done.

On Tue, Feb 1, 2011 at 10:47, Sturla Molden <sturla <at> molden.no> wrote:
> Den 01.02.2011 17:10, skrev Adam Machnik:
>> Portion of strength for men
>>     http://tpios.fap***hpaji.com/
> Mine is strong enough...
> Get the spammer off the list please?
>
> Sturla
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev <at> scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev
>
_______________________________________________
SciPy-Dev mailing list
SciPy-Dev <at> scipy.org
http://mail.scipy.org/mailman/listinfo/scipy-dev
Ralf Gommers | 2 Feb 05:04 2011

Re: ANN: SciPy 0.9.0 release candidate 2



On Mon, Jan 31, 2011 at 11:01 PM, Charles R Harris <charlesr.harris <at> gmail.com> wrote:


On Sun, Jan 30, 2011 at 6:50 PM, Ralf Gommers <ralf.gommers <at> googlemail.com> wrote:
Hi,

I am pleased to announce the availability of the second release candidate of SciPy 0.9.0. This will be the first SciPy release to include support for Python 3 (all modules except scipy.weave), as well as for Python 2.7.

Due to the Sourceforge outage I am not able to put binaries on the normal download site right now, that will probably only happen in a week or so. If you want to try the RC now please build from svn, and report any issues.

Changes since release candidate 1:
- fixes for build problems with MSVC + MKL (#1210, #1376)
- fix pilutil test to work with numpy master branch
- fix constants.codata to be backwards-compatible


I think there should be a fix for ndarray also, the problem with type 5 (int) not being recognized is that it checks for Int32, which on some (all?) 32 bit platforms is a long (7) rather than an int. I think this is a bug and it will cause problems with numpy 1.6.
You mean ndimage I guess. I don't really understand your explanation, if that's the case then those ndimage tests should have been failing before, right?
 
If this needs to be fixed in scipy then we need an RC3. I would like to get that out by the 12th or so if possible.
 
Cheers,
Ralf
_______________________________________________
SciPy-Dev mailing list
SciPy-Dev <at> scipy.org
http://mail.scipy.org/mailman/listinfo/scipy-dev
Ralf Gommers | 2 Feb 05:07 2011

Re: ANN: SciPy 0.9.0 release candidate 2



On Mon, Jan 31, 2011 at 11:56 PM, Christoph Gohlke <cgohlke <at> uci.edu> wrote:


On 1/30/2011 5:50 PM, Ralf Gommers wrote:
> Hi,
>
> I am pleased to announce the availability of the second release
> candidate of SciPy 0.9.0. This will be the first SciPy release to
> include support for Python 3 (all modules except scipy.weave), as well
> as for Python 2.7.
>
> Due to the Sourceforge outage I am not able to put binaries on the
> normal download site right now, that will probably only happen in a week
> or so. If you want to try the RC now please build from svn, and report
> any issues.
>
> Changes since release candidate 1:
> - fixes for build problems with MSVC + MKL (#1210, #1376)
> - fix pilutil test to work with numpy master branch
> - fix constants.codata to be backwards-compatible
>
> Enjoy,
> Ralf
>


I tested msvc9/ifort/MKL builds of scipy 0.9 rc2 with Python 2.6, 2.7,
3.1 and 3.2 on win32 and win-amd64. Besides the known problems with the
MKL builds (<http://projects.scipy.org/scipy/ticket/1238>,
<http://projects.scipy.org/scipy/ticket/1233>,
<http://projects.scipy.org/scipy/ticket/678>), the following tests fail
on win32 only:

 
Tor the first three failures I can adjust the test precision to make the tests pass. For the Powell failure, what are the actual number of funccalls? That type of assertion doesn't work too well, should be <= 116 instead of ==.
 
Ralf
 
======================================================================
FAIL: test_linesearch.TestLineSearch.test_line_search_armijo
----------------------------------------------------------------------
Traceback (most recent call last):
  File "X:\Python27\lib\site-packages\nose\case.py", line 187, in runTest
    self.test(*self.arg)
  File
"X:\Python27\lib\site-packages\scipy\optimize\tests\test_linesearch.py",line
201, in test_line_search_armijo
    assert_equal(fv, f(x + s*p))
  File "X:\Python27\lib\site-packages\numpy\testing\utils.py", line
313, in assert_equal
    raise AssertionError(msg)
AssertionError:
Items are not equal:
 ACTUAL: 1.5675494536393939
 DESIRED: 1.5675494536393932

======================================================================
FAIL: test_linesearch.TestLineSearch.test_line_search_wolfe1
----------------------------------------------------------------------
Traceback (most recent call last):
  File "X:\Python27\lib\site-packages\nose\case.py", line 187, in runTest
    self.test(*self.arg)
  File
"X:\Python27\lib\site-packages\scipy\optimize\tests\test_linesearch.py",
line 164, in test_line_search_wolfe1
    assert_equal(fv, f(x + s*p))
  File "X:\Python27\lib\site-packages\numpy\testing\utils.py", line
313, in assert_equal
    raise AssertionError(msg)
AssertionError:
Items are not equal:
 ACTUAL: 19.185353513927268
 DESIRED: 19.185353513927272

======================================================================
FAIL: test_linesearch.TestLineSearch.test_line_search_wolfe2
----------------------------------------------------------------------
Traceback (most recent call last):
  File "X:\Python27\lib\site-packages\nose\case.py", line 187, in runTest
    self.test(*self.arg)
  File
"X:\Python27\lib\site-packages\scipy\optimize\tests\test_linesearch.py",line
184, in test_line_search_wolfe2
    assert_equal(fv, f(x + s*p))
  File "X:\Python27\lib\site-packages\numpy\testing\utils.py", line
313, in assert_equal
    raise AssertionError(msg)
AssertionError:
Items are not equal:
 ACTUAL: 19.185353513927272
 DESIRED: 19.185353513927268

======================================================================
FAIL: Powell (direction set) optimization routine
----------------------------------------------------------------------
Traceback (most recent call last):
  File
"X:\Python27\lib\site-packages\scipy\optimize\tests\test_optimize.py",
line 123, in test_powell
    assert_(self.funccalls == 116, self.funccalls)
  File "X:\Python27\lib\site-packages\numpy\testing\utils.py", line 34,
in assert_
    raise AssertionError(msg)
AssertionError: 128

--
Christoph
_______________________________________________
SciPy-Dev mailing list
SciPy-Dev <at> scipy.org
http://mail.scipy.org/mailman/listinfo/scipy-dev

_______________________________________________
SciPy-Dev mailing list
SciPy-Dev <at> scipy.org
http://mail.scipy.org/mailman/listinfo/scipy-dev
Christoph Gohlke | 2 Feb 05:34 2011
Picon

Re: ANN: SciPy 0.9.0 release candidate 2


On 2/1/2011 8:07 PM, Ralf Gommers wrote:
>
>
> On Mon, Jan 31, 2011 at 11:56 PM, Christoph Gohlke <cgohlke <at> uci.edu
> <mailto:cgohlke <at> uci.edu>> wrote:
>
>
>
>     On 1/30/2011 5:50 PM, Ralf Gommers wrote:
>     >  Hi,
>     >
>     >  I am pleased to announce the availability of the second release
>     >  candidate of SciPy 0.9.0. This will be the first SciPy release to
>     >  include support for Python 3 (all modules except scipy.weave), as well
>     >  as for Python 2.7.
>     >
>     >  Due to the Sourceforge outage I am not able to put binaries on the
>     >  normal download site right now, that will probably only happen in
>     a week
>     >  or so. If you want to try the RC now please build from svn, and report
>     >  any issues.
>     >
>     >  Changes since release candidate 1:
>     >  - fixes for build problems with MSVC + MKL (#1210, #1376)
>     >  - fix pilutil test to work with numpy master branch
>     >  - fix constants.codata to be backwards-compatible
>     >
>     >  Enjoy,
>     >  Ralf
>     >
>
>
>     I tested msvc9/ifort/MKL builds of scipy 0.9 rc2 with Python 2.6, 2.7,
>     3.1 and 3.2 on win32 and win-amd64. Besides the known problems with the
>     MKL builds (<http://projects.scipy.org/scipy/ticket/1238>,
>     <http://projects.scipy.org/scipy/ticket/1233>,
>     <http://projects.scipy.org/scipy/ticket/678>), the following tests fail
>     on win32 only:
>
> Tor the first three failures I can adjust the test precision to make the
> tests pass. For the Powell failure, what are the actual number of
> funccalls? That type of assertion doesn't work too well, should be <=
> 116 instead of ==.
> Ralf

I ran the test in a loop: most of the times the number of funccalls is 
116, often 117, and sometimes as large as 128. Not sure why this test 
only fails on win32 and not win-amd64.

Christoph

>
>     ======================================================================
>     FAIL: test_linesearch.TestLineSearch.test_line_search_armijo
>     ----------------------------------------------------------------------
>     Traceback (most recent call last):
>        File "X:\Python27\lib\site-packages\nose\case.py", line 187, in
>     runTest
>          self.test(*self.arg)
>        File
>     "X:\Python27\lib\site-packages\scipy\optimize\tests\test_linesearch.py",line
>     201, in test_line_search_armijo
>          assert_equal(fv, f(x + s*p))
>        File "X:\Python27\lib\site-packages\numpy\testing\utils.py", line
>     313, in assert_equal
>          raise AssertionError(msg)
>     AssertionError:
>     Items are not equal:
>       ACTUAL: 1.5675494536393939
>       DESIRED: 1.5675494536393932
>
>     ======================================================================
>     FAIL: test_linesearch.TestLineSearch.test_line_search_wolfe1
>     ----------------------------------------------------------------------
>     Traceback (most recent call last):
>        File "X:\Python27\lib\site-packages\nose\case.py", line 187, in
>     runTest
>          self.test(*self.arg)
>        File
>     "X:\Python27\lib\site-packages\scipy\optimize\tests\test_linesearch.py",
>     line 164, in test_line_search_wolfe1
>          assert_equal(fv, f(x + s*p))
>        File "X:\Python27\lib\site-packages\numpy\testing\utils.py", line
>     313, in assert_equal
>          raise AssertionError(msg)
>     AssertionError:
>     Items are not equal:
>       ACTUAL: 19.185353513927268
>       DESIRED: 19.185353513927272
>
>     ======================================================================
>     FAIL: test_linesearch.TestLineSearch.test_line_search_wolfe2
>     ----------------------------------------------------------------------
>     Traceback (most recent call last):
>        File "X:\Python27\lib\site-packages\nose\case.py", line 187, in
>     runTest
>          self.test(*self.arg)
>        File
>     "X:\Python27\lib\site-packages\scipy\optimize\tests\test_linesearch.py",line
>     184, in test_line_search_wolfe2
>          assert_equal(fv, f(x + s*p))
>        File "X:\Python27\lib\site-packages\numpy\testing\utils.py", line
>     313, in assert_equal
>          raise AssertionError(msg)
>     AssertionError:
>     Items are not equal:
>       ACTUAL: 19.185353513927272
>       DESIRED: 19.185353513927268
>
>     ======================================================================
>     FAIL: Powell (direction set) optimization routine
>     ----------------------------------------------------------------------
>     Traceback (most recent call last):
>        File
>     "X:\Python27\lib\site-packages\scipy\optimize\tests\test_optimize.py",
>     line 123, in test_powell
>          assert_(self.funccalls == 116, self.funccalls)
>        File "X:\Python27\lib\site-packages\numpy\testing\utils.py", line 34,
>     in assert_
>          raise AssertionError(msg)
>     AssertionError: 128
>
>     --
>     Christoph
>     _______________________________________________
>     SciPy-Dev mailing list
>     SciPy-Dev <at> scipy.org <mailto:SciPy-Dev <at> scipy.org>
>     http://mail.scipy.org/mailman/listinfo/scipy-dev
>
>
>
>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev <at> scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev
Charles R Harris | 2 Feb 05:57 2011
Picon

Re: ANN: SciPy 0.9.0 release candidate 2



On Tue, Feb 1, 2011 at 9:04 PM, Ralf Gommers <ralf.gommers <at> googlemail.com> wrote:


On Mon, Jan 31, 2011 at 11:01 PM, Charles R Harris <charlesr.harris <at> gmail.com> wrote:


On Sun, Jan 30, 2011 at 6:50 PM, Ralf Gommers <ralf.gommers <at> googlemail.com> wrote:
Hi,

I am pleased to announce the availability of the second release candidate of SciPy 0.9.0. This will be the first SciPy release to include support for Python 3 (all modules except scipy.weave), as well as for Python 2.7.

Due to the Sourceforge outage I am not able to put binaries on the normal download site right now, that will probably only happen in a week or so. If you want to try the RC now please build from svn, and report any issues.

Changes since release candidate 1:
- fixes for build problems with MSVC + MKL (#1210, #1376)
- fix pilutil test to work with numpy master branch
- fix constants.codata to be backwards-compatible


I think there should be a fix for ndarray also, the problem with type 5 (int) not being recognized is that it checks for Int32, which on some (all?) 32 bit platforms is a long (7) rather than an int. I think this is a bug and it will cause problems with numpy 1.6.
You mean ndimage I guess. I don't really understand your explanation, if that's the case then those ndimage tests should have been failing before, right?
 
If this needs to be fixed in scipy then we need an RC3. I would like to get that out by the 12th or so if possible.
 

I think it needs to be fixed as it is a bug. The problem is that ndimage checks types, but only by Int16, Int32, etc. On 32 bit systems and windows Int32 is a long (type# 7) and integers (type# 5), are treated as unrecognized types even though they are the same thing. Ndimage should accept both types.

Chuck  

_______________________________________________
SciPy-Dev mailing list
SciPy-Dev <at> scipy.org
http://mail.scipy.org/mailman/listinfo/scipy-dev
Ralf Gommers | 2 Feb 06:11 2011

Re: ANN: SciPy 0.9.0 release candidate 2



On Wed, Feb 2, 2011 at 12:57 PM, Charles R Harris <charlesr.harris <at> gmail.com> wrote:


On Tue, Feb 1, 2011 at 9:04 PM, Ralf Gommers <ralf.gommers <at> googlemail.com> wrote:


On Mon, Jan 31, 2011 at 11:01 PM, Charles R Harris <charlesr.harris <at> gmail.com> wrote:


On Sun, Jan 30, 2011 at 6:50 PM, Ralf Gommers <ralf.gommers <at> googlemail.com> wrote:
Hi,

I am pleased to announce the availability of the second release candidate of SciPy 0.9.0. This will be the first SciPy release to include support for Python 3 (all modules except scipy.weave), as well as for Python 2.7.

Due to the Sourceforge outage I am not able to put binaries on the normal download site right now, that will probably only happen in a week or so. If you want to try the RC now please build from svn, and report any issues.

Changes since release candidate 1:
- fixes for build problems with MSVC + MKL (#1210, #1376)
- fix pilutil test to work with numpy master branch
- fix constants.codata to be backwards-compatible


I think there should be a fix for ndarray also, the problem with type 5 (int) not being recognized is that it checks for Int32, which on some (all?) 32 bit platforms is a long (7) rather than an int. I think this is a bug and it will cause problems with numpy 1.6.
You mean ndimage I guess. I don't really understand your explanation, if that's the case then those ndimage tests should have been failing before, right?
 
If this needs to be fixed in scipy then we need an RC3. I would like to get that out by the 12th or so if possible.
 

I think it needs to be fixed as it is a bug. The problem is that ndimage checks types, but only by Int16, Int32, etc. On 32 bit systems and windows Int32 is a long (type# 7) and integers (type# 5), are treated as unrecognized types even though they are the same thing. Ndimage should accept both types.

I'm still a bit puzzled about why it's only failing after the recent changes in numpy master.
 
Sounds like it's a bug, but it's not a regression and we are at rc2 right now. Do you (or does someone else) have time to fix it in the next week or so? The other option is to fix it in 0.9.1, which can come out at the same time as numpy 1.6.0.
 
Cheers,
Ralf

_______________________________________________
SciPy-Dev mailing list
SciPy-Dev <at> scipy.org
http://mail.scipy.org/mailman/listinfo/scipy-dev
Ralf Gommers | 2 Feb 06:17 2011

Re: ANN: SciPy 0.9.0 release candidate 2



On Wed, Feb 2, 2011 at 12:34 PM, Christoph Gohlke <cgohlke <at> uci.edu> wrote:


On 2/1/2011 8:07 PM, Ralf Gommers wrote:
>
>
> On Mon, Jan 31, 2011 at 11:56 PM, Christoph Gohlke <cgohlke <at> uci.edu
> <mailto:cgohlke <at> uci.edu>> wrote:
>
>
>
>     On 1/30/2011 5:50 PM, Ralf Gommers wrote:
>     >  Hi,
>     >
>     >  I am pleased to announce the availability of the second release
>     >  candidate of SciPy 0.9.0. This will be the first SciPy release to
>     >  include support for Python 3 (all modules except scipy.weave), as well
>     >  as for Python 2.7.
>     >
>     >  Due to the Sourceforge outage I am not able to put binaries on the
>     >  normal download site right now, that will probably only happen in
>     a week
>     >  or so. If you want to try the RC now please build from svn, and report
>     >  any issues.
>     >
>     >  Changes since release candidate 1:
>     >  - fixes for build problems with MSVC + MKL (#1210, #1376)
>     >  - fix pilutil test to work with numpy master branch
>     >  - fix constants.codata to be backwards-compatible
>     >
>     >  Enjoy,
>     >  Ralf
>     >
>
>
>     I tested msvc9/ifort/MKL builds of scipy 0.9 rc2 with Python 2.6, 2.7,
>     3.1 and 3.2 on win32 and win-amd64. Besides the known problems with the
>     MKL builds (<http://projects.scipy.org/scipy/ticket/1238>,
>     <http://projects.scipy.org/scipy/ticket/1233>,
>     <http://projects.scipy.org/scipy/ticket/678>), the following tests fail
>     on win32 only:
>
> Tor the first three failures I can adjust the test precision to make the
> tests pass. For the Powell failure, what are the actual number of
> funccalls? That type of assertion doesn't work too well, should be <=
> 116 instead of ==.
> Ralf

I ran the test in a loop: most of the times the number of funccalls is
116, often 117, and sometimes as large as 128. Not sure why this test
only fails on win32 and not win-amd64.

It looks like an actual problem then, and not just a difference between platforms. I saw something like that recently in a Wolfe line search test too, the problem was floating point ==0.0 comparison.

Can you open a ticket?

Ralf


>
>     ======================================================================
>     FAIL: test_linesearch.TestLineSearch.test_line_search_armijo
>     ----------------------------------------------------------------------
>     Traceback (most recent call last):
>        File "X:\Python27\lib\site-packages\nose\case.py", line 187, in
>     runTest
>          self.test(*self.arg)
>        File
>     "X:\Python27\lib\site-packages\scipy\optimize\tests\test_linesearch.py",line
>     201, in test_line_search_armijo
>          assert_equal(fv, f(x + s*p))
>        File "X:\Python27\lib\site-packages\numpy\testing\utils.py", line
>     313, in assert_equal
>          raise AssertionError(msg)
>     AssertionError:
>     Items are not equal:
>       ACTUAL: 1.5675494536393939
>       DESIRED: 1.5675494536393932
>
>     ======================================================================
>     FAIL: test_linesearch.TestLineSearch.test_line_search_wolfe1
>     ----------------------------------------------------------------------
>     Traceback (most recent call last):
>        File "X:\Python27\lib\site-packages\nose\case.py", line 187, in
>     runTest
>          self.test(*self.arg)
>        File
>     "X:\Python27\lib\site-packages\scipy\optimize\tests\test_linesearch.py",
>     line 164, in test_line_search_wolfe1
>          assert_equal(fv, f(x + s*p))
>        File "X:\Python27\lib\site-packages\numpy\testing\utils.py", line
>     313, in assert_equal
>          raise AssertionError(msg)
>     AssertionError:
>     Items are not equal:
>       ACTUAL: 19.185353513927268
>       DESIRED: 19.185353513927272
>
>     ======================================================================
>     FAIL: test_linesearch.TestLineSearch.test_line_search_wolfe2
>     ----------------------------------------------------------------------
>     Traceback (most recent call last):
>        File "X:\Python27\lib\site-packages\nose\case.py", line 187, in
>     runTest
>          self.test(*self.arg)
>        File
>     "X:\Python27\lib\site-packages\scipy\optimize\tests\test_linesearch.py",line
>     184, in test_line_search_wolfe2
>          assert_equal(fv, f(x + s*p))
>        File "X:\Python27\lib\site-packages\numpy\testing\utils.py", line
>     313, in assert_equal
>          raise AssertionError(msg)
>     AssertionError:
>     Items are not equal:
>       ACTUAL: 19.185353513927272
>       DESIRED: 19.185353513927268
>
>     ======================================================================
>     FAIL: Powell (direction set) optimization routine
>     ----------------------------------------------------------------------
>     Traceback (most recent call last):
>        File
>     "X:\Python27\lib\site-packages\scipy\optimize\tests\test_optimize.py",
>     line 123, in test_powell
>          assert_(self.funccalls == 116, self.funccalls)
>        File "X:\Python27\lib\site-packages\numpy\testing\utils.py", line 34,
>     in assert_
>          raise AssertionError(msg)
>     AssertionError: 128
>
>     --
>     Christoph
>     _______________________________________________
>     SciPy-Dev mailing list
>     SciPy-Dev <at> scipy.org <mailto:SciPy-Dev <at> scipy.org>
>     http://mail.scipy.org/mailman/listinfo/scipy-dev
>
>
>
>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev <at> scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev
_______________________________________________
SciPy-Dev mailing list
SciPy-Dev <at> scipy.org
http://mail.scipy.org/mailman/listinfo/scipy-dev

_______________________________________________
SciPy-Dev mailing list
SciPy-Dev <at> scipy.org
http://mail.scipy.org/mailman/listinfo/scipy-dev
Ralf Gommers | 2 Feb 06:36 2011

Re: ANN: SciPy 0.9.0 release candidate 2



On Wed, Feb 2, 2011 at 1:11 PM, Ralf Gommers <ralf.gommers <at> googlemail.com> wrote:


On Wed, Feb 2, 2011 at 12:57 PM, Charles R Harris <charlesr.harris <at> gmail.com> wrote:


On Tue, Feb 1, 2011 at 9:04 PM, Ralf Gommers <ralf.gommers <at> googlemail.com> wrote:


On Mon, Jan 31, 2011 at 11:01 PM, Charles R Harris <charlesr.harris <at> gmail.com> wrote:

I think there should be a fix for ndarray also, the problem with type 5 (int) not being recognized is that it checks for Int32, which on some (all?) 32 bit platforms is a long (7) rather than an int. I think this is a bug and it will cause problems with numpy 1.6.
You mean ndimage I guess. I don't really understand your explanation, if that's the case then those ndimage tests should have been failing before, right?
 
If this needs to be fixed in scipy then we need an RC3. I would like to get that out by the 12th or so if possible.
 

I think it needs to be fixed as it is a bug. The problem is that ndimage checks types, but only by Int16, Int32, etc. On 32 bit systems and windows Int32 is a long (type# 7) and integers (type# 5), are treated as unrecognized types even though they are the same thing. Ndimage should accept both types.

I'm still a bit puzzled about why it's only failing after the recent changes in numpy master.
 
Sounds like it's a bug, but it's not a regression and we are at rc2 right now. Do you (or does someone else) have time to fix it in the next week or so? The other option is to fix it in 0.9.1, which can come out at the same time as numpy 1.6.0.

Sorry, I hadn't noticed that there's already a patch attached to http://projects.scipy.org/numpy/ticket/1724
If you could review and commit it, that would be great though.

Ralf

_______________________________________________
SciPy-Dev mailing list
SciPy-Dev <at> scipy.org
http://mail.scipy.org/mailman/listinfo/scipy-dev

Gmane