In getting a working dev instance running at dev.melkjug.org, I've recently had to peg melkjug trunk to specific versions of various dependencies in its setup.py to prevent incompatible newer versions from being installed:
http://trac.openplans.org/melkjug/changeset/1940 http://trac.openplans.org/melkjug/changeset/1941 http://trac.openplans.org/melkjug/changeset/1948 I remember hearing about some ups and downs to putting this in setup.py... What are best practices re dependency management? Should I be going about this some other way? There could very well be additional newer packages that are getting installed that have introduced breakages I haven't run across yet. Should I go ahead and peg trunk to all the specific package versions I have in my working local instance (installed I can't remember how long ago)?
