Go to file
holger krekel d163d92b33 actually look into all non-dot subdirs for conftest.py files - recursive walk would be too heavy for large source trees but first-level subdirs are fine IMO. Note that prior to py.test 1.0 doing this "look-ahead" was not easily doable because it was hard to avoid global state in conftest.py, this is not true anymore - so i feel ok telling people to cleanup their conftest files if they get problems (you can imagine people doing all kinds of things at global conftest.py module scope, can't you?)
--HG--
branch : trunk
2010-02-06 22:37:04 +01:00
bin cleanup bin-script creation, fix docs, add FAQ entry about py.test --version 2009-12-24 12:27:15 +01:00
bin-for-dist fix doc links, bump to dev version 2010-01-21 19:34:42 +01:00
contrib cleanup py.test.* namespace, docstrings for improved pydoc and interactive usage. 2009-12-29 16:29:48 +01:00
doc fix title to not mention distributed programming which 2010-02-02 11:32:21 +01:00
hacking * delete or text files to hacking/ directory. 2009-09-05 16:09:44 +02:00
py actually look into all non-dot subdirs for conftest.py files - recursive walk would be too heavy for large source trees but first-level subdirs are fine IMO. Note that prior to py.test 1.0 doing this "look-ahead" was not easily doable because it was hard to avoid global state in conftest.py, this is not true anymore - so i feel ok telling people to cleanup their conftest files if they get problems (you can imagine people doing all kinds of things at global conftest.py module scope, can't you?) 2010-02-06 22:37:04 +01:00
testing actually look into all non-dot subdirs for conftest.py files - recursive walk would be too heavy for large source trees but first-level subdirs are fine IMO. Note that prior to py.test 1.0 doing this "look-ahead" was not easily doable because it was hard to avoid global state in conftest.py, this is not true anymore - so i feel ok telling people to cleanup their conftest files if they get problems (you can imagine people doing all kinds of things at global conftest.py module scope, can't you?) 2010-02-06 22:37:04 +01:00
.hgignore a few internal test related fixes as to run on a osx/no-execnet situation 2009-11-12 21:15:59 +01:00
.hgtags Added tag 1.2.0 for changeset 4fc5212f7626 2010-01-18 17:04:52 +01:00
AUTHORS adding a logxml plugin and a --xml=path option generating a junit-xml style result log. The xml result log can be parsed nicely by hudson. 2009-12-31 11:25:07 +01:00
CHANGELOG actually look into all non-dot subdirs for conftest.py files - recursive walk would be too heavy for large source trees but first-level subdirs are fine IMO. Note that prior to py.test 1.0 doing this "look-ahead" was not easily doable because it was hard to avoid global state in conftest.py, this is not true anymore - so i feel ok telling people to cleanup their conftest files if they get problems (you can imagine people doing all kinds of things at global conftest.py module scope, can't you?) 2010-02-06 22:37:04 +01:00
ISSUES.txt fail doc generation if pygments is not installed 2010-01-21 23:24:33 +01:00
LICENSE * use the MIT license for the py lib 2009-10-03 01:11:04 +02:00
MANIFEST.in add report_header_info to release announce 2010-01-18 17:00:22 +01:00
README.txt removing some py.execnet references and moving scripts to execnet repo 2009-10-27 09:19:23 +01:00
conftest.py remove dist-testing and looponfail code from core. there remain some (pytest_runner particularly) tests that test both plain and dist modes which cannot be easily dis-entangled. food for thought. 2010-01-13 16:00:33 +01:00
distribute_setup.py some release preps and cleanups 2009-10-29 12:45:12 +01:00
setup.py fix doc links, bump to dev version 2010-01-21 19:34:42 +01:00

README.txt

The py lib is a Python development support library featuring 
the following tools and modules:

* py.test: tool for distributed automated testing
* py.code: dynamic code generation and introspection
* py.path:  uniform local and svn path objects 

For questions and more information please visit http://pylib.org