Bokeh Guide and cross reference beteen v0.10 and v0.11

Hi,

I would suggest to implement a better way of addressing from bokeh 0.10 man pages to bokehn 0.11 . Tell the user that the address is just ‘lastest’ and let he look for a specific argument is not a good way to help. I make an example.

where is bokeh 0.10 bokeh.session in bokeh 0.11 ? It would be helpfull a link to the specific argument, if exists.

Bokeh is a great tool, but i’m realy struggling to find out infos, many times i need to read the code and even if this would increase my general knowledge of bokeh and python it’s realy time consuming, sometimes too much.

Hi,

Bokeh 0.11 was a major upgrade from version 0.10 and had more than the usual number changes. In particular, bokeh.session no longer exists in >0.11, because it relates to the old bokeh-server that is now gone. We realize such changes can be disruptive, and seek to minimize them, but sometimes they are unavoidable in young projects that are still advancing. The new server that replaced the old bokeh-server is better in every conceivable way: performance, stability, scalability, and ease of use. The sheer number of people using it and the amazing things that have already been created in a few short months are a testatment to how much more usable the new server is. Moving forward on such dramatic improvements was the only option, even if it meant some incompatibilities at this stage. However, to help out, we always publish release notes. And in particular, the notes for 0.11 have an extensive migration guide:

  http://bokeh.pydata.org/en/latest/docs/releases/0.11.0.html

We make an effort to publicize such notes here on the mailing list and on blog posts and twitter and other channels. Perhaps we can still do better though, if you have some specific suggestion, please let us know.

Thanks,

Bryan

···

On Jun 25, 2016, at 2:36 AM, Arjuna Scagnetto <[email protected]> wrote:

Hi,

I would suggest to implement a better way of addressing from bokeh 0.10 man pages to bokehn 0.11 . Tell the user that the address is just 'lastest' and let he look for a specific argument is not a good way to help. I make an example.

where is bokeh 0.10 bokeh.session in bokeh 0.11 ? It would be helpfull a link to the specific argument, if exists.

Bokeh is a great tool, but i'm realy struggling to find out infos, many times i need to read the code and even if this would increase my general knowledge of bokeh and python it's realy time consuming, sometimes too much.

--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/8ff2cad3-f649-4680-90a4-154fc840ee44%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.

I think the simple thing would be to go to the previous versions of the docs for parts that have changed significantly, and point to the new docs. I can imagine that there will be a LOT of lingering code snippets, Stackoverflow answers, etc. that have outdated code in them. When people search for those things in the docs, it would be extremely helpful if they were pointed to the new stuff right there. (Perhaps to the migration guide, or something.)

···

On Sat, Jun 25, 2016 at 2:49 AM, Bryan Van de Ven [email protected] wrote:

Hi,

Bokeh 0.11 was a major upgrade from version 0.10 and had more than the usual number changes. In particular, bokeh.session no longer exists in >0.11, because it relates to the old bokeh-server that is now gone. We realize such changes can be disruptive, and seek to minimize them, but sometimes they are unavoidable in young projects that are still advancing. The new server that replaced the old bokeh-server is better in every conceivable way: performance, stability, scalability, and ease of use. The sheer number of people using it and the amazing things that have already been created in a few short months are a testatment to how much more usable the new server is. Moving forward on such dramatic improvements was the only option, even if it meant some incompatibilities at this stage. However, to help out, we always publish release notes. And in particular, the notes for 0.11 have an extensive migration guide:

    [http://bokeh.pydata.org/en/latest/docs/releases/0.11.0.html](http://bokeh.pydata.org/en/latest/docs/releases/0.11.0.html)

We make an effort to publicize such notes here on the mailing list and on blog posts and twitter and other channels. Perhaps we can still do better though, if you have some specific suggestion, please let us know.

Thanks,

Bryan

On Jun 25, 2016, at 2:36 AM, Arjuna Scagnetto [email protected] wrote:

Hi,

I would suggest to implement a better way of addressing from bokeh 0.10 man pages to bokehn 0.11 . Tell the user that the address is just ‘lastest’ and let he look for a specific argument is not a good way to help. I make an example.

where is bokeh 0.10 bokeh.session in bokeh 0.11 ? It would be helpfull a link to the specific argument, if exists.

Bokeh is a great tool, but i’m realy struggling to find out infos, many times i need to read the code and even if this would increase my general knowledge of bokeh and python it’s realy time consuming, sometimes too much.

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 [email protected].

To post to this group, send email to [email protected].

To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/8ff2cad3-f649-4680-90a4-154fc840ee44%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 [email protected].

To post to this group, send email to [email protected].

To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/361B8207-E618-447E-96D2-12F4293C084E%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.

Peter Wang

CTO, Co-founder