Mailman 3 August 2008 - pytest-dev

[py-dev] 0.9.2 is out
by holger krekel Aug. 29, 2008

Aug. 29, 2008

Hi, thanks to all who helped with the 0.9.2 release! see below for the release announcement. hope that all the eggs now work properly. cheers, holger Welcome to the 0.9.2 py lib and py.test release - mainly fixing Windows issues, providing better packaging and integration with setuptools. Summry of main features: * py.test: cross-project testing tool with many advanced features * py.execnet: ad-hoc code distribution to SSH, Socket and local sub processes * py.magic.greenlet: micro-threads on standard CPython ("stackless-light") * py.path: path abstractions over local and subversion files * rich documentation of py's exported API * tested against Linux, Win32, OSX, works on python 2.3-2.6 good entry points: Pypi pages: http://pypi.python.org/pypi/py/ Download/Install: http://codespeak.net/py/0.9.2/download.html Documentation/API: http://codespeak.net/py/0.9.2/index.html the CHANGELOG excerpt for the 0.9.1 -> 0.9.2 transition: * refined installation and metadata, created new setup.py, now based on setuptools/ez_setup (thanks to Ralf Schmitt for his support). * improved the way of making py.* scripts available in windows environments, they are now added to the Scripts directory as ".cmd" files. * py.path.svnwc.status() now is more complete and uses xml output from the 'svn' command if available (Guido Wesdorp) * fix for py.path.svn* to work with svn 1.5 (Chris Lamb) * fix path.relto(otherpath) method on windows to use normcase for checking if a path is relative. * py.test's traceback is better parseable from editors (follows the filenames:LINENO: MSG convention) (thanks to Osmo Salomaa) * fix to javascript-generation, "py.test --runbrowser" should work more reliably now * removed previously accidentally added py.test.broken and py.test.notimplemented helpers. * there now is a py.__version__ attribute best and have fun, holger krekel -- collaborative expert contracting: http://merlinux.eu PyPy Python/Compiler tool chain: http://codespeak.net/pypy pylib py.test/greenlets/svn APIs: http://pylib.org

4 5

[py-dev] error on trunk in py.path.svn support
by Martijn Faassen Aug. 21, 2008

Aug. 21, 2008

Hi there, I just tried the trunk of Py with my project which makes very heavy use of the py.path SVN facilities, and I get a lot of errors that look like this: File "/home/faassen/buildout/z3c.vcsync/py/py/path/svn/wccommand.py", line 270, in status rootstatus = XMLWCStatus(self).fromstring(out, self) File "/home/faassen/buildout/z3c.vcsync/py/py/path/svn/wccommand.py", line 687, in fromstring for c in commitel.getElementsByTagName('author')[0]\ IndexError: list index out of range It looks to me like a certain assumption about the format of the XML returned is incorrect. The SVN version on my system is svn, version 1.4.3 (r23084) When debugging it, the XML that trips up the code looks like this: <entry path="/tmp/pytest-23/wc"> <wc-status item="normal" props="none" revision="0"> <commit revision="0"> <date>2008-08-19T16:50:53.400198Z</date> </commit> </wc-status> </entry> It looks like this means there is not always an 'author' entry in this XML structure. Attached is a patch to wccommand.py that makes the problem go away (and indeed seems to fix the original problem I was looking into - the trunk has support for the svn status flag R, something that py 0.9.1 didn't have). I realize this patch isn't enough but needs a test as well. I could find no obvious way (in the form of documentation, say, the README.txt, or the website) on how to actually run the tests of the trunk. :) It's quite possible I missed something. Is py 0.9.2 to be based off the work on the trunk? Regards, Martijn

4 9

[py-dev] 0.9.2 beta eggs / Windows Notes / API gen pending
by holger krekel Aug. 21, 2008

Aug. 21, 2008

Hi again, after i fixed a number of bugs (mostly windows specific) and after lots of experimentation i settled for a simpler approach for setup.py: it's now setuptools only and uses the "entry_points" hook as Ralf originally suggested and Martijn now recommended as well. There is no "_findpy" hack anymore. i've uploaded the beta to pypi: http://codespeak.net/py/0.9.2/download.html Note to harald and users who have used py.test and friends with earlier installs: please read the important note and execute the cleanupscript. Guido: i think i need some help with API generation - that link is currently broken and i guess you know what is wrong. best & cheers, holger -- collaborative expert contracting: http://merlinux.eu PyPy Python/Compiler tool chain: http://codespeak.net/pypy pylib py.test/greenlets/svn APIs: http://pylib.org

2 2

[py-dev] 0.9.2 alpha eggs - please test
by holger krekel Aug. 19, 2008

Aug. 19, 2008

Hi all, i am experimenting with building eggs and installation improvements, particularly for windows but also for unix. Would be great if you could give "easy_install" with one of these packages a try and report back any problems: http://codespeak.net/~hpk/py/dist/ This should work nicely out of the box, including accessing "py.magic.greenlet" (the stackless light c-extension) and running "py.test" on the command line on your project. You should be able to remove all previous hacks, additions to the PATH environment setting. thanks & best, holger -- collaborative expert contracting: http://merlinux.eu PyPy Python/Compiler tool chain: http://codespeak.net/pypy pylib py.test/greenlets/svn APIs: http://pylib.org

3 7

[py-dev] setup.py broken in develop mode on trunk
by Martijn Faassen Aug. 19, 2008

Aug. 19, 2008

Hi there, In order to see whether a bugfix in Py trunk fixed a bug in my project, I tried installing the py trunk as a develop egg (using buildout). It's possible "python setup.py develop" is therefore similarly broken. I see files mentioned in MANIFEST which don't exist, so initially I thought this was blocking things. It turns out however that setup.py has references to packages which at least don't appear to exist: py.io.test, py.test.rsession, py.test.terminal. After I remove those from setup.py things seem to work again (that is, I can run the code. I get errors. Another mail about those...) With setuptools, MANIFEST shouldn't be necessary: you can instruct setup.py to automatically assume files that are checked into SVN are in manifest, with something like this: from setuptools import find_packages package_dir={'': 'src'}, packages=find_packages('py'), Regards, Martijn

2 2

[py-dev] setuptools and PYTHONPATH
by holger krekel Aug. 19, 2008

Aug. 19, 2008

Hi Ralf, all, so when i have installed a py egg - i seem to have problems getting my PYTHONPATH env variable respected. i refer to this situation - executed ralf's "setup.py" install - PYTHONPATH=/some/path/to/py/lib/branchdir - python && "import py" && "py.__file__" points to the egg still Does setuptools really force global installation over private environment settings? (i wouldn't regard the need to do "python setup.py develop" or something like a convenient solution, btw) best, holger

2 6

[py-dev] svn st --xml support for py.path - progress
by Guido Wesdorp Aug. 16, 2008

Aug. 16, 2008

Hi! Yesterday I had some time to spare so decided to work on using the XML output of svn st rather than the text to get py.path.svnwc.status() reports. After some refactoring, adding some tests and battling the test code a bit, I ended up with something that at least satisfies the tests - they all work with the new code, using the old code as fallback if the --xml switch gets refused. I did this on a branch, as at first it seemed like I had to do a lot of refactoring of the tests (which I ended up mostly rolling back). The URL of this branch is: https://codespeak.net/svn/py/branch/guido-svnwc-xml-status Unfortunately I didn't find the time to test on any platform other than Linux, using SVN v. 1.3. Therefore I think the code, in its current status, shouldn't be merged into the next release branch, or at least not without more testing (this also because I have the feeling a lot of edge cases aren't covered in the tests). However, what is there should be feature-complete... If people feel like testing, I'd greatly appreciate it... If not, I'll do it the first opportunity I have. I think the most important questions now are if it works on Windows, and on SVN versions besides 1.3. If that's done I think it can be merged into trunk and release branch. Cheers, Guido

2 6

[py-dev] WindowsErrors when removing file (file in use)
by Matthew Edwards Aug. 16, 2008

Aug. 16, 2008

Hi, This kind of relates to my last problem. With my new file-related test setup, I often get WindowsErrors when removing files, because they are still in use, because for some reason the file objects refuse to be closed or deleted, and are still wandering around when teardown_method is called. Again, I'm not sure whether this is something I'm doing wrong or a bug, but I've attached a test (simplified, with attempts at debugging), which fails with the error every second run (every other run the file exists at the start) on Python 2.5.2, py 0.9.1 or svn 57262, Windows XP. Matthew

2 1

[py-dev] oncoming 0.9.2 release
by Harald Armin Massa Aug. 14, 2008

Aug. 14, 2008

Whish-list: pytest -e pytest --testforever includes --startsserver and --runbrowser, loops "forever" until Ctrl+Break on the given file / directory / filtered files and publishes results on Webport. Bonus points for really showing a traffic light :) Harald -- GHUM Harald Massa persuadere et programmare Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607 no fx, no carrier pigeon - EuroPython 2009 will take place in Birmingham - Stay tuned!

3 2

[py-dev] broken/notimplemented?
by holger krekel Aug. 14, 2008

Aug. 14, 2008

Hi Guido, (and maciej?) in the 0.9.1 release i see that "py.test.broken" and "py.test.notimplemented" were introduced into the namespace. What is the rationale? they don't have docstrings for one and they seem to be redundant, i.e. just be versions of skip. In r59284 i removed them for now and adjusted the test to show how you can get the same effect with skip. Also doesn't seem to me like it's used anywhere. holger -- Holger Krekel - freelance manager and programmer pylib py.test/greenlets/svn APIs: http://pylib.org PyPy Python/Compiler tool chain: http://codespeak.net/pypy merlinux collaborative contracting: http://merlinux.eu

3 2