Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New comment] {}.update(b=1) -> TypeError
2. [New comment] {}.update(b=1) -> TypeError
3. [New comment] Should subprocess Work On Mono?
----------------------------------------------
ISSUES
1. [New comment] {}.update(b=1) -> TypeError
http://ironpython.codeplex.com/workitem/34742
User jdhardy has commented on the issue:
"<p>`b` is the name of the argument to the C# [update
function](https://github.com/IronLanguages/main/blob/master/Languages/IronPython/IronPython/Runtime/PythonDictionary.cs#L409),
and this is confusing the named argument resolution.</p>"-----------------
2. [New comment] {}.update(b=1) -> TypeError
http://ironpython.codeplex.com/workitem/34742
User jdhardy has commented on the issue:
"<p>Fixed in 5337519/356b9e1. The trick is to give the parameters
"unspeakable" names that make the source look ugly but make
everything work from the Python side.</p>"-----------------
3. [New comment] Should subprocess Work On Mono?
http://ironpython.codeplex.com/workitem/34751
User jdhardy has commented on the issue:
"<p>First off, I appreciate your thoroughness. I'm not sure I've ever but this
much detail into a bug report.</p><p>The short version is that no, it probably
doesn't work, because I don't think it's ever been tested and then made to
work. I would love for it to be supported on Mono, but I just don't have the
time to do it right now myself. One area that may cause issues is the
subprocess (and multiprocessing) might do things to the process state that Mono
doesn't like (see [System.Unix.Native.Syscall.fork is commented
out](http://mono.1490590.n4.nabble.com/System-Unix-Native-Syscall-fork-is-commented-out-td1535320.html),
for example).</p><p>If you want to tackle it,
[Mono.Unix.Native](http://docs.go-mono.com/?link=N%3aMono.Unix.Native) is
probably going to be your friend to fill in IronPython's posix support.
(Interestingly, IP doesn't have a real posix module right now; the 'nt' module
is re-named to 'posix' when running on Unix...)</p><p>One thing to keep in mind
is that the same DLLs have to work on both; happily, DLL imports are not
resolved unless used, and I'm OK with it failing if someone tries to call a
posix method on Windows (this is how the msvcrt module fails on non-Windows
machines, for example). signal.cs is another example of how it can be handled,
where the module needs to be implemented on both platforms. Finally, it's OK to
use reflection to look for Mono.Posix.dll and pull the values at runtime, and
just ignore them at compile time.</p><p>There doesn't seem to be issues open
for fcntl or a real posix module, so feel free to open them if needed.</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._______________________________________________
Ironpython-users mailing list
Ironpython-users@python.org
https://mail.python.org/mailman/listinfo/ironpython-users
