So as soon as there's a PythonCodeProvider, I think it could be done.
configuration/system.web/compilation/compilers/compiler
Here's from my 1.1 machine.config:
-
-
-
From: [EMAIL PROTECTE
[Python.. ASP.. the combination seems natural to me ;)]
Got this reponse from Scott Guthrie. So I suppose it's a matter of digging
around and seeing exactly how to use the hooks:
Hi Keith,
ASP.NET actually has pluggable language support even in V1.1. It is
driven using the CodeDOM model, and
Title: RE: [IronPython] Access to Enumeration Values
I agree with the automatic conversion and the ability to pass then into int(enum) to get the value out. I think that it makes sense to keep the rest as is, such as print the "Broadcast" when the enum value is such.
Thanks for the feedback,
>We haven't reached decision on this one yet and it would be
interesting to hear feedback as
>to how important having a version if IronPython running on .Net 1.1 is for you.
It would be the only way I'd get to use it at work, so I'd love to
have a 1.1 version, even if it sacrifices some support.
Yeah, I think you've got the priority right for my tastes: CPython parity
before CLR producer status.
Somehow, I don't think it'll take much longer for y'all.
From: [EMAIL PROTECTED] on behalf of Martin Maly
Sent: Thu 8/4/2005 12:21 PM
To: Discussion of IronPy
Hi Keith!
LoadWithPartialName may be indeed removed as the build-time warning suggests suggests. There is a good reasoning behind removing the method (what version, from where, etc ... would the method call load? I think there is a blog out there that talks more about the reasoning:
http:/
Title: RE: [IronPython] IronPython 0.9 released
As for the static compilation, it is another 'maybe' for 1.0 and we are not decided one way or another (it is another topic you can provide feedback on and let us know how important it is to you).
For the 0.9 I actually went somewhat further wi
Title: RE: [IronPython] IronPython 0.9 released
Hi Lorenzo,
Since the .Net 2.0 final has not yet been released, we continue to product our builds on .NET 2.0 Beta 2 which was publicly released and is, in our opinion, most widely adopted by our users. As soon as .Net 2.0 ships its final vers
Yes, it is a known problem. The tab-completion is far, far from finished and this is probably the first thing for me to fix - pressing tab at the beginning of the line should not offer options, but simply tab out.
Thanks for feedback!
MArtin
From: Keith J. Farmer
Sent: 8/4/2005 2:44 AM
To: D
Hi Anthony,
I don't think it is a bug. The value you get when getting an enum value
(SocketOptionName.Broadcast) is indeed the value itself:
x = SocketOptions.Broadcast
x becomes a boxed enum object. It is the ToString() method of the enum
object prints the name. Consider following C# code that
the namespace System.Net.Sockets contains an enumation type named
SocketOptionName for retrieving Socket options. It's definition is:
public enum SocketOptionName
{
// Fields
AcceptConnection = 2,
AddMembership = 12,
AddSourceMembership = 15,
BlockSource = 0x11,
Hello,
I tried to build IronPython 0.9 with Mono. I used Debian package currently
in Sid to do so.
With attached "patch", I succeeded building it, but it doesn't really
run. Transcript follows:
* * *
[EMAIL PROTECTED]:~/fepy$ mono --version
Mono JIT compiler version 1.1.8.2, (C) 2002-2005 Nove
I'm not sure where you got the idea that IronPython 1.0 only works with .NET
1.1?
I can compile the IronPython solution using the VS 2005 Beta 2 release (and
have, several times tonight). For what it's worth, IronPython needs the 2.0
runtime, since it uses 2.0 code generation, and supports 2.0
Enter in several lines, play around with
tab completion.
Then enter:
>>> def foo():
...
Yields:
... previous tab completion results
Apparently the buffer holding the
_expression_ to complete isn’t cleared after a new line is started.
Also, in the event that we are
On 8/2/05, Martin Maly <[EMAIL PROTECTED]> wrote:
> Known issues:
>Rebuilding IronPython on the Community Technology Preview release,
> version 2.0.50630.0 will fix the problem. We decided to maintain the
> dependency of the released binaries on .NET 2.0 Beta 2 (version
> 2.0.50215.44) becau
Just noticing this warning.. Is LoadWithPartialName
expected to remain in 2.0 since it’s close to RTM?
'System.Reflection.Assembly.LoadWithPartialName(string)'
is obsolete: 'This method has been deprecated. Please use Assembly.Load()
instead. http://go.microsoft.com/fwlink/?linkid=14202
16 matches
Mail list logo
