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 | pitrou |
|---|---|
| Recipients | amaury.forgeotdarc, benjamin.peterson, christoph, georg.brandl, pitrou |
| Date | 2008年04月01日.06:41:06 |
| SpamBayes Score | 0.23201112 |
| Marked as misclassified | No |
| Message-id | <1207032069.76.0.0258023691029.issue2517@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Shouldn't it be an exception rather than a warning? The fact that an exception can be downgraded to a warning (and thus involuntarily silenced) is a bit disturbing IMHO. Another possibility would be to display the warning, and *then* to encode the exception message again in "replace" or "ignore" mode rather than "strict" mode. That way exception messages are always displayed, but not always properly. The ASCII part of the message is generally useful, since it gives the exception name and most often the reason too. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年04月01日 06:41:10 | pitrou | set | spambayes_score: 0.232011 -> 0.23201112 recipients: + pitrou, georg.brandl, amaury.forgeotdarc, benjamin.peterson, christoph |
| 2008年04月01日 06:41:09 | pitrou | set | spambayes_score: 0.232011 -> 0.232011 messageid: <1207032069.76.0.0258023691029.issue2517@psf.upfronthosting.co.za> |
| 2008年04月01日 06:41:07 | pitrou | link | issue2517 messages |
| 2008年04月01日 06:41:06 | pitrou | create | |