Question: Target editable install
See original GitHub issueHi @ofek, thanks for this library!
Based on your comment in setuptools
about External Data, I am exploring using hatch
as a wholesale replacement for jupyter_packaging
.
One thing I am stuck on is how to run a specific build script during the editable wheel build phase.
I am happy to provide an example for the documentation if you give me the right spelling. 😄
Issue Analytics
- State:
- Created a year ago
- Comments:16 (10 by maintainers)
Top Results From Across the Web
Why can't I call pip with --target and --editable? - Stack Overflow
pip install --target deploy_directory --editable . I get something like: Complete output from command /my/venv/bin/python -c "import ...
Read more >pip install --editable does not support --target #3246 - GitHub
For a plugin system I'm attempting to pip install --editable into a local path of my choice. For regular plugins I am installing...
Read more >Specification of editable installation - Discussions on Python.org
Editable install (before 19.1, at least) works by invoking setup.py develop . Here is how (Setuptools) make it work, as I understand it ......
Read more >Development Mode (a.k.a. “Editable Installs”) - Setuptools
An “editable installation” works very similarly to a regular install with pip install . , except that it only installs your package dependencies,...
Read more >Use Conditional Logic to Streamline Form Submissions
A target field can also be a source field, and this allows you to create nested logic. For example, the answer to Question...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
So far so good! https://github.com/ipython/ipykernel/pull/931
I like that idea! We can have a
jupyter
one for general use across our projects, and ajupyterlab
one that specifically handlesjupyterlab
extensions, which have a more complicated behavior and set of dependencies.