Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +brett.cannon, ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15867
___
___
Eric Snow added the comment:
As far as the import system goes, Barry Warsaw added a really nice page to the
language reference[1]. However, it sounds like your concern is with taking
advantage of the tools that importlib provides.
First of all, a good thing to recognize is that importlib
Brett Cannon added the comment:
First off, what you want to do isn't easy to begin with. =) You are right that
you want get_code() and that SourceLoader is what you want. The problem is that
importlib inherited PEP 302s APIs, and there are so many that the docs don't
repeat themselves in
Changes by Chris Jerdonek chris.jerdo...@gmail.com:
--
nosy: +cjerdonek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15867
___
___
Nick Coghlan added the comment:
One specific change we should make is that the see also at the start of the
3.3 importlib docs should link to the new section of the language reference,
rather than Guido's packaging essay. We can probably also cull that long list
of PEPs, moving it to the end
New submission from Julian Berman:
I find that the importlib documentation is a bit too low level. Import hooks
are not that common, so requiring a bit of reading is OK with me, but I
somewhat *understand* PEP 302, so I have a general idea of *what* I want to do
and what kind of objects can
Changes by Julian Berman julian+python@grayvines.com:
--
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15867
___
___
