Python organising small project/script

Lot of ground to cover here, you might be better served by splitting these points up into individual questions / queries : )

1. I'd resist splitting classes into individual files unnecessarily. Some classes may depend heavily on others, and I (personally) like to keep them in the same file. I feel that the best convention is to create files based on functionality, rather than a separate file for each class.

   I've taken a lot of inspiration by work from Pocoo projects like Flask and Jinja2. The Jinja2 source provides an excellent example of "bundling" certain related classes within files: Github

2. Standalone scripts typically use something like if __name__ == '__main__', to check if is executed directly (e.g. python scriptname.py), and then execute a function typically main() afterwards (thanks Mike for correcting my mistake).

   To better assist in resolving your issue of main not being called, i'd suggest showing the code your are trying to use.

3. There are many different ways to do this, but the convention seems to be in a tests, test, testsuite directory inside your project. The latter part of this question gets quite tricky, because Python imports vary depending on the structure/type of your Python project (is it a Python package? a standalone collection of scripts?) and your PYTHONPATH.

   This SO post is a wonderful place to start in regards to considering where to put your tests, although the general answer seems to be "wherever is best for you/your team" : ).

   On a slightly related note, I'd also suggest looking into the Nose testing framework, as it removes a lot of the boilerplate from testing with Python.

I will answer questions 1 and 2.

1) This depends. If your classes are small then it is OK to put them in the same file. If they get big they are usually kept in separate files.
2) No, there does not need to be a main method. However, for a script, this is a mighty common idiom:

def main():
    # Your code

# At the bottom of the file
if __name__ == '__main__':
    main()

This way, your main will only get run when the file is run as a script, but it won't be run when imported as a module. Python will just execute any code it encounters not in a function when you import the module, so this protects you if you want to reuse a script as a module later.

This is just an idiom, main has no special meaning in python so you don't have to call it or anything.

1. Does not have to, but if the class is used by several other files/classes it should.
2. It is a good practice see What does <if __name__==“__main__”:> do?
3. Python looks at $PYTHONPATH which is a list of directories to find modules in. You can put modules in subdirectories of one of these directories and import them with import directoryname.module.. You can import a class by from directoryname.module import ClassName.