Re: [IronPython] Welcome Curt to the IronPython team

[Keith J. Farmer]

Yay Curt!

-Original Message-
From: Shri Borde <[EMAIL PROTECTED]>
Sent: Wednesday, 07 May, 2008 14:52
To: Discussion of IronPython 
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Subject: [IronPython] Welcome Curt to the IronPython team

That was subtle indeed. So to fix that, I am pleased to welcome Curt to the 
IronPython team. Curt has been active in both the IronPython and IronRuby 
mailing lists, and we are excited to have him officially be working on these 
projects.

Curt already has a fix in socket support which he should be checking in 
shortly. This might be the second-fastest checkin for a new dev. Dino had 
checked in as part of his interview even before he joined the team, but I can't 
really hold this against Curt since we couldn't accept his patches before :)

Curt will be spending sometime initially on IronRuby too.

Thanks,
Shri
Want to work on IronPython, IronRuby, F#? Visit http://blogs.msdn.com/ironpython


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord
Sent: Wednesday, May 07, 2008 1:06 AM
To: Discussion of IronPython
Subject: Re: [IronPython] socket support in 1.1.2

Curt Hagenlocher wrote:
> Well, Dino tells me that they can't accept any contributions from
> outside Microsoft.  So in order to best serve the IronPython
> community, I've taken the arguably extreme step of joining the
> IronPython team as a developer just to be able to commit this change.
> Afterwards, I expect to stick around for a while and work on Visual
> Studio integration.

That's a subtle announcement Curt. Congratulations to you and the
ongoing success of IronPython! :-D

(I'm interested in the progress of Coils as well - and have an
interesting idea for it, but I need to finish my book first...)

Michael Foord

>
> I still expect to be working on my "wrapper" project after hours --
> I've been quiet about it recently largely because I got sidetracked by
> an attempt to add p/invoke support.  Expect something new in the next
> week or so.
>
> On Fri, Apr 25, 2008 at 9:43 AM, Michael Foord
> <[EMAIL PROTECTED] > wrote:
>
> Curt Hagenlocher wrote:
> >
> > I've attached a patch against 1.1.1 that (I think) fixes this.  It
> > works for my test case, anyway.
> >
> >
>
> We currently ship Microsoft binaries rather than compiling from
> source -
> so we'd rather wait for 1.1.2 than patch at this stage... but thanks.
>
> Michael
>
> 
>
> ___
> Users mailing list
> Users@lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>

___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

[IronPython] Welcome Curt to the IronPython team

[Shri Borde]

That was subtle indeed. So to fix that, I am pleased to welcome Curt to the 
IronPython team. Curt has been active in both the IronPython and IronRuby 
mailing lists, and we are excited to have him officially be working on these 
projects.

Curt already has a fix in socket support which he should be checking in 
shortly. This might be the second-fastest checkin for a new dev. Dino had 
checked in as part of his interview even before he joined the team, but I can't 
really hold this against Curt since we couldn't accept his patches before :)

Curt will be spending sometime initially on IronRuby too.

Thanks,
Shri
Want to work on IronPython, IronRuby, F#? Visit http://blogs.msdn.com/ironpython


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord
Sent: Wednesday, May 07, 2008 1:06 AM
To: Discussion of IronPython
Subject: Re: [IronPython] socket support in 1.1.2

Curt Hagenlocher wrote:
> Well, Dino tells me that they can't accept any contributions from
> outside Microsoft.  So in order to best serve the IronPython
> community, I've taken the arguably extreme step of joining the
> IronPython team as a developer just to be able to commit this change.
> Afterwards, I expect to stick around for a while and work on Visual
> Studio integration.

That's a subtle announcement Curt. Congratulations to you and the
ongoing success of IronPython! :-D

(I'm interested in the progress of Coils as well - and have an
interesting idea for it, but I need to finish my book first...)

Michael Foord

>
> I still expect to be working on my "wrapper" project after hours --
> I've been quiet about it recently largely because I got sidetracked by
> an attempt to add p/invoke support.  Expect something new in the next
> week or so.
>
> On Fri, Apr 25, 2008 at 9:43 AM, Michael Foord
> <[EMAIL PROTECTED] > wrote:
>
> Curt Hagenlocher wrote:
> >
> > I've attached a patch against 1.1.1 that (I think) fixes this.  It
> > works for my test case, anyway.
> >
> >
>
> We currently ship Microsoft binaries rather than compiling from
> source -
> so we'd rather wait for 1.1.2 than patch at this stage... but thanks.
>
> Michael
>
> 
>
> ___
> Users mailing list
> Users@lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>

___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

[IronPython] Some minor int/long bugs

[Dan Eloff]

I found this difference between IronPython and CPython in struct:

CPython
>>> struct.unpack('I','\xedd\x02\x00')
(156909,)

IronPython 2.0b1
>>> struct.unpack('I','\xedd\x02\x00')
(156909L,)

It seems that even although unpack('I', '\xff'*4) has to be a long,
for values of sys.maxint or below, CPython always returns an int.

Python ints and longs behave very similarily, so most of the time this
matters little. Enter bug #2.

ToString(format) doesn't work on python longs, but it will work on
python ints (as long as clr is imported.)

I would suggest that because sometimes it does matter whether you have
an int or a long, it would be best to fix the discrepancy in struct.

As for supporting ToString(format) on longs, I don't see this as being
easy or high priority, perhaps it would be enough to implement it by
converting the long to System.Decimal, and just using it's
ToString(format) which works perfectly.

I will report these on Codeplex.

-Dan
___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

Re: [IronPython] socket support in 1.1.2

[Michael Foord]

Curt Hagenlocher wrote:
Well, Dino tells me that they can't accept any contributions from 
outside Microsoft.  So in order to best serve the IronPython 
community, I've taken the arguably extreme step of joining the 
IronPython team as a developer just to be able to commit this change.  
Afterwards, I expect to stick around for a while and work on Visual 
Studio integration.


That's a subtle announcement Curt. Congratulations to you and the 
ongoing success of IronPython! :-D


(I'm interested in the progress of Coils as well - and have an 
interesting idea for it, but I need to finish my book first...)


Michael Foord

 
I still expect to be working on my "wrapper" project after hours -- 
I've been quiet about it recently largely because I got sidetracked by 
an attempt to add p/invoke support.  Expect something new in the next 
week or so.
 
On Fri, Apr 25, 2008 at 9:43 AM, Michael Foord 
<[EMAIL PROTECTED] > wrote:


Curt Hagenlocher wrote:
>
> I've attached a patch against 1.1.1 that (I think) fixes this.  It
> works for my test case, anyway.
>
>

We currently ship Microsoft binaries rather than compiling from
source -
so we'd rather wait for 1.1.2 than patch at this stage... but thanks.

Michael



___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
  


___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com