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 | cito |
|---|---|
| Recipients | benjamin.peterson, cito, mishok13, rhettinger |
| Date | 2008年07月14日.23:40:25 |
| SpamBayes Score | 0.0025011736 |
| Marked as misclassified | No |
| Message-id | <1216078826.4.0.800253519833.issue3354@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Agree. Seems to be a more general weakness of the argument parsing of builtin functions and methods, that calls for a general solution instead of a local patch. Luckily there are not so many cases where the errors are misleading, since the builtin functions have very few and mostly positioned parameters, so the problem is not as bad as it seems. There may be only very few cases, like the example above, where the errors are really too unspecific or misleading. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月14日 23:40:26 | cito | set | spambayes_score: 0.00250117 -> 0.0025011736 recipients: + cito, rhettinger, benjamin.peterson, mishok13 |
| 2008年07月14日 23:40:26 | cito | set | spambayes_score: 0.00250117 -> 0.00250117 messageid: <1216078826.4.0.800253519833.issue3354@psf.upfronthosting.co.za> |
| 2008年07月14日 23:40:25 | cito | link | issue3354 messages |
| 2008年07月14日 23:40:25 | cito | create | |