[Ironpython-users] IronPython, Daily Digest 11/19/2013

[CodePlex]

Hi ironpython,

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

In today's digest:ISSUES

1. [New comment] open() should not automatically decode files starting with BOM
2. [New comment] IPython does not work on IronPython 2.7.4
3. [Status update] IPython does not work on IronPython 2.7.4
4. [New comment] IPython does not work on IronPython 2.7.4

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

ISSUES

1. [New comment] open() should not automatically decode files starting with BOM
http://ironpython.codeplex.com/workitem/34655
User jdhardy has commented on the issue:

"<p>I wonder if this is intentional, or just a side-effect of using .NET APIs.</p><p>In any case, it seems like justifiable behaviour when opening in text mode. I'm unlikely to change it for 2.7.5, but I will match CPython's behaviour for 3.0.</p>"-----------------

2. [New comment] IPython does not work on IronPython 2.7.4
http://ironpython.codeplex.com/workitem/34657
User paweljasinski has commented on the issue:

"<p>The link to expect.py was dead, it is fixed now.<br></p>"-----------------

3. [Status update] IPython does not work on IronPython 2.7.4
http://ironpython.codeplex.com/workitem/34657
User paweljasinski has updated the issue:
Status has changed from Proposed to Closed with the following comment, 

"Not a problem with IronPython"-----------------

4. [New comment] IPython does not work on IronPython 2.7.4
http://ironpython.codeplex.com/workitem/34657
User ksachdeva has commented on the issue:

"<p>Thanks paweljasinski.</p><p>Yesterday, I started to dig into the source code of IPython myself and started to do modifications to pexpect (very similar to what you have done) and had this sudden realization that why should I fix pexpect because IPython works as it is on Python on windows. After reading the source code I found the main reason why pexpect gets invoked in the first place.</p><p>The first issue is in IPython\utils\process.py :</p><p>if sys.platform == 'win32':<br>    from ._process_win32 import _find_cmd, system, getoutput, AvoidUNCPath, arg_split<br>else:<br>    from ._process_posix import _find_cmd, system, getoutput, arg_split</p><p>since IronPython evaulates sys.platform as 'cli' the above check becomes invalid. I fixed this locally and got the following issue :</p><p>In IPython\core\interactiveshell.py whereever there is a reference to IPython.core.hooks the runtime had issues so I have modify the code to do </p><p>from IPython.core import hooks and then use 'hooks' everywhere.</p><p>##</p><p>I believe the check in IPython is incorrect that assumes the platform to be 'win32' but I do not comprehend why IPython.core.hooks does not work in interactive shell. Since it works in cpython may be it IronPython bug.</p><p>After all these local hacks I could make IPython (master from github) to work with IronPython 2.7.4 but now stuck at making notebook work (for which I started to do the whole exercise in the first place). Having trouble installing pyzmq.</p><p>Regards<br>Kapil</p><p></p><p></p><p></p><p><br></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/20131120/975029b6/attachment.html>