Hi ironpython,

Here's your Daily Digest of new issues for project "IronPython".

In today's digest:ISSUES

1. [New comment] PythonSocket -- unhandled exception in Finalize() in 
restricted AppDomain
2. [New comment] PythonSocket -- unhandled exception in Finalize() in 
restricted AppDomain
3. [New comment] PythonSocket -- unhandled exception in Finalize() in 
restricted AppDomain
4. [New issue] ipy repl gives IOERROR under cygwin MinTTY

----------------------------------------------

ISSUES

1. [New comment] PythonSocket -- unhandled exception in Finalize() in 
restricted AppDomain
http://ironpython.codeplex.com/workitem/33779
User MarkusSchaber has commented on the issue:

"You should be able to catch the exception by attaching to the 
UnhandledException event of your appdomain: 
[http://msdn.microsoft.com/de-de/library/system.appdomain.unhandledexception.aspx](http://msdn.microsoft.com/de-de/library/system.appdomain.unhandledexception.aspx)
"-----------------

2. [New comment] PythonSocket -- unhandled exception in Finalize() in 
restricted AppDomain
http://ironpython.codeplex.com/workitem/33779
User creinke has commented on the issue:

"As I understand it, "the UnhandledException event simply notifies you that an 
exception has gone unhandled, in case you want to try to save state before your 
thread or application dies." [1]  So, yes, I can catch it, but it still brings 
down the host.

[1] 
http://www.codinghorror.com/blog/2005/02/console-apps-and-appdomain-currentdomain-unhandledexception.html"-----------------

3. [New comment] PythonSocket -- unhandled exception in Finalize() in 
restricted AppDomain
http://ironpython.codeplex.com/workitem/33779
User jdhardy has commented on the issue:

"What I can't quite figure out is why it throws on finalization but not 
creation, since `socket.Handle` is called from `socket.Initialize()` as well. I 
also don't know enough about CAS to know if there's a way to make it fail 
sooner, when it might be possible to handle the error."-----------------

4. [New issue] ipy repl gives IOERROR under cygwin MinTTY
http://ironpython.codeplex.com/workitem/33787
User crowell has proposed the issue:

"__Overview__
running ipy.exe or ipy64.exe within cygwin's MinTTY console gives an IOERROR

__Expected Behavior__
a python console for interacting

__Actual Behavior__
console prints (in a loop)
```
>>> Traceback (most recent call last):
IOError: [Errno 6] The handle is invalid.
```
if pass the flag -X:ExceptionDetail
prints 
```
IOError: [Errno 6] The handle is invalid.

>>> The handle is invalid.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.Console.GetBufferInfo(Boolean throwOnNoConsole, Boolean& 
succeeded)
   at Microsoft.Scripting.Hosting.Shell.SuperConsole.Initialize()
   at Microsoft.Scripting.Hosting.Shell.SuperConsole.ReadLine(Int32 
autoIndentSize)
   at Microsoft.Scripting.Hosting.Shell.CommandLine.ReadStatement(Boolean& 
continueInteraction)
   at IronPython.Hosting.PythonCommandLine.RunOneInteraction()
   at IronPython.Hosting.PythonCommandLine.TryInteractiveActionWorker()
   at IronPython.Hosting.PythonCommandLine.TryInteractiveAction()
   at Microsoft.Scripting.Hosting.Shell.CommandLine.RunInteractiveLoop()
```
__Workarounds__
pass -X:BasicConsole to get a functioning python REPL.

__Related Issues__
perhaps related to this cygwin mintty bug 
https://code.google.com/p/mintty/issues/detail?id=56";
----------------------------------------------



----------------------------------------------
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
[email protected]
http://mail.python.org/mailman/listinfo/ironpython-users

Reply via email to