Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=80701 --- shadow/80701 2007-04-13 22:56:57.000000000 -0400 +++ shadow/80701.tmp.16742 2007-04-13 23:26:41.000000000 -0400 @@ -110,6 +110,27 @@ this is all being checked dynamically, so there's not even any safety benefit from static analysis. The environment variable MONO_STRICT_IO_EMULATION was not set either. Maybe there could be a MONO_IO variable that can be set to POSIX/unix/native or Win32? + +------- Additional Comments From [EMAIL PROTECTED] 2007-04-13 23:26 ------- +I guess there's a workaround: + +$ ipy -X:TabCompletion +IronPython 1.0.2441 on .NET 2.0.50727.42 +Copyright (c) Microsoft Corporation. All rights reserved. +>>> f = open("/tmp/test2", "r") +Traceback (most recent call last): + File mscorlib, line unknown, in .ctor + File mscorlib, line unknown, in .ctor +IOError: Sharing violation on path /tmp/test2 + + + +$ MONO_SHARED_DIR=`mktemp -d` ipy -X:TabCompletion +IronPython 1.0.2441 on .NET 2.0.50727.42 +Copyright (c) Microsoft Corporation. All rights reserved. +>>> f = open("/tmp/test2", "r") +>>> + _______________________________________________ mono-bugs maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-bugs
