This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Julian.Scheid
Recipients Julian.Scheid, barry, georg.brandl, lregebro, ncoghlan, r.david.murray
Date 2010-04-15.10:53:35
SpamBayes Score 6.946671e-08
Marked as misclassified No
Message-id <1271328817.57.0.0361384339544.issue7490@psf.upfronthosting.co.za>
In-reply-to
Content
Having this in 2.6/2.7 would be great.

I don't think the ELLIPSIS workaround suggested by Barry works, have you actually tried it?

Below is an example where ELLIPSIS doesn't seem to help (run in 2.6.5).  I have also tried "...Error:" and "...:", and tried replacing ". . ." by "...", to no avail.

I'm assuming this has to do with issue #1192554, or am I making a silly mistake?

Otherwise, are there any other workarounds you can suggest?

Without ellipsis the following example works in 2.6 but of course fails in 3.x.

Failed example:
    Redacted.from_str('1-7@') #doctest: +ELLIPSIS
Expected:
    Traceback (most recent call last):
      . . .
    ...ParserError: <message redacted>:
    1-7@
        ^
    expected digit
Got:
    Traceback (most recent call last):
      <SNIP>
    ParserError: <message redacted>:
    1-7@
        ^
    expected digit
History
Date User Action Args
2010-04-15 10:53:38Julian.Scheidsetrecipients: + Julian.Scheid, barry, georg.brandl, ncoghlan, lregebro, r.david.murray
2010-04-15 10:53:37Julian.Scheidsetmessageid: <1271328817.57.0.0361384339544.issue7490@psf.upfronthosting.co.za>
2010-04-15 10:53:36Julian.Scheidlinkissue7490 messages
2010-04-15 10:53:35Julian.Scheidcreate