[RFC] Pyrex .c file versioning

[Martin Pool]

I'm also about -0.75 on having them stored in the trunk.  In fact, I'd
rather not store them at all until we really know there is a
significant problem.

Pyrex is one of several platform components that might highlight bugs
either in bazaar or the platform.  If and when we have a bug we have a
choice to either fix or workaround it in Bazaar, or take special steps
for that platform - for example we could refuse to build with a
version of Pyrex that's known to be broken.  We will still need to
deal with those problems when Bazaar developers regenerate the files.

There are pros and cons on either side and it seems to me this is
better settled by experiment.  I think it's easier to start out clean
and compromise later if necessary, so what I would like is that we
check in just the pyrex source for now.  If it turns out later that
generating the C files is causing trouble, we can take steps to fix
that.

-- 
Martin