Message113693
| Author | mark.dickinson |
|---|---|
| Recipients | belopolsky, jdwhitley, mark.dickinson |
| Date | 2010-08-12.17:50:15 |
| SpamBayes Score | 0.0012861138 |
| Marked as misclassified | No |
| Message-id | <1281635417.69.0.212347471059.issue9574@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I don't think determining *which* whitespace is allowed is a problem; just use whatever's already being used for the whitespace that's already allowed (around the whole complex input, for example, or between the optional parentheses and the number). Please open a separate bug report for the UnicodeDecodeError. Though I have a suspicion/vague recollection that this has already come up somewhere in the tracker... |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-08-12 17:50:18 | mark.dickinson | set | recipients: + mark.dickinson, belopolsky, jdwhitley |
| 2010-08-12 17:50:17 | mark.dickinson | set | messageid: <1281635417.69.0.212347471059.issue9574@psf.upfronthosting.co.za> |
| 2010-08-12 17:50:16 | mark.dickinson | link | issue9574 messages |
| 2010-08-12 17:50:15 | mark.dickinson | create | |