[issue30372] Status of __builtins__ is not totally clear

2017-05-22 Thread Mariatta Wijaya
Mariatta Wijaya added the comment: PR merged, and I backport it to 3.6 Thanks everyone :) -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue30372] Status of __builtins__ is not totally clear

2017-05-22 Thread Mariatta Wijaya
Mariatta Wijaya added the comment: New changeset 3d3b189f8ef321ccfb144a46d50892939d6004aa by Mariatta in branch '3.6': [3.6] bpo-30372: Clarify that '__builtins__' is a CPython Implementation detail (GH-1725) (GH-1727) https://github.com/python/cpython/commit/3d3b189f8ef321ccfb144a46d50892939d

[issue30372] Status of __builtins__ is not totally clear

2017-05-22 Thread Mariatta Wijaya
Changes by Mariatta Wijaya : -- pull_requests: +1817 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue30372] Status of __builtins__ is not totally clear

2017-05-22 Thread Mariatta Wijaya
Mariatta Wijaya added the comment: New changeset 43c8a9e39bb2d4f25ed7ae17a55f34e375d1868b by Mariatta (Naomi Ceder) in branch 'master': bpo-30372: Clarify that '__builtins__' is a CPython Implementation detail (GH-1725) https://github.com/python/cpython/commit/43c8a9e39bb2d4f25ed7ae17a55f34e37

[issue30372] Status of __builtins__ is not totally clear

2017-05-22 Thread Mariatta Wijaya
Changes by Mariatta Wijaya : -- stage: needs patch -> patch review versions: +Python 3.7 ___ Python tracker ___ ___ Python-bugs-list m

[issue30372] Status of __builtins__ is not totally clear

2017-05-22 Thread Naomi Ceder
Naomi Ceder added the comment: Created a PR on this... it seems that making the Implementation Detail warning come first and deleting the limited execution sentence achieves what's needed here. -- nosy: +NaomiCeder ___ Python tracker

[issue30372] Status of __builtins__ is not totally clear

2017-05-22 Thread Naomi Ceder
Changes by Naomi Ceder : -- pull_requests: +1813 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue30372] Status of __builtins__ is not totally clear

2017-05-19 Thread Terry J. Reedy
Terry J. Reedy added the comment: Moving "CPython implementation detail: " up a paragraph should be trivial. Resolving the conflict between " __builtins__ can be set to a user-created dictionary to create a weak form of restricted execution." and "Users should not touch __builtins__;" seems l

[issue30372] Status of __builtins__ is not totally clear

2017-05-16 Thread Brett Cannon
Brett Cannon added the comment: You're correct that both are CPython implementation details and could be more clearly marked as such. (In case anyone is curious, the code to look up __import__() can be found at https://github.com/python/cpython/blob/c7ac7280c321b3c1679fe5f657a6be0f86adf173/Pyt

[issue30372] Status of __builtins__ is not totally clear

2017-05-15 Thread Malcolm Smith
New submission from Malcolm Smith: https://docs.python.org/3.6/reference/executionmodel.html#builtins-and-restricted-execution describes the various things you can do with __builtins__, but then says "Users should not touch __builtins__; it is strictly an implementation detail." If this is so,