[IronPython] Procedure for Posting Bugs

Jones, Larry Larry.Jones at aspentech.com
Fri Jan 20 20:35:47 CET 2006

This morning, I discovered that importing the unittest module from the
Python 2.4 libraries results in unexpected behavior.
My test code is:
import unittest

class MyTest(unittest.TestCase):
    def testFirst(self):
    def testSecond(self):
if __name__ == '__main__':
The result of executing this script from the command line via the
IronPythonConsole is:
$ /usr/local/bin/ironpython/IronPythonConsole.exe unittesterror.py
Traceback (most recent call last):
curity\proto_azn\unittesterror.py, line 14, i
n Initialize
  File , line 0, in __init__$f78
  File c:\Python24\Lib\unittest.py, line 758, in __init__$f78
  File c:\Python24\Lib\unittest.py, line 787, in parseArgs$f80
  File c:\Python24\Lib\unittest.py, line 507, in loadTestsFromModule$f55
  File c:\Python24\Lib\unittest.py, line 495, in loadTestsFromTestCase$f54
  File c:\Python24\Lib\unittest.py, line 570, in getTestCaseNames$f58
  File , line 0, in Sort
  File , line 0, in QuickSort
  File , line 0, in GetPivotValue
Traceback (most recent call last):
  File , line 0, in GetPivotValue
Exception: Failed to compare two elements in the array.
The result of executing this same script from Python is:
$ python unittesterror.py
Ran 2 tests in 0.016s
After posting the bug, I discovered that by directly invoking the
TextTestRunner directly instead of calling unittest.main(), IronPython
executes the tests correctly.
-----Original Message-----
From: users-bounces at lists.ironpython.com
[mailto:users-bounces at lists.ironpython.com] On Behalf Of Martin Maly
Sent: Friday, January 20, 2006 11:44 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Procedure for Posting Bugs

Posting the bug on GotDotNet into the bug tracker is a great way to let us
know. We monitor the bug tracker continuously for new issues. Another,
equally valid, way is to send an email to this discussion alias. That way,
the community will also become aware of the problem and we can
follow-through discussing workarounds.





From: users-bounces at lists.ironpython.com
[mailto:users-bounces at lists.ironpython.com] On Behalf Of Jones, Larry
Sent: Friday, January 20, 2006 9:38 AM
To: 'users at lists.ironpython.com'
Subject: [IronPython] Procedure for Posting Bugs


Today, while using IronPython to execute unit tests, I discovered what may
be an error.


I have submitted it using the BugTracker link on the GotDotNet.com web page;
however, I'm unclear if that is how we are now posting defects.


How are we notifying the team of apparent errors in IronPython?





Lawrence Allan Jones
Senior Developer / Technical Advisor
Aspen Technology, Inc.
2500 CityWest Blvd. Suite 1500
Houston, Texas 77042
281-504-3324 (work)
281-504-3395 (fax)
larry.jones at aspentech.com <mailto:larry.jones at aspentech.com> 
www.aspentech.com <http://www.aspentech.com/> 




This e-mail and any attachments are intended only for use by the
addressee(s) named herein and may contain legally privileged and/or
confidential information. If you are not the intended recipient of this
e-mail, you are hereby notified any dissemination, distribution or copying
of this email, and any attachments thereto, is strictly prohibited. If you
receive this email in error please immediately notify the sender and
permanently delete the original copy and any copy of any e-mail, and any
printout thereof.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20060120/155cfc7b/attachment.html>

More information about the Ironpython-users mailing list