This is a bug. Unfortunately it looks like one of the version numbers didn't
get updated. In Src\Microsoft.Scripting\Hosting\PlatformAdapationLayer.cs
there are currently some version numbers hard-coded until we get a better
configuration story:
PlatformAdaptationLayer.cs:
_assemb
Unfortunately you're going to need another DLR language in order to demonstrate
that. This refresh only includes IronPython so there isn't much to see there
(as the previously released JS bits won't run against it). Here's some sample
code of how it would work if you had a 2nd language and tha
2007/7/2, David Jensen <[EMAIL PROTECTED]>:
> Will IronPython on the backend support web server software such as Zope and
> CherryPy, and, therefore, Plone, TurboGears, Django, etc.?
This is ultimately the goal of FePy project.
On the other hand, Microsoft doesn't seem to be interested in this
si
Although some folk have had Django running on IP.
Michael Foord
http://www.voidspace.org.uk/ironpython/index.shtml
Sylvain Hellegouarch wrote:
> David Jensen a écrit :
>
>> Will IronPython on the backend support web server software such as Zope and
>> CherryPy, and, therefore, Plone, TurboGear
David Jensen a écrit :
> Will IronPython on the backend support web server software such as Zope and
> CherryPy, and, therefore, Plone, TurboGears, Django, etc.?
>
I cannot speak for Zope but IP1.1 will not run CherryPy 3 as-is because
there are some shotcomings in IP1.1 that prevent it.
Howe
Will IronPython on the backend support web server software such as Zope and
CherryPy, and, therefore, Plone, TurboGears, Django, etc.?
David Jensen
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpy
