Mailman 3 November 2005 - pytest-dev

[py-dev] Hi! And py.log :-)
by François Pinard Jan. 21, 2006

Jan. 21, 2006

Hi, people. I just subscribed to py-dev@codespeak. The page at: http://agiletesting.blogspot.com/2005/06/keyword-based-logging-with-py-libr… says: If you think you can use the keyword-based approach to logging in your own application code, or if you have a use case that you would like to see implemented via py.log, or if you have any suggestions at all, please leave a comment here of send email to py-dev at codespeak dot net. So here! :-) I'm preparing to clean up a big Python application which, among other things, (ab)uses the concept of logging, with many complex, over-loaded logging routines. My guess is that cleaning this single aspect, if done properly, would significantly reduce the amount of noise in the source code of this application, and so, somehow increase its legibility. I'm always starving for clean, simple design, and this is how I got interested in `py.log'. Am I welcome at discussing logging issues here, in the context of `py.log', as they will pop up in our adventure? -- François Pinard http://pinard.progiciels-bpi.ca

6 11

[py-dev] Call py.test.cmdline.main() from a python script
by Ruda Filgueiras Dec. 1, 2005

Dec. 1, 2005

Hello, I'm using py.test to run my unit tests for STOQ 2 [1] project. To run my tests I can execute py.test script, but I nedd to call py.test from a python script that initalize database and executes some doctests using doctest module. To make this, I add this simple code inside my script: +import py +py.test.cmdline.main() My enviroment uses simbolic links from package/module to a directory on my PYTHONPATH. And after using my runtests.py script with these lines, py.test dont import my test modules correctly. (see traceback log attached) Anohter member of STOQ2 staff, Johan Dahlin <jdahlin(a)async.com.br>, verify the problem and propose a one line patch to this problem, and I'm send this patch attached too. Thanks, 1. STOQ2 is a Open Source Reatail System written in python and uses: - pygtk - kiwi (MVC framework on top of pygtk) - SQLObject - py.test (pylib) - twisted component model -- Rudá Porto Filgueiras

2 2

[py-dev] Moving py-lib to setuptools
by Ian Bicking Nov. 21, 2005

Nov. 21, 2005

Does anyone have an opinion on setup.py and how py-lib is packaged? It seems like it was put in place some time ago, and py hasn't really been formally released since then. Anyway, I think a lot of the hackish parts are dealt with by setuptools. setuptools.find_packages() fills out the packages, and its backport of package_data deals with non-Python files, and paste.util.finddata can be copied in to deal with enumerating the package data. setuptools has some possibly useful script generation capability, but that doesn't need to be used. Maybe it should be, though; it creates a .exe file on Windows for each script. I don't know know it would interact with the "py.test" name; I doubt that's been considered on Windows, and probably setuptools should remove dots from scripts on Windows. I was going to upload the setup.py file to use setuptools, but I lost my svn password, so I'll just attach them for now. There's probably some other things I'd add to fully convert it, like just removing the download URL and using the Cheese Shop for file distribution, and perhaps adding a setup.cfg that append svn revisions to the versions of distributions made from the trunk. -- Ian Bicking / ianb(a)colorstudy.com / http://blog.ianbicking.org # Note: you may want to copy this into your setup.py file verbatim, as # you can't import this from another package, when you don't know if # that package is installed yet. import os import sys from fnmatch import fnmatchcase from distutils.util import convert_path # Provided as an attribute, so you can append to these instead # of replicating them: standard_exclude = ('*.py', '*.pyc', '*~', '.*', '*.bak') standard_exclude_directories = ('.*', 'CVS', '_darcs', './build', './dist', 'EGG-INFO', '*.egg-info') def find_package_data( where='.', package='', exclude=standard_exclude, exclude_directories=standard_exclude_directories, only_in_packages=True, show_ignored=False): """ Return a dictionary suitable for use in ``package_data`` in a distutils ``setup.py`` file. The dictionary looks like:: {'package': [files]} Where ``files`` is a list of all the files in that package that don't match anything in ``exclude``. If ``only_in_packages`` is true, then top-level directories that are not packages won't be included (but directories under packages will). Directories matching any pattern in ``exclude_directories`` will be ignored; by default directories with leading ``.``, ``CVS``, and ``_darcs`` will be ignored. If ``show_ignored`` is true, then all the files that aren't included in package data are shown on stderr (for debugging purposes). Note patterns use wildcards, or can be exact paths (including leading ``./``), and all searching is case-insensitive. """ out = {} stack = [(convert_path(where), '', package, only_in_packages)] while stack: where, prefix, package, only_in_packages = stack.pop(0) for name in os.listdir(where): fn = os.path.join(where, name) if os.path.isdir(fn): bad_name = False for pattern in exclude_directories: if (fnmatchcase(name, pattern) or fn.lower() == pattern.lower()): bad_name = True if show_ignored: print >> sys.stderr, ( "Directory %s ignored by pattern %s" % (fn, pattern)) break if bad_name: continue if os.path.isfile(os.path.join(fn, '__init__.py')): if not package: new_package = name else: new_package = package + '.' + name stack.append((fn, '', new_package, False)) else: stack.append((fn, prefix + name + '/', package, only_in_packages)) elif package or not only_in_packages: # is a file bad_name = False for pattern in exclude: if (fnmatchcase(name, pattern) or fn.lower() == pattern.lower()): bad_name = True if show_ignored: print >> sys.stderr, ( "File %s ignored by pattern %s" % (fn, pattern)) break if bad_name: continue out.setdefault(package, []).append(prefix+name) return out if __name__ == '__main__': import pprint pprint.pprint( find_package_data(show_ignored=True)) from setuptools import setup, find_packages from finddata import find_package_data setup( name="py", version="0.8.0-alpha2", description="py.test and the py lib", long_description="""\ The py lib is a development support library featuring py.test, an interactive testing tool which supports unit-testing with practically no boilerplate.""", url="http://codespeak.net/py", author="Holger Krekel & others", author_email="hpk(a)merlinux.de", license="MIT license", download_url="http://codespeak.net/download/py/py-0.8.0-alpha2.tar.gz", packages=find_packages(), package_data=find_package_data(), scripts=['py/bin/_findpy.py', 'py/bin/_makepyrelease.py', 'py/bin/py.cleanup', 'py/bin/py.countloc', 'py/bin/py.lookup', 'py/bin/py.rest', 'py/bin/py.test', 'py/bin/pytest.cmd'], )

2 1

[py-dev] failing import in toplevel module
by Carl Friedrich Bolz Nov. 15, 2005

Nov. 15, 2005

Hi py-dev! today I had the following problem with py.test: I could not find a way to skip tests in a package if the import of the package itself fails (because the __init__.py raises something). Example: assuming I have a package directory "example" with two files in it: __init__.py: ------------ something that can raise ImportError test_it.py: ----------- import py try: import example except ImportError: py.test.skip("missing dependencies, whatever") ... (some tests) In this situation the tests will always fail because py.test automatically tries to import the top-level package. This cannot be circumvented even when using a conftest file since the import of the top-level package happens very early. Is there something I was missing? Couldn't for example py.test only insert the path to the top-level dir into sys.path, so that the "import example" find the correct package? Cheers, Carl Friedrich

1 0

[py-dev] py.log suggestion
by François Pinard Nov. 12, 2005

Nov. 12, 2005

Hi, people. I wrote to this list, a little while ago, about using py.log in some big Python project I should seriously clean up, and which currently abuses of various logging mechanisms. I thought this job would induce me in using quite a flurry of py.log producers. Instead, for the past weeks, I was more active at aggressively forever _removing_ amounts of logging calls. A lot still remain, for which py.log is going to be useful. Today, I saw a situation of logging made in context of tracing the hearth of one of the evaluation engines. When such logging/tracing is active, the application is going to be applied to a toy subset of the real input. Otherwise, logging would be triggered millions of times. The problem is that log messages themselves require a fair amount of extra-computation that would better be spared when tracing is not active (which is most of the time). My suggestion, here, is that producers, besides their ``__call__`` method, could also offer a ``__nonzero__`` method that would return False when the consumer that would apply is None. So, one could write something like: if trace.dossier: diagnostic = prepare_diagnostic_information() trace.dossier(diagnostic) It looks clean and lean to me to use the producer for the test as well as for the call. Do you share this opinion? -- François Pinard http://pinard.progiciels-bpi.ca

3 8

[py-dev] Intent To Package (ITP) for Debian
by Bob Tanner Nov. 11, 2005

Nov. 11, 2005

Hello upstream developers of pylib. I'm working on a debian package for pylib and have some feedback. Please do not take any of my comments personally. I'm just trying to make my job easier :-) at the same time make recommendations on how to make pylib more Debian compliant. 1. svn snapshot from 2005/11/11 has .gif/.png in /usr/lib, according to Filesystem Hierarchy Standard (FHS) architecture-independent files need to be placed within /usr/share instead 2. Finding python scripts that by default aren't executable on installation, should these scripts be executable? /usr/lib/python2.4/site-packages/py/compat/testing/_findpy.py /usr/lib/python2.4/site-packages/py/compat/testing/test_optparse.py /usr/lib/python2.4/site-packages/py/misc/cmdline/countloc.py /usr/lib/python2.4/site-packages/py/compat/testing/_findpy.py and /usr/bin/_findpy.py (see below) look to be the same script, can one or the other be removed? 3. The install puts /usr/bin/pytest.cmd in place on linux, this looks to be a DOS batch file, I don't think it should be installed when the os is linux. 4. Debian requires anything in /usr/bin to have a manpage. I have found help2man to be very useful and maintaining manpages from the -h (--help) and -v (--version) of the program. /usr/bin/_findpy.py /usr/bin/py.cleanup /usr/bin/py.lookup /usr/bin/py.test /usr/bin/_makepyrelease.py /usr/bin/py.countloc /usr/bin/py.rest I'd also like feedback on the _findpy.py and _makepyrelease.py, should they be in a "production" package or are the development tools? The underscore breaks Debian executable naming policy. 5. Good news is even with the Debian "problems" the code works great. $ py.test test/ <snip> tests finished: 138 passed in 19.18 seconds I'm happy to submit patches if you are willing to accept them for review. I much rather have things put into upstream code then maintain separate patches for Debian. Look forward to your (collective) responses. Thanks. -- Bob Tanner <tanner(a)real-time.com> | Phone : (952)943-8700 http://www.real-time.com, Minnesota, Linux | Fax : (952)943-8500 Key fingerprint = AB15 0BDF BCDE 4369 5B42 1973 7CF1 A709 2CC1 B288

1 0

[py-dev] py.test: initializing test environment
by Ian Bicking Nov. 4, 2005

Nov. 4, 2005

I want to add an option that effects the environment before any tests are collected. But I'm having a hard time doing that. I'm thinking that conftest.py files could have a setup_tests() function, that will be called with no arguments after the configuration has been parsed. -- Ian Bicking | ianb(a)colorstudy.com | http://blog.ianbicking.org

2 3