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 ethan.furman
Recipients ethan.furman, ncoghlan
Date 2012-03-27.21:05:16
SpamBayes Score 6.950198e-07
Marked as misclassified No
Message-id <4F722D9F.4070902@stoneleaf.us>
In-reply-to <1330470032.4.0.693972542446.issue14136@psf.upfronthosting.co.za>
Content
Nick Coghlan wrote:
> Nick Coghlan <ncoghlan@gmail.com> added the comment:
> 
> Hah, I've been dealing with Python's regression test suite for 8+ years and there are still cases where I don't understand the rationale for testing things a particular way (beyond "it must have seemed like a good idea at the time"). It has a lot more historical cruft than the standard library does :)
> 
> The "proper" location for a particular test can be a bit of a coin toss in many cases, but one useful guide (which applies in this case) is to try to avoid adding *new* standard library dependencies to a test module if there's an alternate suitable location that already has those dependencies.

I just checked the patch and it still applies cleanly with the two 
effected tests passing.

Nick, any chance of getting this checked in and closed?
History
Date User Action Args
2012-03-27 21:05:18ethan.furmansetrecipients: + ethan.furman, ncoghlan
2012-03-27 21:05:17ethan.furmanlinkissue14136 messages
2012-03-27 21:05:16ethan.furmancreate