[Pytest-commit] commit/pytest: hpk42: a new monkeypatch.replace(target, value) call which derives the

1 new commit in pytest: https://bitbucket.org/hpk42/pytest/commits/b4cd6235587f/ Changeset: b4cd6235587f User:hpk42 Date:2013-08-07 15:35:27 Summary: a new monkeypatch.replace(target, value) call which derives the monkeypatch location from target (can be class/module/function

[Pytest-commit] commit/pytest: hpk42: monkeypatch.replace() now only accepts a string. Improved error handling and

1 new commit in pytest: https://bitbucket.org/hpk42/pytest/commits/7f5dba9095f4/ Changeset: 7f5dba9095f4 User:hpk42 Date:2013-08-07 16:49:29 Summary: monkeypatch.replace() now only accepts a string. Improved error handling and docs thanks to suggestions from flub, pelme, sc

[Pytest-commit] commit/tox: 2 new changesets

2 new commits in tox: https://bitbucket.org/hpk42/tox/commits/77fe073adf32/ Changeset: 77fe073adf32 User:mgood Date:2013-08-07 02:28:33 Summary: Make "usedevelop" a [testenv] setting instead of a [tox] setting Enables setting "usedevelop" per virtualenv. If "[tox]skipsdist"

[Pytest-commit] Issue #111: tox cannot be started on itself with twice the same environment ( tox -e py27, py27) (hpk42/tox)

New issue 111: tox cannot be started on itself with twice the same environment ( tox -e py27,py27) https://bitbucket.org/hpk42/tox/issue/111/tox-cannot-be-started-on-itself-with-twice Anthon van der Neut: I am not sure it should run the same environment twice, but it should not throw an error:

[Pytest-commit] commit/tox: 2 new changesets

2 new commits in tox: https://bitbucket.org/hpk42/tox/commits/1d9e9ed68e53/ Changeset: 1d9e9ed68e53 User:mgood Date:2013-08-07 18:42:20 Summary: Update devenv example docs with "usedevelop" setting Affected #: 1 file diff -r d31aad39e16f4e3b397a0b131834b50a1c265c48 -r 1d9e