pip installed version

[cornhundred]

Hi @thomasballinger, thanks for releasing this repo. I'm glad to see this very useful project on Github :D Will this repo be used to publish the pip installable version of observable_jupyter ?

[thomasballinger]

Hi @cornhundred! Yep, version 0.1.10 currently on pypi was published from this repo, and the plan going forward is for this repo to be where the library is published from.

There's a lot I'd like to add, but as a baseline I'd hope to regularly on runtime library updates, since this library packages @observablehq/runtime which is updated frequently. I'm not living up to that yet, I can get another one of these in later today. Otherwise I'd love to hear if there's something you'd like to see!

[thomasballinger]

It would be clearer that this is the official repo now if it didn't look like a fork, @cornhundred was that part of what made this confusing? Maybe we should ask GitHub support (reportedly a pretty painless process) to unlink this so it doesn't appear to be a fork, and instead link manually to the archived version from the readme.

[cornhundred]

Thanks @thomasballinger, that sounds great. The feature that would be great for us is some way to send additional data to the front-end - but it sounds like we'll have to build a widget for that. When we do build a widget, I'm going to miss being able to develop the front-end in Observable - unless there's some way to use observable_jupyter within a larger widget.

Should we be worried about backward compatibility with changes to the Observable runtime?

[cornhundred]

yeah, @thomasballinger the fork was what made it unclear for me.

[thomasballinger]

re: backward compatibility, nope, Mike et al. are very good about ensuring backcompat. If there were an issue, you'd see it on observablehq.com as well. If you don't want the new version you can request that specific version of observable_jupyter in your Python project.