Brett Cannon wrote:
> On 5/2/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
>> All of the use cases I can think of (introspection for documentation
>> purposes
>> or argument checking purposes) don't really suffer either way
>> regardless of
>> whether the signature retrieval is spelt "obj.__signatu
On 5/2/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
> > One is whether a signature object should be automatically created for
> > every function. As of right now the PEP I am drafting has it on a
> > per-need basis and have it assigned to __signature__ through a
> > built-in f
Brett Cannon wrote:
> One is whether a signature object should be automatically created for
> every function. As of right now the PEP I am drafting has it on a
> per-need basis and have it assigned to __signature__ through a
> built-in function or putting it 'inspect'. Now automatically creating
On Mon, May 01, 2006, Brett Cannon wrote:
> On 5/1/06, Aahz <[EMAIL PROTECTED]> wrote:
>>On Mon, May 01, 2006, Brett Cannon wrote:
>>>
>>> But there are two things that I can't quite decide upon.
>>>
>>> One is whether a signature object should be automatically created
>>> for every function. As o
On 5/1/06, Aahz <[EMAIL PROTECTED]> wrote:
> On Mon, May 01, 2006, Brett Cannon wrote:
> >
> > But there are two things that I can't quite decide upon.
> >
> > One is whether a signature object should be automatically created
> > for every function. As of right now the PEP I am drafting has it
> >
On Mon, May 01, 2006, Brett Cannon wrote:
>
> But there are two things that I can't quite decide upon.
>
> One is whether a signature object should be automatically created
> for every function. As of right now the PEP I am drafting has it
> on a per-need basis and have it assigned to __signature_
Brett Cannon wrote:
> The second question is whether it is worth providing a function that
> will either figure out if a tuple and dict representing arguments
> would work in calling the function. Some have even suggested a
> function that returns the actual bindings if the call were to occur.
>
Signature objects (which has been lightly discussed on python-3000,
but I realize should be retargeted to 2.6 since there is no
incompatibility problems) are the idea of having an object that
represents the parameters of a function for easy introspection. But
there are two things that I can't quit
