Marek, I suggest that you summarize Pygr's exact Pyrex version dependencies, since they seem to be multiplying... For example, I remember a couple of different Pyrex bugs that make the Pyrex version crucial. I think they're both in the issue tracker. Getting rid of "prefixed module filenames" would add a third dependency (since Istvan says this was only added in 0.9.8). I suggest you add your summary to the tracker as a new 0.8 issue "What pyrex version should pygr require?", and then the developer group can discuss and decide this issue. Finally, we'll also add this dependency information to both the documentation and setup.py pyrex version check.
-- Chris On Jan 27, 2009, at 8:48 AM, Istvan Albert wrote: >> Does this make Pyrex a required dependency, even if existing pyrexc- >> generated C files are used? > > as it is now yes, > > I suppose it would be fairly straightforward to add a behavior that > falls back to regular extension building if pyrex is not present yet > the C files are there. > > 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 -~----------~----~----~----~------~----~------~--~---
