RFC: pyrex source file naming

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Collins wrote:
> I'd like to suggest we change from
> _foo_c.pyx
> to
> _foo_pyx.pyx
> 
> - it makes it more obvious that the master code is pyrex, and not c, at
> least to me.
> 
> -Rob

Well, at one step it actually is C code. And one could argue that it stands
for "compiled".

In the end, I don't really care. I think there are a few notations that I
could switch away from. Like naming the functions themselves foo_c or foo_py.
It will be in the traceback, even if it won't be in 'func.__name__'.

For now, I'll stick with _c.pyx, but if we decide to change it, we can
probably just rename the lot of them.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIriCjJdeBCYSNAAMRAhKJAKDQZdO/asj2H8u5pHOoRRoyj/Vi5gCfYuTF
Fmle1u/9rOOZFW6JSlUscAk=
=t9KP
-----END PGP SIGNATURE-----