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 paul.moore
Recipients brett.cannon, eric.snow, erik.bray, jdemeyer, ncoghlan, paul.moore, petr.viktorin, scoder, sth
Date 2018-08-05.17:13:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CACac1F_Wyoh_b=DQpx=oc=QNU=j+1doGSRSY=XXrY_m8DFw5qw@mail.gmail.com>
In-reply-to <CAP1=2W74nkt=+RgY6M5A+ptgo3=xHSLvQmPOSni8Mc+De8xQ9Q@mail.gmail.com>
Content
On Sun, 5 Aug 2018 at 18:10, Brett Cannon <report@bugs.python.org> wrote:

> One other thing I will say is that the PEP 302 APIs were seemingly designed
> for working with Python source and were not necessarily oriented towards
> alternative code representations that were executed, e.g. Quixote was
> supported because it transpiled to Python source (although Paul is a
> co-author on the PEP and could more definitively answer 😄). IOW the APIs
> are oriented towards the Python programming language, not the CPython
> interpreter. This is why, for instance, I'm suggesting that if a more
> general solution is desired to be made official, then trying to force
> everything into the current APIs might not turn out well

That's how I recall it. The only cases we really considered were Python
modules (source code plus pyc) and extension modules (no source, loader
should return None).

Paul
History
Date User Action Args
2018-08-05 17:13:42paul.mooresetrecipients: + paul.moore, brett.cannon, ncoghlan, scoder, petr.viktorin, erik.bray, eric.snow, sth, jdemeyer
2018-08-05 17:13:42paul.moorelinkissue32797 messages
2018-08-05 17:13:42paul.moorecreate