Message86224
| Author |
shamilbi |
| Recipients |
shamilbi, vinay.sajip |
| Date |
2009年04月21日.08:37:56 |
| SpamBayes Score |
7.673721e-07 |
| Marked as misclassified |
No |
| Message-id |
<cd7fd19c0904210137o4e89d3d5h19947a4d554e5aa5@mail.gmail.com> |
| In-reply-to |
<1240294054.15.0.04277158269.issue5170@psf.upfronthosting.co.za> |
| Content |
>
> Can you retry with setting the "encoding" attribute of the file to
> "cp1251"? That should work and that should be the appropriate method to
> avoid the problem.
>
> test_logging.py in the Python distribution has a test which exercises
> Unicode functionality using cp1251, does that test work in your
> environment?
logging to file is OK (since 2.6.2), logging to console __was__ OK (2.6.1),
not now (2.6.2)
shamil |
| Files |
| File name |
Uploaded |
|
unnamed
|
shamilbi,
2009年04月21日.08:37:56
|
|