Excerpts from Robert Collins's message of 2015-07-09 10:37:17 +1200: > I don't remember if this has previously been discussed, but as our > Python3 readiness increases folk are going to feel pain from testr due > to a silly Python 2/3 incompatibility around dbm files. > > https://bugs.launchpad.net/testrepository/+bug/1212909 > > OpenStack (alone in the universe as far as I can tell) installs > testrepository *inside* a tox venv. This then causes the timing > database to be Python version specific. It also causes the test venv > to suck in any dependencies testr might add. > > But testrepository is like tox- its meant to be installed systemwide > (or at least in its own venv) and then just used to *run* test runners > within whatever context. > > So - I'm looking to: > > A) have a discussion and identify any issues with moving testr out of > the venvs. (Note: this doesn't mean stop using it, just removing it > from test-requirements.txt, in the same way that tox isn't in > test-requirements.txt). > B) Capture that in a spec if its non-trivial. > C) find volunteers to make it happen.
How much work would it be to make testrepository use a database format that would be the same under all versions of python? Doug __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
