Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
ability to define required plugins in tox.ini #783
In many cases tox needs some plugins for adding extra functionality and at this moment there is no way for the user to declare them inside the
Ideally tox should load a
This would ease the development process as the user would not have to write bootstrapping scripts before running tox.
Current behaviour is not productive because user may run tox which would behave differently if the plugins are not installed, in many cases even passing but without intended behaviour.
Probably we can't just install the plugins automatically because
There is another side: if tox is installed along with it's plugins, in some cases they might affect the build.
I would propose:
Personally I would not mind if tox would attempt to install the package on current system (pip install --user or direct in case of virtualenv presence). I did this in few places over time and worked well. If it fails due to permissions at least it fails for 1/10 users and they will know what to do, much better than failing for 9/10 users.
Regardin @vlcinsky proposal, this is bit tricky and maybe we should approach a more flexible approach, as I seen on other systems using plugins (ansible, and even pytest if it remember well.)
With something like this we should allow users to enable plugins and control them without forcing them to change tox.ini files. We need to be sure that we avoid a case where the user has to change
added a commit
Aug 9, 2018
tox will not install packages, but will notify the user to do so, done via #936. As bonus can be used to specify general requirements of the tox run env (not just tox plugins). It has full PEP-517 support meaning you can use markers to filter for optional dependencies.