*On Behalf Of *Andrew
*Sent:* Wednesday, February 14, 2007 10:54 AM
*To:* Discussion of IronPython
*Subject:* Re: [IronPython] Bug in handling of keyword arguments for
__call__
It seems that this refers to Item # 7594:
http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=7594
2
f these are fixed in some internal (post v1.1) builds
but the bad news is those aren't on CodePlex yet.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew
Sent: Wednesday, February 14, 2007 10:54 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Bug in handling of
t. I've opened bug #8246 to track this (
http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=8246).
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Giles Thomas
> Sent: Wednesday, February 14, 2007 7:17 AM
> To: Discussion of IronP
L PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Giles Thomas
> Sent: Wednesday, February 14, 2007 7:17 AM
> To: Discussion of IronPython
> Subject: [IronPython] Bug in handling of keyword arguments for __call__
>
> Hi,
>
> It looks like there's a problem with calling a
AM
To: Discussion of IronPython
Subject: [IronPython] Bug in handling of keyword arguments for __call__
Hi,
It looks like there's a problem with calling a callable object using the
"**" dictionary-unpacking syntax for keyword arguments. Here's a
minimal repro.
In CPython:
Hi,
It looks like there's a problem with calling a callable object using the
"**" dictionary-unpacking syntax for keyword arguments. Here's a
minimal repro.
In CPython:
Python 2.4.3 (#69, Mar 29 2006, 17:35:34) [MSC v.1310 32 bit (Intel)] on
win32
Type "help", "copyr
