[pytest-dev] next bug day: Wednesday April 2nd, 2014
holger krekel
holger at merlinux.eu
Thu Mar 27 08:23:51 CET 2014
Hi all,
it's settled, the next bug day is Wednesday coming week, 2nd April 2014.
Bound to participate:
holger krekel
Jurko Gospodnetić
Anatoly Bubenkov
Floris Bruynooghe
Ronny Pfannschmidt
Everyone else: please consider participating as well!
See you on #pylib,
holger
On Wed, Mar 26, 2014 at 09:46 +0000, holger krekel wrote:
> Hi pytest users and contributors,
>
> Since 2.5.2 we've had around 40 new issues and we need help
> to resolve these:
>
> https://bitbucket.org/hpk42/pytest/issues?status=new&status=open
>
> Please see if you can find the time to look and possibly resolve a few
> through a Pull request. Further below i'll dump the titles and issue
> links for your convenience.
>
> Furthermore we should do a new pytest bug day. Here is a doodle:
>
> http://doodle.com/k26yek52yxvsmpc8#table
>
> The one choice, the 11th April, is during Pycon in Canada but i assume i'll
> still have a lot of Jet Lag and also can make time during Canadian
> day time.
>
> best,
> holger
>
>
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/487/
> request.param mentioned in docs but not listed in the request API docs
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/486/
> `--help` should not fail with an exception on conftest.py errors / handle conftest imports more gracefully/meaningful
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/483/
> 'function' object has no attribute 'im_func' with twisted TestCases on python 3
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/481/
> Running doctests with -s fails?
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/480/
> SkipTest is not handled properly in setUpModule
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/478/
> --pyargs does not understand namespace packages
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/477/
> excluding name patterns from consideration
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/476/
> Fixtures defined in separate files are not available to tests
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/475/
> Misleading pytest exception description
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/474/
> Running tests with xdist (-n4) causes failures with Django TestCases (DB access denied)
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/473/
> Cannot use @mark and multiple @patch class decorators
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/471/
> pytest keeps running deleted tests
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/470/
> crash when a test changes the cwd to something that gets removed later on without propper cleanup
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/469/
> junitxml parses report.nodeid incorrectly
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/466/
> IOError when writing --junitxml report
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/465/
> running pytest.main(...) from python script breaks cov plugin
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/462/
> What is the correct spelling when using unicode in assertions?
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/461/
> Resources warning when combining capfd and skip()
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/460/
> AttributeError: 'SubRequest' object has no attribute 'param'
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/459/
> doctest-modules + pyreadline means default color becomes black
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/458/
> KeyError: 'COV_CORE_SOURCE' when clearing environment
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/457/
> parser.addoption(type="float") backwards incompatibility
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/455/
> Using xdist with -f option runs tests twice on a detected test source code change
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/454/
> Console output text color missing when pytest run using xdist's -f option
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/453/
> assertion rewriting fails with object whose __repr__ contains '{\n'
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/452/
> Incorrect capfd description/documentation
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/451/
> Incorrectly formatted PDF documentation tables in chapter 7
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/450/
> pytest --fixtures console output should not include text formatted as rst source
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/448/
> pytest-xdist: AttributeError: 'module' object has no attribute '__all__'
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/443/
> Misleading documentation on the "skipped/xfail" page
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/441/
> parametrized fixture + module scope + failing test + '-x' option = invalid fixture finalizer output
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/440/
> parametrized fixture output captured inconsistently
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/439/
> capsys fixture does not collect the same test output as reported by pytest
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/437/
> Different tests collected on two nodes with xdist
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/436/
> Command-line arguments that are files which exist cause conftest.py not to be loaded from the usual location
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/435/
> python_files causes reload to fail?
> ----
> new bug https://bitbucket.org/hpk42/pytest/issue/412/
> crash on bad stdout
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/488/
> Add ability to configure the "patience" of xprocess when waiting for process to start
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/485/
> xdist: --boxed test crash throws away STDOUT and STDERR even if they have data
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/468/
> guaranteed print to stdout and stderr
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/463/
> Add alias for parametrize or provide better error reporting
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/456/
> Support per-request scope for fixtures
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/449/
> better indicate that there were xpassed test results in a test run
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/442/
> Make reported captured output include function scope fixture finalizer output.
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/434/
> Standalone test script should allow custom interpreter in shebang
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/430/
> Config variable to set locations to try for conftest.py files
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/427/
> Option to have pytest rewrite assertions in additional non-test modules
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/421/
> Adding external tests to a collection
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/415/
> Allow disabling the 'assertions disabled' warning.
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/411/
> Documentation: misleading deep inspection
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/410/
> No warning when class is skipped due to __init__
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/401/
> Reduce pytest's overhead for running tests
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/393/
> non-parameterized fixtures not torn down after last use
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/391/
> "native" ipdb as well
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/390/
> support pdb.set_trace() with pytest-xdist
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/389/
> enhance readability of assertion introspection on bound methods
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/387/
> keyword-selection mechanism is too fuzzy
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/374/
> plugins reading from shared py.test config file
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/363/
> Using monkeypatch in non function scoped fixture
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/351/
> Show repr() of exceptions passed to @parametrize
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/344/
> Change doctest runner's flags
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/332/
> Logging of fixture setup
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/331/
> failure when callable object has test name prefix but no __name__
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/327/
> Add improved support for numpy testing
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/313/
> Allow callable to be passed to @pytest.mark.parametrize in order to generate tests
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/309/
> Doctest count
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/303/
> add number of tests per file back into reporting
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/301/
> serializing collection process (per host) on xdist to avoid conflicts/collection errors
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/297/
> in docs, recwarn.txt lacks any :ref: targets
> ----
> open enhancement https://bitbucket.org/hpk42/pytest/issue/295/
> lazy import of doctest in pdb breaks debugging if the environment makes doctest unimportable
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/285/
> Allow funcargs to be used in conjunction with default argument values
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/283/
> traceback filtering hook
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/282/
> allow disabling setuptools plugin discovery
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/277/
> Markers as functions
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/272/
> flush c buffers for fdcapture after each test
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/268/
> isolation when importing test modules (nose-style)
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/263/
> testscenarios support
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/259/
> Test that unexpectedly passes doesn't produce exit code
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/254/
> No visual separation between test failures in narrow terminals
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/253/
> pytest should integrate with warnings module
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/252/
> Allow fixtures to execute only once per session even if parallel running (xdist) is enabled
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/249/
> document and/or change display of parametrization values in IDs
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/230/
> Make getting test results from fixtures easier
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/228/
> Recwarn empty
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/227/
> yield and funcarg don't mix
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/207/
> remember/return returnvalues of test functions
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/204/
> allow to dynamically modify all ini-values from plugins
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/196/
> error reprs not changable availiable via hooks
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/195/
> traceback pruning not possible/changable via hooks
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/193/
> xdist: support for --boxed on windows
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/175/
> way to control how pytest-xdist runs tests in parallel?
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/174/
> Configuration Files - Add an option to read them from command line parameter or an environment variable
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/170/
> Add traceback matching for expected failures
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/167/
> pytest.call_nocapture(func, *k, **kw)
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/166/
> exposed api for generating test items
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/162/
> Store terminal width on config object
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/157/
> --verbose should report why a test case was skipped
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/155/
> Bring japanese translation online / reorg website
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/152/
> local plugin-list and early conftest opt-out
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/150/
> improve pylint / pytest compatibility
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/147/
> take a look into documenting this more complete setup.py testrunner
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/138/
> support 3.3 chained exceptions
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/137/
> Expose an "addfinalizer" to add callable items for cleanup
> ----
> open enhancement https://bitbucket.org/hpk42/pytest/issue/133/
> xdist does not color output
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/132/
> Pygmentize native tracebacks
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/122/
> allow to pass argvalues as an iterator to pytest.mark.parametrize()
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/116/
> result log to include stdout\err
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/114/
> Skip report refers to skipping plugin when using skipif marker
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/105/
> testdir funcarg is slow during setup
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/103/
> Move py.code to pytest.code
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/96/
> a segfault in a test case causes the testrunner to crash with it
> ----
> open enhancement https://bitbucket.org/hpk42/pytest/issue/82/
> sys.path is extended with every dir containg conftest.py
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/62/
> better html output for examples (sphinx highlighter)
> ----
> new enhancement https://bitbucket.org/hpk42/pytest/issue/56/
> Feature: report exceptions in threads as errors
> ----
> new task https://bitbucket.org/hpk42/pytest/issue/183/
> investigate armin rigos conftest
> ----
> new task https://bitbucket.org/hpk42/pytest/issue/161/
> investigate trouble around items with the same id
> ----
> new task https://bitbucket.org/hpk42/pytest/issue/142/
> move pastebin to plugin
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/467/
> Cache fixtures which raise pytest.skip.Exception and pytest.fail.Exception
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/446/
> Alternative syntax: allow no-argument fixture functions to be used as decorators
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/432/
> Testing docs and doc tests
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/431/
> opt-in to store the last n sets of reports
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/402/
> let the capture plugin provide a way to run code with capture suspended
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/372/
> raises regexp
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/364/
> shorter traceback style by default
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/349/
> Using fixtures in pytest.mark.parametrize
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/337/
> there is no warning when tests have the same name
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/310/
> Conditional skip and xfail in doctests
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/304/
> add option to only show tracebacks on keyboard interrup
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/291/
> tmpdir names get too long on Windows (exceeding PATH_MAX)
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/288/
> Pass test result to finalizer for cleaning up debug data
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/270/
> HINT: How to provide coloring in demo with failing tests in docs
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/255/
> Add a flag to track assertion statistics
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/239/
> not collect deselected tests
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/238/
> Introduce "ids" argument to pytest.fixture
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/229/
> implement something like the nose importer to avoid altering sys.path
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/218/
> Add a new test hook that allows displaying custom information on an exception
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/153/
> test intents
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/145/
> filenames in junitxml output
> ----
> open proposal https://bitbucket.org/hpk42/pytest/issue/136/
> Make rsync roots optional not mandatory
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/121/
> make pytest.mark available outside pytest
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/111/
> add a hook for serializing/unserializing report sections
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/95/
> assertion helpers for simplified value checks
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/78/
> pytest_addoption - Command-line options not added
> ----
> new proposal https://bitbucket.org/hpk42/pytest/issue/73/
> sys.excepthook tracking for pytest.raises
> ----
> open proposal https://bitbucket.org/hpk42/pytest/issue/16/
> weird setupstate behaviour for yield tests
> _______________________________________________
> Pytest-dev mailing list
> Pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
More information about the Pytest-dev
mailing list