On Tue, Feb 17, 2009 at 06:06:20AM -0800, Istvan Albert wrote: -> On Feb 16, 8:51?pm, "C. Titus Brown" <[email protected]> wrote: -> -> > 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. -> -> yes, my thoughts exactly. -> -> there is one slight usability issue, in that if you have an older -> pyrex, it will exit with an error message rather than continuing on -> with compiling the C files (that it would do if you had no pyrex at -> all). -> -> It is not clear what the right behavior is here, continuing on could -> mask the message ending up causing a lot more frustrating situations.
Yes, I did actually run across this. I upgraded my Pyrex ;). How about outputting a warning and then continue by just using the C code? Then people who have no idea what Pyrex is can just ignore the warning, and those who know (== developers of some sort) will get notified. 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 -~----------~----~----~----~------~----~------~--~---
