-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
Workaround for datetime streaming bug in bokeh #2383
Conversation
4490594
to
3dd2e32
Compare
so my code with bokeh-0.12.5.dev1 will break also ? would it be possible to include it in the test ? |
Probably a good idea. |
3dd2e32
to
ba377db
Compare
ba377db
to
86b886c
Compare
Ready to merge. |
Looks like this change will require pinning to bokeh>=0.12.14, which also affects 1.9.5 since I ported this change there. |
Are you going to pin bokeh in this PR? I would also like to see an issue to remove this hack once it is fixed in bokeh to make sure we remove this code when we can. Otherwise, happy to merge. |
Unless we want to remove support for bokeh 0.12.14 we can't really delete this. But I'll pin bokeh now. |
We will be happy to remove support for bokeh 0.12.14 eventually so I would still file an issue. Maybe assign it to the 2.0 milestone. |
Looks good. Merging. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Very ugly workaround for bokeh/bokeh#7587 in bokeh datetime streaming.