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 vstinner
Recipients chris.jerdonek, ned.deily, vstinner
Date 2012-07-28.12:39:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> Regardless of whether MAX_STRING_LENGTH is increased, my instinct is that the test should work for long install paths independent of the setting's value.  I wonder if there is a way to adjust the test so that the file name can still be checked in such a scenario (i.e. so that we do not simply add "or '...'" logic to the regular expression).

The purpose of the test is to check that the traceback is correct:
it's important to check that the filename ends with "". If
you don't know in which file the bug occured, the traceback is

Changing the MAX_STRING_LENGTH should be enough to fix this issue
before Python 3.3 final.
Date User Action Args
2012-07-28 12:39:05vstinnersetrecipients: + vstinner, ned.deily, chris.jerdonek
2012-07-28 12:39:05vstinnerlinkissue15463 messages
2012-07-28 12:39:05vstinnercreate