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 | methane |
|---|---|
| Recipients | docs@python, methane |
| Date | 2016年08月03日.09:01:25 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1470214886.13.0.870924776007.issue27671@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
https://docs.python.org/3/faq/design.html#why-does-python-use-methods-for-some-functionality-e-g-list-index-but-functions-for-other-e-g-len-list > The major reason is history. ... > but it’s a part of Python, and it’s too late to make such fundamental changes now. The functions have to remain to avoid massive code breakage. People seeing this answer may think "it's bad design, but remains for historical reason." But there is more positive reason why len is still function. http://effbot.org/pyfaq/why-does-python-use-methods-for-some-functionality-e-g-list-index-but-functions-for-other-e-g-len-list.htm |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016年08月03日 09:01:26 | methane | set | recipients: + methane, docs@python |
| 2016年08月03日 09:01:26 | methane | set | messageid: <1470214886.13.0.870924776007.issue27671@psf.upfronthosting.co.za> |
| 2016年08月03日 09:01:26 | methane | link | issue27671 messages |
| 2016年08月03日 09:01:25 | methane | create | |