On Mon, Feb 16, 2009 at 05:13:43PM -0800, Marek Szuba wrote:
-> On Mon, 16 Feb 2009 14:45:24 -0800
-> "C. Titus Brown" <[email protected]> wrote:
-> 
-> > Reviewed, tested on multiple platforms, appropriately extracted into a
-> > patch, and nominated for inclusion:
-> While I generally agree this is great work, there is one issue I would
-> like to raise before the patches are incorporated into the master
-> branch - it seems the update simultaneously forces Pyrex version to be
-> at least 0.9.8.
-> 
-> Given most major Linux/Unix distributions do not feature this version
-> in their repositories yet (a quick search using Google has yielded the
-> following:
->  - Debian "lenny" / Ubuntu "intrepid" - 0.9.7;
->  - Red Hat Enterprise 5 - 0.9.6;
->  - Gentoo - features 0.9.8 but only with "testing" flag set, latest
-> stable is 0.9.4;
->  - FreeBSD - 0.9.8 is in ports)
->  - Fedora 10 - the first release to offer 0.9.8;
->  - OpenBSD 4.4 - first release to offer 0.9.8;
-> etc.), I strongly suggest we should bear with problems with older Pyrex
-> versions for some more time.
-> 
-> Istvan, would you be able to disentangle the two issues?

Marek, I thought about this, and my conclusion was that it did not
matter for users.

First, we can (and should) release either pyx-compiled C code OR
binaries.  I don't think we should expect users to have a full dev
environment.

Second, Pyrex is continually being improved; there were reasonably
annoying bugs that we've had to work around in pygr because of Pyrex
problems just in the last year.  Therefore I would prefer to give people
something compiled with the latest version of Pyrex rather than expect
pygr to work properly under any recent version of Pyrex.

Another problem that I didn't mention, though, is that the patch
requires 2.4.  I think this is reasonable but it is a change that was
not explicitly agreed upon.

cheers,
--titus
-- 
C. Titus Brown, [email protected]

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pygr-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to