On 25 January 2014 22:19, Larry Hastings <la...@hastings.org> wrote: > 1) New policy for what can and cannot be converted during the Derby > The new policy for conversion work for Python 3.4: > > We may only convert functions that have signatures that we can represent > 100% accurately in an inspect.Signature object.
+1. The builtin callables hit a few of these, and I think simply putting them aside for reconsideration post 3.4 release is our best option right now. > I encourage you to add a little text saying why, like: > > /* AC 3.4: waiting for *args support */ So, here's a suggestion I know you're not going to like, but I think is still worth considering: how about postponing varargs support in Argument Clinic until 3.5? Such a decision is not without cost: at least min, max and print can't be made to support programmatic introspection without it, and having unittest.mock.auto_spec(print) work would be a nice demonstration of *why* we think the cost of switching from print-as-statement to print-as-function was worth it in terms of unifying it with the rest of the language. However, you've indicated that adding varargs support is going to take you quite a bit of work, so postponing it is an option definitely worth considering at this point in the release cycle. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
