Message115174
| Author | jdwhitley |
|---|---|
| Recipients | belopolsky, jdwhitley, mark.dickinson |
| Date | 2010-08-29.01:41:19 |
| SpamBayes Score | 4.2427388e-07 |
| Marked as misclassified | No |
| Message-id | <1283046082.72.0.062114866377.issue9574@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I can write a documentation patch for this: http://docs.python.org/library/functions.html?highlight=complex#complex to highlight the expected format of the string argument. As others have pointed out here, there are a number of other options available to correctly parse the complex string argument: * using eval where appropriate; and * preprocessing to remove whitespace. I think that the current options are sufficient that a patch to apply new behaviour isn't required. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-08-29 01:41:23 | jdwhitley | set | recipients: + jdwhitley, mark.dickinson, belopolsky |
| 2010-08-29 01:41:22 | jdwhitley | set | messageid: <1283046082.72.0.062114866377.issue9574@psf.upfronthosting.co.za> |
| 2010-08-29 01:41:21 | jdwhitley | link | issue9574 messages |
| 2010-08-29 01:41:20 | jdwhitley | create | |