> +1, although to jumpy to the defence of whoever did the commit, it's not > obvious that such a change breaks virtualenv because there are not > tests. > Maybe we should setup a buildbot to run virtualenv's tests with the > nightly pypy? > I didn't do that when I added virtualenv support for the simple reason > that at that time virtualenv had no tests, but maybe the situation > improved nowadays?
There are unit tests and an integration test that would have caught it, see https://github.com/pypa/virtualenv/blob/develop/.travis.yml and https://travis-ci.org/pypa/virtualenv . Travis doesn't have up to date PyPy nightlies, they were using a PPA that is lagging behind: https://launchpad.net/~pypy/+archive/ppa _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
