Win32 binaries for Python 3.3, 3.4?
Hi guys, Am I right in thinking we don't have binary installers for Pythons 3.3 and 3.4 for Scipy 0.14.0? Is this because of the need for VS 10? [1] Are there plans for these guys? Can I help? Cheers, Matthew [1] http://matthew-brett.github.io/pydagogue/python_msvc.html#visual-studio-vers...
On Fri, May 16, 2014 at 10:01 PM, Matthew Brett <matthew.brett@gmail.com>wrote:
Hi guys,
Am I right in thinking we don't have binary installers for Pythons 3.3 and 3.4 for Scipy 0.14.0?
You're right.
Is this because of the need for VS 10? [1]
This is because my build environment (Wine on OS X) refuses to install Python 3.3/3.4, and I have not yet switched to an alternative setup. I think Julian built 3.3/3.4 installers on Linux, so it should still be possible with Wine. Are there plans for these guys? Can I help?
If you'd be willing to fix this situation, that would be fantastic. There's a plan on my todo list that says "fix this", but my todo list never seems to get shorter...... Ralf
Cheers,
Matthew
[1] http://matthew-brett.github.io/pydagogue/python_msvc.html#visual-studio-vers... _______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
Hi, On Sat, May 17, 2014 at 7:43 AM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
On Fri, May 16, 2014 at 10:01 PM, Matthew Brett <matthew.brett@gmail.com> wrote:
Hi guys,
Am I right in thinking we don't have binary installers for Pythons 3.3 and 3.4 for Scipy 0.14.0?
You're right.
Is this because of the need for VS 10? [1]
This is because my build environment (Wine on OS X) refuses to install Python 3.3/3.4, and I have not yet switched to an alternative setup. I think Julian built 3.3/3.4 installers on Linux, so it should still be possible with Wine.
Are there plans for these guys? Can I help?
If you'd be willing to fix this situation, that would be fantastic. There's a plan on my todo list that says "fix this", but my todo list never seems to get shorter......
I built them on Windows, it was a bit ugly, notes here: https://github.com/numpy/numpy/wiki/building_scipy_superpack I tested them on a clean virtual machine. The Python 3.4 test run found the same intermittent failure that Christoph found here: http://mail.scipy.org/pipermail/scipy-dev/2013-August/019118.html Error message: ====================================================================== FAIL: test_windows.test_windowfunc_basics ---------------------------------------------------------------------- Traceback (most recent call last): File "C:\Python34\lib\site-packages\nose\case.py", line 198, in runTest self.test(*self.arg) File "C:\Python34\lib\site-packages\scipy\signal\tests\test_windows.py", line 100, in test_windowfunc_basics assert_array_almost_equal(w1, w2) File "C:\Python34\lib\site-packages\numpy\testing\utils.py", line 811, in assert_array_almost_equal header=('Arrays are not almost equal to %d decimals' % decimal)) File "C:\Python34\lib\site-packages\numpy\testing\utils.py", line 644, in assert_array_compare raise AssertionError(msg) AssertionError: Arrays are not almost equal to 6 decimals (mismatch 100.0%) x: array([ 0.1892781 , 1. , 0.30368426, 0.30368426, 0.06227148, 0.18297787, 0.30368426]) y: array([ 1. , 0.79697112, 0.51113591, 0.00201155, 0.28611295, 0.4936433 , 0.00201155]) It seems to fail in about 2/3 of runs. Is this benign? Cheers, Matthew
On Wed, May 21, 2014 at 11:03 AM, Matthew Brett <matthew.brett@gmail.com>wrote:
Hi,
On Sat, May 17, 2014 at 7:43 AM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
On Fri, May 16, 2014 at 10:01 PM, Matthew Brett <matthew.brett@gmail.com
wrote:
Hi guys,
Am I right in thinking we don't have binary installers for Pythons 3.3 and 3.4 for Scipy 0.14.0?
You're right.
Is this because of the need for VS 10? [1]
This is because my build environment (Wine on OS X) refuses to install Python 3.3/3.4, and I have not yet switched to an alternative setup. I
think
Julian built 3.3/3.4 installers on Linux, so it should still be possible with Wine.
Are there plans for these guys? Can I help?
If you'd be willing to fix this situation, that would be fantastic. There's a plan on my todo list that says "fix this", but my todo list never seems to get shorter......
I built them on Windows, it was a bit ugly, notes here:
https://github.com/numpy/numpy/wiki/building_scipy_superpack
I tested them on a clean virtual machine. The Python 3.4 test run found the same intermittent failure that Christoph found here:
http://mail.scipy.org/pipermail/scipy-dev/2013-August/019118.html
Error message:
====================================================================== FAIL: test_windows.test_windowfunc_basics ---------------------------------------------------------------------- Traceback (most recent call last): File "C:\Python34\lib\site-packages\nose\case.py", line 198, in runTest self.test(*self.arg) File "C:\Python34\lib\site-packages\scipy\signal\tests\test_windows.py", line 100, in test_windowfunc_basics assert_array_almost_equal(w1, w2) File "C:\Python34\lib\site-packages\numpy\testing\utils.py", line 811, in assert_array_almost_equal header=('Arrays are not almost equal to %d decimals' % decimal)) File "C:\Python34\lib\site-packages\numpy\testing\utils.py", line 644, in assert_array_compare raise AssertionError(msg) AssertionError: Arrays are not almost equal to 6 decimals
(mismatch 100.0%) x: array([ 0.1892781 , 1. , 0.30368426, 0.30368426, 0.06227148, 0.18297787, 0.30368426]) y: array([ 1. , 0.79697112, 0.51113591, 0.00201155, 0.28611295, 0.4936433 , 0.00201155])
It seems to fail in about 2/3 of runs.
Is this benign?
Only if you don't use that function :) I have seen that error myself when building packages @ Enthought, I never took the time to track it down.
Cheers,
Matthew _______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
Hi, On Wed, May 21, 2014 at 5:32 AM, David Cournapeau <cournape@gmail.com> wrote:
On Wed, May 21, 2014 at 11:03 AM, Matthew Brett <matthew.brett@gmail.com> wrote:
Hi,
On Sat, May 17, 2014 at 7:43 AM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
On Fri, May 16, 2014 at 10:01 PM, Matthew Brett <matthew.brett@gmail.com> wrote:
Hi guys,
Am I right in thinking we don't have binary installers for Pythons 3.3 and 3.4 for Scipy 0.14.0?
You're right.
Is this because of the need for VS 10? [1]
This is because my build environment (Wine on OS X) refuses to install Python 3.3/3.4, and I have not yet switched to an alternative setup. I think Julian built 3.3/3.4 installers on Linux, so it should still be possible with Wine.
Are there plans for these guys? Can I help?
If you'd be willing to fix this situation, that would be fantastic. There's a plan on my todo list that says "fix this", but my todo list never seems to get shorter......
I built them on Windows, it was a bit ugly, notes here:
https://github.com/numpy/numpy/wiki/building_scipy_superpack
I tested them on a clean virtual machine. The Python 3.4 test run found the same intermittent failure that Christoph found here:
http://mail.scipy.org/pipermail/scipy-dev/2013-August/019118.html
Error message:
====================================================================== FAIL: test_windows.test_windowfunc_basics ---------------------------------------------------------------------- Traceback (most recent call last): File "C:\Python34\lib\site-packages\nose\case.py", line 198, in runTest self.test(*self.arg) File "C:\Python34\lib\site-packages\scipy\signal\tests\test_windows.py", line 100, in test_windowfunc_basics assert_array_almost_equal(w1, w2) File "C:\Python34\lib\site-packages\numpy\testing\utils.py", line 811, in assert_array_almost_equal header=('Arrays are not almost equal to %d decimals' % decimal)) File "C:\Python34\lib\site-packages\numpy\testing\utils.py", line 644, in assert_array_compare raise AssertionError(msg) AssertionError: Arrays are not almost equal to 6 decimals
(mismatch 100.0%) x: array([ 0.1892781 , 1. , 0.30368426, 0.30368426, 0.06227148, 0.18297787, 0.30368426]) y: array([ 1. , 0.79697112, 0.51113591, 0.00201155, 0.28611295, 0.4936433 , 0.00201155])
It seems to fail in about 2/3 of runs.
Is this benign?
Only if you don't use that function :)
I have seen that error myself when building packages @ Enthought, I never took the time to track it down.
OK then to upload these binaries to sourceforge? I'll try and debug the error later today. Cheers, Matthew
On Wed, May 21, 2014 at 5:32 AM, David Cournapeau <cournape@gmail.com> wrote:
On Wed, May 21, 2014 at 11:03 AM, Matthew Brett <matthew.brett@gmail.com> wrote:
Hi,
On Sat, May 17, 2014 at 7:43 AM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
On Fri, May 16, 2014 at 10:01 PM, Matthew Brett <matthew.brett@gmail.com> wrote:
Hi guys,
Am I right in thinking we don't have binary installers for Pythons 3.3 and 3.4 for Scipy 0.14.0?
You're right.
Is this because of the need for VS 10? [1]
This is because my build environment (Wine on OS X) refuses to install Python 3.3/3.4, and I have not yet switched to an alternative setup. I think Julian built 3.3/3.4 installers on Linux, so it should still be possible with Wine.
Are there plans for these guys? Can I help?
If you'd be willing to fix this situation, that would be fantastic. There's a plan on my todo list that says "fix this", but my todo list never seems to get shorter......
I built them on Windows, it was a bit ugly, notes here:
https://github.com/numpy/numpy/wiki/building_scipy_superpack
I tested them on a clean virtual machine. The Python 3.4 test run found the same intermittent failure that Christoph found here:
http://mail.scipy.org/pipermail/scipy-dev/2013-August/019118.html
Error message:
====================================================================== FAIL: test_windows.test_windowfunc_basics ---------------------------------------------------------------------- Traceback (most recent call last): File "C:\Python34\lib\site-packages\nose\case.py", line 198, in runTest self.test(*self.arg) File "C:\Python34\lib\site-packages\scipy\signal\tests\test_windows.py", line 100, in test_windowfunc_basics assert_array_almost_equal(w1, w2) File "C:\Python34\lib\site-packages\numpy\testing\utils.py", line 811, in assert_array_almost_equal header=('Arrays are not almost equal to %d decimals' % decimal)) File "C:\Python34\lib\site-packages\numpy\testing\utils.py", line 644, in assert_array_compare raise AssertionError(msg) AssertionError: Arrays are not almost equal to 6 decimals
(mismatch 100.0%) x: array([ 0.1892781 , 1. , 0.30368426, 0.30368426, 0.06227148, 0.18297787, 0.30368426]) y: array([ 1. , 0.79697112, 0.51113591, 0.00201155, 0.28611295, 0.4936433 , 0.00201155])
It seems to fail in about 2/3 of runs.
Is this benign?
Only if you don't use that function :)
I have seen that error myself when building packages @ Enthought, I never took the time to track it down.
I tracked it down to different values returned from calls to linalg.eig on the same input data : https://github.com/scipy/scipy/issues/3675 Cheers, Matthew
participants (3)
-
David Cournapeau -
Matthew Brett -
Ralf Gommers