- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message391030
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 | aidan.feldman |
|---|---|
| Recipients | aidan.feldman, docs@python |
| Date | 2021-04-14.04:38:04 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1618375085.85.0.211628673766.issue43837@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
I am teaching a class on Python for people who are new to coding, and I was talking them through the operator precedence table: https://docs.python.org/3/reference/expressions.html#operator-precedence A couple things that confused the students: - "Highest precedence" is on the bottom, while "lowest precedence" is on top - There isn't any mention of variables. While not operators, probably worth mentioning that they (effectively?) have higher precedence than any of the operators. I'd be happy to try making my first contribution to Python if there's interest in those edits. Also, I have an example breaking down operator precedence in practice here, which I could include: https://colab.research.google.com/github/afeld/python-public-policy/blob/main/lecture_2.ipynb#scrollTo=UTxeT5RvqSFl Thanks! |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2021-04-14 04:38:05 | aidan.feldman | set | recipients: + aidan.feldman, docs@python |
| 2021-04-14 04:38:05 | aidan.feldman | set | messageid: <1618375085.85.0.211628673766.issue43837@roundup.psfhosted.org> |
| 2021-04-14 04:38:05 | aidan.feldman | link | issue43837 messages |
| 2021-04-14 04:38:04 | aidan.feldman | create | |

