The attached patch ports the implementation of keyword-only arguments
from revision 52491 back to trunk.

This is the first time I've worked on the C internals, so here are some
notes:

- test_collections is the only test which fails, because it tries to
call a function with more than 255 arguments, which results in a
SyntaxError because of the following added code in Python/ast.c. What
should be done about it?

    if (nposargs + nkwonlyargs > 255) {
        ast_error(n, "more than 255 arguments");
        return NULL;
    }

- The patch only adds what's in revision 52491. There is at least one
more change involving keyword-only arguments, for example issue1573. Are
there others? Should they be included in this patch or in a separate one?

- There are some changes which were generated, like Python/Python-ast.c
(which needs to be checked in separately).

- Is there documentation which needs to be updated?

Another note: Because the marshalling of code objects is changed, is
there a version number of the format which has to be incremented?

Thanks for tackling this!

What line in test_collections.py is calling a function with >255 args? 
I'm a bit surprised since this has always been disallowed AFAICT.

I'd like to see everything related to keyword-only args included in one
patch.  Hopefully the unittests and/or svn history will give you an idea
of what to do.

There should be docs in the reference manual.  Maybe Georg knows where.

Don't worry about the generated Python-ast.c patch.

The version number you're looking for is MAGIC in Python/import.c.

Keyword-only-args are not yet documented.

Thanks for the feedback!

It's on line 111 in test_collections.py::

        n = 10000
        import string, random
        names = [''.join([random.choice(string.letters) for j in
range(10)]) for i in range(n)]
        Big = namedtuple('Big', names)
        b = Big(*range(n))

I think the condition is triggered because Big's __new__ (which seems to
be dynamically generated by namedtuple using exec) has an argument list
with 10000 arguments.

Ok, I'm now looking through SVN logs and have already added some more
changes to my patchset.

Thanks, I had changed MAGIC but didn't know that marshal.c uses it.

So I won't handle documentation in this issue then.

I vaguely remember that I had to modify the tests to use 254 args in
Python 3.0.

There's something I misunderstand then.  I thought 2.x also didn't
accept >255 args, but that test would seem to prove I'm wrong.

Guido: The check was only done for call nodes, not for function definitions.

Ok, I checked all the logs and updated the patch. test_collections uses
n = 254 now and all tests pass.

I left revision 54043 out on purpose, because it fixes Lib/inspect.py
and Lib/pydoc.py for both PEP 3102 and 3107, so it should be included in
the patch for PEP 3107.

I've updated the patch to apply cleanly again.

Bumping priority.

The patch doesn't apply cleanly for me.  I can fix the non-clean patch,
but another error is that obj2ast_arguments doesn't call arguments()
with the correct parameters.  If I pass in NULL's for the new params,
all tests pass, but that just tells me it's not being tested thoroughly.

I'll spend some time looking at it, but if anyone else wants to look at
it, go ahead.

This will probably have to be deferred to 2.7.

What's holding back the backport to 2.6?

On Mon, Aug 4, 2008 at 1:35 AM, tav <report@bugs.python.org> wrote:
>
> tav <tav@espians.com> added the comment:
>
> What's holding back the backport to 2.6?

The fact that we are working towards the 3rd and final beta.
>
> ----------
> nosy: +tav
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue1745>
> _______________________________________
>

-- 
Cheers,
Benjamin Peterson
"There's no place like 127.0.0.1."

This will definitely not be in 2.6.

Running out of time for 2.7 as well...

2009/4/3 Michael Foord <report@bugs.python.org>:
>
> Michael Foord <michael@voidspace.org.uk> added the comment:
>
> Running out of time for 2.7 as well...

How so? The first 2.7 alpha probably won't be until the end of summer.

Is there any update on this for 2.7 ?

FWIW I updated the patch to r79264; it applies cleanly and passes the tests but other than that I can't tell if it's ready. It would be nice to have it in 2.7 though.

Now, that 2.7 is out we won't able to commit this anymore. It is sad to abandon a good patch like this.