Issue 1774369: Unify builtins -> builtin (original) (raw)

Issue1774369

➜

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.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/45310

classification

process

Created on 2007-08-14 22:35 by christian.heimes, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (4)
msg53026 - (view)	Author: Christian Heimes (christian.heimes) *	Date: 2007-08-14 22:35
The patch renames __builtins__ to __builtin__ in the C and Python sources and renames builtins to builtin in the C code. Missing: * documentation update * 2to3 fixer
msg53027 - (view)	Author: Guido van Rossum (gvanrossum) *	Date: 2007-08-18 20:34
Thanks! (Though I wish you'd left the C variable names alone, the patch is unnecessarily big this way.) I am also wondering about some semantic endcases; in 2.x, it is *possible* to have __builtin__ and __builtins__ point to different place, and I am going to do some soul-searching to make sure that's not a loss of functionality. No need to update the patch, I just have to think about it some more.
msg53028 - (view)	Author: Christian Heimes (christian.heimes) *	Date: 2007-08-19 13:50
Personally I prefer to have one and just one way to spell a variable. I'd find it confusing to have __builtin__ (singular form) but a C variable named builtins (plural form). I changed it for aesthetic and consistency reasons.
msg55452 - (view)	Author: Guido van Rossum (gvanrossum) *	Date: 2007-08-30 00:26
I've thought this over very carefully, and I want something different -- I want to keep both concepts, but I want to rename __builtins__ to __rootns__ (i.e. Root namespace), indicating its purpose. This will prevent further confusion while not conflating the two different features.