Ticket #1286 (closed defect: fixed)

Opened 7 years ago

Last modified 6 years ago

Obsolete Python Numeric should be replaced by NumPy

Reported by: bemasc Owned by: dsd
Priority: normal Milestone: 8.2.0 (was Update.2)
Component: distro Version:
Keywords: relnote Cc: dgilmore, cscott, bemasc
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description

As of build 368, the OS image includes the "Numeric" Python library. "Numeric" is obsolete, having been replaced by "NumArray", which is also deprecated in favor of "NumPy", which is current. Programs written for "Numeric" should be trivial to convert to "NumPy", and the authors provide automated tools for converting Python code from one to the other.

Unless there is a specific reason to continue using this obsolete library, it should be upgraded.

See  http://numpy.scipy.org/

Change History

Changed 7 years ago by jg

  • cc krstic, dcbw added
  • owner changed from sj to jg
  • component changed from library to distro
  • milestone changed from Untriaged to BTest-3

Changed 7 years ago by jg

  • owner changed from jg to J5
  • verified unset
  • milestone changed from BTest-4 to Trial-2

Changed 7 years ago by J5

Ok, we need this now. In tests creating a 960000 element array it takes 21 seconds normally and 15.5 seconds if we optimize it. With NumPy it takes 0.014 seconds. This is all at a cost of about 6M of packages (which means it is larger uncompressed) but it is well worth it since other people want this and we need it to get rid of half the time it takes to go from X to sugar. Will be in next build.

Changed 7 years ago by J5

  • status changed from new to closed
  • resolution set to fixed

in 552

Changed 7 years ago by bemasc

  • status changed from closed to reopened
  • resolution fixed deleted
  • milestone Trial-3 deleted

As of joyride-184, numpy is in the build, but so is Numeric. This is redundant, and a waste of valuable disk space. Numeric should be removed, unless something depends on it and cannot be ported. I will volunteer to port any Python apps still using Numeric.

Changed 7 years ago by jg

  • owner changed from J5 to dgilmore
  • status changed from reopened to new
  • type changed from enhancement to defect
  • cc dcbw removed
  • milestone set to Future Release

Changed 6 years ago by cscott

  • priority changed from low to normal
  • owner changed from dgilmore to bemasc
  • next_action set to never set
  • cc dgilmore added; krstic removed
  • milestone changed from Future Release to 8.2.0 (was Update.2)

Currently python-numeric is needed by pygtk2-2.12.1 and pygame-1.7.1 in F9. bemasc, can I take you up on your volunteering to fix this? Dennis can probably help you if you need Fedora-foo to make this happen.

Changed 6 years ago by bemasc

Pygame seems to be fixed in 1.8.0. pygtk is a little iffier; I'll look into it.

Changed 6 years ago by bemasc

PyGTK knows about this bug; it's  http://bugzilla.gnome.org/show_bug.cgi?id=397544

That bug links to an agreed-upon patch; they're just waiting for the next major release to break compatibility. I think we should apply that patch.

Changed 6 years ago by cscott

  • cc dsd, bemasc added
  • owner changed from bemasc to dsd

dsd, could you help bemasc shepherd this patch into our pygtk?

Changed 6 years ago by dsd

  • cc cscott added; dsd removed

I patched it and put some RPMs in my public_rpms for testing. However pygame also depends on numeric, we are still using v1.7. Do we want to fork and upgrade?

Changed 6 years ago by cscott

What's the compatibility between pygame 1.7 and 1.8? I'm fine with upgrading to pygame 1.8 for 8.2, if that doesn't break all of the pygame-based activities out there. If I'm reading  http://www.seul.org/viewcvs/viewcvs.cgi/trunk/WHATSNEW?rev=1513&root=PyGame&view=markup there weren't any "breaks old code" changes made between 1.7 and 1.8.

Maybe the best way to find out is to upgrade to 1.8, with the possibility of reverting if folks revolt. Pygame is pretty heavily used by kids learning to write activities, so it seems like keeping up to date with upstream releases would be a Good Thing.

Is there any reason why F9 didn't move to 1.8 already?

Changed 6 years ago by dsd

OK, pushed a public_rpm which dropped numeric from the build. Will give that a few days to see if any breakage appears.

Also filed an upstream bug with the other questions,  https://bugzilla.redhat.com/show_bug.cgi?id=457074

Changed 6 years ago by cscott

dsd, could you open new bugs for the activities which need to be updated as a result of this change? Thanks.

Changed 6 years ago by cscott

  • keywords relnote added

Changed 6 years ago by cscott

  • status changed from new to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.