We practice highly componentised development using Java, we have about 250 modules in trunk that have independent life cycles. Dependencies are managed through Maven (that’s a best practice right there), every iteration (bi-weekly) actively developed modules get tagged with a new version. 3 digit version numbers with strict semantics (major.minor.build – major changes means backwards … Read more
A Python file is called a “module” and it’s one way to organize your software so that it makes “sense”. Another is a directory, called a “package”. A module is a distinct thing that may have one or two dozen closely-related classes. The trick is that a module is something you’ll import, and you need … Read more
Unix On Linux, other Unix variants, Git Bash on Windows, or Cygwin, use the jar (or unzip -v), grep, and find commands. The following lists all class files that match a given name: for i in *.jar; do jar -tvf “$i” | grep -Hsi ClassName && echo “$i”; done If you know the entire list … Read more
There’re two kind of Django “projects” that I have in my ~/projects/ directory, both have a bit different structure.: Stand-alone websites Pluggable applications Stand-alone website Mostly private projects, but doesn’t have to be. It usually looks like this: ~/projects/project_name/ docs/ # documentation scripts/ manage.py # installed to PATH via setup.py project_name/ # project dir (the … Read more
Doesn’t too much matter. Whatever makes you happy will work. There aren’t a lot of silly rules because Python projects can be simple. /scripts or /bin for that kind of command-line interface stuff /tests for your tests /lib for your C-language libraries /doc for most documentation /apidoc for the Epydoc-generated API docs. And the top-level … Read more