Code organization
bruno at modulix
onurb at xiludom.gro
Wed Feb 15 09:07:41 EST 2006
More information about the Python-list mailing list
Wed Feb 15 09:07:41 EST 2006
- Previous message (by thread): Win32_Process.Create -- not starting process
- Next message (by thread): Code organization
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thomas Girod wrote: > Hi. > > I found a lot of documentation about how to code in Python, but not > much about how you organize your code in various modules / packages ... > As I am not yet used to python, this puzzle me a bit. > > So, can anyone explain how one should organize and store its code ? the > uses of __init__.py files ? Maybe my question is not very clear, but I > hope someone will understand anyway ... Well... As a starting point relative to Python specific stuff (use of __init__.py etc), the Fine Manual is your friend: http://www.python.org/doc/2.4.2/tut/node8.html Now for best practices and whatnots, this isn't really specific to Python. Try to have modules with high cohesion and low coupling, and it'll be fine. Eventually try to provide a facade class or function for complex packages (this is a current pattern in the standard lib). Also, python-is-not-java, so don't feel commited to putting everything in classes when plain functions would do, and avoid the 1:1 class/file Java plague !-) My 2 cents... -- bruno desthuilliers python -c "print '@'.join(['.'.join([w[::-1] for w in p.split('.')]) for p in 'onurb at xiludom.gro'.split('@')])"
- Previous message (by thread): Win32_Process.Create -- not starting process
- Next message (by thread): Code organization
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list