[13:53] <skay> cjwatson: the readme in python-oops-datedir-repo is missing a step for testing. is the launchpad-dev still using the same build/testing scheme for launchpad projects? if so, could you point me to a more fleshed out readme?
[13:54] <skay> cjwatson: but if not, is there a good repo I can use as a reference to get this one up to date so that it is consistent with what your team does?
[13:55] <skay> otherwise I can run around going weeeeeee and use some trendy testing tool like python unittest or pytest or something :p :)
[13:57] <skay> (this is a really minor bug, but we use this repo for an internal django repo that I'm finally upgrading and I'm taking the opportunity to trim our dependencies down)
[13:57] <skay> pipdeptree is pretty awesome for helping map out transitive dependencies
[14:39] <cjwatson> skay: Sorry, I've never looked at this codebase significantly, and the various repos that use buildout are all a bit of a mess in different ways.  If I were you I'd just get it to the point where it has a more or less standard setup.py and requirements.txt such that it's possible to set up a suitable virtualenv with pip, and env/bin/python -m unittest discover -v or something built on top of that
[14:39] <cjwatson> skay: Most of our repositories use buildout for historical reasons, but it's no longer what we prefer
[14:39] <skay> ack
[14:40] <cjwatson> skay: I guess turnip (which is in git) is the most modern build system we have