A thought on catching setup.py related problems early. mkdir sdist-test cd sdist-test hg clone .../satchmo satchmo cd satchmo python setup.py sdist -d .. (cd .. ; tar zxpvvf ../Satchmo*.tar.gz) diff -urwp -x .svn -x .hg -x dist -x build . ../Satchmo-*/.
If SOURCES.txt is being created correctly by setuptools, the only difference should be an egg_info section of setup.cfg. If it's broken (like the current issues with satchmo-trunk checked out with current subversion)... you'll get a fair amount of Only in ./docs: _static Only in ./docs: _templates Only in .: ez_setup.py type output. I realize that you don't use setup.py in your deployments, but I'd much prefer the most automated and repeatable process available for deploying satchmo (Or anything else) in its own sandbox. Setuptools provides a lot of automation, including dependencies. Granted, it also provides a lot of brokenness :-). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
