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 | brett.cannon |
|---|---|
| Recipients | brett.cannon, christian.heimes, gvanrossum |
| Date | 2007年10月20日.03:49:36 |
| SpamBayes Score | 0.05095283 |
| Marked as misclassified | No |
| Message-id | <1192852176.62.0.0513306170104.issue1267@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
58557 as the fix. Yes, it was stupid on OS X's part and I was lucky to just think of the possible solution. Basically OS X does not like it when you do stuff with a file pointer but then poke around with the file descriptor. That means that when PyTokenizer_FindEncoding() seeked on the file pointer it was not being picked up by the the file descriptor that the file pointer represented. This suggests that perhaps we should standardize on file pointers or file descriptors in Python to prevent something like this from happening again. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年10月20日 03:49:36 | brett.cannon | set | spambayes_score: 0.0509528 -> 0.05095283 recipients: + brett.cannon, gvanrossum, christian.heimes |
| 2007年10月20日 03:49:36 | brett.cannon | set | spambayes_score: 0.0509528 -> 0.0509528 messageid: <1192852176.62.0.0513306170104.issue1267@psf.upfronthosting.co.za> |
| 2007年10月20日 03:49:36 | brett.cannon | link | issue1267 messages |
| 2007年10月20日 03:49:36 | brett.cannon | create | |