I'm pleased to announce the release of NumPy 1.0.3 Hopefully, this release will work better with multiple interpreters as well as having some significant bugs fixed. Other changes include * x/y follows Python standard on mixed-sign division * iinfo added to provide information on integer data-types * improvements to SwIG typemaps, numpy.distutils, and f2py * improvements to separator handling in fromfile and fromstring * many, many bug fixes Thank you to everybody who contributed to the recent release. Best regards, NumPy Developers http://numpy.scipy.org
On Wed, 23 May 2007, Travis Oliphant wrote:
I'm pleased to announce the release of NumPy 1.0.3
Hopefully, this release will work better with multiple interpreters as well as having some significant bugs fixed.
Great stuff. Could you (or someone) please take care of the last 4 active tickets for the 1.0.3 milestone? http://projects.scipy.org/scipy/numpy/query?status=new&status=assigned&status=reopened&milestone=1.0.3+Release I think at least 113, 114 and 385 can be closed. Not sure about 228. Cheers. Albert
When I try to install numpy from sourses, either 1.0.2 or 1.0.3, I always get the debugged program raised the exception unhandled ".../site-packages/numpy/core/multiarray.so: undefined symbol: PyUnicodeUCS2_FromUnicode" File: /usr/local/lib/python2.5/site-packages/numpy/core/__init__.py. Line: 5 Currently I use numpy1.0b.deb Does anyone know how to fix the problem? Thx, D. Travis Oliphant wrote:
I'm pleased to announce the release of NumPy 1.0.3
Hopefully, this release will work better with multiple interpreters as well as having some significant bugs fixed.
Other changes include
* x/y follows Python standard on mixed-sign division * iinfo added to provide information on integer data-types * improvements to SwIG typemaps, numpy.distutils, and f2py * improvements to separator handling in fromfile and fromstring * many, many bug fixes
Thank you to everybody who contributed to the recent release.
Best regards,
NumPy Developers http://numpy.scipy.org
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
dmitrey wrote:
When I try to install numpy from sourses, either 1.0.2 or 1.0.3, I always get the debugged program raised the exception unhandled ".../site-packages/numpy/core/multiarray.so: undefined symbol: PyUnicodeUCS2_FromUnicode" File: /usr/local/lib/python2.5/site-packages/numpy/core/__init__.py. Line: 5
There is most likely a problem with your Python header files. For some reason you are running a "wide"-build of Python (where unicode characters are 4-bytes each), but are compiling extensions to use 2-byte unicode functions. It's possible you have a /usr/local copy of Python and a /usr copy of Python built with different widths for the unicode characters and you are grabbing the wrong include files when you compile. -Travis
On Wed, May 23, 2007 at 05:31:50PM -0600, Travis Oliphant wrote:
I'm pleased to announce the release of NumPy 1.0.3
numpy 1.0.3 is causing a warning on scipy 0.5.2: In [1]: import numpy In [2]: numpy.__version__ Out[2]: '1.0.3' In [3]: import scipy /Users/mike/Library/Python/2.5/site-packages/scipy/misc/__init__.py:25: DeprecationWarning: ScipyTest is now called NumpyTest; please update your code test = ScipyTest().test In [4]: scipy.__version__ Out[4]: '0.5.2' I wasn't getting this error with numpy 1.0.1 (I skipped 1.0.2, but would be happy to check if it would be useful). Assuming that I can live with the warning message, is there anything to worry about here? Do I need to upgrade to scipy svn? -- Mike
On 5/24/07, Michael Williams <williams@astro.ox.ac.uk> wrote:
In [3]: import scipy /Users/mike/Library/Python/2.5/site-packages/scipy/misc/__init__.py:25: DeprecationWarning: ScipyTest is now called NumpyTest; please update your code test = ScipyTest().test
In [4]: scipy.__version__ Out[4]: '0.5.2'
I wasn't getting this error with numpy 1.0.1 (I skipped 1.0.2, but would be happy to check if it would be useful). Assuming that I can live with the warning message, is there anything to worry about here? Do I need to upgrade to scipy svn?
You can safely ignore it. It is just a warning; the code still works as before. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/
Anyone have plans to build the latest release to put up on pythonmac? I could do it, but I'm busy, not the most qualified, and don't want to duplicate effort. If no one else is, though, I'll try to fit it in. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov
Since I have to install a numpy on my new Mac, I'll try. Chris, you have a pre-Intel Mac to try it out on, correct? Anyone: are there issues I should be aware of besides building it Universal? ANSI v. Unicode? Should I build against older versions of Python? If so, how far back should I go? Etc. DG Christopher Barker wrote:
Anyone have plans to build the latest release to put up on pythonmac?
I could do it, but I'm busy, not the most qualified, and don't want to duplicate effort. If no one else is, though, I'll try to fit it in.
-Chris
-- ERD/ORR/NOS/NOAA <http://response.restoration.noaa.gov/emergencyresponse/>
David L Goldsmith wrote:
Since I have to install a numpy on my new Mac, I'll try. Chris, you have a pre-Intel Mac to try it out on, correct? Anyone: are there issues I should be aware of besides building it Universal? ANSI v. Unicode?
Build against the Universal python 2.4 and 2.5 distributed at pythonmac. That way you'll get something compatible with those, which is what we want. And yes, I can test on PPC. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov
OK, I'm having difficulties, so if anyone can beat me to it, that'd be great. DG David L Goldsmith wrote:
Since I have to install a numpy on my new Mac, I'll try. Chris, you have a pre-Intel Mac to try it out on, correct? Anyone: are there issues I should be aware of besides building it Universal? ANSI v. Unicode? Should I build against older versions of Python? If so, how far back should I go? Etc.
DG
Christopher Barker wrote:
Anyone have plans to build the latest release to put up on pythonmac?
I could do it, but I'm busy, not the most qualified, and don't want to duplicate effort. If no one else is, though, I'll try to fit it in.
-Chris
-- ERD/ORR/NOS/NOAA <http://response.restoration.noaa.gov/emergencyresponse/>
Hold on again, I think I did it: it works on my BSN Intel Mac and Chris is about to test it on his not-so-new PPC Mac. Assuming I built a viable product, how do I put it in the right place (i.e., @ http://pythonmac.org/packages/py25-fat/index.html)? Thanks! DG David L Goldsmith wrote:
OK, I'm having difficulties, so if anyone can beat me to it, that'd be great.
DG
David L Goldsmith wrote:
Since I have to install a numpy on my new Mac, I'll try. Chris, you have a pre-Intel Mac to try it out on, correct? Anyone: are there issues I should be aware of besides building it Universal? ANSI v. Unicode? Should I build against older versions of Python? If so, how far back should I go? Etc.
DG
Christopher Barker wrote:
Anyone have plans to build the latest release to put up on pythonmac?
I could do it, but I'm busy, not the most qualified, and don't want to duplicate effort. If no one else is, though, I'll try to fit it in.
-Chris
-- ERD/ORR/NOS/NOAA <http://response.restoration.noaa.gov/emergencyresponse/>
In article <46560757.2000005@noaa.gov>, David L Goldsmith <David.L.Goldsmith@noaa.gov> wrote:
Hold on again, I think I did it: it works on my BSN Intel Mac and Chris is about to test it on his not-so-new PPC Mac. Assuming I built a viable product, how do I put it in the right place (i.e., @ http://pythonmac.org/packages/py25-fat/index.html)? Thanks!
Put it on a server and send the link to Bob Ippolito: bob (insert at here) redivi (insert dot here) com Two other suggestions: - Include the date in your filename. That way if you have to modify the installer users can tell there's been a change. - Make it a .dmg file (e.g. by running Disk Utility and drag it onto the icon in the dock). I've found a few users have trouble with zip files. Thank you for doing this. -- Russell
Thanks, sent it to Bob over the weekend; sorry, I'm pretty sure I didn't include the date in the filename, and Bob specifically requested a zip (after I sent him a mkpg, I believe), so that's what I sent him - Bob, do you need me to repackage and send again? DG Russell E Owen wrote:
In article <46560757.2000005@noaa.gov>, David L Goldsmith <David.L.Goldsmith@noaa.gov> wrote:
Hold on again, I think I did it: it works on my BSN Intel Mac and Chris is about to test it on his not-so-new PPC Mac. Assuming I built a viable product, how do I put it in the right place (i.e., @ http://pythonmac.org/packages/py25-fat/index.html)? Thanks!
Put it on a server and send the link to Bob Ippolito: bob (insert at here) redivi (insert dot here) com
Two other suggestions: - Include the date in your filename. That way if you have to modify the installer users can tell there's been a change. - Make it a .dmg file (e.g. by running Disk Utility and drag it onto the icon in the dock). I've found a few users have trouble with zip files.
Thank you for doing this.
-- Russell
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
-- ERD/ORR/NOS/NOAA <http://response.restoration.noaa.gov/emergencyresponse/>
participants (8)
-
Albert Strasheim -
Christopher Barker -
David L Goldsmith -
dmitrey -
Jarrod Millman -
Michael Williams -
Russell E Owen -
Travis Oliphant