Re: [Python-3000] Ambiguity in PEP 3115 and the args to __prepare__

2007-09-02 Thread Brett Cannon
On 9/2/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > On 9/2/07, Brett Cannon <[EMAIL PROTECTED]> wrote: > > PEP 3115 says a metaclass' __prepare__ takes two positional arguments, > > name and bases. But the example has it actually accept an arbitrary > > number of arguments: name and then ever

Re: [Python-3000] Ambiguity in PEP 3115 and the args to __prepare__

2007-09-02 Thread Guido van Rossum
On 9/2/07, Brett Cannon <[EMAIL PROTECTED]> wrote: > PEP 3115 says a metaclass' __prepare__ takes two positional arguments, > name and bases. But the example has it actually accept an arbitrary > number of arguments: name and then everything else is bound to bases. > > Which happens to be true? I

Re: [Python-3000] Ambiguity in PEP 3115 and the args to __prepare__

2007-09-02 Thread Guilherme Polo
2007/9/2, Brett Cannon <[EMAIL PROTECTED]>: > PEP 3115 says a metaclass' __prepare__ takes two positional arguments, > name and bases. But the example has it actually accept an arbitrary > number of arguments: name and then everything else is bound to bases. > > Which happens to be true? I've pla

[Python-3000] Ambiguity in PEP 3115 and the args to __prepare__

2007-09-02 Thread Brett Cannon
PEP 3115 says a metaclass' __prepare__ takes two positional arguments, name and bases. But the example has it actually accept an arbitrary number of arguments: name and then everything else is bound to bases. Which happens to be true? I'm too tired to even fully trust that I am reading the PEP c