Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New comment] sys.args[0] dissapears in ipy-script compiled with pyc.py
2. [New comment] sys.args[0] dissapears in ipy-script compiled with pyc.py
3. [New comment] sys.args[0] dissapears in ipy-script compiled with pyc.py
4. [New comment] sys.args[0] dissapears in ipy-script compiled with pyc.py
5. [New comment] Compiling issue in IronPython 2.7.2 RC 1
6. [New comment] Compiling issue in IronPython 2.7.2 RC 1
7. [New comment] Compiling issue in IronPython 2.7.2 RC 1
8. [New comment] Compiling issue in IronPython 2.7.2 RC 1
9. [New comment] Compiling issue in IronPython 2.7.2 RC 1
10. [New comment] Compiling issue in IronPython 2.7.2 RC 1
11. [Status update] Compiling issue in IronPython 2.7.2 RC 1
12. [New issue] Import does not search current working directory
13. [New comment] Import does not search current working directory
14. [New comment] Import does not search current working directory
15. [New comment] zipimport does not search current working directory
16. [New comment] zipimport does not search current working directory
17. [Status update] zipimport does not search current working directory
18. [New issue] Fatal app exit on import uuid
19. [New comment] Fatal app exit on import uuid
----------------------------------------------
ISSUES
1. [New comment] sys.args[0] dissapears in ipy-script compiled with pyc.py
http://ironpython.codeplex.com/workitem/30263
User slide_o_mix has commented on the issue:
"Is there any problem that the args[0] will be the executable rather than a
.py?"-----------------
2. [New comment] sys.args[0] dissapears in ipy-script compiled with pyc.py
http://ironpython.codeplex.com/workitem/30263
User peterSchwalm has commented on the issue:
"I think the .exe-path as argv[0] should be not be problem.
I think that should be considered in terms of compatibility with CPython (and
C/C++). In these environments argv[1] ... argv[n] are always the "real"
commandline arguments, whereas argv[0] is always "the program", usually
identical to the way the program was effectively called (on the command line,
by a link or whatever).
So:
argv[0] should give infos about the way the script/program is called, at least
it should allow to extract the script name, possibly by using os.path.basename
/ os.path.dirname / os.path.splitext.
argv[1] ... argv[n] should be the "real" arguments
If I have script fileCopy.py, copying file source to file target, then
fileCopy.py should be able to copy file argv[1] to file argv[2] regardless of
whether the command line reads:
ipy fileCopy.py infileName outFileName
or
fileCopy.exe inFileName outFileName
or simply
fileCopy inFileName outFileName
"-----------------
3. [New comment] sys.args[0] dissapears in ipy-script compiled with pyc.py
http://ironpython.codeplex.com/workitem/30263
User peterSchwalm has commented on the issue:
"... addition to last comment.
In CPython these conditions are met with direct execution (python fileCopy.py
...) as well as with execution of a frozen script (fileCopy.exe ...)
"-----------------
4. [New comment] sys.args[0] dissapears in ipy-script compiled with pyc.py
http://ironpython.codeplex.com/workitem/30263
User slide_o_mix has commented on the issue:
"Fixed in c0ec50a"-----------------
5. [New comment] Compiling issue in IronPython 2.7.2 RC 1
http://ironpython.codeplex.com/workitem/32345
User slide_o_mix has commented on the issue:
"Can you attach your test script just to make sure there is not something I am
missing?"-----------------
6. [New comment] Compiling issue in IronPython 2.7.2 RC 1
http://ironpython.codeplex.com/workitem/32345
User slide_o_mix has commented on the issue:
"Actually, now that I look at this issue again, you are saying that only the
version of pyc.py that comes with the binaries of the RC1 shows this issue? If
you use the installer, it does not?"-----------------
7. [New comment] Compiling issue in IronPython 2.7.2 RC 1
http://ironpython.codeplex.com/workitem/32345
User slide_o_mix has commented on the issue:
"I can't reproduce this issue with the binaries. Can you verify that you don't
have another IronPython installation in your path, or that the IronPython DLL's
from an older version are not in the GAC?"-----------------
8. [New comment] Compiling issue in IronPython 2.7.2 RC 1
http://ironpython.codeplex.com/workitem/32345
User krysros has commented on the issue:
""IronPython DLL's from an older version are not in the GAC?"
Perhaps this caused this issue. I tried again IronPython 2.7.2 RC 1 Binaries
and it works. Now I have installed IronPython 2.7.2 RC 1 Installer version, I
did not add path to IronPython to PATH variable. I'm using absolute paths as
above.
"you are saying that only the version of pyc.py that comes with the binaries of
the RC1 shows this issue? If you use the installer, it does not?"
Exactly.
"Can you attach your test script"
It's not a test of pyc.py, it's just an example. Script in the
attachment."-----------------
9. [New comment] Compiling issue in IronPython 2.7.2 RC 1
http://ironpython.codeplex.com/workitem/32345
User slide_o_mix has commented on the issue:
"I think this is not an issue then, correct?"-----------------
10. [New comment] Compiling issue in IronPython 2.7.2 RC 1
http://ironpython.codeplex.com/workitem/32345
User krysros has commented on the issue:
"Corrent. To close."-----------------
11. [Status update] Compiling issue in IronPython 2.7.2 RC 1
http://ironpython.codeplex.com/workitem/32345
User slide_o_mix has updated the issue:
Status has changed from Active to Closed with the following comment,
"Not a bug"-----------------
12. [New issue] Import does not search current working directory
http://ironpython.codeplex.com/workitem/32352
User mchalkley has proposed the issue:
"According to http://docs.python.org/tutorial/modules.html, import includes the
current working directory in its search path by default.
Ironpython does not appear to do so."-----------------
13. [New comment] Import does not search current working directory
http://ironpython.codeplex.com/workitem/32352
User slide_o_mix has commented on the issue:
"Please attach a test script to reproduce."-----------------
14. [New comment] Import does not search current working directory
http://ironpython.codeplex.com/workitem/32352
User mchalkley has commented on the issue:
"It appears the problem lies with zipimport, which would explain some of the
earlier confusion.
A script consisting simply of "import testlib" works, assuming testlib is a
file named testlib.py and located in the same directory as the exe.
If testlib is a zip file named testlib.zip, it doesn't work."-----------------
15. [New comment] zipimport does not search current working directory
http://ironpython.codeplex.com/workitem/32352
User slide_o_mix has commented on the issue:
"I don't think zip files are automatically searched on CPython
either."-----------------
16. [New comment] zipimport does not search current working directory
http://ironpython.codeplex.com/workitem/32352
User mchalkley has commented on the issue:
"You're correct - the behavior is the same as CPython.
This issue can be closed."-----------------
17. [Status update] zipimport does not search current working directory
http://ironpython.codeplex.com/workitem/32352
User slide_o_mix has updated the issue:
Status has changed from Proposed to Closed with the following comment,
"Not a bug."-----------------
18. [New issue] Fatal app exit on import uuid
http://ironpython.codeplex.com/workitem/32355
User ned14 has proposed the issue:
"The below says it all:
G:\BEurtle\BEXML>ipy
IronPython 2.7.2rc1 (2.7.0.40) on .NET 4.0.30319.261 (32-bit)
Type "help", "copyright", "credits" or "license" for more information.
>>> import uuid
Unhandled Exception: System.AccessViolationException: Attempted to read or
write protected memory. This is often an indication that other memory is
corrupt.
at IronPython.Modules.NativeFunctions.LoadLibrary(String lpFileName)
at IronPython.Modules.NativeFunctions.LoadDLL(String filename, Int32 flags)
at IronPython.Modules.CTypes.LoadLibrary(String library, Int32 mode)
at
Microsoft.Scripting.Interpreter.FuncCallInstruction`3.Run(InterpretedFrame
frame)
at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
at Microsoft.Scripting.Interpreter.LightLambda.Run5[T0,T1,T2,T3,T4,TRet](T0
arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4)
at
System.Dynamic.UpdateDelegates.UpdateAndExecute4[T0,T1,T2,T3,TRet](CallSite
site, T0 arg0, T1 arg1, T2 arg2, T3 arg3)
at
Microsoft.Scripting.Interpreter.FuncCallInstruction`7.Run(InterpretedFrame
frame)
at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
at Microsoft.Scripting.Interpreter.LightLambda.Run5[T0,T1,T2,T3,T4,TRet](T0
arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4)
at
IronPython.Compiler.Ast.CallExpression.Invoke2Instruction.Run(InterpretedFrame
frame)
at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
at
Microsoft.Scripting.Interpreter.LightLambda.Run7[T0,T1,T2,T3,T4,T5,T6,TRet](T0
arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4, T5 arg5, T6 arg6)
at
Microsoft.Scripting.Interpreter.FuncCallInstruction`9.Run(InterpretedFrame
frame)
at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
at Microsoft.Scripting.Interpreter.LightLambda.Run5[T0,T1,T2,T3,T4,TRet](T0
arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4)
at
System.Dynamic.UpdateDelegates.UpdateAndExecute4[T0,T1,T2,T3,TRet](CallSite
site, T0 arg0, T1 arg1, T2 arg2, T3 arg3)
at
IronPython.Runtime.Types.LateBoundInitBinder.FastInitSite`1.CallTarget(CallSite
site, CodeContext context, Object inst, T0 arg0)
at System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite
site, T0 arg0, T1 arg1, T2 arg2)
at IronPython.Runtime.Types.PythonType.FastTypeSite`1.CallTarget(CallSite
site, CodeContext context, Object type, T0 arg0)
at System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite
site, T0 arg0, T1 arg1, T2 arg2)
at Microsoft.Scripting.Interpreter.DynamicInstruction`4.Run(InterpretedFrame
frame)
at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
at Microsoft.Scripting.Interpreter.LightLambda.Run1[T0,TRet](T0 arg0)
at IronPython.Compiler.RuntimeScriptCode.InvokeTarget(Scope scope)
at IronPython.Compiler.RuntimeScriptCode.Run(Scope scope)
at IronPython.Runtime.PythonContext.InitializeModule(String fileName,
ModuleContext moduleContext, ScriptCode scriptCode, ModuleOptions options)
at IronPython.Runtime.PythonContext.CompileModule(String fileName, String
moduleName, SourceUnit sourceCode, ModuleOptions options, ScriptCode&
scriptCode)
at IronPython.Runtime.Importer.LoadModuleFromSource(CodeContext context,
String name, String path)
at IronPython.Runtime.Importer.LoadFromDisk(CodeContext context, String
name, String fullName, String str)
at IronPython.Runtime.Importer.ImportFromPathHook(CodeContext context,
String name, String fullName, List path, Func`5 defaultLoader)
at IronPython.Runtime.Importer.ImportFromPath(CodeContext context, String
name, String fullName, List path)
at IronPython.Runtime.Importer.ImportTopAbsolute(CodeContext context, String
name)
at IronPython.Runtime.Importer.ImportModule(CodeContext context, Object
globals, String modName, Boolean bottom, Int32 level)
at IronPython.Modules.Builtin.__import__(CodeContext context, String name,
Object globals, Object locals, Object fromlist, Int32 level)
at
Microsoft.Scripting.Interpreter.FuncCallInstruction`7.Run(InterpretedFrame
frame)
at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
at
Microsoft.Scripting.Interpreter.LightLambda.Run7[T0,T1,T2,T3,T4,T5,T6,TRet](T0
arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4, T5 arg5, T6 arg6)
at IronPython.Runtime.Importer.ImportLightThrow(CodeContext context, String
fullName, PythonTuple from, Int32 level)
at IronPython.Runtime.Operations.PythonOps.ImportTop(CodeContext context,
String fullName, Int32 level)
at
Microsoft.Scripting.Interpreter.FuncCallInstruction`4.Run(InterpretedFrame
frame)
at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
at Microsoft.Scripting.Interpreter.LightLambda.Run1[T0,TRet](T0 arg0)
at IronPython.Compiler.RuntimeScriptCode.InvokeTarget(Scope scope)
at IronPython.Compiler.RuntimeScriptCode.Run(Scope scope)
at IronPython.Hosting.PythonCommandLine.RunFileWorker(String fileName)
at IronPython.Hosting.PythonCommandLine.RunFile(String fileName)
at Microsoft.Scripting.Hosting.Shell.CommandLine.Run()
at IronPython.Hosting.PythonCommandLine.Run()
at Microsoft.Scripting.Hosting.Shell.CommandLine.Run(ScriptEngine engine,
IConsole console, ConsoleOptions options)
at Microsoft.Scripting.Hosting.Shell.ConsoleHost.RunCommandLine()
at Microsoft.Scripting.Hosting.Shell.ConsoleHost.ExecuteInternal()
at PythonConsoleHost.ExecuteInternal()
at Microsoft.Scripting.Hosting.Shell.ConsoleHost.Execute()
at Microsoft.Scripting.Hosting.Shell.ConsoleHost.Run(String[] args)
at PythonConsoleHost.Main(String[] args)
Same problem in v2.7.1 stable.
Niall"-----------------
19. [New comment] Fatal app exit on import uuid
http://ironpython.codeplex.com/workitem/32355
User ned14 has commented on the issue:
"Attaching the traceback ..."
----------------------------------------------
----------------------------------------------
You are receiving this email because you subscribed to notifications on
CodePlex.
To report a bug, request a feature, or add a comment, visit IronPython Issue
Tracker. You can unsubscribe or change your issue notification settings on
CodePlex.com._______________________________________________
Ironpython-users mailing list
Ironpython-users@python.org
http://mail.python.org/mailman/listinfo/ironpython-users
