Curt Hagenlocher wrote:
On Fri, Jul 25, 2008 at 12:30 PM, Michael Foord
<[EMAIL PROTECTED]> wrote:
At Resolver Systems we've used the DllImport attribute extensively.
If we had a good ctypes/native interop mechanism, would it take care of that?
Yep. :-)
Thanks
Michae;
In my o
On Fri, Jul 25, 2008 at 12:30 PM, Michael Foord
<[EMAIL PROTECTED]> wrote:
>
> At Resolver Systems we've used the DllImport attribute extensively.
If we had a good ctypes/native interop mechanism, would it take care of that?
> In my own projects I've used the Silverlight Scriptable attribute seve
So I think, actually, that this could be done without changing
much if any external API. They'd probably need to change some of
the internals to return dynamic variants of the info types, but I
think that's doable.
____________
From: [E
of IronPython; Discussion of IronPython
Subject: Re: [IronPython] IronPython Post 2.0 Roadmap
I can answer both in one: To be able to use IronPython to create data classes,
marked up with attributes, to be consumed by APIs probably written in something
other than IronPython.
That's it..
nPython
Subject: Re: [IronPython] IronPython Post 2.0 Roadmap
So, we had a brief hallway discussion today about this topic, and the upshot is
that I'm interested in hearing your "real world" use cases for
a) attributes, and
b) static type generation in general
By "use case
D] on behalf of Curt Hagenlocher
Sent: Wed 7/23/2008 4:39 PM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython Post 2.0 Roadmap
So, we had a brief hallway discussion today about this topic, and the upshot is
that I'm interested in hearing your "real world" use cases for
eder/dotnet/Default.aspx?Target=code://mscorlib:2.0.0.0:b77a5c561934e089/System.Boolean>
> inherit);
> }
>
>
> So I think, actually, that this could be done without changing much if any
> external API. They'd probably need to change some of the internals to
> return dynam
to change some of the internals to return
dynamic variants of the info types, but I think that's doable.
From: [EMAIL PROTECTED] on behalf of Harry Pierson
Sent: Mon 7/21/2008 12:59 PM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython Post 2.0
mentions below.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord
Sent: Monday, July 21, 2008 12:48 PM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython Post 2.0 Roadmap
Keith J. Farmer wrote:
> Attributes can be applied
*From:* [EMAIL PROTECTED] on behalf of Curt Hagenlocher
*Sent:* Mon 7/21/2008 9:51 AM
*To:* Discussion of IronPython
*Subject:* Re: [IronPython] IronPython Post 2.0 Roadmap
"Availability of a static type" not because IronPython would need to
access one but because it would need
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harry
Pierson
Sent: Sunday, July 20, 2008 11:14 PM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython Post 2.0 Roadmap
Can you give me some examples where you would use these?
From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Harry Pierson
> Sent: Sunday, July 20, 2008 11:14 PM
> To: Discussion of IronPython
> Subject: Re: [IronPython] IronPython Post 2.0 Roadmap
>
> Can you give me some examples where you would use these? The problem I see
&
om: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harry Pierson
Sent: Sunday, July 20, 2008 11:14 PM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython Post 2.0 Roadmap
Can you give me some examples where you would use these? The problem I see is
that many scenarios (WCF cont
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keith J. Farmer
Sent: Saturday, July 19, 2008 8:13 PM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython Post 2.0 Roadmap
votes++
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord
Sent
.NET 3.5 "extension".
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dody Gunawinata
Sent: Sunday, July 20, 2008 6:26 AM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython Post 2.0 Roadmap
I was thinking more in the line of being able to use Python class
2008/7/20 Dody Gunawinata <[EMAIL PROTECTED]>:
> I was thinking more in the line of being able to use Python classes directly
> from C#. But again, this has nothing to do with the Python language in the
> first place.
I think that would be the feature of C#.
--
Seo Sanghyeon
. Though that's arguably a
> DLR-level issue.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Keith J. Farmer
> Sent: Saturday, July 19, 2008 8:13 PM
> To: Discussion of IronPython
> Subject: Re: [IronPython]
ython Post 2.0 Roadmap
votes++
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord
Sent: Saturday, July 19, 2008 10:38 AM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython Post 2.0 Roadmap
Sanghyeon Seo wrote:
> 2008/7/20 Harry
votes++
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord
Sent: Saturday, July 19, 2008 10:38 AM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython Post 2.0 Roadmap
Sanghyeon Seo wrote:
> 2008/7/20 Harry Pierson <
Sanghyeon Seo wrote:
2008/7/20 Harry Pierson <[EMAIL PROTECTED]>:
Hosting features are all done via the DLR, so that's a separate team. As for
"ability to interact with the rest of the .Net framework", can you be more
specific about what you're looking for in that space? What *isn't* IPy doin
2008/7/20 Harry Pierson <[EMAIL PROTECTED]>:
> Hosting features are all done via the DLR, so that's a separate team. As for
> "ability to interact with the rest of the .Net framework", can you be more
> specific about what you're looking for in that space? What *isn't* IPy doing
> that you want it
as are any good,
you'll have to ram them down people's throats."
- Howard Aiken<http://en.wikipedia.org/wiki/Howard_Aiken>
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dody Gunawinata
Sent: Saturday, July 19, 2008 12:56 AM
To: Discussion of IronPytho
For me, the main strength of IronPython is its hosting API and the
simplicity of the Python language. It's pretty amazing on what combination
of C# and IronPython hosting API can do - we use it from running business
rules table, sending python command in a game project and powering our CMS.
In our
> There is a fair possibility that the 'community' will prefer Python 2 for
> several years (3-4 guesstimate).
>
> Michael
>
I would guess it will take less time for IronPython, because most of
the libraries don't work in ipy anyway. There's fewer things to hold
you back at the 2 level. If IronPyt
Curt Hagenlocher wrote:
On Thu, Jul 17, 2008 at 3:40 PM, Michael Foord
<[EMAIL PROTECTED]> wrote:
One question. When IronPython 3 is started, targeting CPython 3.0, will you
actively
maintain IronPython 2 and IronPython 3 in parallel?
I think it's fair to say that this will be driven
On Thu, Jul 17, 2008 at 3:40 PM, Michael Foord
<[EMAIL PROTECTED]> wrote:
>
> One question. When IronPython 3 is started, targeting CPython 3.0, will you
> actively
> maintain IronPython 2 and IronPython 3 in parallel?
I think it's fair to say that this will be driven mostly by the needs
of our c
Hi Harry - nice write-up, thanks! It's great to hear about the way you
guys see IronPython developing in the future.
My comment on Twitter wasn't really aimed at you - I was hoping to prod
Dino, Martin or Sri into blogging more!
One question. When IronPython 3 is started, targeting CPython 3.
Posted to my blog @
http://devhawk.net/2008/07/17/IronPython+Post+20+Roadmap.aspx but reproduced
below for your convenience.
IronPython Post 2.0 Roadmap
Michael Foord (aka voidspace) twittered that "None of the IronPython team can
get it together to blog regularly, except @jschementi of cour
28 matches
Mail list logo
