borg/tox.ini

# tox configuration - if you change anything here, run this to verify:
# fakeroot -u tox --recreate

[tox]
envlist = py32, py33, py34, py35

[testenv]
# Change dir to avoid import problem for cython code. The directory does
# not really matter, should be just different from the toplevel dir.
changedir = {toxworkdir}
deps = -rrequirements.d/development.txt
commands = py.test --cov=borg --pyargs {posargs:borg.testsuite}
# fakeroot -u needs some env vars:
passenv = *
improved tox configuration, documented there how to invoke it the usage of some py.test features in the previous locking changesets somehow broke the test environment. it seems to help to point py.test to some specific package or module (and not just invoke "py.test" without arguments). 2015-07-13 16:45:49 +00:00			`# tox configuration - if you change anything here, run this to verify:`
			`# fakeroot -u tox --recreate`

Packaging improvements 2013-06-24 11:53:02 +00:00			`[tox]`
more platform support, works on py 3.5 xattrs and ACLs on OpenBSD and NetBSD need development or adaptation of the platform-specific code. 2015-09-16 09:44:53 +00:00			`envlist = py32, py33, py34, py35`
Packaging improvements 2013-06-24 11:53:02 +00:00
			`[testenv]`
improved tox configuration, documented there how to invoke it the usage of some py.test features in the previous locking changesets somehow broke the test environment. it seems to help to point py.test to some specific package or module (and not just invoke "py.test" without arguments). 2015-07-13 16:45:49 +00:00			`# Change dir to avoid import problem for cython code. The directory does`
			`# not really matter, should be just different from the toplevel dir.`
			`changedir = {toxworkdir}`
add development.txt and modify tox.ini 2015-07-25 13:39:42 +00:00			`deps = -rrequirements.d/development.txt`
fix test coverage / codecov.io, use xcode6.4 2015-08-07 23:55:46 +00:00			`commands = py.test --cov=borg --pyargs {posargs:borg.testsuite}`
improved tox configuration, documented there how to invoke it the usage of some py.test features in the previous locking changesets somehow broke the test environment. it seems to help to point py.test to some specific package or module (and not just invoke "py.test" without arguments). 2015-07-13 16:45:49 +00:00			`# fakeroot -u needs some env vars:`
			`passenv = *`