[Notes] [Git][BuildStream/buildstream][phil/tox-vev-environment] tox.ini: Add 'venv' environment to run arbitrary commands in a venv

[Phil Dawson <gitlab mg gitlab com>]

Title: GitLab

Phil Dawson pushed to branch phil/tox-vev-environment at BuildStream / buildstream

Commits:

• 3cd7a184
  by Phil Dawson at 2019-02-14T12:27:37Z

  tox.ini: Add 'venv' environment to run arbitrary commands in a venv
  
  This is a handy way for developers to make use of the venvs we're
  constructing for our test suite to run in.
  

2 changed files:

• CONTRIBUTING.rst
• tox.ini

Changes:

CONTRIBUTING.rst

---

...	...	@@ -1585,6 +1585,15 @@ can run ``tox`` with ``-r`` or ``--recreate`` option.
1585	1585
1586	1586	./setup.py test --addopts 'tests/frontend/buildtrack.py::test_build_track'
1587	1587
	1588	+.. tip::
	1589	+
	1590	+ We also have an environment called 'venv' which takes any arguments
	1591	+ you give it and runs them inside the same virtualenv we use for our
	1592	+ tests::
	1593	+
	1594	+ tox -e venv -- <your command(s) here>
	1595	+
	1596	+ Any commands after ``--`` will be run a virtualenv managed by tox.
1588	1597
1589	1598	Observing coverage
1590	1599	~~~~~~~~~~~~~~~~~~

tox.ini

---

...	...	@@ -91,3 +91,10 @@ commands =
91	91	deps =
92	92	click-man >= 0.3.0
93	93	-rrequirements/requirements.txt
	94	+
	95	+#
	96	+# Usefull for running arbitrary scripts in a BuildStream virtual env
	97	+#
	98	+[testenv:venv]
	99	+commands = {posargs}
	100	+whitelist_externals = *

—
View it on GitLab.
You're receiving this email because of your account on gitlab.com. If you'd like to receive fewer emails, you can adjust your notification settings.