bokeh-server: command not found

On Dec 6, 2015, at 1:45 PM, wu.tianchen2015@gmail.com wrote:

I have clone the source code from github and installed in the following way

http://bokeh.pydata.org/en/latest/docs/quickstart.html#quick-installation

version

    '0.11.0dev2-433-g96576eb'

Everything works fine, except for bokeh server

type in "bokeh server" in command line, get

    bokeh-server: command not found

but "bokeh serve" does start the tornado server, which in documentation say Flask is used ?

--
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/57fb89fe-045d-4575-b3e9-d7a436fc8703%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

On Dec 6, 2015, at 2:13 PM, Bryan Van de Ven <bryan@bokeh.org> wrote:

Hi,

Bokeh had an older server "bokeh-server" which was Flask based. Unfortunately it did not scale well or meet the performance we wanted to achieve. There is a new "bokeh server" command that is currently in the master branch of the repository. The new server is based on Tornado and a pure websocket protocol. It is easier to deploy and use, but it is still under active development. In particular, we are still working on the documentaion for it (The 0.11 release will not happen until full documentation is in place). Additionally, the changes needed to support the new server and protocol were incompatible in fundamental ways with the old server, so it has been completely removed. If you need to use "bokeh-server" at present, I must advise staying on the last stable release, 0.10 for now.

If you'd like to try the new server, we'd be happy to help, and I would direct you to any of the examples (except crossfilter, which is still being fixed up) at:

  https://github.com/bokeh/bokeh/tree/master/examples/app

Thanks,

Bryan

On Dec 6, 2015, at 1:45 PM, wu.tianchen2015@gmail.com wrote:

I have clone the source code from github and installed in the following way

http://bokeh.pydata.org/en/latest/docs/quickstart.html#quick-installation

version

   '0.11.0dev2-433-g96576eb'

Everything works fine, except for bokeh server

type in "bokeh server" in command line, get

   bokeh-server: command not found

but "bokeh serve" does start the tornado server, which in documentation say Flask is used ?

--
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/57fb89fe-045d-4575-b3e9-d7a436fc8703%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

On Sunday, December 6, 2015 at 11:06:07 PM UTC, Bryan Van de ven wrote:

FYI there are now some preliminary bokeh command docs up at:

    [http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli](http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli)

These will be continually expanded and improve as we move towards the 0.11 release in early January.

Bryan

On Dec 6, 2015, at 2:13 PM, Bryan Van de Ven bry...@continuum.io wrote:

Hi,

Bokeh had an older server “bokeh-server” which was Flask based. Unfortunately it did not scale well or meet the performance we wanted to achieve. There is a new “bokeh server” command that is currently in the master branch of the repository. The new server is based on Tornado and a pure websocket protocol. It is easier to deploy and use, but it is still under active development. In particular, we are still working on the documentaion for it (The 0.11 release will not happen until full documentation is in place). Additionally, the changes needed to support the new server and protocol were incompatible in fundamental ways with the old server, so it has been completely removed. If you need to use “bokeh-server” at present, I must advise staying on the last stable release, 0.10 for now.

If you’d like to try the new server, we’d be happy to help, and I would direct you to any of the examples (except crossfilter, which is still being fixed up) at:

    [https://github.com/bokeh/bokeh/tree/master/examples/app](https://github.com/bokeh/bokeh/tree/master/examples/app)

Thanks,

Bryan

On Dec 6, 2015, at 1:45 PM, wu.tian...@gmail.com wrote:

I have clone the source code from github and installed in the following way

http://bokeh.pydata.org/en/latest/docs/quickstart.html#quick-installation

version

‘0.11.0dev2-433-g96576eb’

Everything works fine, except for bokeh server

type in “bokeh server” in command line, get

bokeh-server: command not found

but “bokeh serve” does start the tornado server, which in documentation say Flask is used ?

–
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/57fb89fe-045d-4575-b3e9-d7a436fc8703%40continuum.io.

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

On Dec 7, 2015, at 6:44 AM, yhdanid via Bokeh Discussion - Public <bokeh@continuum.io> wrote:

BTW, the bundled bokeh-server script file, which resides in the Scripts directory,does not run on windows-- not unless some hack is made somewhere like running it under a bash shell.

One solution is maybe provide a cmd/batch file that itself calls the script file and passes it all the options. Like so:

REM Start of contents of bokeh-server.cmd
@python F:\Python27\Scripts\bokeh-server %*
REM End of contents of file

Another approach is to create what is referred to as a console script, a solution many module developers seem to prefer, where the script is turned into an exe file by setuptools and deposited in the Script directory. This approach is done through defining appropriate settings in the script.py file with something like the following:

     py_modules=['bokeh'],
     entry_points={
        'console_scripts': [
            'bokeh-server = bokeh-server:main',
        ],
  },

On Sunday, December 6, 2015 at 11:06:07 PM UTC, Bryan Van de ven wrote:
FYI there are now some preliminary bokeh command docs up at:

        http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli

These will be continually expanded and improve as we move towards the 0.11 release in early January.

Bryan

> On Dec 6, 2015, at 2:13 PM, Bryan Van de Ven <bry...@continuum.io> wrote:
>
> Hi,
>
> Bokeh had an older server "bokeh-server" which was Flask based. Unfortunately it did not scale well or meet the performance we wanted to achieve. There is a new "bokeh server" command that is currently in the master branch of the repository. The new server is based on Tornado and a pure websocket protocol. It is easier to deploy and use, but it is still under active development. In particular, we are still working on the documentaion for it (The 0.11 release will not happen until full documentation is in place). Additionally, the changes needed to support the new server and protocol were incompatible in fundamental ways with the old server, so it has been completely removed. If you need to use "bokeh-server" at present, I must advise staying on the last stable release, 0.10 for now.
>
> If you'd like to try the new server, we'd be happy to help, and I would direct you to any of the examples (except crossfilter, which is still being fixed up) at:
>
> https://github.com/bokeh/bokeh/tree/master/examples/app
>
> Thanks,
>
> Bryan
>
>> On Dec 6, 2015, at 1:45 PM, wu.tian...@gmail.com wrote:
>>
>> I have clone the source code from github and installed in the following way
>>
>> http://bokeh.pydata.org/en/latest/docs/quickstart.html#quick-installation
>>
>> version
>>
>> '0.11.0dev2-433-g96576eb'
>>
>> Everything works fine, except for bokeh server
>>
>> type in "bokeh server" in command line, get
>>
>> bokeh-server: command not found
>>
>> but "bokeh serve" does start the tornado server, which in documentation say Flask is used ?
>>
>>
>> --
>> 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/57fb89fe-045d-4575-b3e9-d7a436fc8703%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/0f46801c-8375-4bcf-9957-75de143d6489%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

On Thursday, December 10, 2015 at 5:09:08 AM UTC, Bryan Van de ven wrote:

There should not be a “bokeh-server” if you are using a Bokeh 0.11 pre-release dev build. Either you have an old file laying around after update, or we have an issue in our windows packaging. The new command is simply “bokeh” with a “bokeh serve” subcommand. Can you confirm what version of bokeh you have installed?

Bryan

On Dec 7, 2015, at 6:44 AM, yhdanid via Bokeh Discussion - Public bo...@continuum.io wrote:

BTW, the bundled bokeh-server script file, which resides in the Scripts directory,does not run on windows-- not unless some hack is made somewhere like running it under a bash shell.

One solution is maybe provide a cmd/batch file that itself calls the script file and passes it all the options. Like so:

REM Start of contents of bokeh-server.cmd

@python F:\Python27\Scripts\bokeh-server %*

REM End of contents of file

Another approach is to create what is referred to as a console script, a solution many module developers seem to prefer, where the script is turned into an exe file by setuptools and deposited in the Script directory. This approach is done through defining appropriate settings in the script.py file with something like the following:

 py_modules=['bokeh'],

 entry_points={

    'console_scripts': [

        'bokeh-server = bokeh-server:main',

    ],

},

On Sunday, December 6, 2015 at 11:06:07 PM UTC, Bryan Van de ven wrote:

FYI there are now some preliminary bokeh command docs up at:

    [http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli](http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli)

These will be continually expanded and improve as we move towards the 0.11 release in early January.

Bryan

On Dec 6, 2015, at 2:13 PM, Bryan Van de Ven bry...@continuum.io wrote:

Hi,

Bokeh had an older server “bokeh-server” which was Flask based. Unfortunately it did not scale well or meet the performance we wanted to achieve. There is a new “bokeh server” command that is currently in the master branch of the repository. The new server is based on Tornado and a pure websocket protocol. It is easier to deploy and use, but it is still under active development. In particular, we are still working on the documentaion for it (The 0.11 release will not happen until full documentation is in place). Additionally, the changes needed to support the new server and protocol were incompatible in fundamental ways with the old server, so it has been completely removed. If you need to use “bokeh-server” at present, I must advise staying on the last stable release, 0.10 for now.

If you’d like to try the new server, we’d be happy to help, and I would direct you to any of the examples (except crossfilter, which is still being fixed up) at:

    [https://github.com/bokeh/bokeh/tree/master/examples/app](https://github.com/bokeh/bokeh/tree/master/examples/app)

Thanks,

Bryan

On Dec 6, 2015, at 1:45 PM, wu.tian...@gmail.com wrote:

I have clone the source code from github and installed in the following way

http://bokeh.pydata.org/en/latest/docs/quickstart.html#quick-installation

version

‘0.11.0dev2-433-g96576eb’

Everything works fine, except for bokeh server

type in “bokeh server” in command line, get

bokeh-server: command not found

but “bokeh serve” does start the tornado server, which in documentation say Flask is used ?

–
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/57fb89fe-045d-4575-b3e9-d7a436fc8703%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+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/0f46801c-8375-4bcf-9957-75de143d6489%40continuum.io.

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

On Dec 10, 2015, at 12:53 AM, yhdanid via Bokeh Discussion - Public <bokeh@continuum.io> wrote:

If this is addressed to me, then my answer is I have bokeh-0.10.0 installed, which has a bokeh-server file (with no extension) copied to the Scripts directory. That file needs bash to work; and on Windows must be run within bash somehow, hence my resorting to creating a cmd/batch file to be invoked by the command "bokeh-server" and which calls the bokeh-server actual file and passes to it whatever options that were given to the cmd/batch file.

On Thursday, December 10, 2015 at 5:09:08 AM UTC, Bryan Van de ven wrote:
There should not be a "bokeh-server" if you are using a Bokeh 0.11 pre-release dev build. Either you have an old file laying around after update, or we have an issue in our windows packaging. The new command is simply "bokeh" with a "bokeh serve" subcommand. Can you confirm what version of bokeh you have installed?

Bryan

> On Dec 7, 2015, at 6:44 AM, yhdanid via Bokeh Discussion - Public <bo...@continuum.io> wrote:
>
> BTW, the bundled bokeh-server script file, which resides in the Scripts directory,does not run on windows-- not unless some hack is made somewhere like running it under a bash shell.
>
> One solution is maybe provide a cmd/batch file that itself calls the script file and passes it all the options. Like so:
>
> REM Start of contents of bokeh-server.cmd
> @python F:\Python27\Scripts\bokeh-server %*
> REM End of contents of file
>
> Another approach is to create what is referred to as a console script, a solution many module developers seem to prefer, where the script is turned into an exe file by setuptools and deposited in the Script directory. This approach is done through defining appropriate settings in the script.py file with something like the following:
>
>
> py_modules=['bokeh'],
> entry_points={
> 'console_scripts': [
> 'bokeh-server = bokeh-server:main',
> ],
> },
>
>
> On Sunday, December 6, 2015 at 11:06:07 PM UTC, Bryan Van de ven wrote:
> FYI there are now some preliminary bokeh command docs up at:
>
> http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli
>
> These will be continually expanded and improve as we move towards the 0.11 release in early January.
>
> Bryan
>
>
> > On Dec 6, 2015, at 2:13 PM, Bryan Van de Ven <bry...@continuum.io> wrote:
> >
> > Hi,
> >
> > Bokeh had an older server "bokeh-server" which was Flask based. Unfortunately it did not scale well or meet the performance we wanted to achieve. There is a new "bokeh server" command that is currently in the master branch of the repository. The new server is based on Tornado and a pure websocket protocol. It is easier to deploy and use, but it is still under active development. In particular, we are still working on the documentaion for it (The 0.11 release will not happen until full documentation is in place). Additionally, the changes needed to support the new server and protocol were incompatible in fundamental ways with the old server, so it has been completely removed. If you need to use "bokeh-server" at present, I must advise staying on the last stable release, 0.10 for now.
> >
> > If you'd like to try the new server, we'd be happy to help, and I would direct you to any of the examples (except crossfilter, which is still being fixed up) at:
> >
> > https://github.com/bokeh/bokeh/tree/master/examples/app
> >
> > Thanks,
> >
> > Bryan
> >
> >> On Dec 6, 2015, at 1:45 PM, wu.tian...@gmail.com wrote:
> >>
> >> I have clone the source code from github and installed in the following way
> >>
> >> http://bokeh.pydata.org/en/latest/docs/quickstart.html#quick-installation
> >>
> >> version
> >>
> >> '0.11.0dev2-433-g96576eb'
> >>
> >> Everything works fine, except for bokeh server
> >>
> >> type in "bokeh server" in command line, get
> >>
> >> bokeh-server: command not found
> >>
> >> but "bokeh serve" does start the tornado server, which in documentation say Flask is used ?
> >>
> >>
> >> --
> >> 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/57fb89fe-045d-4575-b3e9-d7a436fc8703%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+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/0f46801c-8375-4bcf-9957-75de143d6489%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/bf855d50-88a3-4763-84dc-668028642ec0%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

On Thursday, December 17, 2015 at 8:22:26 AM UTC-8, Bryan Van de ven wrote:

I would advise anyone against using the “bokeh-server” in 0.10 at this point, I described things in more detail here:

    [https://groups.google.com/a/continuum.io/d/msg/bokeh/FhRk1O2ji6E/GVhzBEE7CAAJ](https://groups.google.com/a/continuum.io/d/msg/bokeh/FhRk1O2ji6E/GVhzBEE7CAAJ)

Bryan

On Dec 10, 2015, at 12:53 AM, yhdanid via Bokeh Discussion - Public bo...@continuum.io wrote:

If this is addressed to me, then my answer is I have bokeh-0.10.0 installed, which has a bokeh-server file (with no extension) copied to the Scripts directory. That file needs bash to work; and on Windows must be run within bash somehow, hence my resorting to creating a cmd/batch file to be invoked by the command “bokeh-server” and which calls the bokeh-server actual file and passes to it whatever options that were given to the cmd/batch file.

On Thursday, December 10, 2015 at 5:09:08 AM UTC, Bryan Van de ven wrote:

There should not be a “bokeh-server” if you are using a Bokeh 0.11 pre-release dev build. Either you have an old file laying around after update, or we have an issue in our windows packaging. The new command is simply “bokeh” with a “bokeh serve” subcommand. Can you confirm what version of bokeh you have installed?

Bryan

On Dec 7, 2015, at 6:44 AM, yhdanid via Bokeh Discussion - Public bo...@continuum.io wrote:

BTW, the bundled bokeh-server script file, which resides in the Scripts directory,does not run on windows-- not unless some hack is made somewhere like running it under a bash shell.

One solution is maybe provide a cmd/batch file that itself calls the script file and passes it all the options. Like so:

REM Start of contents of bokeh-server.cmd
@python F:\Python27\Scripts\bokeh-server %*
REM End of contents of file

Another approach is to create what is referred to as a console script, a solution many module developers seem to prefer, where the script is turned into an exe file by setuptools and deposited in the Script directory. This approach is done through defining appropriate settings in the script.py file with something like the following:

 py_modules=['bokeh'],
 entry_points={
    'console_scripts': [
        'bokeh-server = bokeh-server:main',
    ],

},

On Sunday, December 6, 2015 at 11:06:07 PM UTC, Bryan Van de ven wrote:
FYI there are now some preliminary bokeh command docs up at:

    [http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli](http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli)

These will be continually expanded and improve as we move towards the 0.11 release in early January.

Bryan

On Dec 6, 2015, at 2:13 PM, Bryan Van de Ven bry...@continuum.io wrote:

Hi,

Bokeh had an older server “bokeh-server” which was Flask based. Unfortunately it did not scale well or meet the performance we wanted to achieve. There is a new “bokeh server” command that is currently in the master branch of the repository. The new server is based on Tornado and a pure websocket protocol. It is easier to deploy and use, but it is still under active development. In particular, we are still working on the documentaion for it (The 0.11 release will not happen until full documentation is in place). Additionally, the changes needed to support the new server and protocol were incompatible in fundamental ways with the old server, so it has been completely removed. If you need to use “bokeh-server” at present, I must advise staying on the last stable release, 0.10 for now.

If you’d like to try the new server, we’d be happy to help, and I would direct you to any of the examples (except crossfilter, which is still being fixed up) at:

    [https://github.com/bokeh/bokeh/tree/master/examples/app](https://github.com/bokeh/bokeh/tree/master/examples/app)

Thanks,

Bryan

On Dec 6, 2015, at 1:45 PM, wu.tian...@gmail.com wrote:

I have clone the source code from github and installed in the following way

http://bokeh.pydata.org/en/latest/docs/quickstart.html#quick-installation

version

‘0.11.0dev2-433-g96576eb’

Everything works fine, except for bokeh server

type in “bokeh server” in command line, get

bokeh-server: command not found

but “bokeh serve” does start the tornado server, which in documentation say Flask is used ?

–
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/57fb89fe-045d-4575-b3e9-d7a436fc8703%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+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/0f46801c-8375-4bcf-9957-75de143d6489%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+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/bf855d50-88a3-4763-84dc-668028642ec0%40continuum.io.

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

On Wednesday, January 6, 2016 at 2:25:17 PM UTC-8, xsydne...@gmail.com wrote:

I am also having issues running the bokeh server on windows. Even in the 0.11 release, there is no executable bokeh command (or bokeh-server), though both files are present in my python27/scripts folder. I’m going to try wrapping each into a batch shell as previously suggested and see what happens… it would be nice if it worked right out of the box though!

On Thursday, December 17, 2015 at 8:22:26 AM UTC-8, Bryan Van de ven wrote:

I would advise anyone against using the “bokeh-server” in 0.10 at this point, I described things in more detail here:

    [https://groups.google.com/a/continuum.io/d/msg/bokeh/FhRk1O2ji6E/GVhzBEE7CAAJ](https://groups.google.com/a/continuum.io/d/msg/bokeh/FhRk1O2ji6E/GVhzBEE7CAAJ)

Bryan

On Dec 10, 2015, at 12:53 AM, yhdanid via Bokeh Discussion - Public bo...@continuum.io wrote:

If this is addressed to me, then my answer is I have bokeh-0.10.0 installed, which has a bokeh-server file (with no extension) copied to the Scripts directory. That file needs bash to work; and on Windows must be run within bash somehow, hence my resorting to creating a cmd/batch file to be invoked by the command “bokeh-server” and which calls the bokeh-server actual file and passes to it whatever options that were given to the cmd/batch file.

On Thursday, December 10, 2015 at 5:09:08 AM UTC, Bryan Van de ven wrote:

There should not be a “bokeh-server” if you are using a Bokeh 0.11 pre-release dev build. Either you have an old file laying around after update, or we have an issue in our windows packaging. The new command is simply “bokeh” with a “bokeh serve” subcommand. Can you confirm what version of bokeh you have installed?

Bryan

On Dec 7, 2015, at 6:44 AM, yhdanid via Bokeh Discussion - Public bo...@continuum.io wrote:

BTW, the bundled bokeh-server script file, which resides in the Scripts directory,does not run on windows-- not unless some hack is made somewhere like running it under a bash shell.

One solution is maybe provide a cmd/batch file that itself calls the script file and passes it all the options. Like so:

REM Start of contents of bokeh-server.cmd
@python F:\Python27\Scripts\bokeh-server %*
REM End of contents of file

Another approach is to create what is referred to as a console script, a solution many module developers seem to prefer, where the script is turned into an exe file by setuptools and deposited in the Script directory. This approach is done through defining appropriate settings in the script.py file with something like the following:

 py_modules=['bokeh'],
 entry_points={
    'console_scripts': [
        'bokeh-server = bokeh-server:main',
    ],

},

On Sunday, December 6, 2015 at 11:06:07 PM UTC, Bryan Van de ven wrote:
FYI there are now some preliminary bokeh command docs up at:

    [http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli](http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli)

These will be continually expanded and improve as we move towards the 0.11 release in early January.

Bryan

On Dec 6, 2015, at 2:13 PM, Bryan Van de Ven bry...@continuum.io wrote:

Hi,

Bokeh had an older server “bokeh-server” which was Flask based. Unfortunately it did not scale well or meet the performance we wanted to achieve. There is a new “bokeh server” command that is currently in the master branch of the repository. The new server is based on Tornado and a pure websocket protocol. It is easier to deploy and use, but it is still under active development. In particular, we are still working on the documentaion for it (The 0.11 release will not happen until full documentation is in place). Additionally, the changes needed to support the new server and protocol were incompatible in fundamental ways with the old server, so it has been completely removed. If you need to use “bokeh-server” at present, I must advise staying on the last stable release, 0.10 for now.

If you’d like to try the new server, we’d be happy to help, and I would direct you to any of the examples (except crossfilter, which is still being fixed up) at:

    [https://github.com/bokeh/bokeh/tree/master/examples/app](https://github.com/bokeh/bokeh/tree/master/examples/app)

Thanks,

Bryan

On Dec 6, 2015, at 1:45 PM, wu.tian...@gmail.com wrote:

I have clone the source code from github and installed in the following way

http://bokeh.pydata.org/en/latest/docs/quickstart.html#quick-installation

version

‘0.11.0dev2-433-g96576eb’

Everything works fine, except for bokeh server

type in “bokeh server” in command line, get

bokeh-server: command not found

but “bokeh serve” does start the tornado server, which in documentation say Flask is used ?

–
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/57fb89fe-045d-4575-b3e9-d7a436fc8703%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+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/0f46801c-8375-4bcf-9957-75de143d6489%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+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/bf855d50-88a3-4763-84dc-668028642ec0%40continuum.io.

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

On Wed, Jan 6, 2016 at 6:13 PM xsydneyclaire@gmail.com wrote:

Ah, if I run “python bokeh serve” from within my python scripts file, the server starts. Running “python bokeh-server” gives me an error that bokeh-server is no longer supported, though it was installed from pypi in the 0.11 package. Maybe it should be deleted from 0.11?

On Wednesday, January 6, 2016 at 2:25:17 PM UTC-8, xsydne...@gmail.com wrote:

I am also having issues running the bokeh server on windows. Even in the 0.11 release, there is no executable bokeh command (or bokeh-server), though both files are present in my python27/scripts folder. I’m going to try wrapping each into a batch shell as previously suggested and see what happens… it would be nice if it worked right out of the box though!

On Thursday, December 17, 2015 at 8:22:26 AM UTC-8, Bryan Van de ven wrote:

I would advise anyone against using the “bokeh-server” in 0.10 at this point, I described things in more detail here:

    [https://groups.google.com/a/continuum.io/d/msg/bokeh/FhRk1O2ji6E/GVhzBEE7CAAJ](https://groups.google.com/a/continuum.io/d/msg/bokeh/FhRk1O2ji6E/GVhzBEE7CAAJ)

Bryan

On Dec 10, 2015, at 12:53 AM, yhdanid via Bokeh Discussion - Public bo...@continuum.io wrote:

If this is addressed to me, then my answer is I have bokeh-0.10.0 installed, which has a bokeh-server file (with no extension) copied to the Scripts directory. That file needs bash to work; and on Windows must be run within bash somehow, hence my resorting to creating a cmd/batch file to be invoked by the command “bokeh-server” and which calls the bokeh-server actual file and passes to it whatever options that were given to the cmd/batch file.

On Thursday, December 10, 2015 at 5:09:08 AM UTC, Bryan Van de ven wrote:

There should not be a “bokeh-server” if you are using a Bokeh 0.11 pre-release dev build. Either you have an old file laying around after update, or we have an issue in our windows packaging. The new command is simply “bokeh” with a “bokeh serve” subcommand. Can you confirm what version of bokeh you have installed?

Bryan

On Dec 7, 2015, at 6:44 AM, yhdanid via Bokeh Discussion - Public bo...@continuum.io wrote:

BTW, the bundled bokeh-server script file, which resides in the Scripts directory,does not run on windows-- not unless some hack is made somewhere like running it under a bash shell.

One solution is maybe provide a cmd/batch file that itself calls the script file and passes it all the options. Like so:

REM Start of contents of bokeh-server.cmd
@python F:\Python27\Scripts\bokeh-server %*
REM End of contents of file

Another approach is to create what is referred to as a console script, a solution many module developers seem to prefer, where the script is turned into an exe file by setuptools and deposited in the Script directory. This approach is done through defining appropriate settings in the script.py file with something like the following:

 py_modules=['bokeh'],
 entry_points={
    'console_scripts': [
        'bokeh-server = bokeh-server:main',
    ],

},

On Sunday, December 6, 2015 at 11:06:07 PM UTC, Bryan Van de ven wrote:
FYI there are now some preliminary bokeh command docs up at:

    [http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli](http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli)

These will be continually expanded and improve as we move towards the 0.11 release in early January.

Bryan

On Dec 6, 2015, at 2:13 PM, Bryan Van de Ven bry...@continuum.io wrote:

Hi,

Bokeh had an older server “bokeh-server” which was Flask based. Unfortunately it did not scale well or meet the performance we wanted to achieve. There is a new “bokeh server” command that is currently in the master branch of the repository. The new server is based on Tornado and a pure websocket protocol. It is easier to deploy and use, but it is still under active development. In particular, we are still working on the documentaion for it (The 0.11 release will not happen until full documentation is in place). Additionally, the changes needed to support the new server and protocol were incompatible in fundamental ways with the old server, so it has been completely removed. If you need to use “bokeh-server” at present, I must advise staying on the last stable release, 0.10 for now.

If you’d like to try the new server, we’d be happy to help, and I would direct you to any of the examples (except crossfilter, which is still being fixed up) at:

    [https://github.com/bokeh/bokeh/tree/master/examples/app](https://github.com/bokeh/bokeh/tree/master/examples/app)

Thanks,

Bryan

On Dec 6, 2015, at 1:45 PM, wu.tian...@gmail.com wrote:

I have clone the source code from github and installed in the following way

http://bokeh.pydata.org/en/latest/docs/quickstart.html#quick-installation

version

‘0.11.0dev2-433-g96576eb’

Everything works fine, except for bokeh server

type in “bokeh server” in command line, get

bokeh-server: command not found

but “bokeh serve” does start the tornado server, which in documentation say Flask is used ?

–
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/57fb89fe-045d-4575-b3e9-d7a436fc8703%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+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/0f46801c-8375-4bcf-9957-75de143d6489%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+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/bf855d50-88a3-4763-84dc-668028642ec0%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/b8e3d3b4-8456-4b45-a63a-a97a24ed1332%40continuum.io.

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

On Jan 6, 2016, at 5:17 PM, James Santucci <james.santucci@gmail.com> wrote:

You're not supposed to use bokeh-server anymore, just bokeh serve. There was discussion a bit ago about adding a helpful warning because that was expected to be a common error, but maybe that didn't happen.

On Wed, Jan 6, 2016 at 6:13 PM <xsydneyclaire@gmail.com> wrote:
Ah, if I run "python bokeh serve" from within my python scripts file, the server starts. Running "python bokeh-server" gives me an error that bokeh-server is no longer supported, though it was installed from pypi in the 0.11 package. Maybe it should be deleted from 0.11?

On Wednesday, January 6, 2016 at 2:25:17 PM UTC-8, xsydne...@gmail.com wrote:
I am also having issues running the bokeh server on windows. Even in the 0.11 release, there is no executable bokeh command (or bokeh-server), though both files are present in my python27/scripts folder. I'm going to try wrapping each into a batch shell as previously suggested and see what happens... it would be nice if it worked right out of the box though!

On Thursday, December 17, 2015 at 8:22:26 AM UTC-8, Bryan Van de ven wrote:
I would advise anyone against using the "bokeh-server" in 0.10 at this point, I described things in more detail here:

        https://groups.google.com/a/continuum.io/d/msg/bokeh/FhRk1O2ji6E/GVhzBEE7CAAJ

Bryan
  
> On Dec 10, 2015, at 12:53 AM, yhdanid via Bokeh Discussion - Public <bo...@continuum.io> wrote:
>
> If this is addressed to me, then my answer is I have bokeh-0.10.0 installed, which has a bokeh-server file (with no extension) copied to the Scripts directory. That file needs bash to work; and on Windows must be run within bash somehow, hence my resorting to creating a cmd/batch file to be invoked by the command "bokeh-server" and which calls the bokeh-server actual file and passes to it whatever options that were given to the cmd/batch file.
>
>
> On Thursday, December 10, 2015 at 5:09:08 AM UTC, Bryan Van de ven wrote:
> There should not be a "bokeh-server" if you are using a Bokeh 0.11 pre-release dev build. Either you have an old file laying around after update, or we have an issue in our windows packaging. The new command is simply "bokeh" with a "bokeh serve" subcommand. Can you confirm what version of bokeh you have installed?
>
> Bryan
>
>
> > On Dec 7, 2015, at 6:44 AM, yhdanid via Bokeh Discussion - Public <bo...@continuum.io> wrote:
> >
> > BTW, the bundled bokeh-server script file, which resides in the Scripts directory,does not run on windows-- not unless some hack is made somewhere like running it under a bash shell.
> >
> > One solution is maybe provide a cmd/batch file that itself calls the script file and passes it all the options. Like so:
> >
> > REM Start of contents of bokeh-server.cmd
> > @python F:\Python27\Scripts\bokeh-server %*
> > REM End of contents of file
> >
> > Another approach is to create what is referred to as a console script, a solution many module developers seem to prefer, where the script is turned into an exe file by setuptools and deposited in the Script directory. This approach is done through defining appropriate settings in the script.py file with something like the following:
> >
> >
> > py_modules=['bokeh'],
> > entry_points={
> > 'console_scripts': [
> > 'bokeh-server = bokeh-server:main',
> > ],
> > },
> >
> >
> > On Sunday, December 6, 2015 at 11:06:07 PM UTC, Bryan Van de ven wrote:
> > FYI there are now some preliminary bokeh command docs up at:
> >
> > http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli
> >
> > These will be continually expanded and improve as we move towards the 0.11 release in early January.
> >
> > Bryan
> >
> >
> > > On Dec 6, 2015, at 2:13 PM, Bryan Van de Ven <bry...@continuum.io> wrote:
> > >
> > > Hi,
> > >
> > > Bokeh had an older server "bokeh-server" which was Flask based. Unfortunately it did not scale well or meet the performance we wanted to achieve. There is a new "bokeh server" command that is currently in the master branch of the repository. The new server is based on Tornado and a pure websocket protocol. It is easier to deploy and use, but it is still under active development. In particular, we are still working on the documentaion for it (The 0.11 release will not happen until full documentation is in place). Additionally, the changes needed to support the new server and protocol were incompatible in fundamental ways with the old server, so it has been completely removed. If you need to use "bokeh-server" at present, I must advise staying on the last stable release, 0.10 for now.
> > >
> > > If you'd like to try the new server, we'd be happy to help, and I would direct you to any of the examples (except crossfilter, which is still being fixed up) at:
> > >
> > > https://github.com/bokeh/bokeh/tree/master/examples/app
> > >
> > > Thanks,
> > >
> > > Bryan
> > >
> > >> On Dec 6, 2015, at 1:45 PM, wu.tian...@gmail.com wrote:
> > >>
> > >> I have clone the source code from github and installed in the following way
> > >>
> > >> http://bokeh.pydata.org/en/latest/docs/quickstart.html#quick-installation
> > >>
> > >> version
> > >>
> > >> '0.11.0dev2-433-g96576eb'
> > >>
> > >> Everything works fine, except for bokeh server
> > >>
> > >> type in "bokeh server" in command line, get
> > >>
> > >> bokeh-server: command not found
> > >>
> > >> but "bokeh serve" does start the tornado server, which in documentation say Flask is used ?
> > >>
> > >>
> > >> --
> > >> 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/57fb89fe-045d-4575-b3e9-d7a436fc8703%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+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/0f46801c-8375-4bcf-9957-75de143d6489%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+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/bf855d50-88a3-4763-84dc-668028642ec0%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/b8e3d3b4-8456-4b45-a63a-a97a24ed1332%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/CABCQrHZf_Eys5rxq7Y_8jQ64za1xSy5s%2B6MH5YYQ8AUcZceB6A%40mail.gmail.com\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

On Wednesday, January 6, 2016 at 4:02:00 PM UTC-8, Bryan Van de ven wrote:

To clarify, “bokeh-server” was the command for the old Flask based server that has been removed. We added a new “bokeh-server” script that prints this message:

    The 'bokeh-server' command from versions 0.10 and earlier no longer exists.

    Please see the documentation for the new 'bokeh' command here:



      [http://bokeh.pydata.org/en/latest/docs/user_guide/cli.html](http://bokeh.pydata.org/en/latest/docs/user_guide/cli.html)

But I see now that perhaps it should more more explicit and state that “bokeh serve” is the new way to do things.

Thanks,

Bryan

On Jan 6, 2016, at 5:17 PM, James Santucci james.s...@gmail.com wrote:

You’re not supposed to use bokeh-server anymore, just bokeh serve. There was discussion a bit ago about adding a helpful warning because that was expected to be a common error, but maybe that didn’t happen.

On Wed, Jan 6, 2016 at 6:13 PM xsydne...@gmail.com wrote:

Ah, if I run “python bokeh serve” from within my python scripts file, the server starts. Running “python bokeh-server” gives me an error that bokeh-server is no longer supported, though it was installed from pypi in the 0.11 package. Maybe it should be deleted from 0.11?

On Wednesday, January 6, 2016 at 2:25:17 PM UTC-8, xsydne...@gmail.com wrote:

I am also having issues running the bokeh server on windows. Even in the 0.11 release, there is no executable bokeh command (or bokeh-server), though both files are present in my python27/scripts folder. I’m going to try wrapping each into a batch shell as previously suggested and see what happens… it would be nice if it worked right out of the box though!

On Thursday, December 17, 2015 at 8:22:26 AM UTC-8, Bryan Van de ven wrote:

I would advise anyone against using the “bokeh-server” in 0.10 at this point, I described things in more detail here:

    [https://groups.google.com/a/continuum.io/d/msg/bokeh/FhRk1O2ji6E/GVhzBEE7CAAJ](https://groups.google.com/a/continuum.io/d/msg/bokeh/FhRk1O2ji6E/GVhzBEE7CAAJ)

Bryan

On Dec 10, 2015, at 12:53 AM, yhdanid via Bokeh Discussion - Public bo...@continuum.io wrote:

If this is addressed to me, then my answer is I have bokeh-0.10.0 installed, which has a bokeh-server file (with no extension) copied to the Scripts directory. That file needs bash to work; and on Windows must be run within bash somehow, hence my resorting to creating a cmd/batch file to be invoked by the command “bokeh-server” and which calls the bokeh-server actual file and passes to it whatever options that were given to the cmd/batch file.

On Thursday, December 10, 2015 at 5:09:08 AM UTC, Bryan Van de ven wrote:
There should not be a “bokeh-server” if you are using a Bokeh 0.11 pre-release dev build. Either you have an old file laying around after update, or we have an issue in our windows packaging. The new command is simply “bokeh” with a “bokeh serve” subcommand. Can you confirm what version of bokeh you have installed?

Bryan

On Dec 7, 2015, at 6:44 AM, yhdanid via Bokeh Discussion - Public bo...@continuum.io wrote:

BTW, the bundled bokeh-server script file, which resides in the Scripts directory,does not run on windows-- not unless some hack is made somewhere like running it under a bash shell.

One solution is maybe provide a cmd/batch file that itself calls the script file and passes it all the options. Like so:

REM Start of contents of bokeh-server.cmd
@python F:\Python27\Scripts\bokeh-server %*
REM End of contents of file

Another approach is to create what is referred to as a console script, a solution many module developers seem to prefer, where the script is turned into an exe file by setuptools and deposited in the Script directory. This approach is done through defining appropriate settings in the script.py file with something like the following:

 py_modules=['bokeh'],
 entry_points={
    'console_scripts': [
        'bokeh-server = bokeh-server:main',
    ],

},

On Sunday, December 6, 2015 at 11:06:07 PM UTC, Bryan Van de ven wrote:
FYI there are now some preliminary bokeh command docs up at:

    [http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli](http://bokeh.pydata.org/en/server_branch/docs/user_guide/cli.html#userguide-cli)

These will be continually expanded and improve as we move towards the 0.11 release in early January.

Bryan

On Dec 6, 2015, at 2:13 PM, Bryan Van de Ven bry...@continuum.io wrote:

Hi,

Bokeh had an older server “bokeh-server” which was Flask based. Unfortunately it did not scale well or meet the performance we wanted to achieve. There is a new “bokeh server” command that is currently in the master branch of the repository. The new server is based on Tornado and a pure websocket protocol. It is easier to deploy and use, but it is still under active development. In particular, we are still working on the documentaion for it (The 0.11 release will not happen until full documentation is in place). Additionally, the changes needed to support the new server and protocol were incompatible in fundamental ways with the old server, so it has been completely removed. If you need to use “bokeh-server” at present, I must advise staying on the last stable release, 0.10 for now.

If you’d like to try the new server, we’d be happy to help, and I would direct you to any of the examples (except crossfilter, which is still being fixed up) at:

    [https://github.com/bokeh/bokeh/tree/master/examples/app](https://github.com/bokeh/bokeh/tree/master/examples/app)

Thanks,

Bryan

On Dec 6, 2015, at 1:45 PM, wu.tian...@gmail.com wrote:

I have clone the source code from github and installed in the following way

http://bokeh.pydata.org/en/latest/docs/quickstart.html#quick-installation

version

‘0.11.0dev2-433-g96576eb’

Everything works fine, except for bokeh server

type in “bokeh server” in command line, get

bokeh-server: command not found

but “bokeh serve” does start the tornado server, which in documentation say Flask is used ?

–
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/57fb89fe-045d-4575-b3e9-d7a436fc8703%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+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/0f46801c-8375-4bcf-9957-75de143d6489%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+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/bf855d50-88a3-4763-84dc-668028642ec0%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+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/b8e3d3b4-8456-4b45-a63a-a97a24ed1332%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+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/CABCQrHZf_Eys5rxq7Y_8jQ64za1xSy5s%2B6MH5YYQ8AUcZceB6A%40mail.gmail.com.

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