Nick Coghlan wrote: > functools.partial style functionality doesn't always play well > with methods,
I can see it not working well with *unbound* methods. Bound methods shouldn't be any problem, since from the outside they're called just like any other function. But applying partial to an unbound method seems like a screwy thing to do in the first place. I'm going to need to see a concrete use case for *that* which can't be fixed by explicitly using a special version of partial that inserts after the first argument. -- Greg _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
