[issue8454] unittest Module Problem with different Kinds of Invocation

Changes by Michael Foord : -- resolution: -> wont fix stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue8454] unittest Module Problem with different Kinds of Invocation

Michael Foord added the comment: I'm sure that there are many places using the API as it is, inserting a dummy entry into the argv they pass. Although the fix you propose would solve the problem for users who are currently using the API wrongly it would break code for people who are using it

[issue8454] unittest Module Problem with different Kinds of Invocation

Perbandt added the comment: Yes, the proposed fix would be an incompatible change. But my assumption is that in scenarios where main(...) is called programmatically the fix would correct an erroneous behavior. In these scenarios whatever is being passed as the first entry in the argv array ge

[issue8454] unittest Module Problem with different Kinds of Invocation

Michael Foord added the comment: That change would be backwards incompatible with existing scripts calling main(...) programattically though. -- ___ Python tracker ___ _

[issue8454] unittest Module Problem with different Kinds of Invocation

Changes by Ezio Melotti : -- nosy: +ezio.melotti, michael.foord versions: +Python 2.6, Python 2.7 -Python 2.5 ___ Python tracker ___ __

[issue8454] unittest Module Problem with different Kinds of Invocation

New submission from Perbandt : I just figured out a problem with the Python module 'unittest.py', version 1.63. The function '__init__' behaves a bit strange in certain circumstances. It is called either directly from the command line or it is called when unit tests are to be executeded from a s