Mailman 3 December 2009 - pytest-dev

[py-dev] py.test : setup / teardown at the directory level
by Philippe Fremy April 16, 2010

April 16, 2010

Hi, I was wondering if there is a possibility to have or emulate setup/teardown method for an entire directory of tests ? I have an expensive setup/teardown method, which I share through about 10 modules, each with about 20 tests. I would save time if I could do the setup/teardown just for that directory. cheers, Philippe

3 9

[py-dev] Local import
by Joan Miller Jan. 23, 2010

Jan. 23, 2010

I'm using the next function to access to the source from tests without install it (python setup.py develop). It's very usefull during development so it could be added to py. ------------------------ import os import sys def import_local(parent='test', child='lib'): """Inserts local library on 'sys.path'. Goes up until the root of the project (upper of 'parent' directory) and inserts the 'child' directory. """ parent_path = os.path.abspath(os.path.dirname(__file__)) while parent in os.path.basename(parent_path): parent_path = os.path.dirname(parent_path) sys.path.insert(0, os.path.join(parent_path, child)) ------------------------

2 6

[py-dev] funcarg in a class
by Joan Miller Jan. 1, 2010

Jan. 1, 2010

Is possible to run a funcarg inner of a class? The nex code doesnt works. -------------------------- class TestFoo(object): def pytest_funcarg__myfuncarg(self, request): return 13 def test_function(self, append): assert self.myfuncarg == 13 -------------------------- http://codespeak.net/py/dist/test/funcargs.html

2 3

Re: [py-dev] [py-svn] py-trunk commit 3b9141d6bd7d: internal: always use scripts found in the environment
by Samuele Pedroni Dec. 31, 2009

Dec. 31, 2009

this broke the way I tend to run the oejskit tests which use testdir.runpytest for some functional tests, I tend to setup a virtualenv in which the current py.test trunk is installed via setup.py develop, path-to-virtualenv/bin/py.test then is how I invoke py.test and it that case there is no py.test at all findable through the environment. commits-noreply(a)bitbucket.org wrote: > # HG changeset patch -- Bitbucket.org > # Project py-trunk > # URL http://bitbucket.org/hpk42/py-trunk/overview/ > # User holger krekel <holger(a)merlinux.eu> > # Date 1262272511 -3600 > # Node ID 3b9141d6bd7df061b8f4bace364d1ea66fb0fe16 > # Parent 2f97b1b6a2cc27197238679b991a8e6a289f65b1 > internal: always use scripts found in the environment > > --- a/py/plugin/pytest_pytester.py > +++ b/py/plugin/pytest_pytester.py > @@ -307,13 +307,8 @@ class TmpTestdir: > return self.run(*fullargs) > > def _getpybinargs(self, scriptname): > - bindir = py._dir.dirpath('bin') > - if not bindir.check(): > - script = py.path.local.sysfind(scriptname) > - else: > - script = bindir.join(scriptname) > - assert script.check() > - return py.std.sys.executable, script > + script = py.path.local.sysfind(scriptname) > + return script, > > def runpython(self, script): > return self.run(py.std.sys.executable, script) > _______________________________________________ > py-svn mailing list > py-svn(a)codespeak.net > http://codespeak.net/mailman/listinfo/py-svn >

1 0

[py-dev] Class instance at module level
by Joan Miller Dec. 31, 2009

Dec. 31, 2009

Is pssible to instance a class at module level (setup_module) and that it can be used from a test class?

2 2

[py-dev] py.test3, py.test-jython, py.test-pypy ...
by holger krekel Dec. 28, 2009

Dec. 28, 2009

Hi all, i just committed a change which i'd release together with a bunch of other things as py-1.1.2. It makes py.test install as py.test # if python executable has basename 'python' py.test3 # if python executable has version_info >= (3,0) py.test2.x # if python executable has basename 'python2.x' (x in '4567') py.test-jython # if we are running on jython2.5 py.test-pypy # if we are running on pypy does this make sense to you, objections? It does for me because i can more easily run tests with various interpreters. But it means if you run "python2.4 setup.py install" you will not get a 'py.test2.4' only, and no 'py.test' proper. cheers, holger

5 17

[py-dev] execnet-1.0.2: channel-over-channels / bug fixes
by holger krekel Dec. 23, 2009

Dec. 23, 2009

execnet is a small stable pure-python library for working with local or remote clusters of Python interpreters, with ease. The 1.0.2 release is fully backward compatible and: - introduces a generalized way to send channels over channels - makes gateways more resilient against callback failures - speeds up local gateway creation, now at <50ms on an old 1.5GHZ machine - fixes a bug in channel.receive() which could wrongly timeout More info, new tested examples and links to blog entries here: http://codespeak.net/execnet cheers and i wish you all relaxed days of this decade, holger changes in 1.0.2 -------------------------------- - generalize channel-over-channel sending: you can now have channels anywhere in a data structure (i.e. as an item of a container type). Add according examples. - automatically close a channel when a remote callback raises an exception, makes communication more robust because until now failing callbacks rendered the receiverthread unuseable leaving the remote side in-accessible. - internally split socket gateways, speeds up popen-gateways by 10% (now at <50 milliseconds per-gateway on a 1.5 GHZ machine) - fix bug in channel.receive() that would wrongly raise a TimeoutError after 1000 seconds (thanks Ronny Pfannschmidt)

1 0

[py-dev] Setup function at starting of all tests
by Joan Miller Dec. 23, 2009

Dec. 23, 2009

Hi everybody! How to run a setup function at all-tests level? I mean that it been run only at starting; and another one at the end --of all tests--. It's for setup and shutdown the logging. Thanks in advance!

2 1

Re: [py-dev] py.test3, py.test-jython, py.test-pypy ...
by Laura Creighton Dec. 20, 2009

Dec. 20, 2009

In a message of Sun, 20 Dec 2009 22:48:52 +0100, holger krekel writes: >Hi all, > >i just committed a change which i'd release together with a bunch >of other things as py-1.1.2. It makes py.test install as > > py.test # if python executable has basename 'python' > py.test3 # if python executable has version_info >= (3,0) > py.test2.x # if python executable has basename 'python2.x' (x in >'4567') > py.test-jython # if we are running on jython2.5 > py.test-pypy # if we are running on pypy > >does this make sense to you, objections? It does for me because >i can more easily run tests with various interpreters. But >it means if you run "python2.4 setup.py install" you will not >get a 'py.test2.4' only, and no 'py.test' proper. > >cheers, >holger Ah, you mean you _will_ only get a py.text2.4 ?? or ... Laura

3 5

Re: [py-dev] py.test3, py.test-jython, py.test-pypy ...
by Laura Creighton Dec. 20, 2009

Dec. 20, 2009

In a message of Sun, 20 Dec 2009 23:00:34 +0100, holger krekel writes: >yes, currently it would be 'py.test2.4' only if the executable is >named "python2.4". If it's named "python" and has version_info==(2,4,..) >it would still install as 'py.test'. > >holger Thank you for clarifying, and, yes I don't have a problem with this. Laura

1 0