Re: [IronPython] 2.0 deployment

2009-03-09 Thread Dody Gunawinata
1. You will need to deploy all the lib * ipy.exe * IronPython.dll * IronPython.Modules.dll * Microsoft.Scripting.Core.dll * Microsoft.Scripting.dll * Microsoft.Scripting.ExtensionAttribute.dll The last three dlls are DLR which IP 2.0 relies on. I never use ipy to deploy application so I'm not su

[IronPython] DLR Source typo

2009-03-09 Thread Keith J. Farmer
In case someone wants to catch it before it's too late: CallSiteBinder.Bind's comment: "hte" -> "the" J ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

Re: [IronPython] 2.0 deployment

2009-03-09 Thread Howland-Rose, Kyle
Hi Dody, Fair question :) Just a script run from the Windows scheduler that reads a database and writes some files. Kyle -Original Message- From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Tuesday, 10 March 2009 4

Re: [IronPython] 2.0 deployment

2009-03-09 Thread Dody Gunawinata
What kind of application are you trying to deploy? ASP.Net with IP support? Application with hosted IP? IP scripts? Dody G. On Tue, Mar 10, 2009 at 5:27 AM, Howland-Rose, Kyle wrote: > Hi all, > > My understanding of http://www.ironpython.info/index.php/Deployment is that > when deploying to Wi

[IronPython] unchanged version numbers (was Re: Announcing IronPython 2.0.1)

2009-03-09 Thread John Machin
On 14/02/2009 9:39 AM, Dino Viehland wrote: It’s an in-place upgrade so you don’t need to re-build hosts that were built against the previous versions of IronPython – they’ll just continue to work. If we changed the .NET assembly version then you’d either have to apply policy or rebuild. The

[IronPython] 2.0 deployment

2009-03-09 Thread Howland-Rose, Kyle
Hi all, My understanding of http://www.ironpython.info/index.php/Deployment is that when deploying to Windows the following need to be deployed: * .NET 2.0 or 3.0 installed * ipy.exe * IronPython.dll * IronMath.dll I thought the IPy 2.0 equiv might be to copy: * ipy.exe * IronPython.dll * Ir

[IronPython] IPy2.0 and VS 2008

2009-03-09 Thread Howland-Rose, Kyle
Hi all, I have been using IPy from the command line but want others at work to use it too and they pretty much use Visual Studio all the time. Mainly we work in Visual Studio 2008 but there is not much information about IPy 2.0 and Visual Studio that I could find. What are people's experience

Re: [IronPython] __slots__

2009-03-09 Thread Michael Foord
Dino Viehland wrote: The fact that we allow setting to the dictionary when we shouldn't be much to worry about - it is just odd. In either case we still have a .NET type defined something like: class NewType : YourBaseTypeHere { public PythonDictionary __dict__; public object[

Re: [IronPython] __slots__

2009-03-09 Thread Dino Viehland
The fact that we allow setting to the dictionary when we shouldn't be much to worry about - it is just odd. In either case we still have a .NET type defined something like: class NewType : YourBaseTypeHere { public PythonDictionary __dict__; public object[] __slots__; ..

Re: [IronPython] __slots__

2009-03-09 Thread Michael Foord
Curt Hagenlocher wrote: On Mon, Mar 9, 2009 at 5:28 AM, Michael Foord wrote: Curt Hagenlocher wrote: I believe this is already fixed in the current (ie 2.6ish) source. Any chance for 2.0.2? That's Dino's call. The fix in 2.6 is actually a massive restructuring of some c

Re: [IronPython] __slots__

2009-03-09 Thread Curt Hagenlocher
On Mon, Mar 9, 2009 at 5:28 AM, Michael Foord wrote: > > Curt Hagenlocher wrote: >> >> I believe this is already fixed in the current (ie 2.6ish) source. > > Any chance for 2.0.2? That's Dino's call. The fix in 2.6 is actually a massive restructuring of some code, so the backport would likely ha

Re: [IronPython] __slots__

2009-03-09 Thread Michael Foord
Curt Hagenlocher wrote: I believe this is already fixed in the current (ie 2.6ish) source. Any chance for 2.0.2? Michael On Mon, Mar 9, 2009 at 5:19 AM, Michael Foord mailto:fuzzy...@voidspace.org.uk>> wrote: Hello guys, It looks like __slots__ and inheritance are a bit odd in

Re: [IronPython] __slots__

2009-03-09 Thread Curt Hagenlocher
I believe this is already fixed in the current (ie 2.6ish) source. On Mon, Mar 9, 2009 at 5:19 AM, Michael Foord wrote: > Hello guys, > > It looks like __slots__ and inheritance are a bit odd in IronPython > (2.0.1). slots.py: > > class A(object): > __slots__ = [] > class B(A): > __slots__ =

[IronPython] __slots__

2009-03-09 Thread Michael Foord
Hello guys, It looks like __slots__ and inheritance are a bit odd in IronPython (2.0.1). slots.py: class A(object): __slots__ = [] class B(A): __slots__ = [] i = B() i.test = 3 Running with IronPython and CPython: C:\compile\resolver-michael>"C:\Program Files (x86)\IronPython

Re: [IronPython] IronPython to JavaScript

2009-03-09 Thread Jimmy Schementi
The AddReference issue sounds bad ... I have to figure out exactly what's happening there. And the onload thing is also really messed up; I'll ask around to find out what it actually does. From: users-boun...@lists.ironpython.com [users-boun...@lists.ironp