Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New issue] IronPython coding obeys PEP0263, inconsistent with Emacs
2. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
3. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
4. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
5. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
6. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
7. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
8. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
9. [New comment] Still doesn't recognise *valid* PEP0263 codings in source files
10. [Status update] Issues installing IronPython 2.6.1 on windows 7 64 bit
11. [New comment] Need to investigate various doctest failures
12. [Status update] Support pep-263 file encodings
13. [New comment] Trivial: isdigit() return "False" in IronPython with unicode
object from u'\u2460' to u'\u2468'
14. [New comment] Compatibility: IronPython does not allow space before coding
declaration
15. [Status update] ipy.exe / pyc.py fails to create working WPF .exe on
Windows Server 2008-64, .NET 4.0
16. [Status update] CallingDotNet example fails
17. [Status update] json load converts empty dict to empty list
18. [New issue] Communicate with package maintainers for various distributions
----------------------------------------------
ISSUES
1. [New issue] IronPython coding obeys PEP0263, inconsistent with Emacs
http://ironpython.codeplex.com/workitem/32856
User russel_winder has proposed the issue:
"PEP0263 and Emacs appear to be mutually inconsistent regarding coding
specification. Emacs says:
# -*- coding:utf-8; -*-
whilst PEP0263 says:
# -*- coding:utf-8 -*-
CPython, PyPy and Jython all allow for both and so are compatible with Emacs.
IronPython treats the Emacs form as invalid syntax. IronPython should be
consistent with CPython, PyPy and Jython and be flexible so as to be compatible
with Emacs rather than adhere strictly to PEP0263."-----------------
2. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
http://ironpython.codeplex.com/workitem/32856
User russel_winder has commented on the issue:
"Sorry I should have added that I am using the IronPython that is standard on
Debian Unstable, which is 2.6~beta2-4."-----------------
3. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
http://ironpython.codeplex.com/workitem/32856
User slide_o_mix has commented on the issue:
"Are you getting an error? Can you post any stack traces, etc that you have
gotten?"-----------------
4. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
http://ironpython.codeplex.com/workitem/32856
User slide_o_mix has commented on the issue:
"This is a diff from the current tree with an update that should fix this
issue. It should be trivial to backport to your 2.6 version, if you can build
from source. I will look into how we can work with the Debian package
maintainers and get an updated version. I'll also commit this for
2.7."-----------------
5. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
http://ironpython.codeplex.com/workitem/32856
User russel_winder has commented on the issue:
"The program:
# -*- coding:utf-8; -*-
print 'worked.'
works fine with python, pypy and jython. With ipy I get:
|> ipy ironPythonCodingCheck.py
File "ironPythonCodingCheck.py", line ?
^
SyntaxError: unknown encoding type
"-----------------
6. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
http://ironpython.codeplex.com/workitem/32856
User slide_o_mix has commented on the issue:
"Also, the PEP actually just says that it should match the following regex
(which both the PEP0263 example and the Emacs examples you supplied do). This
is the fix I put in.
coding[:=]\s*([-\w.]+)"-----------------
7. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
http://ironpython.codeplex.com/workitem/32856
User russel_winder has commented on the issue:
"Sorry about the loss of formatting on the previous comment, this is the first
time I have used this system and I have no idea how to enforce formatting. Also
I already dislike the ordering of comments, they go the wrong way :-(
"-----------------
8. [New comment] IronPython coding obeys PEP0263, inconsistent with Emacs
http://ironpython.codeplex.com/workitem/32856
User slide_o_mix has commented on the issue:
"Fixed in 0316c67"-----------------
9. [New comment] Still doesn't recognise *valid* PEP0263 codings in source files
http://ironpython.codeplex.com/workitem/19861
User slide_o_mix has commented on the issue:
"Fixed in 0316c67"-----------------
10. [Status update] Issues installing IronPython 2.6.1 on windows 7 64 bit
http://ironpython.codeplex.com/workitem/28657
User slide_o_mix has updated the issue:
Status has changed from Proposed to Closed with the following comment,
"Cannot reproduce"-----------------
11. [New comment] Need to investigate various doctest failures
http://ironpython.codeplex.com/workitem/24549
User slide_o_mix has commented on the issue:
"Can you please add some more description to this?"-----------------
12. [Status update] Support pep-263 file encodings
http://ironpython.codeplex.com/workitem/23655
User slide_o_mix has updated the issue:
Status has changed from Active to Closed with the following comment,
"Duplicate"-----------------
13. [New comment] Trivial: isdigit() return "False" in IronPython with unicode
object from u'\u2460' to u'\u2468'
http://ironpython.codeplex.com/workitem/23855
User slide_o_mix has commented on the issue:
"Fixed in 67ec3d1"-----------------
14. [New comment] Compatibility: IronPython does not allow space before coding
declaration
http://ironpython.codeplex.com/workitem/29193
User slide_o_mix has commented on the issue:
"Fixed in 67ec3d1"-----------------
15. [Status update] ipy.exe / pyc.py fails to create working WPF .exe on
Windows Server 2008-64, .NET 4.0
http://ironpython.codeplex.com/workitem/29028
User slide_o_mix has updated the issue:
Status has changed from Proposed to Closed with the following comment,
"Issue resolved"-----------------
16. [Status update] CallingDotNet example fails
http://ironpython.codeplex.com/workitem/32742
User slide_o_mix has updated the issue:
Status has changed from Proposed to Closed with the following comment,
"Cannot reproduce."-----------------
17. [Status update] json load converts empty dict to empty list
http://ironpython.codeplex.com/workitem/29041
User slide_o_mix has updated the issue:
Status has changed from Active to Closed with the following comment,
"This works in 2.7.3"-----------------
18. [New issue] Communicate with package maintainers for various distributions
http://ironpython.codeplex.com/workitem/32860
User slide_o_mix has proposed the issue:
"Debian is using a fairly old version of IronPython, this may be the case with
other distros as well. It would be good to be in contact with the package
maintainers for various distros to try and push new versions into circulation."
----------------------------------------------
----------------------------------------------
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
Ironpython-users@python.org
http://mail.python.org/mailman/listinfo/ironpython-users
