Message 14329 - Python tracker

➜

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.

Recipients
Author	tim.peters
Date	2003年04月28日.19:55:05
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
Logged In: YES user_id=31435 Sorry, I've had nothing to do with mmap beyond fixing bugs. The "access" feature was due to Jay Miller, although I believe I checked in his patch. Martin, I don't understand why you think it's reasonable for flush to complain here: the mmap is open for writing, so what's surprising about expecting to be able to flush after a write? Simply that there's no associated file, due to copy-on- write? Then user code would have to be acutely aware of how an mmap'ed object was opened, just to avoid nuisance complaints when they flush after writing. So that's a third alternative: alter the implementation to make mmap.flush() do nothing when an mmap object was opened as copy-on-write.

Content

Logged In: YES 
user_id=31435
Sorry, I've had nothing to do with mmap beyond fixing bugs. 
The "access" feature was due to Jay Miller, although I believe 
I checked in his patch.
Martin, I don't understand why you think it's reasonable for 
flush to complain here: the mmap is open for writing, so 
what's surprising about expecting to be able to flush after a 
write? Simply that there's no associated file, due to copy-on-
write? Then user code would have to be acutely aware of how 
an mmap'ed object was opened, just to avoid nuisance 
complaints when they flush after writing.
So that's a third alternative: alter the implementation to make 
mmap.flush() do nothing when an mmap object was opened 
as copy-on-write.

History
Date	User	Action	Args
2007年08月23日 14:10:37	admin	link	issue678250 messages
2007年08月23日 14:10:37	admin	create

homepage