Opened 12 years ago
Closed 11 years ago
#38174 closed update (fixed)
py*-numpy @1.6.2_1: Update to 1.7 available
Reported by: | cdeil (Christoph Deil) | Owned by: | dh@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | michaelld (Michael Dickens), stromnov (Andrey Stromnov) | |
Port: | py-numpy |
Description
Numpy 1.7 was released Feb 10.
Is it possible to update the numpy port?
I guess because so many scientific Python packages depend on this there should be some testing first?
Let me know if I can help!
Change History (4)
comment:1 Changed 12 years ago by cdeil (Christoph Deil)
comment:2 Changed 12 years ago by larryv (Lawrence Velázquez)
Cc: | dh@… removed |
---|---|
Owner: | changed from macports-tickets@… to dh@… |
Summary: | py-numpy: Please update to 1.7 → py*-numpy @1.6.2_1: Update to 1.7 available |
Version: | 2.1.3 |
Thanks for the ticket.
comment:3 Changed 12 years ago by cdeil (Christoph Deil)
It seems numpy 1.7 contains a memory leak that e.g. affects scikit-learn:
- https://github.com/numpy/numpy/issues/2969
- https://github.com/scikit-learn/scikit-learn/issues/1715
I don't know how serious it is, but given that probably zero Python packages rely on numpy 1.7 features at the moment, it might be a good idea to wait for numpy 1.7.1 before upgrading numpy in Macports.
comment:4 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | michaelld@… stromnov@… added |
---|---|
Resolution: | → fixed |
Status: | new → closed |
py-numpy was updated to 1.7.1 in r105000.
Note: See
TracTickets for help on using
tickets.
Currently there is a
py33-numpy
port, but the build fails on Mac OS X 10.7 (see log https://gist.github.com/cdeil/5019928 ).This is a known issue with numpy 1.6.2 that won't be fixed: https://github.com/numpy/numpy/issues/673