Tulip thread/process name analogue

[GoogleCodeExporter]

This is a feature request, not a bug.

Thread names are a common logging aide in Python and other mainstream 
languages. Since a particular Tulip event loop is inherently single threaded, 
yet can still multiplex complex independent activities I propose a mechanism to 
assign names to Tulip's thread analogues - Tasks/coroutines. This information 
should then be accessible in some way by logger instances.

This should maybe be designed in a way that is useful to other async event loop 
implementations, such as Twisted and Tornado?

Guido has expressed interest in the idea, but maybe not in the first release.

Original issue reported on code.google.com by tinches...@gmail.com on 6 Oct 2013 at 1:09