ypes.
-Original Message-
From: users-boun...@lists.ironpython.com [mailto:users-
boun...@lists.ironpython.com] On Behalf Of Tom Wright
Sent: Tuesday, November 10, 2009 10:08 AM
To: Discussion of IronPython
Subject: Re: [IronPython] clr.CompileSubclassTypes restrictions on list of
types
Than
e w/ the way you
split them up.
-Original Message-
From: users-boun...@lists.ironpython.com [mailto:users-
boun...@lists.ironpython.com] On Behalf Of Tom Wright
Sent: Tuesday, November 10, 2009 9:39 AM
To: Discussion of IronPython
Subject: [IronPython] clr.CompileSubclassTypes restrictions on
Hi,
Are there any restrictions placed on the list of types that can be
passed to CompileSubclassTypes?
We are having issues with a clr.AddReference(DllContainingSubclasses)
being very slow, so are trying to split the compiled subclasses across
multiple dlls to indicate progress between the l
/IronPython/WorkItem/View.aspx?WorkItemId=20921
for more details and a repro.
Tom Wright
Resolver Systems Ltd.
___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
ciate that this is problematic
and that there are good reasons for having PythonFiles wrap FileStreams.
Tom
William Reade wrote:
Just a quick note: you can't necessarily just P/invoke out to msvcrt,
because CPython was built with msvcr71. Sorry :(.
Tom Wright wrote:
I'm not sur
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython and file descriptors
On Mon, Dec 15, 2008 at 11:18 AM, Tom Wright
mailto:tom.wri...@resolversystems.com>> wrote:
> Agreed. It is certainly possible with some work to get a file
descriptor and
> pa
t directly on top of Windows HANDLE
To get from the IronPython fd to a clib fd, you need to translate down
the first chain and up the second.
On Mon, Dec 15, 2008 at 9:37 AM, Tom Wright
<mailto:tom.wri...@resolversystems.com>> wrote:
Not so: Though admittedly you have to do quite a bi
see a way to get handles for stdin, stdout or stderr, though,
except that these ought to be easy to translate by hand.
On Mon, Dec 15, 2008 at 8:03 AM, Tom Wright
<mailto:tom.wri...@resolversystems.com>> wrote:
Hi,
At the moment file.fileno() returns an arbitrary identifier
Hi,
At the moment file.fileno() returns an arbitrary identifier of a python
file rather than a true file descriptor. This is semi-blocking the
Ironclad port of PIL.
Code in PIL gets an integer using fileno() and passes it directly to C
code where a call to write() is made. To fix this one w
