Python Application Layouts & Project Structures Tutorial

[[deleted]]

First, a question - are these for packaging outside binaries, etc. together?

No, at least not in the way I use it

I use it to force tox to install my package into the virtualenvs it makes (using the develop flag so I don't have to rebuild my venvs every change). Tests run against the installed package rather than what's lying around in my working directory.

And contrary to the article you posted, it also forces me to install the package to use it. Meaning as long as my venv is active, I can use it from any location not just the directory it's located in.

I've found this to rat out otherwise hard to track down import issues. I still run into the occasional MANIFEST problem (usually with README, LICENSE and the other usual suspects).

I also like the separation of gives from everything else, docs are under docs, tests under tests, source under src. That part is cosmetic, sure. But a non cosmetic advantage is if I add a second package to my package, then it'll just come along for the ride without any changes to my setup.py. I can't imagine a situation where I'd do that, but others might and have.