Project structure - Best practices

Aaron Watters aaron.watters at gmail.com
Mon Dec 1 00:16:46 CET 2008


On Nov 30, 11:55 am, "Filip Gruszczyński" <grusz... at gmail.com> wrote:
> >http://jcalderone.livejournal.com/39794.html
>
> That's exactly what I have read before posting here ;-)
>
> --
> Filip Gruszczyński

I too would like to see a meatier discussion of best practices
for python packagizing.  I particularly object to jcalderone's
suggestion that all tests should be within the package.  Often my
test cases are 100 times the size of the code, if you include
sample data -- it doesn't make sense to install it, I think.

Lately I tend to have something like

root/
   setup.py
   README.txt
   packagename/
       main source modules
       submodules...
   test/
       test code and submodules
   doc/
   scripts/
   testdata/
   demos/
etcetera...  I have no real idea if this is a good
way to do it, but it works for me in isolation.

I'm completely confused about any implications related to
integrated system testing or "easyinstall"...

Wise, pragmatic advice would be appreciated.  (But if we
could avoid the "buzzillion directories" approach prevalent
in the java alternative universe, that would be nice.)
   -- Aaron Watters

===
Now we see the violence inherent in the system!
Help! Help! I'm being repressed!




More information about the Python-list mailing list