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 abarry
Recipients ThiefMaster, abarry, ezio.melotti, gvanrossum, mrabarnett
Date 2016-01-09.21:39:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452375570.99.0.855885499651.issue26068@psf.upfronthosting.co.za>
In-reply-to
Content
Truncating at 200 characters is actually a common occurrence in the C code, just barely anyone notice this, as it's not common to need more than 200 characters for most expressions.

I don't think this needs to be changed at all; the rare case should not affect the common ones. If eval()'ing your repr fails, you can always access the full regex from `exp.pattern` - which doesn't truncate at 200 characters :)
History
Date User Action Args
2016-01-09 21:39:31abarrysetrecipients: + abarry, gvanrossum, ezio.melotti, mrabarnett, ThiefMaster
2016-01-09 21:39:30abarrysetmessageid: <1452375570.99.0.855885499651.issue26068@psf.upfronthosting.co.za>
2016-01-09 21:39:30abarrylinkissue26068 messages
2016-01-09 21:39:30abarrycreate