[IronPython] Problems with -X:SaveAssemblies

I found this while testing precompiled module feature, but it's the same with plain 1.1a1. I'm not sure whether this is IronPython problem. Can anyone confirm this on .NET, not Mono? How to reproduce: 1. Create x/__init__.py and y/__init__.py as empty files. 2. Create z.py with content "import x,

Re: [IronPython] Loading XAML files

Today the Blend team gave us a short demo about their product. I tried their internal beta2 build. Seems the issue has been addressed. With the coming beta2, you can choose "file->new item->Page" (within a project), uncheck "include code file". The generated xaml file will not have x:Class. Fro

Re: [IronPython] Feedback needed for bug fix:Import pre-compiledmodules

Why do you assume the deployment will involve dropping IronPython in the application directory? Sure, you *could*, but it's unreasonable, I think, to force the end user to have Yet Another Copy of a dll when it could just reference the latest-and-greatest at a central location. The situation I

Re: [IronPython] Feedback needed for bug fix:Import pre-compiledmodules

Yes, the current implementation is not ideal. There are 3 ways to load assemblies in .NET: Load, LoadFrom, and LoadFile. - In order to use Load, the generated assemblies have to be strong named; which means the ironpython dlls has to be strong named too. - If an assembly with the same identity is

Re: [IronPython] Feedback needed for bug fix:Import pre-compiledmodules

Could IP just ignore the timestamp on ironpython.dll and let the .Net runtime figure out if there are any references to no-longer-present mechanisms within the binary? Keith, is it really the case that your clients without Python source are going to download new versions of IP and (this is impo

Re: [IronPython] re.sub at the start of the string

When is there going to be a 1. manual on Iron Python and 2 and IDE! On 1/21/07, Sanghyeon Seo <[EMAIL PROTECTED]> wrote: import re print re.sub('^', 'x', 'abc') CPython prints xabc, IronPython prints just abc. For FePy users: you can use FEPY_OPTIONS=regex to avoid this bug for the time being

Re: [IronPython] Feedback needed for bug fix:Import pre-compiledmodules

the upgraded-ironpython scenario >>> I do not think this is supported. The pre-compiled module has much >>> dependency on IronPython.dll. Some emitted calls in those modules could be >>> changed (or removed) in the next version of IronPython.dll. That makes me itch... I understand runtime de

Re: [IronPython] Feedback needed for bug fix: Import pre-compiledmodules

If ironpython.dll is newer than lib.exe, and lib.py does not exist, we should expect an exception? >>> Yes the upgraded-ironpython scenario >>> I do not think this is supported. The pre-compiled module has much >>> dependency on IronPython.dll. Some emitted calls in those modules could be >>> c

Re: [IronPython] Feedback needed for bug fix: Import pre-compiledmodules

""" "import lib" prefers loading lib.exe to lib.py, if neither ironpython.dll nor lib.py is newer than lib.exe. """ So: If lib.py doesn't exist, and lib.exe does, it'll import the exe. If lib.py does exist, it'll load lib.exe if the .exe is newer. (Assuming in both cases that iron

[IronPython] Feedback needed for bug fix: Import pre-compiled modules

We recently checked in a fix for codeplex work item# 358 (Implement import of pre-compiled modules). If possible, please download the source, and try it with your scenarios to see whether it addresses your issue (since many o

Re: [IronPython] Empty func_defaults

And lucky for us both of those evaluate to false which at least makes the situation somewhat reasonable unless someone checks for equality to None directly. Anyway, we should match the behavior. I've opened CodePlex bug #7532 for this (http://www.codeplex.com/IronPython/WorkItem/View.aspx?Work

Re: [IronPython] re.sub at the start of the string

Thanks for the bug report Seo! I've filed bug #7531 for this (http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=7531). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sanghyeon Seo Sent: Sunday, January 21, 2007 5:51 AM To: Discussion of I