[Ironpython-users] IronPython 2.7.3 with .NET 4.5

2013-01-11 Thread Piotr Nestorow
Hi Are there any known problems/issues when using IronPython 2.7.3 on a Windows system with .NET 4.5 ? Best Regards Piotr ___ Ironpython-users mailing list [email protected] http://mail.python.org/mailman/listinfo/ironpython-users

[Ironpython-users] IronPython, Daily Digest 1/10/2013

2013-01-11 Thread no_reply
Hi ironpython, Here's your Daily Digest of new issues for project "IronPython". In today's digest:ISSUES 1. [New comment] GetEncodings called in StringOps.cs fails using Mono 2. [New issue] DAQMX Code which works fine with "Python 2.7.3" giving issue with IRONPYTHON 3. [New issue] DAQmxCreateDO

[Ironpython-users] importing .net assembly as module in a package

2013-01-11 Thread Pawel Jasinski
hi, I am looking for a way to use module created as .net assembly as part of the package So instead of having: import clr clr.AddReferenceToFileAndPath(".\maplookup.dll") import maplookup I prefer: import clr clr.AddReferenceToFileAndPath(".\maplookup.dll") import xmldiff.maplookup Is there

Re: [Ironpython-users] crash on Win8 64bit at IronPython expression evaluation

2013-01-11 Thread Jeff Hardy
What version of .NET is installed on the Windows 7 machines? I wonder if this is a .NET 4.5 vs. .NET 4 issue and not a Win8 vs Win7 issue. - Jeff On Thu, Jan 10, 2013 at 11:43 PM, Zsidó Zoltán wrote: > Keith, you are absolutely right. Not the background thread causes this > error. > > I trie

Re: [Ironpython-users] IronPython 2.7.3 with .NET 4.5

2013-01-11 Thread Jeff Hardy
Not that I know of, but I don't think I've ever run the full test suite on a .NET 4.5 machine. The basic stuff works, but that doesn't mean it doesn't have some weird corner cases. - Jeff On Fri, Jan 11, 2013 at 12:59 AM, Piotr Nestorow < [email protected]> wrote: > Hi > A

Re: [Ironpython-users] importing .net assembly as module in a package

2013-01-11 Thread Jeff Hardy
On Fri, Jan 11, 2013 at 6:37 AM, Pawel Jasinski wrote: > > hi, > > > I am looking for a way to use module created as .net assembly as part of the > package > > So instead of having: > > import clr > clr.AddReferenceToFileAndPath(".\maplookup.dll") > import maplookup > > I prefer: > > import clr >

[Ironpython-users] Fwd: importing .net assembly as module in a package

2013-01-11 Thread Pawel Jasinski
-- Forwarded message -- From: Pawel Jasinski Date: Fri, Jan 11, 2013 at 5:58 PM Subject: Re: [Ironpython-users] importing .net assembly as module in a package To: Jeff Hardy On Fri, Jan 11, 2013 at 5:02 PM, Jeff Hardy wrote: > On Fri, Jan 11, 2013 at 6:37 AM, Pawel Jasinski

Re: [Ironpython-users] Fwd: importing .net assembly as module in a package

2013-01-11 Thread Michael van der Kolff
Why not just add xmldiff to maplookup's namespace? i.e. instead of namespace maplookup { public static class maplookup { public const string __doc__ = "test string"; ... } Write: namespace xmldiff.maplookup { public static class maplookup { public const string __doc__ =

Re: [Ironpython-users] Fwd: importing .net assembly as module in a package

2013-01-11 Thread Pawel Jasinski
Thanks for the idea The following appears to work as long as it is the only thing in xmldiff. [assembly: PythonModule("maplookup", typeof(xmldiff.maplookup))] namespace xmldiff { public static class maplookup { ... } however, if it try to mix it with other parts of the xmldiff package which