-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jan 3, 2007, at 2:29 PM, Martin v. Löwis wrote:
Guido van Rossum schrieb:
Maybe this should be done in a more systematic fashion? E.g. by giving all "internal" header files a "py_" prefix?
Yet another alternative would be to move all such header files into a py/ directory, so you would refer to them as
I think I prefer this, although I'd choose "python/object.h" just for explicitness. But if you go with a header prefix, then the shorter "py_" is fine.
FWIW, I tried to do a quick grep around some of our code and I found that the only "internal" header we include is structmember.h. Why is that not part of Python.h again?