Mailman 3 March 2008 - pytest-dev

[py-dev] Py lib 0.9.1 released
by Guido Wesdorp March 30, 2008

March 30, 2008

py lib 0.9.1: bugfix release ============================= The py lib team has just released version 0.9.1 of the py lib - a library aiming to support agile and test-driven python development on various levels. This is mostly a bugfix release, with a couple of new features sneaked in. Most important changes: * reduced the number of threads used in py.execnet * some new functionality (authentication, export, locking) in py.path's Subversion APIs * stability and segfault fixes in execnet * numerous small fixes in py.test's rsession (experimental pluggable session) and generative test features * some fixes in the py.test core * added py.misc.killproc, which allows killing processes on (some flavours of) Windows and UNIX For a complete list of changes, see doc/changes-0.9.1.txt in the source package. Download/Install: http://codespeak.net/py/0.9.1/download.html Documentation/API: http://codespeak.net/py/0.9.1/index.html Work on the py lib has been partially funded by the European Union IST programme and by http://merlinux.de within the PyPy project. best, have fun and let us know what you think! holger krekel, Maciej Fijalkowski, Carl Friedrich Bolz, Guido Wesdorp

1 0

[py-dev] unittest docstring behavior in py.test?
by Jim Vickroy March 27, 2008

March 27, 2008

Hello all, I'm a recent convert to py.test (from unittest). I like py.test, and wish to thanks its developers. One feature I like about unittest is its ability to optionally echo each test docstring (if provided) as it runs. I used this feature to make a simple statement about a behavior of the component being tested. This proved useful for requirements validation since at the conclusion of a test run, I had a set of statements about the behaviors of the components being tested. Is there some comparable capability with py.test? If not, is there some alternate approach to achieve this (namely, a set of statements about the behaviors of tested components)? Thanks for your feedback. -- jv

1 0

[py-dev] Building the C extensions on Windows
by Guido Wesdorp March 21, 2008

March 21, 2008

Hi! I was wondering if anyone knows how to build the C extensions on Windows. I would like to get a release out of the door and I'm not sure how to do the Windows part... Cheers, Guido

1 0

[py-dev] problem with py.test --exec switch
by Stephan Diehl March 18, 2008

March 18, 2008

Hi, problem: I want to run pypy/lib/app_test/test_stackless.py. It runs fine, if I just do a py.test test_stackless.py (this runs the stackless tests on top of CPython with the help of greenlets) But if I try to use another python interpreter with, for example (stackless is my stackless interpreter; could be pypy-c instead, whatever really): py.test --exec=stackless test_stackless.py It hangs in the 'test_send_counter'. This really seems to be a problem with the '--exec', because if I do a stackless /my/path/to/py.test test_stackless.py I see no problems. Are there any obvious entry points to look at? (py.test does has it's 'magic' moments) Thanks Stephan

1 0

[py-dev] Merged changes back into the trunk, please test...
by Guido Wesdorp March 17, 2008

March 17, 2008

Hi! After some more delays, I've now applied a set of trunk changes to the 0.9.0-bugfix branch that seems to result in a relatively stable situation, hopefully good enough for 0.9.1. Please, if you have some time, check out the branch, run the tests and let me know what you think... Branch URL: https://codespeak.net/svn/py/branch/bugfix-0.9.0 Thanks in advance! Cheers, Guido

2 1

[py-dev] Cannot build Python 2.4 SRPM on x64 platform
by Eric B. March 16, 2008

March 16, 2008

Hi, For those on several python lists, I appologize in advance for cross-posting, but I'm really not sure which list is best to ask for assistance with this. Currently, I am trying to build the python2.4 SRPM from Python.org on a RHEL4 x64 platform, but the build is failing with a very non-descript error message. .... + cd /var/tmp/python2.4-2.4-root/usr/bin + mv -f pydoc pydoc2.4 + cd /var/tmp/python2.4-2.4-root/usr/bin + mv -f idle idle2.4 + echo '#!/bin/bash' + echo 'exec /usr/bin/python2.4 /usr/lib64/python2.4/idlelib/idle.py' + chmod 755 /var/tmp/python2.4-2.4-root/usr/bin/idle2.4 + cp -a Tools /var/tmp/python2.4-2.4-root/usr/lib64/python2.4 + rm -f mainpkg.files + find /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/lib-dynload -type f + sed 's|^/var/tmp/python2.4-2.4-root|/|' + grep -v -e '_tkinter.so$' error: Bad exit status from /var/tmp/rpm-tmp.55639 (%install) RPM build errors: user jafo does not exist - using root group jafo does not exist - using root user jafo does not exist - using root group jafo does not exist - using root Bad exit status from /var/tmp/rpm-tmp.55639 (%install) If I try to run /var/tmp/rpm-tmp.55639 manually from the prompt manually after the rpmbuild fails, it runs properly to completion. If I try to comment out that last line (find /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/lib-dynload -type f | sed 's|^/var/tmp/python2.4-2.4-root|/|' | grep -v -e '_tkinter.so$' ) that seems to be causing the script to fail, rpmbuild finishes, but with several error msgs, complaining about missing files in the lib64 directories: + rm -f /tmp/python-rpm-files.4859 + /usr/lib/rpm/brp-compress + /usr/lib/rpm/brp-strip + /usr/lib/rpm/brp-strip-static-archive + /usr/lib/rpm/brp-strip-comment-note Processing files: python2.4-2.4-1pydotorg error: File not found by glob: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/*.txt error: File not found by glob: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/*.py* error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/pdb.doc error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/profile.doc error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/curses error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/distutils error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/encodings error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/plat-linux2 error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/site-packages error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/test error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/xml error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/email error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/compiler error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/bsddb error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/hotshot error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/logging error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/lib-old Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.95118 + umask 022 + cd /usr/src/redhat/BUILD + cd Python-2.4 + DOCDIR=/var/tmp/python2.4-2.4-root/usr/share/doc/python2.4-2.4 + export DOCDIR + rm -rf /var/tmp/python2.4-2.4-root/usr/share/doc/python2.4-2.4 + /bin/mkdir -p /var/tmp/python2.4-2.4-root/usr/share/doc/python2.4-2.4 + cp -pr Misc/README Misc/cheatsheet Misc/Porting /var/tmp/python2.4-2.4-root/usr/share/doc/python2.4-2.4 + cp -pr LICENSE Misc/ACKS Misc/HISTORY Misc/NEWS /var/tmp/python2.4-2.4-root/usr/share/doc/python2.4-2.4 + exit 0 Processing files: python2.4-devel-2.4-1pydotorg error: File not found: /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/config Processing files: python2.4-tools-2.4-1pydotorg Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(VersionedDependencies) <= 3.0.3-1 Requires: /bin/bash /bin/sh /usr/bin/env Finally, if I try searching for any files in the usr/lib64/python2.4/lib-dynload or usr/lib64/python2.4/idlelib directories manually, I don't see any files at all in those directories. To me, it seems as though python is either not installing the files in the right places, or the script is searching for files in the wrong places, but I'm completely guessing here. Has anyone managed to build Python2.4 on a RHEL4 x64 system? Can anyone point me in the right direction to complete this build successfully? I'm hoping to get the binaries built so I can contribute them to the python.org site so others don't need to go through these problems in the future. Any hints / ideas / suggestions / guidance that anyone can provide would amazing, because I'm completely out of ideas at this point. Like I said, I'm trying to build this on a RHEL4 x64 system, with all latest updates. Thanks so much! Eric

1 0

[py-dev] 0.9.1 progress
by Guido Wesdorp March 11, 2008

March 11, 2008

Hello! Since I'm rather busy, progress on the py lib release has been slow, but not entirely fruitless: I wrote a script that grabs the 0.9 branch and a list of revisions, then gets a diff from the trunk for each of those revisions, extracts patches from the diffs and applies them incrementally (updating the branch on each revision). Then, for each revision, after the patches are applied, the tests are run. This script seems to work nicely, I've played around a bit and if I only apply the bugfix releases I end up with a fully working working copy (iow: all tests pass after application of the last patch). When I also do all small features (simple changes that required one or two checkins directly on the trunk), I have one single exception somewhere in py.test, can't remember the exact details but it seemed easy enough to fix. When I also apply all merges (so larger features that were developed on a branch and merged to the trunk) I get a failure on the 'less threads for execnet' feature (merged in rev. 45539), I didn't investigate in detail yet, as I think merging this is out of scope for 0.9.1 anyway. So here comes my question: do you guys agree to just apply the bugfix revisions (see one of my previous mails on py-dev for the exact list - it's the 'bugfixes/refactorings' part)? And if not, which revisions do you want to have in 0.9.1 besides the ones mentioned in the list? I'll be spending tomorrow (wednesday) on applying the bugfixes, and will check the results in on a branch. If all goes well, the branch should be ready for release (although some testing first would be nice, of course :) tomorrow evening. Cheers, Guido

2 2

[py-dev] away / dev status
by Holger Krekel March 1, 2008

March 1, 2008

Hello py-dev, this is note to tell that i am offline at least for march due to personal troubles. As to development issues: Guido thankfully agreed to care for a 0.9.1 release which is to include his svn-auth work and bugfixes since 0.9.0. Larger changes, much of the current trunk development, and in particular the event-branch will probably have to wait. The event branch contains major cleanups and refactorings. Here are some notes: * py/test2 is the directory with the new code. This is so that you can use "py.test" to test the refactorings. Otherwise it would not be possible to easily use py.test to test py.test functionality as refactorings would directly affect test runs themselves. * config objects now have an event "bus" which has a basic simple (zope3-like) subscribe/notify mechanism. See test_bus.py * ItemTestReports events contain the result of test runs and there is support for marshalling and unmarshalling their contents. This is the key thing that allowed to get rid of "SerializableOutcome" and duplications of code resulting from the worlds of "in-process" and "distrihuted testing". The idea is that the to-be-written reporters deal with "ItemTestReport" events which already contain formatted traceback information which is generated directly at the time a failure occurs (previously such information was extracted much later when the failure reports were actually printed at the end of a test run) * main TODO item is the re-instantiation and re-viving of the Text- and other reporters which need to be adapated to the new event mechanisms. It should also be possible to have e.g. a Webreporter and a Testreporter and a new "File-reporter"co-exist because they all just subscribe to CollectionStart/Finish and ItemTestReports. * If you work on the branch i'd suggest to first read the files of the current py/test2. I am saying this because the previous code contained a lot of painful duplication and it'd be good to avoid this happening again. anyway, wish you all a good time, take care, holger

2 1