Re: [gnulib-tool-py] Separate classes into different packages

[Bruno Haible]

Hi Dmitriy,

> What do you think if I'll separate each class into standalone script? Here
> is the proposed hierarchy:
> 
> pygnulib/
>     __init__.py
>     constants.py
>     classes.py
>     GNULibMode.py
>     GNULibImport.py
>     GNULibModule.py
>     GNULibTestDir.py
>     GNULibMegaTestDir.py
>     [ET CETERA]

Such a structure can also be made at the end, in August. Therefore the
decision whether to do it now or later is solely: which code structure
allows you to work more efficiently? If you are searching around within
the file frequently, then it's easier to work with a single file than
with multiple files. On the other hand, if you use the scrollbar (of 'kate')
frequently to find a certain piece of code, then it's easier to work
with a set of smaller files.

There have been nearly religious wars about this topic, at times when
text editors that are capable of opening multiple files at once were
rare. It was wasted religious zeal. It all comes down to a metter of
efficiency.

Bruno