-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Docs: replace an esoteric Von Neumann mention #137598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
79734e6 to
878fdcc
Compare
|
|
||
| .. XXX it *is* now possible in some cases to change an object's | ||
| type, under certain controlled conditions | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed this comment since it is now an actual footnote.
| is represented by objects or by relations between objects. Even code is | ||
| represented by objects. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code isn't represented by objects: the compiled bytecode, or the abstract tree, or the tokens are though. The previous sentence has "In a sense ... code is also represented by objects", which (by hedging) seems more accurate?
If the Von Neumann aside is to go, perhaps it makes more sense to bin the full sentence?:
| is represented by objects or by relations between objects. Even code is | |
| represented by objects. | |
| is represented by objects or by relations between objects. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd say for the first paragraph it's good enough to say code is represented by objects. It carries the point of the original sentence, to underscore how pervasive objects are in the Python world.
|
@AA-Turner any concerns about merging this? |
|
Thanks @nedbat for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
* Docs: replace an esoteric Von Neumann mention * oops, don't need to edit topics.py (cherry picked from commit 237dca5) Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>
* Docs: replace an esoteric Von Neumann mention * oops, don't need to edit topics.py (cherry picked from commit 237dca5) Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>
|
GH-140371 is a backport of this pull request to the 3.13 branch. |
|
Interestingly the bot successfully backported, miss-islington@1e62f3b, but did not open the PR. I will try re-applying the labels to jog it. |
|
Thanks @nedbat for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
* Docs: replace an esoteric Von Neumann mention * oops, don't need to edit topics.py (cherry picked from commit 237dca5) Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>
|
Sorry @nedbat, I had trouble completing the backport. |
|
Second time over, commit is created: miss-islington@11f701f yet the PR is not. Third time lucky? |
|
Thanks @nedbat for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
* Docs: replace an esoteric Von Neumann mention * oops, don't need to edit topics.py (cherry picked from commit 237dca5) Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>
|
Sorry @nedbat, I had trouble completing the backport. |
|
I fold, for the third time, Miss Islington successfully backports but fails on opening the PR. I will do it manually. |
|
GH-141071 is a backport of this pull request to the 3.14 branch. |
* Docs: replace an esoteric Von Neumann mention * oops, don't need to edit topics.py (cherry picked from commit 237dca5) Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>
|
It does indeed backport cleanly. |
* Docs: replace an esoteric Von Neumann mention * oops, don't need to edit topics.py
📚 Documentation preview 📚: https://cpython-previews--137598.org.readthedocs.build/