- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message411087
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 | tim.peters |
|---|---|
| Recipients | Dennis Sweeney, dam1784, eric.smith, python-dev, rhettinger, tim.peters |
| Date | 2022-01-21.05:46:25 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1642743985.93.0.122925102988.issue46071@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
>> the meanings of "predecessor" and "successor" are >> universally agreed upon > I disagree. I can post literally hundreds of citations that all agree: in u -> v, u is a direct predecessor of v, and v is a direct successor of u. Here's one: http://pages.cs.wisc.edu/~vernon/cs367/notes/13.GRAPH.html Here's another from a Python context: https://networkx.org/documentation/stable/reference/classes/generated/networkx.DiGraph.predecessors.html """ A predecessor of n is a node m such that there exists a directed edge from m to n. """ On & on & on. Hence my "universal". Can you link to any that disagree? As to the meaning of "point to", in "u -> v" it's obvious that the arrow points _from_ u _to_ v. I very strongly doubt you can find a credible source disputing that either. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-01-21 05:46:25 | tim.peters | set | recipients: + tim.peters, rhettinger, eric.smith, python-dev, Dennis Sweeney, dam1784 |
| 2022-01-21 05:46:25 | tim.peters | set | messageid: <1642743985.93.0.122925102988.issue46071@roundup.psfhosted.org> |
| 2022-01-21 05:46:25 | tim.peters | link | issue46071 messages |
| 2022-01-21 05:46:25 | tim.peters | create | |

