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 eric.araujo
Recipients eric.araujo
Date 2011-06-10.16:19:09
SpamBayes Score 0.00011897126
Marked as misclassified No
Message-id <1307722749.85.0.48203387339.issue12314@psf.upfronthosting.co.za>
In-reply-to
Content
When regrtest tells me that os.environ was modified by test_packaging, it’s very hard to find which test is responsible.  The -vv output is hard to read: it prints four dictionaries, which I have to visually delineate, copy, paste, pretty-print and diff to find what’s changed.  Then I edit the source code of regrtest so that it fails earlier, or I add a debug print in the packaging.util code that touches os.environ.

I’d like regrtest to tell me what exactly was changed, and where.  For the first request, I think each checked object could use a type-specific method, for example _compare_dict would see if any value was changed and if keys are different, and print only that info.
History
Date User Action Args
2011-06-10 16:19:09eric.araujosetrecipients: + eric.araujo
2011-06-10 16:19:09eric.araujosetmessageid: <1307722749.85.0.48203387339.issue12314@psf.upfronthosting.co.za>
2011-06-10 16:19:09eric.araujolinkissue12314 messages
2011-06-10 16:19:09eric.araujocreate