[Pyrex] Pyrex idioms and optimizations?

[Chris Mellon]

On 7/24/07, Jim Kleckner <jek-gmane at kleckner.net> wrote:
> Robert Bradshaw wrote:
>
>  > As part of the SAGE project, and due to the difficulty in getting
>  > some essential (to us) patches upstream, we have been keeping a
>  > separate branch of Pyrex named SageX. It's just Pyrex + (a bunch of
>  > patches), about many of which are optimizations (including the one
>  > mentioned above, which is a 10-fold speedup).
>
> Is SageX a proper superset of the current Pyrex?  i.e., the version
> string in the code base says:
>   version = '0.9.4.1'
> but the current is:
>   0.9.5.1a
>
> Getting the code into SourceForge or codespeak using subversion would
> allow Greg's mainline code to exist in a branch and then apply
> the changes to that code to the trunk as changes occur.
>

For what it's worth, when I tried compiling my current Pyrex projects
with Sagex I ran into 2 problems. One was relatively trivial - sagex
produces a GCC-specific output - and the other was that there was a
runtime crash (access violation) using my sagex compiled code. Since I
was just checking quickly I didn't have the time to set up a debug
Python environment (it's a fair amount of work on Windows) to find try
to find the error, although I did scan the generated source for
anything obviously wrong and found nothing. So for at least one sample
case, no, it's not a strict superset of Pyrex functionality.