I apologize, Dino. I didn't take advantage of the moment during today's
C# chat to plug the job req you've been advertising.
Someone asked in the chat today about Microsoft's commitment to
"lightweight programming frameworks". I mentioned the IP had hit 1.0b4
today, but didn't mention that y'all
We support some of these but not all of them right now. Currently these should
work:
__add__, __sub__, __pow__, __mul__, __floordiv__, __div__, __truediv__,
__mod__, __lshift__, __rshift__, __and__, __or__, __xor__, __lt__, __gt__,
__le__, __ge__, __eq__, and __ne__ and all of the r and i vers
I am relatively new to Python, I have been playing with a CPython and
IronPython.
Does IronPython support special methods? For example:
>>> class C:
... v=0
... def __init__(self,v):
... self.v=v
... def __int__(self):
... return int(self.v)
...
>>> c=C(33)
Have you added the location of test.dll to your path yet?
If not you need to do that first. We do not search the current directory, only
the path. So if you want the CWD you'll need to do:
import nt
import clr
clr.Path.append(nt.getcwd())
and then clr.AddReferenceToFile() should work fine.
T
Hello,
I have a doubt:
In IP Beta 2, I was able to write:
>>>import clr
>>>clr.AddReferenceToFile("test.dll")
>>>import test
>>>
but in Beta 4, if I write clr.AddReferenceToFile("test.dll") I get:
Traceback (most recent call last):
File , line 0, in input##678
File , line 0, in AddReference
Thanks Stan, I'll give it a look.
>From: Stanislas Pinte <[EMAIL PROTECTED]>
>To: Discussion of IronPython ,"Todd M. Chapman"
><[EMAIL PROTECTED]>
>CC: users@lists.ironpython.com
>Subject: Re: [IronPython] Compatibility with .NET 1.1
>Date: Thu, 9 Mar 2006 16:44:11 +
>
>Hi Todd,
>
>you may
Hello IronPython Community,
We have just released IronPython 1.0 Beta 4. This is yet
another release focusing primarily on fixing bugs. Since the beta 3 release
we’ve cut our active number of bugs in half. Unfortunately we
didn’t get to review the PythonEngine APIs in this release bu
Dino Viehland wrote:
> The first bug will be fixed in beta 4 - we've done a bunch of cleanup around
> the file class to make it all around more compatible with CPython. That not
> only includes fixing binary mode but also fixing universal new line mode to
> be much more compatible. FYI beta 4
The first bug will be fixed in beta 4 - we've done a bunch of cleanup around
the file class to make it all around more compatible with CPython. That not
only includes fixing binary mode but also fixing universal new line mode to be
much more compatible. FYI beta 4 should be available real soon
Hi Todd,
you may want to use PythonDotNet...still in 1.1, and working nicely.
http://www.zope.org/Members/Brian/PythonNet/
Stan.
Selon "Todd M. Chapman" <[EMAIL PROTECTED]>:
> I'm doing quite a bit of work with Microsoft CRM. CRM is based on .NET 1.1
> and there's not much chance of that cha
Has anyone at MS made any specific commitments to Iron
Python? I am trying to get my company to standardize on IP for our build
scripting and configuration Management. It seems a natural fit since we are
going the Team Foundation Server route. But I need to build a case and this
will be o
I'm doing quite a bit of work with Microsoft CRM. CRM is based on .NET 1.1
and there's not much chance of that changing until the next major release in
2007 or so. I see some really solid benefits of using IP with CRM for
administrative tasks, prototyping, etc. Although IP is currently based
Hi,
I've got a gripe with IronPython's file implementation. The following code
produces two different results in CPython and IronPython:
print ''.join('%02x' % ord(c) for c in file('some_binary_file').read(32))
CPython:
01044c1045a1470ec20112012000ec0f03006f1efcc5
IronPytho
13 matches
Mail list logo
