On Tue, Feb 24, 2015 at 4:24 PM, Daniel Holth <dho...@gmail.com> wrote: > > That might mostly do what you want, since tox could install any > additional test requirements based on its configuration.
Does "that" refer to using tests_require=['tox'] as I described below? This means using easy_install implicitly and being exposed to easy_install bugs. Note that my attempts to avoid easy_install so far led to dependency hell starting from the need to install virtualenv. Unlike setuptools, pip does not seem to be able to install dependencies in a temporary directory. It wants a full-blown venv tree. > > > On Tue, Feb 24, 2015 at 4:21 PM, Alexander Belopolsky > <alexander.belopol...@gmail.com> wrote: > > > > On Tue, Feb 24, 2015 at 2:03 PM, Daniel Holth <dho...@gmail.com> wrote: > >> > >> > Is there a recommended way to invoke pip from setup.py? When I specify > >> > "tests_require=" and run "python setup.py test", the requirements get > >> > installed using setuptools' easy_install function. > >> > >> The solution is to not do that. A substitute is to specify your test > >> requirements in a [test] extra and install them with pip or to run > >> tests with tox. This gives control of the installer back to the user > >> instead of the setup.py author. > > > > > > Isn't this a chicken and egg problem? I currently have > > > > tests_require=['tox'], > > > > and this is exactly what tox recommends: > > > > https://testrun.org/tox/latest/example/basic.html#integration-with-setuptools-distribute-test-commands > > > > > > Note that my CI box is a CentOS 6.5 with Python 2.6.6, setuptools 0.6. This > > is still a very common server configuration. What is the recommended way to > > bootstrap tox in such environment? > >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
