Ticket #184 (new defect)
Pyinstaller doesn't work properly with threading.Thread module
| Reported by: | jackson@jacksonc.com | Owned by: | giovannibajo |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | PyInstaller | Version: | PyInstaller 1.4 |
| Severity: | blocker | Keywords: | |
| Cc: |
Description
A program that scans wifi networks using the threading.Thread module doesn't work, so I stripped the program down until I found where execution wasn't as expected. And it seems that things go weird when they enter the threading.Thread.run() method. After building the following code...
import threading class TestThreadClass(threading.Thread): def __init__(self): threading.Thread.__init__(self) def run(self): print 'ONE' print 'TWO' print 'THREE' TestThreadClass().start()
When executed from the terminal in Ubuntu 10.04 and Python 2.6.5 it consistently prints "ONE\nTWO\nTHREE". But when built with PyInstaller? (latest SVN as of 7th May), if I run the program over and over I get different output every time.
eg...
jackson@jackson-laptop:~/Desktop/obscure-bug/dist/test-obscure-bug$ ./test-obscure-bug ONE TWO THREE jackson@jackson-laptop:~/Desktop/obscure-bug/dist/test-obscure-bug$ ./test-obscure-bug jackson@jackson-laptop:~/Desktop/obscure-bug/dist/test-obscure-bug$ ./test-obscure-bug jackson@jackson-laptop:~/Desktop/obscure-bug/dist/test-obscure-bug$ ./test-obscure-bug ONEjackson@jackson-laptop:~/Desktop/obscure-bug/dist/test-obscure-bug$ ./test-obscure-bug ONE TWO jackson@jackson-laptop:~/Desktop/obscure-bug/dist/test-obscure-bug$ ./test-obscure-bug ONE jackson@jackson-laptop:~/Desktop/obscure-bug/dist/test-obscure-bug$ ./test-obscure-bug jackson@jackson-laptop:~/Desktop/obscure-bug/dist/test-obscure-bug$ ./test-obscure-bug ONE jackson@jackson-laptop:~/Desktop/obscure-bug/dist/test-obscure-bug$ ./test-obscure-bug ONE TWO jackson@jackson-laptop:~/Desktop/obscure-bug/dist/test-obscure-bug$ ./test-obscure-bug jackson@jackson-laptop:~/Desktop/obscure-bug/dist/test-obscure-bug$
Attachments
Change History
Note: See
TracTickets for help on using
tickets.
