Yay Curt!
-Original Message-
From: Shri Borde [EMAIL PROTECTED]
Sent: Wednesday, 07 May, 2008 14:52
To: Discussion of IronPython users@lists.ironpython.com
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] mailto:[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
