Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How should I organize Python source code? [closed]

I'm getting started with Python (it's high time I give it a shot), and I'm looking for some best practices.

My first project is a queue which runs command-line experiments in multiple threads. I'm starting to get a very long main.py file, and I'd like to break it up. In general, I'm looking for: How do python programmers organize multiple source files? Is there a particular structure that works for you?

My specific questions include:

  1. Should each class be in a separate file?
  2. How should I organize unit tests relative to source code?
  3. Where should I put doc comments, specifically those for command-line operation?
  4. If I use multiple directories, how do I import classes between them?

I can probably draw some of my own conclusions here by trial and error, but I'd rather start from something good.

like image 362
Andres Jaan Tack Avatar asked Dec 04 '09 20:12

Andres Jaan Tack


People also ask

How do I keep my Python code organized?

Keeping your code in the same file as it grows makes your code difficult to maintain. At this point, Python modules and packages help you to organize and group your content by using files and folders. Modules are files with “. py” extension containing Python code.

Which allows you to logically organize your Python files?

A module allows you to logically organize your Python code. Grouping related code into a module makes the code easier to understand and use. A module is a Python object with arbitrarily named attributes that you can bind and reference. Simply, a module is a file consisting of Python code.

How are Python projects organized?

Organize your modules into packages. Each package must contain a special __init__.py file. Your project should generally consist of one top-level package, usually containing sub-packages. That top-level package usually shares the name of your project, and exists as a directory in the root of your project's repository.


2 Answers

The article Eric pointed to is awesome because it covers details of organising large Python code bases.

If you've landed here from Google and are trying to find out how to split one large source file into multiple, more manageable, files I'll summarise the process briefly.

Assume you currently have everything in a file called main.py:

  • Create another source file in the same folder (let's call ours utils.py for this example)
  • Move whatever classes, functions, statements, etc you need from main.py into utils.py
  • In main.py add a single line at the top: import utils

Conceptually what this does is to create a new module called utils in another source file. You can then import it wherever it's needed.

like image 192
Drew Noakes Avatar answered Sep 24 '22 22:09

Drew Noakes


The way you should organise your code and tests is exactly the same you would for any OO language.

Answers from the way I do it. It may not be right but works for me

  1. Depends on how your functionality is split. For my main python app I have 1 file with classes for the entry points and then packages of different bits of functionality
  2. I use PyDev for eclipse and organise it like I would for Java.
>  Workspace >     | >     |-Src >     |   |-Package1 >     |   |-Package2 >     |   |-main.py >     |-Test >         |-TestPackage1 >         |-TestPackage2 
  1. Use DocString everywhere to keep track of everything
  2. After making sure that the relevant __init__.py files are in the folders. its just a simple case of from module import class
like image 38
AutomatedTester Avatar answered Sep 25 '22 22:09

AutomatedTester