[Pytest-commit] Issue #134: Ability to specify the return code for success (hpk42/tox)

2013-11-01 Thread Laurens Van Houtven
New issue 134: Ability to specify the return code for success https://bitbucket.org/hpk42/tox/issue/134/ability-to-specify-the-return-code-for Laurens Van Houtven: Right now, tox assumes that a return code of 0 means "success". That's almost always true, but I've ran into a case where it isn't.

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

2013-11-01 Thread commits-noreply
2 new commits in pytest: https://bitbucket.org/hpk42/pytest/commits/d98f7495d1c7/ Changeset: d98f7495d1c7 Branch: multi-marks User:jameslan Date:2013-11-02 05:10:13 Summary: Support multiple marks for individual parametrized argument set Affected #: 2 files diff -r 8e6

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

2013-11-01 Thread commits-noreply
2 new commits in pytest: https://bitbucket.org/hpk42/pytest/commits/9909daf848ee/ Changeset: 9909daf848ee User:hpk42 Date:2013-10-25 16:50:05 Summary: add german pytest talk (pyconde2013) Affected #: 1 file diff -r 8e65b5b17d12942193881ddcb9a244bc470a6fff -r 9909daf848eef2