{"issue":{"user":{"id":1264587,"login":"reliable61","url":"https://api.github.com/users/reliable61","avatar_url":"https://secure.gravatar.com/avatar/c9624f2cfb3aab7ecbda3a9869c5044c?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"c9624f2cfb3aab7ecbda3a9869c5044c"},"milestone":null,"title":"Overall modularity of the system to fine grained","created_at":"2011-12-16T05:14:31Z","labels":[],"updated_at":"2011-12-16T05:14:31Z","state":"open","id":2576455,"html_url":"https://github.com/cuckoobox/cuckoo/issues/17","closed_at":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"body":"Often I find that the code is too modular as in f.e. the logging module is made up of four files which could be easily put into the __init__.py file and thus be available with a simple \"from cuckoo import logging\" . Why splitting logic to that extend. It not a bad programming practice to define two/more classes/functions in the same file unless they are huge and/or have a completely different purpose which is not the case in the above example. The reason to put them together is much easier readability of the code for example if it would be only a logging.py file in the cuckoo directory. Besides putting empty directories in the source tree is absolutely unnecessary and confusing to the reader. Those can easily be created during runtime where they belong to anyway.","number":17,"url":"https://api.github.com/repos/cuckoobox/cuckoo/issues/17","comments":0,"assignee":null},"action":"opened"}