BTW, if you find the bytecode-specific APIs are sub-par while trying to
update them, let me know as I have been toying with cleaning them up and
centralizing them under importlib for a while and just never gotten around
to sitting down and coming up with a better design that warranted putting
the t
Thanks, Guido and everyone who submitted feedback!
I guess I know what I'll be doing this weekend.
On Fri, Sep 29, 2017, at 08:18, Guido van Rossum wrote:
> Let me try that again.
>
> There have been no further comments. PEP 552 is now accepted.
>
> Congrats, Benjamin! Go ahead and send your im
ACTIVITY SUMMARY (2017-09-22 - 2017-09-29)
Python tracker at https://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open6208 (+12)
closed 37181 (+74)
total 43389 (+86)
Open issues wi
Let me try that again.
There have been no further comments. PEP 552 is now accepted.
Congrats, Benjamin! Go ahead and send your implementation for review.Oops.
Let me try that again.
PS. PEP 550 is still unaccepted, awaiting a new revision from Yury and
Elvis.
--
--Guido van Rossum (python.org
Hi all,
Do the accepted PEP were 552, not 550?
Thanks,
Louie.
2017-09-29 22:40 GMT+08:00 Guido van Rossum :
> It's Friday!
>
> There have been no further comments. PEP 550 is now accepted.
>
> Congrats, Benjamin! Go ahead and send your implementation for review.
>
> --Guido
>
> On Tue, Sep 26,
It's Friday!
There have been no further comments. PEP 550 is now accepted.
Congrats, Benjamin! Go ahead and send your implementation for review.
--Guido
On Tue, Sep 26, 2017 at 1:47 PM, Guido van Rossum wrote:
> I've read the current version of PEP 552 over and I think everything looks
> good
