Larry Hastings added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19927> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
