Earlier this year

• Nov 13, 2009

  issue 6 (No module named elementtree.ElementTree) reported by e.jelly   -   After installing python-nosexml using easy_install, running nosetests causing the following error message /Library/Python/2.5/site-packages/nose-0.11.1-py2.5.egg/nose/plugins/manager.py:369: RuntimeWarning: Unable to load plugin nosexml = nosexml.plugin:NoseXML: No module named elementtree.ElementTree RuntimeWarning)

  After installing python-nosexml using easy_install, running nosetests causing the following error message /Library/Python/2.5/site-packages/nose-0.11.1-py2.5.egg/nose/plugins/manager.py:369: RuntimeWarning: Unable to load plugin nosexml = nosexml.plugin:NoseXML: No module named elementtree.ElementTree RuntimeWarning)
• Oct 09, 2009

  issue 5 (nosexml pypi out of date or dependencies missing) commented on by gfxmonk   -   Thanks. I think there is now xunit support, but that doesn't seem to allow custom XML outputters.

  Thanks. I think there is now xunit support, but that doesn't seem to allow custom XML outputters.
• Oct 09, 2009

  issue 5 (nosexml pypi out of date or dependencies missing) commented on by paul.joseph.davis   -   Ahh. I'll get to that in a bit. PyPi renamed this package quite awhile ago. Also, have you checked to see if nose has direct XML support? I thought I read they were gonna include this or something similar directly. But I could be wrong.

  Ahh. I'll get to that in a bit. PyPi renamed this package quite awhile ago. Also, have you checked to see if nose has direct XML support? I thought I read they were gonna include this or something similar directly. But I could be wrong.
• Oct 09, 2009

  issue 5 (nosexml pypi out of date or dependencies missing) commented on by gfxmonk   -   aha! sorry to keep spamming, but I think I've figured it out now. The "name" argument to setup is "nosexml", not "python-nosexml". This causes setuptools to ignore it, even when it finds the correct package (I tried with a local build).

  aha! sorry to keep spamming, but I think I've figured it out now. The "name" argument to setup is "nosexml", not "python-nosexml". This causes setuptools to ignore it, even when it finds the correct package (I tried with a local build).
• Oct 09, 2009

  issue 5 (nosexml pypi out of date or dependencies missing) commented on by gfxmonk   -   (also, it's probably worth updating the google code homepage to point to the new package name, it still instructs users to install "nosexml")

  (also, it's probably worth updating the google code homepage to point to the new package name, it still instructs users to install "nosexml")
• Oct 09, 2009

  issue 5 (nosexml pypi out of date or dependencies missing) commented on by gfxmonk   -   okay, so I must not be very good at easy_install: easy_install python-nosexml Searching for python-nosexml Reading http://pypi.python.org/simple/python-nosexml/ Reading http://code.google.com/p/python-nosexml/ No local packages or download links found for python-nosexml error: Could not find suitable distribution for Requirement.parse('python-nosexml') Is there something wrong with the version string, maybe? It's clearly visiting the right website, but refusing to find anything...

  okay, so I must not be very good at easy_install: easy_install python-nosexml Searching for python-nosexml Reading http://pypi.python.org/simple/python-nosexml/ Reading http://code.google.com/p/python-nosexml/ No local packages or download links found for python-nosexml error: Could not find suitable distribution for Requirement.parse('python-nosexml') Is there something wrong with the version string, maybe? It's clearly visiting the right website, but refusing to find anything...
• Oct 07, 2009

  issue 5 (nosexml pypi out of date or dependencies missing) commented on by gfxmonk   -   ahh! so it did. Thanks :)

  ahh! so it did. Thanks :)
• Oct 07, 2009

  issue 5 (nosexml pypi out of date or dependencies missing) commented on by paul.joseph.davis   -   You're installing something else I think. On pypi, this package got renamed to python-nosexml if I'm not mistaken.

  You're installing something else I think. On pypi, this package got renamed to python-nosexml if I'm not mistaken.
• Jun 23, 2009

  issue 5 (nosexml pypi out of date or dependencies missing) reported by gfxmonk   -   I'm pretty sure this just needs an update for pypi, since the source doesn't have any references to elementtree. What steps will reproduce the problem? 1. easy_install nosexml Install Output: Searching for nosexml Reading http://pypi.python.org/simple/nosexml/ Best match: NoseXML 0.19 Downloading http://pypi.python.org/packages/source/N/NoseXML/NoseXML-0.19.tar.gz#md5=cdb35f6517f0f87bc0d398d6e0d39507 Processing NoseXML-0.19.tar.gz Running NoseXML-0.19/setup.py -q bdist_egg --dist-dir /tmp/easy_install-I4QIiz/NoseXML-0.19/egg-dist-tmp-1IVFtX zip_safe flag not set; analyzing archive contents... Adding NoseXML 0.19 to easy-install.pth file But when run: nose-0.11.1-py2.6.egg/nose/plugins/manager.py:369: RuntimeWarning: Unable to load plugin nosexml = nosexml.plugin:NoseXML: No module named elementtree.ElementTree RuntimeWarning)

  I'm pretty sure this just needs an update for pypi, since the source doesn't have any references to elementtree. What steps will reproduce the problem? 1. easy_install nosexml Install Output: Searching for nosexml Reading http://pypi.python.org/simple/nosexml/ Best match: NoseXML 0.19 Downloading http://pypi.python.org/packages/source/N/NoseXML/NoseXML-0.19.tar.gz#md5=cdb35f6517f0f87bc0d398d6e0d39507 Processing NoseXML-0.19.tar.gz Running NoseXML-0.19/setup.py -q bdist_egg --dist-dir /tmp/easy_install-I4QIiz/NoseXML-0.19/egg-dist-tmp-1IVFtX zip_safe flag not set; analyzing archive contents... Adding NoseXML 0.19 to easy-install.pth file But when run: nose-0.11.1-py2.6.egg/nose/plugins/manager.py:369: RuntimeWarning: Unable to load plugin nosexml = nosexml.plugin:NoseXML: No module named elementtree.ElementTree RuntimeWarning)
• Jun 14, 2009

  issue 4 ([feature] nosexml should omit trace frames where `__unittest...) reported by gfxmonk   -   The unittest class (and other test classes, in order to work with unittest) defines `__unittest` as a module-level global variable in order to separate unittest internal code from the user code being tested in stack frames. Omitting such frames provides less noisy stack traces. Patch attached, for svn-r18

  The unittest class (and other test classes, in order to work with unittest) defines `__unittest` as a module-level global variable in order to separate unittest internal code from the user code being tested in stack frames. Omitting such frames provides less noisy stack traces. Patch attached, for svn-r18
• Jun 13, 2009

  issue 3 (Failing test cases appear unexpanded) commented on by gfxmonk   -   works great! (sorry for the exceedingly slow feedback, and backwards patch ;))

  works great! (sorry for the exceedingly slow feedback, and backwards patch ;))

Older

• Dec 21, 2008

  issue 1 (stderr does not get captured) Status changed by paul.joseph.davis   -   r15 and r16 both address handling stderr. Marking this as closed. Reopen if you find anything broken.

  Status: Fixed

  r15 and r16 both address handling stderr. Marking this as closed. Reopen if you find anything broken.

  Status: Fixed
• Dec 21, 2008

  issue 3 (Failing test cases appear unexpanded) commented on by paul.joseph.davis   -   I just manually applied your patch, let me know if it works.

  I just manually applied your patch, let me know if it works.
• Dec 21, 2008

  r18 (Changed textmate html to autoexpand errors and warnings. Tha...) committed by paul.joseph.davis   -   Changed textmate html to autoexpand errors and warnings. Thanks to gfxmonk for the heads up.

  Changed textmate html to autoexpand errors and warnings. Thanks to gfxmonk for the heads up.
• Dec 21, 2008

  issue 3 (Failing test cases appear unexpanded) commented on by paul.joseph.davis   -   Is it just me or is that patch backwards? Otherwise, looks good to me.

  Is it just me or is that patch backwards? Otherwise, looks good to me.
• Dec 21, 2008

  issue 3 (Failing test cases appear unexpanded) reported by gfxmonk   -   What steps will reproduce the problem? 1. Run a test case with some failing, some error and some successful cases using textmate What is the expected output? What do you see instead? All output is left in its compact mode. It's obviously a question of preference / taste, but I would much prefer to instantly see why my tests are failing or erroring instead of having to manually expand each one. If it can't be made default behaviour, could there be an option? I've attached the (rather trivial) diff required...

  What steps will reproduce the problem? 1. Run a test case with some failing, some error and some successful cases using textmate What is the expected output? What do you see instead? All output is left in its compact mode. It's obviously a question of preference / taste, but I would much prefer to instantly see why my tests are failing or erroring instead of having to manually expand each one. If it can't be made default behaviour, could there be an option? I've attached the (rather trivial) diff required...
• Oct 03, 2008

  r17 (Bumped the version number before updating pypi. ) committed by paul.joseph.davis   -   Bumped the version number before updating pypi.

  Bumped the version number before updating pypi.
• Oct 03, 2008

  r16 (Added a flag to disable capturing stderr. ) committed by paul.joseph.davis   -   Added a flag to disable capturing stderr.

  Added a flag to disable capturing stderr.
• Oct 03, 2008

  r15 (Capturing stderr. Few more docs in the formatter class. ) committed by paul.joseph.davis   -   Capturing stderr. Few more docs in the formatter class.

  Capturing stderr. Few more docs in the formatter class.