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 | facundobatista |
|---|---|
| Recipients | facundobatista, georg.brandl, ncoghlan, nessus42, rhettinger, skip.montanaro |
| Date | 2008年03月19日.18:52:17 |
| SpamBayes Score | 0.1198503 |
| Marked as misclassified | No |
| Message-id | <1205952738.16.0.24027049769.issue1152248@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I took a look at it... It's not as not-complicated as I original thought. The way would be to adapt the Py_UniversalNewlineFread() function to *not* process the normal separators (like \n or \r), but the passed one. A critical point would be to handle more-than-1-byte characters... I concur with Nick that this would better suited for Py3k. So, I'm stepping down from this, and flagging it for that version. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月19日 18:52:18 | facundobatista | set | spambayes_score: 0.11985 -> 0.1198503 recipients: + facundobatista, rhettinger, birkenfeld, ncoghlan, montanaro.historic, nessus42 |
| 2008年03月19日 18:52:18 | facundobatista | set | spambayes_score: 0.11985 -> 0.11985 messageid: <1205952738.16.0.24027049769.issue1152248@psf.upfronthosting.co.za> |
| 2008年03月19日 18:52:17 | facundobatista | link | issue1152248 messages |
| 2008年03月19日 18:52:17 | facundobatista | create | |