[PATCH][setuptools] Add test_runner support to setup
Hi all, for our nightly build system I needed the capability to use a different test runner, namely one that outputs junit compatible xml files. In order to support that through the setup.py test command I hacked on setuptools. Is there a simpler way to do this? If not you might want to consider attached patch for addition (Should be against latest svn.) Cheers, Klaus
At 05:15 PM 4/5/2008 +0200, Klaus Zimmermann wrote:
Hi all,
for our nightly build system I needed the capability to use a different test runner, namely one that outputs junit compatible xml files. In order to support that through the setup.py test command I hacked on setuptools.
Is there a simpler way to do this? If not you might want to consider attached patch for addition (Should be against latest svn.)
Add documentation to the patch and you've got yourself a deal. :)
Am Samstag, den 05.04.2008, 19:53 -0400 schrieb Phillip J. Eby:
At 05:15 PM 4/5/2008 +0200, Klaus Zimmermann wrote:
Hi all,
for our nightly build system I needed the capability to use a different test runner, namely one that outputs junit compatible xml files. In order to support that through the setup.py test command I hacked on setuptools.
Is there a simpler way to do this? If not you might want to consider attached patch for addition (Should be against latest svn.)
Add documentation to the patch and you've got yourself a deal. :)
Updated patch attached. Have fun, Klaus
Hi Phillip, *, Am Sonntag, den 06.04.2008, 13:40 +0200 schrieb Klaus Zimmermann:
Am Samstag, den 05.04.2008, 19:53 -0400 schrieb Phillip J. Eby:
At 05:15 PM 4/5/2008 +0200, Klaus Zimmermann wrote:
Hi all,
for our nightly build system I needed the capability to use a different test runner, namely one that outputs junit compatible xml files. In order to support that through the setup.py test command I hacked on setuptools.
Is there a simpler way to do this? If not you might want to consider attached patch for addition (Should be against latest svn.)
Add documentation to the patch and you've got yourself a deal. :)
Updated patch attached. Have fun, Klaus
was the patch satisfactory or is it still lacking? Or do I need to do anything more for it to be applied? On a side note: In the test.py command I noticed another option, test-module, which, if I understand it correctly, is somewhat a stripped-down, undocumented version of test-suite. Should it be deprecated or removed? Cheers, Klaus
At 08:30 AM 4/11/2008 +0200, Klaus Zimmermann wrote:
Hi Phillip, *,
Am Sonntag, den 06.04.2008, 13:40 +0200 schrieb Klaus Zimmermann:
Am Samstag, den 05.04.2008, 19:53 -0400 schrieb Phillip J. Eby:
At 05:15 PM 4/5/2008 +0200, Klaus Zimmermann wrote:
Hi all,
for our nightly build system I needed the capability to use a different test runner, namely one that outputs junit compatible xml files. In order to support that through the setup.py test command I hacked on setuptools.
Is there a simpler way to do this? If not you might want to consider attached patch for addition (Should be against latest svn.)
Add documentation to the patch and you've got yourself a deal. :)
Updated patch attached. Have fun, Klaus
was the patch satisfactory or is it still lacking? Or do I need to do anything more for it to be applied?
It's sitting in my folder of patches to eventually be applied. :)
On a side note: In the test.py command I noticed another option, test-module, which, if I understand it correctly, is somewhat a stripped-down, undocumented version of test-suite. Should it be deprecated or removed?
Probably, but not in the 0.6 line.
On Fri, Apr 11, 2008 at 6:01 PM, Phillip J. Eby <pje@telecommunity.com> wrote:
was the patch satisfactory or is it still lacking? Or do I need to do anything more for it to be applied?
It's sitting in my folder of patches to eventually be applied. :)
What about this one ? http://mail.python.org/pipermail/distutils-sig/2008-April/009187.html Do you have a public tracker where we can submit patches ? Thanks Tarek
FYI, I've added this feature to the trunk (for 0.7a1), but it will not be added to 0.6. Use "easy_install setuptools==dev" to get the trunk version. Thanks. At 01:40 PM 4/6/2008 +0200, Klaus Zimmermann wrote:
Am Samstag, den 05.04.2008, 19:53 -0400 schrieb Phillip J. Eby:
At 05:15 PM 4/5/2008 +0200, Klaus Zimmermann wrote:
Hi all,
for our nightly build system I needed the capability to use a different test runner, namely one that outputs junit compatible xml files. In order to support that through the setup.py test command I hacked on setuptools.
Is there a simpler way to do this? If not you might want to consider attached patch for addition (Should be against latest svn.)
Add documentation to the patch and you've got yourself a deal. :)
Updated patch attached. Have fun, Klaus
I have a distutils.cfg file which looks something like this: ----------- [easy_install] find_links=http://europe1.internal/eggs http://europe2.internal/eggs http://europe3.internal/eggs \\usa1.internal\eggs \\usa2.internal\eggs ----------- All of the five sources contain the exact same collection of files. Most users who can access the european web-servers cannot access the American UNC paths and vice-versa. That usually works out well, because the sources a user cannot access will quickly time-out and the user will get the egg they need from a source they can access. The problem comes with users who can access both the web-servers *and* the UNC paths easy_install. For example a mobile, "international" user might have access to everything but with a slow connection. Even if the egg needed can be found on any one of the hosts the remaining two (the UNC paths) will always be checked by setuptools. This makes setuptools run very slow indeed: I have found that easy_install is needlessly checking all five sources even if checking only one would be good enough. Is there a way to make setuptools stop searching as soon as it's found the first source which contains the required egg? Sal PS. I'm using setuptools-0.6c8-py2.4.egg This email does not create a legal relationship between any member of the Crédit Agricole group and the recipient or constitute investment advice. The content of this email should not be copied or disclosed (in whole or part) to any other person. It may contain information which is confidential, privileged or otherwise protected from disclosure. If you are not the intended recipient, you should notify us and delete it from your system. Emails may be monitored, are not secure and may be amended, destroyed or contain viruses and in communicating with us such conditions are accepted. Any content which does not relate to business matters is not endorsed by us. Calyon is authorised by the Commission Bancaire in France and regulated by the Financial Services Authority for the conduct of business in the United Kingdom. Calyon is incorporated in France with limited liability and registered in England & Wales. Registration number: FC008194. Registered office: Broadwalk House, 5 Appold Street, London, EC2A 2DA.
participants (4)
-
Fadhley Salim
-
Klaus Zimmermann
-
Phillip J. Eby
-
Tarek Ziadé