[pytest-dev] pytest-3.0 / tox-2.4 release plans

[holger krekel]

hi from the pytest/tox sprint ... here is the current plan (keyword
points) for getting  pytest-3.0 and tox-2.4 finalized.  It's WIP
and we aim to complete as much as possible today.

best. h.

tox-conda/roadmap/development discussion:
    - (TBD) two pending PRs
    - (TBD) 2.4.0 relase (to be released end June)
    - (TBD) write doc draft for conda integration (hooks + ini)
    - (TBD) move to github


pytest-3.0 discussion:
    - TO BE RELEASED BEFORE EUROPYTHON2016 -- between 11th and 14th
    definitely part of 3.0
    - new --setup-only, --setup-plan options
    - (Steffen, Danielle, TBD) reporitng hooks for fixture
      setup/teardown
    - (DONE) new main entry point pytest (and py.test)
    - (TBD) remove py.test-X* entrypoints  (with changelog entry)
    - (TBD) doc restructuring
    - (TBD) display pytest warnings by default (one line per warning)
    - (TBD) remove all deprecated command line options for 3.0
    - (TBD) fixture conftest sharing / fixture namespace control, draft
      suggestion document
    - (TBD) merged fixtures becomes a doc draft (raphael, me)
    - (TBD) introduce deprecation docs based on oliver's sprint
      lightning talk
    - (TBD, Omar, Ted, Daniel) new option "--override-ini|-o
      ININAME=INIVALUE" to overrides ini values from the command line
      so that one can do e.g. "-o xfail_strict=True".  We don't change the default.
    - (TBD) see about issuing a deprecation warning for yielding test
      functions
    - (TBD, Floris) remove reinterp assert

    maybe in 3.0:

    - (TBD) invocation-scope: e.g. monkeypatch and mocker would be
      useable
      from any scope. Will be marked experimental for 3.0.

    rather later than 3.0:
    - (rather later than 3.0) merge pytest-warnings module and
      route internal pytest warnings through python's warning
      system and integrate the pytest-warnings plugin into core
      (bruno, ronny will discuss)
    - holger/floris' original pycon work with "markdef" to introduce
      a markdef decorator to process all mark creations should go to 4.0
    - yielding test functions: we could deprecate using setup state in
      yielding test functions so they can only be used for parametrization

    other issues:
    __multicall__: don't remove for 3.0

    marks refactoring / PR merge (ronny, omar...)
    - ronny's refactoring should be closed and redone:
      - either first just move code
      - or do changes in mark.py

    - as to whitespace/flakes/pep warnings:
      do that while changing code anyway but no big pure whitespace/style changes
      xfail strict behaviour by default? not doing it for 3.0

    - introduce xflaky in docs and as a synonmym for xfail(strict=False)
      (needs more discussion)