This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients jkloth, larry, serhiy.storchaka
Date 2014-01-07.21:58:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <9594188.oEjLz4mIuz@raxxla>
In-reply-to <>
call() just converts all args to Tcl list. Is Argument Clinic supports *args 
and **kwargs? I'm not sure there is a benefit with using Argument Clinic here.

splitlist() and split() first call PyArg_ParseTuple with one argument, check 
the input, and then may call PyArg_ParseTuple with other argument. They need 
large refactoring to use Argument Clinic.

getint(), getdouble(), getboolean() first manually unpack arguments tuple, and 
then may call PyArg_ParseTuple. Same as above.

setvar()/globalsetvar(), getvar()/globalgetvar(), unsetvar()/globalunsetvar() 
shares common code parametrized by flags. I think this is resolvable. But 
worse, they can delegates their execution to other thread and should save all 
arguments in events queue. And this looks absolutely unsuitable for Argument 
Date User Action Args
2014-01-07 21:58:06serhiy.storchakasetrecipients: + serhiy.storchaka, larry, jkloth
2014-01-07 21:58:06serhiy.storchakalinkissue20168 messages
2014-01-07 21:58:06serhiy.storchakacreate