On Wed, Jan 28, 2009 at 07:54:59AM -0800, Istvan Albert wrote: -> 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.
I have a new employee starting, Justin Flynn, who will be setting up (and more importantly, maintaining!) buildbots for the different versions of Python and pygr. So hopefully we should get a view on this soon, and be able to keep an eye on it. -> 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 I agree. I think a good target is whatever the main distros are supporting, as that's what people will generally be using. Mac OS X now supports 2.4, for example. Chris, I don't remember the rationale for 2.2 (other than "we want to maintain backwards compatibility as long as possible"). Anything more specific? 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 -~----------~----~----~----~------~----~------~--~---
