[Python-Dev] Should the io-c modules be put in their own directory? (original) (raw)

Guido van Rossum guido at python.org
Fri Apr 3 23:32:42 CEST 2009

On Fri, Apr 3, 2009 at 2:15 PM, Benjamin Peterson <benjamin at python.org> wrote:

2009/4/3 "Martin v. Löwis" <martin at v.loewis.de>:

I just noticed that the new io-c modules were merged in the py3k branch (I know, I am kind late on the news—blame school work). Anyway, I am just wondering if it would be a good idea to put the io-c modules in a sub-directory (like sqlite), instead of scattering them around in the Modules/ directory.

Welcome back! I have no particular opinion on this. I suggest waiting for Benjamin's advice and following it :-) I would suggest to leave it as is: a) never change a running system b) flat is better than nested It doesn't make sense, though, to have the 8 files that make up the io module scattered around in a directory with scores of other ones.

I think Benjamin is right. While most of the C source is indeed exactly one level below the root, there's plenty of code that isn't, e.g. _ctypes, cjkcodecs, expat, _multiprocessing, zlib. And even Objects/stringlib.

-- --Guido van Rossum (home page: http://www.python.org/~guido/)

More information about the Python-Dev mailing list