[py-dev] pytest-2.3 release finalization / little help appreciated

[holger krekel]

Hi all,

a quick heads up: i am trying hard to finalize the pytest-2.3 release.
Help appreciated as documementation and code are starting to be up to a
release (i hope).  What you could do is:

* read http://pytest.org/dev/fixture.html and give feedback
  on readability and sense.

* try installing the release candidate with 

    pip install -i http://pypi.testrun.org -U pytest

  and see if your pytest-using project continues to work unchanged

* try out the new features and find something that is broken
  (you get a beer the next time i see you if you do find something :)

For the record, here are some decisions since the last discussions
here and on IRC a few weeks ago::

- @pytest.fixture() is now the name for defining fixture functions.
  Apart from the usual funcarg usage you can now also use a
  @pytest.mark.usefixtures(fixture1, fixture2, ...) marker 
  on classes to make a fixture function get called.

- @pytest.setup() is gone and is now an "autoactive" fixture - i.e.
  @pytest.fixture(autoactive=True).  It's not a simple spelling
  but it is recommended and expected that using default fixtures
  and refering them explicitely with a funcarg or a "usefixtures"
  markers is anyway better.
  
Catch me on IRC or here on the list for feedback or discussion.

cheers and many thanks to Floris in particular who endured a lot
of variations of the above features, helping much to evolve things
to where they currently stand.

best,

holger