Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#38438 closed update (fixed)

py-numpy: update to version 1.7.0

Reported by: stromnov (Andrey Stromnov) Owned by: dh@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: haspatch Cc:
Port: py-numpy

Description


Attachments (4)

numpy-1.7.0.diff.gz (87.4 KB) - added by stromnov (Andrey Stromnov) 11 years ago.
patch-numpy-whitespace.diff (13.4 KB) - added by seanfarley (Sean Farley) 11 years ago.
whitespace change
patch-numpy-upgrade-1.7.0.diff (777.1 KB) - added by seanfarley (Sean Farley) 11 years ago.
upgrade numpy to 1.7.0
patch-numpy-default-variant.diff (1.1 KB) - added by seanfarley (Sean Farley) 11 years ago.
change default compiler variant

Download all attachments as: .zip

Change History (9)

Changed 11 years ago by stromnov (Andrey Stromnov)

Attachment: numpy-1.7.0.diff.gz added

comment:1 Changed 11 years ago by stromnov (Andrey Stromnov)

Successfully tested on ML (py24-numpy, py24-numpy+atlas+gcc45, py24-numpy+atlas+gcc47, py27-numpy, py27-numpy+atlas+gcc45, py27-numpy+atlas+gcc47, py33-numpy, py33-numpy+atlas+gcc45, py33-numpy+atlas+gcc47).

comment:2 Changed 11 years ago by seanfarley (Sean Farley)

Holy unrelated whitespace change, Batman! I've split this patch into whitespace change + updating to numpy 1.7 and also added another patch to change the default compiler to gcc 4.7. I'll attach the patches I just made to the ticket so other devs can look them over.

Also, I went ahead and removed the commented block of code for python 3.2. I just ran the test suite and it runs fine for this new version.

Changed 11 years ago by seanfarley (Sean Farley)

Attachment: patch-numpy-whitespace.diff added

whitespace change

Changed 11 years ago by seanfarley (Sean Farley)

upgrade numpy to 1.7.0

Changed 11 years ago by seanfarley (Sean Farley)

change default compiler variant

comment:3 Changed 11 years ago by mf2k (Frank Schima)

Resolution: fixed
Status: newclosed
Version: 2.1.3

comment:4 in reply to:  2 ; Changed 11 years ago by jmroot (Joshua Root)

Why remove the code for deleting unregistered .pyc files in the py32 subport? That's important to avoid activation failure for anyone who hasn't been upgrading regularly.

(Edit: never mind my original question to sean, I get it, it was commented in the original gzipped diff.)

Last edited 11 years ago by jmroot (Joshua Root) (previous) (diff)

comment:5 in reply to:  4 Changed 11 years ago by stromnov (Andrey Stromnov)

Replying to jmr@…:

Why remove the code for deleting unregistered .pyc files in the py32 subport? That's important to avoid activation failure for anyone who hasn't been upgrading regularly.

Unregister hack first time appears at r95253 (9 months ago). It's not really clear, why this hack exists at all, and exists only for py32 subport?

Note: See TracTickets for help on using tickets.