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.
I think simplicity and explicit behavior wins out. Better to be simple
and provide an easily modifiable setup.py rather than building into it
a bunch of special cases that are fixing problems that only
hypothetically exist.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
