RFC: pyrex source file naming

[Robert Collins]

On Thu, 2008-08-21 at 21:12 -0500, John Arbash Meinel wrote:

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

Sure. The _py files get compiled too :). The point for me is that when I
tab complete I like knowing where to stop, and for _c.c vs _c.pyx I need
to remember :).

> 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__'.

I didn't realise we did this one :).

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

Sure.

-Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20080822/1934e65e/attachment-0001.pgp