You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the news aliases are all over the module, the version change notice is at the top of the page:
"""
Note
Starting with Python 2.6, this module provides PEP-8 compliant aliases and properties to replace the camelCase names that were inspired by Java’s threading API. This updated API is compatible with that of the multiprocessing module. However, no schedule has been set for the deprecation of the camelCase names and they remain fully supported in both Python 2.x and 3.x.
"""
Activity
atagar1 commentedon Jun 21, 2012
The threading module's isAlive() method had an is_alive() alias first created in python 2.6. The documentation page doesn't mention this...
http://docs.python.org/library/threading.html#threading.Thread.is_alive
However, this is noted for other methods like the Event's is_set()...
http://docs.python.org/library/threading.html#threading.Event.is_set
Very minor issue, just meant that I needed to do a bit of experimentation to figure it out.
atagar1 commentedon Jun 21, 2012
I'm gonna hazard the guess that other methods like currentThread() and current_thread() are the same...
http://docs.python.org/library/threading.html#threading.current_thread
birkenfeld commentedon Jun 21, 2012
Since the news aliases are all over the module, the version change notice is at the top of the page:
"""
Note
Starting with Python 2.6, this module provides PEP-8 compliant aliases and properties to replace the camelCase names that were inspired by Java’s threading API. This updated API is compatible with that of the multiprocessing module. However, no schedule has been set for the deprecation of the camelCase names and they remain fully supported in both Python 2.x and 3.x.
"""