Bug#400158: numpy 1.0 available
severity 400158 grave thank you No progress on this bug for 24 days now - inflating severity please dd's give us numpy1.0.1 in etch... On Tue, 2006-12-12 at 20:08 +0100, Matthias Klose wrote: Ed Schofield writes: [...] Yes, it would be great. But I think, unfortunately, it's too late for Etch: just talked to Andreas Barth that we can upload the updated packages to unstable; once all packages are in place they may be considered for etch. So please go ahead and upload, we can't make things worse. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400158: numpy 1.0 available
On Tue, 2006-12-12 at 13:09 +1100, Ed Schofield wrote:
Matthias Klose wrote:
Marco Presi writes:
|| On Fri, 24 Nov 2006 08:48:32 +0100
|| Soeren Sonnenburg [EMAIL PROTECTED] wrote:
ss Package: python-numpy
ss Version: 1:1.0rc1-1
ss Severity: normal
ss we don't want to rc1 to be in sarge if there is 1.0-1 right ?
ss
http://sourceforge.net/project/showfiles.php?group_id=1369package_id=175103
Not really. Numpy 1.0 is not compatible both with current
versions of scipy and matplotlib.
A newver Scipy version compatible with numpy-1.0 has been
released yesterday. I am going to upload it, but I don't think
it will be possible to include both of them in Etch.
iff 1.0rc1 is incompatible with 1.0, we should try to get 1.0 into
etch. is matplotlib released in a version which compatible to 1.0?
Yes, certainly. matplotlib 0.87.7 was released soon after NumPy 1.0, but
primarily to provide compatibility for the Win / Mac crowd, since
NumPy's ABI changed between 1.0rc2 and 1.0rc3. But the API has only
changed in minor ways, and I'm fairly confident that any of the last few
releases of matplotlib (0.87.{5,6,7}) will compile and run fine against
NumPy 1.0. I guess we'd need a version bump for the soname.
I just recently installed numpy1.0 on cygwin/osx together with
matplotlib 0.87.7 and there is/was no problem using it. However travis
also mentioned that scipy lagged behind, but as this is now fixed it
would really be a good idea to get the so name change going now... and
quickly upload scipy/matplotlib afterwards.
Soeren
--
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400158: numpy 1.0 available
Soeren Sonnenburg wrote:
On Tue, 2006-12-12 at 13:09 +1100, Ed Schofield wrote:
Matthias Klose wrote:
Marco Presi writes:
|| On Fri, 24 Nov 2006 08:48:32 +0100
|| Soeren Sonnenburg [EMAIL PROTECTED] wrote:
ss Package: python-numpy
ss Version: 1:1.0rc1-1
ss Severity: normal
ss we don't want to rc1 to be in sarge if there is 1.0-1 right ?
ss
http://sourceforge.net/project/showfiles.php?group_id=1369package_id=175103
Not really. Numpy 1.0 is not compatible both with current
versions of scipy and matplotlib.
A newver Scipy version compatible with numpy-1.0 has been
released yesterday. I am going to upload it, but I don't think
it will be possible to include both of them in Etch.
iff 1.0rc1 is incompatible with 1.0, we should try to get 1.0 into
etch. is matplotlib released in a version which compatible to 1.0?
Yes, certainly. matplotlib 0.87.7 was released soon after NumPy 1.0, but
primarily to provide compatibility for the Win / Mac crowd, since
NumPy's ABI changed between 1.0rc2 and 1.0rc3. But the API has only
changed in minor ways, and I'm fairly confident that any of the last few
releases of matplotlib (0.87.{5,6,7}) will compile and run fine against
NumPy 1.0. I guess we'd need a version bump for the soname.
snip
However travis also mentioned that scipy lagged behind, but as this is now
fixed it would really be a good idea to get the so name change going now... and
quickly upload scipy/matplotlib afterwards.
Yes, it would be great. But I think, unfortunately, it's too late for Etch:
http://lwn.net/Articles/213566/
Shame on us all for not pushing for this earlier!
-- Ed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400158: numpy 1.0 available
Ed Schofield writes:
Soeren Sonnenburg wrote:
On Tue, 2006-12-12 at 13:09 +1100, Ed Schofield wrote:
Matthias Klose wrote:
Marco Presi writes:
|| On Fri, 24 Nov 2006 08:48:32 +0100
|| Soeren Sonnenburg [EMAIL PROTECTED] wrote:
ss Package: python-numpy
ss Version: 1:1.0rc1-1
ss Severity: normal
ss we don't want to rc1 to be in sarge if there is 1.0-1 right ?
ss
http://sourceforge.net/project/showfiles.php?group_id=1369package_id=175103
Not really. Numpy 1.0 is not compatible both with current
versions of scipy and matplotlib.
A newver Scipy version compatible with numpy-1.0 has been
released yesterday. I am going to upload it, but I don't think
it will be possible to include both of them in Etch.
iff 1.0rc1 is incompatible with 1.0, we should try to get 1.0 into
etch. is matplotlib released in a version which compatible to 1.0?
Yes, certainly. matplotlib 0.87.7 was released soon after NumPy 1.0, but
primarily to provide compatibility for the Win / Mac crowd, since
NumPy's ABI changed between 1.0rc2 and 1.0rc3. But the API has only
changed in minor ways, and I'm fairly confident that any of the last few
releases of matplotlib (0.87.{5,6,7}) will compile and run fine against
NumPy 1.0. I guess we'd need a version bump for the soname.
snip
However travis also mentioned that scipy lagged behind, but as this is now
fixed it would really be a good idea to get the so name change going now...
and quickly upload scipy/matplotlib afterwards.
Yes, it would be great. But I think, unfortunately, it's too late for Etch:
just talked to Andreas Barth that we can upload the updated packages
to unstable; once all packages are in place they may be considered for
etch. So please go ahead and upload, we can't make things worse.
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400158: [Deb-scipy-devel] Bug#400158: numpy 1.0 available
|| On Fri, 24 Nov 2006 08:48:32 +0100 || Soeren Sonnenburg [EMAIL PROTECTED] wrote: ss Package: python-numpy ss Version: 1:1.0rc1-1 ss Severity: normal ss we don't want to rc1 to be in sarge if there is 1.0-1 right ? ss http://sourceforge.net/project/showfiles.php?group_id=1369package_id=175103 Not really. Numpy 1.0 is not compatible both with current versions of scipy and matplotlib. A newver Scipy version compatible with numpy-1.0 has been released yesterday. I am going to upload it, but I don't think it will be possible to include both of them in Etch. Regards Marco -- I videogiochi non influenzano i bambini. Voglio dire, se Pac-Man avesse influenzato la nostra generazione, staremmo tutti saltando in sale scure, masticando pillole magiche e ascoltando musica elettronica ripetitiva. Videogames do not influence kids. I mean, if Pac-Man influenced our generation, we were all jumping in dark rooms, chomping pills and listening to electronic repeating music. Kristian Wilson, Nintendo Inc. 1989 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400158: [Deb-scipy-devel] Bug#400158: numpy 1.0 available
Marco Presi writes: || On Fri, 24 Nov 2006 08:48:32 +0100 || Soeren Sonnenburg [EMAIL PROTECTED] wrote: ss Package: python-numpy ss Version: 1:1.0rc1-1 ss Severity: normal ss we don't want to rc1 to be in sarge if there is 1.0-1 right ? ss http://sourceforge.net/project/showfiles.php?group_id=1369package_id=175103 Not really. Numpy 1.0 is not compatible both with current versions of scipy and matplotlib. A newver Scipy version compatible with numpy-1.0 has been released yesterday. I am going to upload it, but I don't think it will be possible to include both of them in Etch. iff 1.0rc1 is incompatible with 1.0, we should try to get 1.0 into etch. is matplotlib released in a version which compatible to 1.0? Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400158: numpy 1.0 available
Matthias Klose wrote:
Marco Presi writes:
|| On Fri, 24 Nov 2006 08:48:32 +0100
|| Soeren Sonnenburg [EMAIL PROTECTED] wrote:
ss Package: python-numpy
ss Version: 1:1.0rc1-1
ss Severity: normal
ss we don't want to rc1 to be in sarge if there is 1.0-1 right ?
ss
http://sourceforge.net/project/showfiles.php?group_id=1369package_id=175103
Not really. Numpy 1.0 is not compatible both with current
versions of scipy and matplotlib.
A newver Scipy version compatible with numpy-1.0 has been
released yesterday. I am going to upload it, but I don't think
it will be possible to include both of them in Etch.
iff 1.0rc1 is incompatible with 1.0, we should try to get 1.0 into
etch. is matplotlib released in a version which compatible to 1.0?
Yes, certainly. matplotlib 0.87.7 was released soon after NumPy 1.0, but
primarily to provide compatibility for the Win / Mac crowd, since
NumPy's ABI changed between 1.0rc2 and 1.0rc3. But the API has only
changed in minor ways, and I'm fairly confident that any of the last few
releases of matplotlib (0.87.{5,6,7}) will compile and run fine against
NumPy 1.0. I guess we'd need a version bump for the soname.
For a complete list of changes since 1.0rc1, see
http://www.scipy.org/ReleaseNotes/NumPy_1.0
By the way, the maintenance release NumPy 1.0.1 is now out.
-- Ed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400158: [Deb-scipy-devel] Bug#400158: numpy 1.0 available
Marco Presi wrote: || On Fri, 24 Nov 2006 08:48:32 +0100 || Soeren Sonnenburg [EMAIL PROTECTED] wrote: ss Package: python-numpy ss Version: 1:1.0rc1-1 ss Severity: normal ss we don't want to rc1 to be in sarge if there is 1.0-1 right ? ss http://sourceforge.net/project/showfiles.php?group_id=1369package_id=175103 Not really. Numpy 1.0 is not compatible both with current versions of scipy and matplotlib. I am myself using numpy svn (post 1.0) and scipy svn, with last release of matplotlib (0.87.7): they all work together since the release of numpy 1.0 and matplotlib 0.87.7 (0.87.6 did not work with numpy 1.0, if I remember correctly), AFAIK. Is the incompatibility specific to some architectures ? David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400158: numpy 1.0 available
Package: python-numpy Version: 1:1.0rc1-1 Severity: normal we don't want to rc1 to be in sarge if there is 1.0-1 right ? http://sourceforge.net/project/showfiles.php?group_id=1369package_id=175103 -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19-rc6-sonne Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages python-numpy depends on: ii atlas3-base [liblapack.s 3.6.0-20.2 Automatically Tuned Linear Algebra ii lapack3 [liblapack.so.3] 3.0.2531a-6 library of linear algebra routines ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii python 2.4.4-1 An interactive high-level object-o ii python-central 0.5.12 register and build utility for Pyt ii refblas3 [libblas.so.3] 1.2-8 Basic Linear Algebra Subroutines 3 python-numpy recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
