[issue12525] Unable to run a thread

2011-07-10 Thread Georg Brandl
Georg Brandl added the comment: While it's not explicitly documented that run() also shouldn't be called multiple times, it does not need to be supported. Threads can be started exactly once -- this is already mentioned in the docs. Note that run() simply calls the thread target with the giv

[issue12525] Unable to run a thread

2011-07-10 Thread Amandeep Singh
Amandeep Singh added the comment: May be this is a behavior change, that a thread can not be run again. I think documentation needs to be changed in this case. -- ___ Python tracker __

[issue12525] Unable to run a thread

2011-07-10 Thread Amandeep Singh
Amandeep Singh added the comment: I am also not able to call run() twice. I have python 2.5.2 with me, in which I am able to call run method twice and calling run after start is working. -- status: pending -> open ___ Python tracker

[issue12525] Unable to run a thread

2011-07-10 Thread Eric V. Smith
Eric V. Smith added the comment: Don't call both start() and run(). From the documentation, start() arranges for run() to be called. After the call to start(), 'abc' is printed. -- components: +Extension Modules -Build nosy: +eric.smith resolution: -> invalid status: open -> pending

[issue12525] Unable to run a thread

2011-07-10 Thread Amandeep Singh
New submission from Amandeep Singh : I created a thread, and started it and then called its run method. It raised an AttributeError exception from threading import Thread def func(): print 'abc' t = Thread(None, func) t.start() t.run() here t.run() raises an exception. -- compone