[Pytest-commit] Issue #450: pytest --fixtures console output should not include text formatted as rst source (hpk42/pytest)

2014-02-10 Thread Jurko Gospodnetić
New issue 450: pytest --fixtures console output should not include text formatted as rst source https://bitbucket.org/hpk42/pytest/issue/450/pytest-fixtures-console-output-should-not Jurko Gospodnetić: When running pytest --fixtures, console output includes text formatted as *rst* source such a

[Pytest-commit] Issue #455: Using xdist with -f option runs tests twice on a detected test source code change (hpk42/pytest)

2014-02-10 Thread Jurko Gospodnetić
New issue 455: Using xdist with -f option runs tests twice on a detected test source code change https://bitbucket.org/hpk42/pytest/issue/455/using-xdist-with-f-option-runs-tests-twice Jurko Gospodnetić: When using the xdist plugin and with its ```-f``` option to wait for source changes and aut

[Pytest-commit] Issue #456: Test with fixtures that share a parent fixture not getting called (hpk42/pytest)

2014-02-10 Thread brettatoms
New issue 456: Test with fixtures that share a parent fixture not getting called https://bitbucket.org/hpk42/pytest/issue/456/test-with-fixtures-that-share-a-parent brettatoms: I'm not sure how to really describe this but here's a code sample that demonstrates the issue. Basically if I create a

[Pytest-commit] Issue #449: better indicate that there were xpassed test results in a test run (hpk42/pytest)

2014-02-10 Thread Jurko Gospodnetić
New issue 449: better indicate that there were xpassed test results in a test run https://bitbucket.org/hpk42/pytest/issue/449/better-indicate-that-there-were-xpassed Jurko Gospodnetić: This is a usability related enhancement suggestion. When running tests what I really want to know first is:

[Pytest-commit] Issue #451: Incorrectly formatted PDF documentation tables in chapter 7 (hpk42/pytest)

2014-02-10 Thread Jurko Gospodnetić
New issue 451: Incorrectly formatted PDF documentation tables in chapter 7 https://bitbucket.org/hpk42/pytest/issue/451/incorrectly-formatted-pdf-documentation Jurko Gospodnetić: Tables in [pytest PDB documentation chapter 7](https://pytest.org/latest/pytest.pdf#chapter.7) are badly formatted an

[Pytest-commit] Issue #454: Console output text color missing when pytest run using xdist's -f option (hpk42/pytest)

2014-02-10 Thread Jurko Gospodnetić
New issue 454: Console output text color missing when pytest run using xdist's -f option https://bitbucket.org/hpk42/pytest/issue/454/console-output-text-color-missing-when Jurko Gospodnetić: When running a test suite using pytest and its xdist plugin without using xdist's ```-f``` command-line

[Pytest-commit] Issue #452: Incorrect capfd description/documentation (hpk42/pytest)

2014-02-10 Thread Jurko Gospodnetić
New issue 452: Incorrect capfd description/documentation https://bitbucket.org/hpk42/pytest/issue/452/incorrect-capfd-description-documentation Jurko Gospodnetić: When you run ```py.test --fixtures``` you get the following output: ``` #!text capfd enables capturing of writes to file descript

[Pytest-commit] Issue #453: assertion rewriting fails with object whose __repr__ contains '{\n' (hpk42/pytest)

2014-02-10 Thread Tim Sampson
New issue 453: assertion rewriting fails with object whose __repr__ contains '{\n' https://bitbucket.org/hpk42/pytest/issue/453/assertion-rewriting-fails-with-object Tim Sampson: Consider the following: ``` #!python resp = self.user.service.content.get_journal(initial_sync=True) >

[Pytest-commit] Issue #457: parser.addoption(type="float") backwards incompatibility (hpk42/pytest)

2014-02-10 Thread Floris Bruynooghe
New issue 457: parser.addoption(type="float") backwards incompatibility https://bitbucket.org/hpk42/pytest/issue/457/parseraddoption-type-float-backwards Floris Bruynooghe: The parser.addoption(type="...") api has changed from optparse to argparse and the conversion from "int" -> int and "string

[Pytest-commit] Issue #151: Specify bugfix Python version (hpk42/tox)

2014-02-10 Thread Hernan Grecco
New issue 151: Specify bugfix Python version https://bitbucket.org/hpk42/tox/issue/151/specify-bugfix-python-version Hernan Grecco: In my system, Tox is using an obsolete Python 2.6 (I guess is 2.6.1, the one installed in the system which I cannot upgrade as I do not have root privileges). I ne

[Pytest-commit] Issue #458: KeyError: 'COV_CORE_SOURCE' when clearing environment (hpk42/pytest)

2014-02-10 Thread space one
New issue 458: KeyError: 'COV_CORE_SOURCE' when clearing environment https://bitbucket.org/hpk42/pytest/issue/458/keyerror-cov_core_source-when-clearing space one: For security purposes i am clearing the environment in my application. This raises the following error in combination with coverage.

[Pytest-commit] Issue #459: doctest-modules + pyreadline means default color becomes black (hpk42/pytest)

2014-02-10 Thread Jason R. Coombs
New issue 459: doctest-modules + pyreadline means default color becomes black https://bitbucket.org/hpk42/pytest/issue/459/doctest-modules-pyreadline-means-default Jason R. Coombs: Slightly related to #399, but also different. ![color.jpg](https://bitbucket.org/repo/Kd84B/images/3291019784-color