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 ncoghlan
Recipients Arfrever, berker.peksag, brett.cannon, eric.snow, larry, ncoghlan
Date 2013-11-11.23:19:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7eM4wDDm-+ZrChsJy3wKNCbADL4sN6oPg_5EZnjqQuT4w@mail.gmail.com>
In-reply-to <1384209885.37.0.368595610714.issue18864@psf.upfronthosting.co.za>
Content
Yeah, don't replace any tests, add new ones for the new APIs. Given the
needs of 2/3 compatible loader implementations, the deprecations referred
to in the PEP should also be documentation-only for 3.4.

A more conservative approach also gives us a chance to make sure we have
provided a full replacement for load_module - it occurred to me after the
PEP was accepted that we may eventually need a "can_load_into(target)"
loader API after all, since loaders may not be finder specific. That means
that with the current API of passing the target to find_spec, I potentially
talked us into repeating the "load_module" mistake on the finder side of
things by asking the finder to handle more than it needed to.
History
Date User Action Args
2013-11-11 23:19:27ncoghlansetrecipients: + ncoghlan, brett.cannon, larry, Arfrever, eric.snow, berker.peksag
2013-11-11 23:19:27ncoghlanlinkissue18864 messages
2013-11-11 23:19:27ncoghlancreate