Hi all
Not sure if this is the right forum, but I ask my question anyway.
I would like to use IronPython for creating a hardware testing environment,
consisting of a Device Under Test and some
measurement equipment like a lab power supply and voltage meter and things
like that.
These
Bug added to DLR project.
From: Curt Hagenlocher
Sent: Sunday, March 15, 2009 11:50 PM
To: Discussion of IronPython
Subject: Re: [IronPython] IPy embedding problem
Can you please open a bug for this on the DLR site
(http://www.codeplex.com/dlr)? There's a few methods that basically have
The resolution of that bug was that we now expose explicitly implemented
interfaces automatically if there are no naming conflicts. But with COM it's
usually a different story - the members should always just be there. Do the
interop libraries use explicit interface implementation (if they
That did the trick. Thanks!
- Jeff
On Sun, Mar 15, 2009 at 3:15 PM, Curt Hagenlocher c...@hagenlocher.org wrote:
You probably need to run with -X:Python26 (for now).
On Sun, Mar 15, 2009 at 1:34 PM, Jeff Hardy jdha...@gmail.com wrote:
Hi,
Both byte literals (#19544) and the with statement
Hi,
Is there any quick workaround for #21569? It's causing about a third
of the Genshi errors I'm hitting. Trying to override __init__ in the
subclass gives the same error.
class Foo(unicode):
def __init__(self, val):
pass
f = Foo(1)
Traceback (most recent call last):
File foo.py,
Jeff Hardy wrote:
Hi,
Is there any quick workaround for #21569? It's causing about a third
of the Genshi errors I'm hitting. Trying to override __init__ in the
subclass gives the same error.
class Foo(unicode):
def __init__(self, val):
pass
f = Foo(1)
Traceback (most recent call
Does this make it work?
class x(unicode):
def __init__(self, val): pass
def __new__(cls, val):
return unicode.__new__(cls, unicode(val))
x(1)
I've voted for the bug and raised the priority to medium. I've left it
proposed until we triage it as a team (we triage bugs every
It works on CPython 2.6 at least. You should only have to override __new__ if
you wanted to support different arguments than str/unicode.__new__ supports.
-Original Message-
From: users-boun...@lists.ironpython.com [mailto:users-
boun...@lists.ironpython.com] On Behalf Of Michael
Dino Viehland wrote:
It works on CPython 2.6 at least. You should only have to override __new__ if
you wanted to support different arguments than str/unicode.__new__ supports.
Of course. D'oh - it was late, and is now even later. :-)
Michael
-Original Message-
From:
