Work is love made visible.- Kihlal Gibran
Path consumption is now supported in Selector. This better supports multiple dispatch. I had previously been a little skeptical about consuming PATH_INFO in the dispatcher object itself, but it is a convenient option and there seems to be some popular demand for it. If you still want to keep your dispatch decoupled from your path consumption, you can simply turn it off.
Thanks to Jason Kirtland, Luke Opperman and Samuel Montgomery-Blinn.
The previously proposed convention of storing dispatch args in the 'wsgi.url_vars' environ key has now been marked as accepted but the key has been renamed to 'wsgiorg.routing_args'. That means that this is no longer an experimental feature and you can rely on it going forward. That was quick!
environ['wsgiorg.routing_args'] == (list_or_tuple, a_dict)
See the Selector page for more info.
I have made yet another round of little improvements to Selector.
The proposed wsgi.url_vars spec is now used. Positional args are now supported in path expressions. Some little decorators to map the args (vars, captures... whatever) from the URL to the callable's signature have been included. Naked-object and HTTP-method-to-object-method styles of dispatch are now provided for completeness. I am hoping that the slight cleverness of some of these features does not lead to their overuse, but what is one to do? Finally, selector is now LGPL.
See the Selector page for more info.