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 | mkc |
|---|---|
| Recipients | effbot, fdrake, jburgy, mkc, skip.montanaro, tim.peters |
| Date | 2007年09月03日.21:22:28 |
| SpamBayes Score | 0.008609702 |
| Marked as misclassified | No |
| Message-id | <1188854549.5.0.903815986295.issue852532@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Well, I think we can conclude that it's expected by *them*. :-) I still find it surprising, and it somewhat lessens the utility of re.split for my use cases. (I think re.finditer may also suffer from the same problem, but I don't recall.) If you look at the comments attached to the patch for this bug, it looks like akuchling and rhettinger more or less saw this as being a bug worth fixing, though there were questions about exactly what the correct fix should be. http://bugs.python.org/issue988761 One comment about the your doc fix: You highlight a fairly useless zero-character match (e.g., "x*") to demonstrate the behavior, which might leave the user scratching his head. (I think this case was originally mentioned as a corner case, not one that would be useful.) It'd be nice to highlight a more useful case like '^(?=S)' or perhaps a little more generically something like '^(?=HEADER)' or '^(?=BEGIN)' which is a usage that tripped me up in the first place. Thanks for working on this! |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年09月03日 21:22:30 | mkc | set | spambayes_score: 0.0086097 -> 0.008609702 recipients: + mkc, tim.peters, fdrake, effbot, skip.montanaro, jburgy |
| 2007年09月03日 21:22:29 | mkc | set | spambayes_score: 0.0086097 -> 0.0086097 messageid: <1188854549.5.0.903815986295.issue852532@psf.upfronthosting.co.za> |
| 2007年09月03日 21:22:29 | mkc | link | issue852532 messages |
| 2007年09月03日 21:22:28 | mkc | create | |