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 | jafo |
|---|---|
| Recipients | effbot, fdrake, jafo, nirs |
| Date | 2007年09月17日.11:05:19 |
| SpamBayes Score | 0.08385045 |
| Marked as misclassified | No |
| Message-id | <1190027120.19.0.201352326943.issue1123@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I believe this is just a place where the documentation could be cleared up. Seems to me the confusion is from the document saying (paraphrased): "white space is removed from both ends". Perhaps it should say something like "runs of 1 or more whitespace are collapsed (up to the maximum split), and then split on" or simply "split on runs of 1 or more whitespace. In other words, 3 spaces together would be treated as a single split-point instead of 3 0-length fields separated by spaces." So, in the first example provided by "nirs" in this issue, "both ends" refers to both the left and right side of "k:". Since maxsplit is 1, the second part (v) is left untouched. This is the intended operation. This is a documentation bug, not a library bug. Fred: Thoughts on wording? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年09月17日 11:05:20 | jafo | set | spambayes_score: 0.0838505 -> 0.08385045 recipients: + jafo, fdrake, effbot, nirs |
| 2007年09月17日 11:05:20 | jafo | set | spambayes_score: 0.0838505 -> 0.0838505 messageid: <1190027120.19.0.201352326943.issue1123@psf.upfronthosting.co.za> |
| 2007年09月17日 11:05:20 | jafo | link | issue1123 messages |
| 2007年09月17日 11:05:19 | jafo | create | |