Re: [IronPython] Two engines and clr.AddReference don't work together.

2009-02-05 Thread Orestis Markou
...@lists.ironpython.com] On Behalf Of Michael Foord Sent: Friday, January 30, 2009 3:30 PM To: Discussion of IronPython Subject: Re: [IronPython] Two engines and clr.AddReference don't work together. Dino Viehland wrote: You're right that it worked in 1.0 - but of course in 1.0 we would also end up

Re: [IronPython] Two engines and clr.AddReference don't work together.

2009-02-05 Thread Dino Viehland
Subject: Re: [IronPython] Two engines and clr.AddReference don't work together. Hi Dino, is this going to be backported to 2.0.x? If so, when should we expect a release? We have a workaround right now, but to maintain API compatibility we probably have to monkeypatch clr.AddReference which

Re: [IronPython] Two engines and clr.AddReference don't work together.

2009-02-05 Thread Orestis Markou
To: Discussion of IronPython Subject: Re: [IronPython] Two engines and clr.AddReference don't work together. Hi Dino, is this going to be backported to 2.0.x? If so, when should we expect a release? We have a workaround right now, but to maintain API compatibility we probably have

[IronPython] Two engines and clr.AddReference don't work together.

2009-01-30 Thread Tom Wright
Hi, Having two engines in the same AppDomain causes interesting behaviour when trying trying to add references. Only the sys.path of the first engine that was created seems to be taken into account when calling clr.AddReference, the second sys.path is ignored. See

Re: [IronPython] Two engines and clr.AddReference don't work together.

2009-01-30 Thread Curt Hagenlocher
How do we love thee, Fusion? Let me count the ways... On Fri, Jan 30, 2009 at 10:34 AM, Tom Wright tom.wri...@resolversystems.com wrote: Hi, Having two engines in the same AppDomain causes interesting behaviour when trying trying to add references. Only the sys.path of the first engine

Re: [IronPython] Two engines and clr.AddReference don't work together.

2009-01-30 Thread Dino Viehland
Message- From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Tom Wright Sent: Friday, January 30, 2009 10:34 AM To: Discussion of IronPython Subject: [IronPython] Two engines and clr.AddReference don't work together. Hi, Having two engines

Re: [IronPython] Two engines and clr.AddReference don't work together.

2009-01-30 Thread Michael Foord
of IronPython Subject: [IronPython] Two engines and clr.AddReference don't work together. Hi, Having two engines in the same AppDomain causes interesting behaviour when trying trying to add references. Only the sys.path of the first engine that was created seems to be taken into account when calling

Re: [IronPython] Two engines and clr.AddReference don't work together.

2009-01-30 Thread Dino Viehland
Foord Sent: Friday, January 30, 2009 3:30 PM To: Discussion of IronPython Subject: Re: [IronPython] Two engines and clr.AddReference don't work together. Dino Viehland wrote: You're right that it worked in 1.0 - but of course in 1.0 we would also end up with an arbitrary ordering between engines

Re: [IronPython] Two engines and clr.AddReference don't work together.

2009-01-30 Thread Michael Foord
-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Michael Foord Sent: Friday, January 30, 2009 3:30 PM To: Discussion of IronPython Subject: Re: [IronPython] Two engines and clr.AddReference don't work together. Dino Viehland wrote: You're right