[py-dev] py-test-1.1.0 candidate

[schmir at gmail.com]

holger krekel <holger at merlinux.eu> writes:

> Hi folks,
>
> i have a candidate tar ball for the 1.1.0 release 
> which i'd like to release final thursday or friday.
> Could someone 
>
>     easy_install/pip http://merlinux.eu/~hpk/py-1.1.0.tar.gz 
>
> with a Python2 or Python3 environment and tell me if "py.test -h" 
> and "py.test -v" work?  And maybe run it on your test suite
> that used to work with 1.0.2? 
>

This all seems to work. But did you really expect "py.test -v" to break?
I've tested with a 64 bit linux running python 2.6.4 and a 32 bit linux
running python 2.4.6. I've also run the mwlib test suite and didn't find
any issues.

,----
| [py24-test-mwlib] ~/t/ % py.test -v
| ================================================================ test session starts =================================================================
| python: platform linux2 -- Python 2.4.6 -- pytest-1.1.0 -- /home/ralf/py24-test-mwlib/bin/python
| test object 1: /home/ralf/t
| 
| ==================================================================  in 0.00 seconds ==================================================================
| [py24-test-mwlib] ~/t/ % py.test -h
| usage: py.test [options] [file_or_dir] [file_or_dir] [...]
| 
| options:
|   -h, --help          show this help message and exit
| 
|   running and selection options:
|     -x, --exitfirst   exit instantly on first error or failed test.
|     -k KEYWORD        only run test items matching the given space separated
|                       keywords.  precede a keyword with '-' to negate.
|                       Terminate the expression with ':' to treat a match as a
|                       signal to run all subsequent tests.
|     -p PLUGINS        load the specified plugin after command line parsing.
|     --boxed           box each test run in a separate process
|     --capture=method  set capturing method during tests: fd (default)|sys|no.
|     -s                shortcut for --capture=no.
|     --pdb             start pdb (the Python debugger) on errors.
|     --pastebin=mode   send failed|all info to Pocoo pastebin service.
| 
|   terminal reporting:
|     -v, --verbose     increase verbosity.
|     -l, --showlocals  show locals in tracebacks (disabled by default).
|     --report=opts     comma separated reporting options
|     --tb=style        traceback verboseness (long/short/no).
|     --fulltrace       don't cut any tracebacks (default is to cut).
| 
|   test process debugging and configuration:
|     --basetemp=dir    base temporary directory for this test run.
|     --collectonly     only collect tests, don't execute them.
|     --traceconfig     trace considerations of conftest.py files.
|     --nomagic         don't reinterpret asserts, no traceback cutting.
|     --debug           generate and show internal debugging information.
|     --help-config     show available conftest.py and ENV-variable names.
|     --version         display py lib version and import information.
|     --no-assert       disable python assert expression reinterpretation.
`----


Regards,
- Ralf