[Ironpython-users] IronPython, Daily Digest 5/2/2014

[CodePlex]

Hi ironpython,

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

In today's digest:ISSUES

1. [Status update] no public usable FunctionType.__new__
2. [New comment] no public usable FunctionType.__new__
3. [New comment] types.FunctionType(...) raise NotImplementedError
4. [New comment] types.FunctionType(...) raise NotImplementedError

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

ISSUES

1. [Status update] no public usable FunctionType.__new__
http://ironpython.codeplex.com/workitem/34932
User paweljasinski has updated the issue:
Status has changed from Proposed to Closed with the following comment, 

"There is a new issue with active discussion."-----------------

2. [New comment] no public usable FunctionType.__new__
http://ironpython.codeplex.com/workitem/34932
User paweljasinski has commented on the issue:

"<p>Dupplicate: https://ironpython.codeplex.com/workitem/35180</p>"-----------------

3. [New comment] types.FunctionType(...) raise NotImplementedError
http://ironpython.codeplex.com/workitem/35180
User jdhardy has commented on the issue:

"<p>From DinoV:</p><p>"I think the reason it's not implemented is due to the closure object and the globals dictionary.  Those need to be converted into the appropriate MutableTuple and into the correct CodeContext which defines the function.  If there is a closure then that means going off and constructing a RuntimeVariablesDictionaryStorage for the dictionary used for the code context of the function.</p><p>"Depending on the function that's being copied it might be easy enough to make this work in the non-closure case (checking both the FunctionCode and the passed in closure tuple) and throwing NotImplemented in the closure case.  Or someone needs to work through recreating these data structures.  I'd actually have to go back and look at how we're generating functions to remember what goes into the MutableTuple, I suspect it's the actual ClosureCell objects and maybe the CodeContext as well.  It's probably not too difficult to implement it was just never necessary :)"</p>"-----------------

4. [New comment] types.FunctionType(...) raise NotImplementedError
http://ironpython.codeplex.com/workitem/35180
User paweljasinski has commented on the issue:

"<p>dupplicate: https://ironpython.codeplex.com/workitem/34932</p>"
----------------------------------------------



----------------------------------------------
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20140503/260d87df/attachment.html>