[Pyrex] Pyrex idioms and optimizations?

[Jim Kleckner]

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.

William Stein wrote:

>>>     CompiledPython
>> What about "Pyreks" or "Pyfix"? Or maybe just "Pyrex2".
> 
> We thought of some of these names.  I'm worried that Pyrex2 might just be
> annoying to Greg, since it basically says our project is the next version of
> Pyrex or something.  Pyreks is tempting, but I think it is only fair to Pyrex
> to choose a genuinely different name than "Pyrex".  I'm not sure what
> the motivation for "Pyfix" is.     My viewpoint might completely change if
> Greg were to comment on all this.

Greg, I'm very grateful for your work and you respond amazingly fast
to a wide variety of queries.  Can you at least respond about
whether it would bother you to set up a repository for the code?