On Jan 28, 8:35 am, "C. Titus Brown" <[email protected]> wrote:
> time. No strong reason against it, though, other than sheer
> conservatism... I'm also not sure it's 2.2 compatible.
I just tested this, code generated by pyrex 0.9.8 won't compile with
python 2.2.3
(but the original C files will). Since probably none of us is actually
using old versions of python, there is no way to really know what the
actual compatibility status is.
For example True/False were added in python 2.2.1 This means that
parts of the code that use that (and there is plenty such code) will
not run on python 2.1. Does it mean that we should swap those to 1/0s,
heck no. Also I forgot at what version but bsdbd has been
significantly improved.
Data analysis is not unlike running high performance games, you're
supposed to upgrade to reasonably recent drivers etc. so it might be
best to make the backward compatibility a moving target say -2
versions down from the latest python version
Istvan
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
