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 | gregory.p.smith |
|---|---|
| Recipients | anthonybaxter, christian.heimes, georg.brandl, gregory.p.smith, jafo, janixia, jhylton, jyasskin, loewis, pitrou, tim.peters |
| Date | 2008年04月06日.06:25:04 |
| SpamBayes Score | 0.010335307 |
| Marked as misclassified | No |
| Message-id | <1207463111.88.0.471066510324.issue815646@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I've attached my patch that I want to commit. The main change from filethread4 is some cleanup in file_test to make it run a lot faster and add verbose mode output to indicate how well it is actually testing the problem (counting the times that close raises IOError). One concern holding up my commit: Will this test pass on windows? It is opening and closing the same file in 'w+' mode from multiple threads of the same process at once. Can someone with a windows dev environment please apply this patch and test it. If it dislikes the above file behavior, can you propose a fix for it (set windows file non-exclusive flags or whatever you're supposed to do... the worse alternative would be to use a new filename on each open but that could cause a nightmare of thousands of new files being created by the test which then have to be cleaned up)? thanks, -gps |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年04月06日 06:25:12 | gregory.p.smith | set | spambayes_score: 0.0103353 -> 0.010335307 recipients: + gregory.p.smith, tim.peters, loewis, jhylton, anthonybaxter, georg.brandl, jafo, janixia, pitrou, christian.heimes, jyasskin |
| 2008年04月06日 06:25:11 | gregory.p.smith | set | spambayes_score: 0.0103353 -> 0.0103353 messageid: <1207463111.88.0.471066510324.issue815646@psf.upfronthosting.co.za> |
| 2008年04月06日 06:25:10 | gregory.p.smith | link | issue815646 messages |
| 2008年04月06日 06:25:10 | gregory.p.smith | create | |