-
-
Notifications
You must be signed in to change notification settings - Fork 508
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
pn.state.onload
doesn't work with threads
#5819
Comments
Thanks, I was confused. It looks like the onload callbacks all run on the same separate thread but aren't scheduled concurrently. |
Note that I did not enable this by default in #5862 because people might have relied on consecutive execution. So to enable this you will have to do |
Thanks, @philippjfr ! Would it be easy to add a similar option to |
Seems like a good feature request, mind filing a separate issue for that? Doesn't have to be super descriptive or anything. |
Did you consider setting making a deprecation warning for threaded=False? And then in for example 1.5 use True as default value. |
ALL software version info
Python 3.10.13
Panel: 1.3.1
Bokeh: 3.3.0
Param: 2.0.0
Description of expected behavior and the observed behavior
By enabling multi-threading (using
pn.config.nthreads
), I expect differnet callbacks registered withpn.state.onload
to run in parallel on different threads. But currently they all run on the main process only.Complete, minimal, self-contained example code that reproduces the issue
Stack traceback and/or browser JavaScript console output
Screenshots or screencasts of the bug in action
The text was updated successfully, but these errors were encountered: