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 | rhettinger |
|---|---|
| Recipients | benjamin.peterson, cito, mishok13, rhettinger |
| Date | 2008年07月14日.21:44:21 |
| SpamBayes Score | 0.019328665 |
| Marked as misclassified | No |
| Message-id | <1216071863.47.0.99460635021.issue3354@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I think this is closer to a language wide change and should probably be addressed for 2.7 and 3.1. It would be great to change the C argument parsing API to make its error messages more specific. For Py2.6, I think things are fine as it stands. This isn't a bug (tests pass, it matches results from previous pythons, etc) Reclassifying as a feature request for improved error reports for the argument parsing API. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月14日 21:44:23 | rhettinger | set | spambayes_score: 0.0193287 -> 0.019328665 recipients: + rhettinger, cito, benjamin.peterson, mishok13 |
| 2008年07月14日 21:44:23 | rhettinger | set | spambayes_score: 0.0193287 -> 0.0193287 messageid: <1216071863.47.0.99460635021.issue3354@psf.upfronthosting.co.za> |
| 2008年07月14日 21:44:22 | rhettinger | link | issue3354 messages |
| 2008年07月14日 21:44:22 | rhettinger | create | |