Thanks Dino.
Incidentally, for some reason, mmap objects are constructed with filenos
rather than files, which may complicate matters for you... in Ironclad
I'm planning to get around this by forcing users to use real
PyFileObjects if they want to mmap them. In the general case it'll be an
annoying departure from the intended transparency, but at least I can
patch known-mmaping modules like numpy.core.memmap so that they, at
least, silently use the correct file type.
(Yes, it's evil, but it seems to be the least evil option; if anyone has
a better suggestion (or is writing code which assumes uniqueness of ipy
filenos), please let me know.)
Dino Viehland wrote:
Harry had started implementing _csv but I think he's stalled out on
playing w/ __clrtype__. No one here has touched mmap - I believe
.NET 4.0 will have a managed wrapper around memory mapped files
which would give us a chance to do it in the future but until then
we wouldn't even think about it.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of William Reade
Sent: Tuesday, May 19, 2009 2:37 AM
To: Discussion of IronPython
Subject: [IronPython] mmap, csv, others
Hi all
Life permitting, the next version of Ironclad should have a few of the
built-in C extensions included in it. I have vague plans that the first
two will be mmap and _csv (because I've had to fake both of those out
for numpy); however, I just wanted to check whether anybody else was
doing the same thing.
Cheers
william
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
