➜

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 larry
Recipients brett.cannon, eric.snow, larry, ncoghlan
Date 2013-12-22.18:45:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1387737903.73.0.797522660355.issue19927@psf.upfronthosting.co.za>
In-reply-to
Content 
1. Is this patch going to change best practice for working with ModuleSpec?

2. If we delayed it to 3.5, will users have to ignore it to work around the deficiencies of the ModuleSpec implementation in 3.4?

I'm guessing the answer to both of these is "well, no, not really" simply because comparing ModuleSpec objects is not expected to be a regular operation.
History
Date User Action Args
2013-12-22 18:45:03larrysetrecipients: + larry, brett.cannon, ncoghlan, eric.snow
2013-12-22 18:45:03larrysetmessageid: <1387737903.73.0.797522660355.issue19927@psf.upfronthosting.co.za>
2013-12-22 18:45:03larrylinkissue19927 messages
2013-12-22 18:45:03larrycreate