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 | anthonybaxter, christian.heimes, jafo, janixia, jhylton, loewis, pitrou, tim.peters |
| Date | 2008年03月28日.18:20:44 |
| SpamBayes Score | 0.28508484 |
| Marked as misclassified | No |
| Message-id | <1206728445.2.0.626667070174.issue815646@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Another approach would be to add a dedicated lock for each PyFileObject. This sounds a bit bad performance-wise but after all the GIL itself is a lock, and we release and re-acquire it on each file operation, so why not? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月28日 18:20:45 | pitrou | set | spambayes_score: 0.285085 -> 0.28508484 recipients: + pitrou, tim.peters, loewis, jhylton, anthonybaxter, jafo, janixia, christian.heimes |
| 2008年03月28日 18:20:45 | pitrou | set | spambayes_score: 0.285085 -> 0.285085 messageid: <1206728445.2.0.626667070174.issue815646@psf.upfronthosting.co.za> |
| 2008年03月28日 18:20:44 | pitrou | link | issue815646 messages |
| 2008年03月28日 18:20:44 | pitrou | create | |