☰Read-only archive⌕
Looking for help with Bokeh?

This is a read-only archive. Ask questions and join the conversation on GitHub.

Visit Community Support on GitHub →
Archived discussions · Captured October 28, 2026

Errors in Bokeh Terminal but App Runs

Community Support
Robbie_Pritchard
Robbie_Pritchard

Attached is the terminal output.

platform: OSX 10.11.6

Browser: Chrome 52.0.2743.116

Bokeh: 0.12.1

Django: 1.9.8

Python: 3.5.2

When refreshing the webpage the app is embedded into using django, the app doesn’t get displayed. error is shown in the 2nd terminal output.

⌁   Link to post
Robbie_Pritchard
Robbie_Pritchard

also using
script = autoload_server(model=None, app_path=‘/emptydetails_graph’,
url=“http://127.0.0.1:5006/”)

``

to get the script which is being embedded into the html.
···

On Thursday, September 1, 2016 at 3:14:16 PM UTC-5, Robbie Pritchard wrote:

Attached is the terminal output.

platform: OSX 10.11.6

Browser: Chrome 52.0.2743.116

Bokeh: 0.12.1

Django: 1.9.8

Python: 3.5.2

When refreshing the webpage the app is embedded into using django, the app doesn’t get displayed. error is shown in the 2nd terminal output.

⌁   Link to post
Bryan
Bryan

Do you still have bokeh.client code in the app (i.e. "push_session"?) That is unnecessary when running apps directly with "bokeh serve", and should be removed.

To expand: bokeh.client is *only* useful for connecting a different, separate python process to a Bokeh server. When you run "bokeh serve app.py" those functions are useless -- there is no need to connect to the server, the code is running *in* the server.

That said, I thought we detected and warned when these functions were used accidentally this way..

Thanks,

Bryan

···

On Sep 1, 2016, at 3:15 PM, Robbie Pritchard <rpritchard@ordinalscience.com> wrote:

also using
script = autoload_server(model=None, app_path='/emptydetails_graph',
url="http://127.0.0.1:5006/&quot;\)
to get the script which is being embedded into the html.

On Thursday, September 1, 2016 at 3:14:16 PM UTC-5, Robbie Pritchard wrote:
Attached is the terminal output.

platform: OSX 10.11.6
Browser: Chrome 52.0.2743.116
Bokeh: 0.12.1
Django: 1.9.8
Python: 3.5.2

When refreshing the webpage the app is embedded into using django, the app doesn't get displayed. error is shown in the 2nd terminal output.

--
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bokeh+unsubscribe@continuum.io.
To post to this group, send email to bokeh@continuum.io.
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/f8db1da9-2439-4140-87eb-92da22f3dc2d%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

⌁   Link to post
Robbie_Pritchard
Robbie_Pritchard

That did it. Thanks again!

···

On Thursday, September 1, 2016 at 3:25:14 PM UTC-5, Bryan Van de ven wrote:

Do you still have bokeh.client code in the app (i.e. “push_session”?) That is unnecessary when running apps directly with “bokeh serve”, and should be removed.

To expand: bokeh.client is only useful for connecting a different, separate python process to a Bokeh server. When you run “bokeh serve app.py” those functions are useless – there is no need to connect to the server, the code is running in the server.

That said, I thought we detected and warned when these functions were used accidentally this way…

Thanks,

Bryan

On Sep 1, 2016, at 3:15 PM, Robbie Pritchard rprit...@ordinalscience.com wrote:

also using
script = autoload_server(model=None, app_path=‘/emptydetails_graph’,

url=“http://127.0.0.1:5006/”)

to get the script which is being embedded into the html.

On Thursday, September 1, 2016 at 3:14:16 PM UTC-5, Robbie Pritchard wrote:

Attached is the terminal output.

platform: OSX 10.11.6

Browser: Chrome 52.0.2743.116

Bokeh: 0.12.1

Django: 1.9.8

Python: 3.5.2

When refreshing the webpage the app is embedded into using django, the app doesn’t get displayed. error is shown in the 2nd terminal output.

–
You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” group.

To unsubscribe from this group and stop receiving emails from it, send an email to bokeh+un...@continuum.io.

To post to this group, send email to bo...@continuum.io.

To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/f8db1da9-2439-4140-87eb-92da22f3dc2d%40continuum.io.

For more options, visit https://groups.google.com/a/continuum.io/d/optout.

⌁   Link to post
send2jmuller
send2jmuller

Bryan,
I am new to bokeh but I have found it very useful to run the server with

bokeh serve

and then connect a client process to the server using push_session.

The reason I like this is that I can run this in my debugger.

Is this functionality going away?

If so, will I still be able to run the code in the debugger somehow?

If not … great!

thanks

  • john muller
···

On Thursday, September 1, 2016 at 4:25:14 PM UTC-4, Bryan Van de ven wrote:

Do you still have bokeh.client code in the app (i.e. “push_session”?) That is unnecessary when running apps directly with “bokeh serve”, and should be removed.

To expand: bokeh.client is only useful for connecting a different, separate python process to a Bokeh server. When you run “bokeh serve app.py” those functions are useless – there is no need to connect to the server, the code is running in the server.

That said, I thought we detected and warned when these functions were used accidentally this way…

Thanks,

Bryan

On Sep 1, 2016, at 3:15 PM, Robbie Pritchard rprit...@ordinalscience.com wrote:

also using
script = autoload_server(model=None, app_path=‘/emptydetails_graph’,

url=“http://127.0.0.1:5006/”)

to get the script which is being embedded into the html.

On Thursday, September 1, 2016 at 3:14:16 PM UTC-5, Robbie Pritchard wrote:

Attached is the terminal output.

platform: OSX 10.11.6

Browser: Chrome 52.0.2743.116

Bokeh: 0.12.1

Django: 1.9.8

Python: 3.5.2

When refreshing the webpage the app is embedded into using django, the app doesn’t get displayed. error is shown in the 2nd terminal output.

–
You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” group.

To unsubscribe from this group and stop receiving emails from it, send an email to bokeh+un...@continuum.io.

To post to this group, send email to bo...@continuum.io.

To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/f8db1da9-2439-4140-87eb-92da22f3dc2d%40continuum.io.

For more options, visit https://groups.google.com/a/continuum.io/d/optout.

⌁   Link to post
Bryan
Bryan

Hi,

"push_session" is not going away. But as I stated, push_session", etc. are not useful when running apps directly on a Bokeh server, e.g. with "bokeh serve app.py". I was merely speculating about what the other user's problem might be with the limited information provided.

Thanks,

Bryan

···

On Jan 4, 2017, at 2:02 PM, send2jmuller@gmail.com wrote:

Bryan,
I am new to bokeh but I have found it very useful to run the server with
  bokeh serve
and then connect a client process to the server using push_session.

The reason I like this is that I can run this in my debugger.
Is this functionality going away?
If so, will I still be able to run the code in the debugger somehow?
If not ... great!

thanks
  - john muller

On Thursday, September 1, 2016 at 4:25:14 PM UTC-4, Bryan Van de ven wrote:
Do you still have bokeh.client code in the app (i.e. "push_session"?) That is unnecessary when running apps directly with "bokeh serve", and should be removed.

To expand: bokeh.client is *only* useful for connecting a different, separate python process to a Bokeh server. When you run "bokeh serve app.py" those functions are useless -- there is no need to connect to the server, the code is running *in* the server.

That said, I thought we detected and warned when these functions were used accidentally this way..

Thanks,

Bryan

> On Sep 1, 2016, at 3:15 PM, Robbie Pritchard <rprit...@ordinalscience.com> wrote:
>
> also using
> script = autoload_server(model=None, app_path='/emptydetails_graph',
> url="http://127.0.0.1:5006/&quot;\)
> to get the script which is being embedded into the html.
>
> On Thursday, September 1, 2016 at 3:14:16 PM UTC-5, Robbie Pritchard wrote:
> Attached is the terminal output.
>
>
> platform: OSX 10.11.6
> Browser: Chrome 52.0.2743.116
> Bokeh: 0.12.1
> Django: 1.9.8
> Python: 3.5.2
>
>
> When refreshing the webpage the app is embedded into using django, the app doesn't get displayed. error is shown in the 2nd terminal output.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bokeh+un...@continuum.io.
> To post to this group, send email to bo...@continuum.io.
> To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/f8db1da9-2439-4140-87eb-92da22f3dc2d%40continuum.io\.
> For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

--
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bokeh+unsubscribe@continuum.io.
To post to this group, send email to bokeh@continuum.io.
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/b1054ff0-81e4-423a-a27a-6eb0e0af4436%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

⌁   Link to post

End of archived discussion · Replies are disabled