Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New comment] Failure to bind base accessor if only one accessor is
overridden in derived class
2. [New issue] struct.pack not threadsafe
----------------------------------------------
ISSUES
1. [New comment] Failure to bind base accessor if only one accessor is
overridden in derived class
http://ironpython.codeplex.com/workitem/31861
User mvdk has commented on the issue:
"On line 228 of PythonTypeInfo.cs: res =
FilterSpecialNames(binder.GetMember(curType, name), name, action);
binder.GetMember(curType, name) needs flags to tell it to retrieve resp.
GetField | GetProperty, SetField | SetProperty. Perhaps these should be higher
priority resolvers."-----------------
2. [New issue] struct.pack not threadsafe
http://ironpython.codeplex.com/workitem/33720
User mvdk has proposed the issue:
"When using paramiko with more than one process spawning, I
occasionally get the following:
System.InvalidOperationException: The LinkedList node already belongs
to a LinkedList.
at System.Collections.Generic.LinkedList`1.ValidateNewNode(LinkedListNode`1
node) at System.Collections.Generic.LinkedList`1.AddFirst(LinkedListNode`1
node)
at IronPython.Modules.PythonStruct.pack(CodeContext context, String
fmt, Object[] values)
at CallSite.Target(Closure , CallSite , CodeContext , Object ,
String , Object )
at paramiko.message$37.add_int$491(PythonFunction $function, Object
self, Object n) in
C:\repo\trunk\external\python\paramiko\message.py:line 227
at paramiko.message$37.add_string$494(PythonFunction $function,
Object self, Object s) in
C:\repo\trunk\external\python\paramiko\message.py:line 259
at paramiko.transport$13.open_channel$273(PythonFunction $function,
Object self, Object kind, Object dest_addr, Object src_addr) in
C:\repo\trunk\external\python\paramiko\transport.py:line 773
... Lots more in the stack trace.
I think that this is due to PythonStruct.pack's usage of CacheDict,
which is explicitly marked as not thread safe. A quick and dirty hack
would be to force all users of _cache to lock it first, though I'm
sure there's a better answer.
Reproducing this has been troublesome (with what we have, I found that it
triggered maybe once every 10 runs), but I'm sure that someone can think of a
way :)"
----------------------------------------------
----------------------------------------------
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
