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 | akuchling |
|---|---|
| Recipients | akuchling, loewis, pboddie, vdupras |
| Date | 2008年02月17日.01:55:39 |
| SpamBayes Score | 0.012813332 |
| Marked as misclassified | No |
| Message-id | <1203213340.37.0.330254099001.issue2124@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
What if we just tried to make the remote accesses apparent to the user, by making a warning.warn() call in the default implementation that was deactivated by a setFeature() call. With a warning, code will continue to run but the user will at least be aware they're hitting a remote resource, and can think about it, even if they decide to suppress the warning. We should also modify the docs to point this out; it's not likely to help very much, but it's still worth doing. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年02月17日 01:55:40 | akuchling | set | spambayes_score: 0.0128133 -> 0.012813332 recipients: + akuchling, loewis, pboddie, vdupras |
| 2008年02月17日 01:55:40 | akuchling | set | spambayes_score: 0.0128133 -> 0.0128133 messageid: <1203213340.37.0.330254099001.issue2124@psf.upfronthosting.co.za> |
| 2008年02月17日 01:55:39 | akuchling | link | issue2124 messages |
| 2008年02月17日 01:55:39 | akuchling | create | |