New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thread issues #281
Comments
@mpmc - I've updated the functions so that args are passed better, let me know if it helps... |
Sadly it doesn't. I now get..
Possible fix here. |
third time lucky? |
Yep, |
Discovered another kwargs issue 😞
with error..
|
Phew - I think this one isn't my fault :) tkinter's |
It's not too much of an problem but I thought you should be aware so you can make a note of it in the "after" doc :). I'll just call the methods directly instead of using after, my initial intention was to add a small delay so the operation could be cancelled. |
The docs only mention |
Yep, I know, but most people whenever they see *args, assume they can use **kwargs as well 👅 |
Fair point! |
There seems to be some weird issues with thread (on next_release).
self.thread(self.device_info_thread, None, **kwargs)
result:
TypeError: thread() got an unexpected keyword argument 'addr'
.Seems thread "eats" unpacked variables?
calling
self.thread(self.device_info_thread, kwargs)
result:
The only positional argument is self..
def device_info_thread(self, **kwargs):
thread always passes kwargs as args, an example.While testing this I crashed my machine (hard lock) & made Python die three times 🤣.
The text was updated successfully, but these errors were encountered: