pip install . as an option for source/developer builds? #11676
Replies: 2 comments
-
There are a few options:
|
Beta Was this translation helpful? Give feedback.
-
All of that said, I do want to make sure we are not encouraging downstream packagers to build and distribute their own versions of BokehJS, which may differ slightly from the CDN versions, if they use different tools. That seem like a very bad place to be in. Re-packagers (conda-forge, Anaconda, linux distros?) should package from the sdist, which has the BokehJS that we built bundled inside. So we might want to include a section for external package maintainers as well. |
Beta Was this translation helpful? Give feedback.
-
As discussed with @ianthomas23 and @bryevdv in #11662 (comment) and #11662 (comment), we might want to consider using
pip install .
as an alternative topython setup.py install
.Pro: future-proof and in line with https://www.python.org/dev/peps/pep-0518
Con: Because of the more complex toolchain for building BokehJS, additional steps are required (i.e. have the required TS-related tools set up correctly)
@bryevdv suggests the following:
This sounds like a good plan to me. I'd be happy to help updating the docs to reflect whatever we decide to do!
Beta Was this translation helpful? Give feedback.
All reactions