Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with editable installs and setuptools >=64 #461

Open
wch opened this issue Apr 24, 2023 · 0 comments
Open

Problems with editable installs and setuptools >=64 #461

wch opened this issue Apr 24, 2023 · 0 comments

Comments

@wch
Copy link
Collaborator

wch commented Apr 24, 2023

With Python 3.11.3, I installed Shiny in a venv for another project, with pip install -e ../py-shiny, but when I did this, the new project couldn't find the py.typed file.

I'm not 100% sure, but I believe that this is because setuptools >=64 uses a new mechanism instead of egg-link.
See:

Apparently one can also install with strict mode (https://setuptools.pypa.io/en/latest/userguide/development_mode.html#strict-editable-installs):

pip install -e ../py-shiny --config-settings editable_mode=strict

I tried this with py-shiny, and it resulted in the JS and CSS web assets not being available when running an app. So we'll probably want to fix it in that case.

What does work for now is to use compat mode:

pip install -e ../py-shiny --config-settings editable_mode=compat
@wch wch changed the title Problems with editable installs Problems with editable installs and setuptools >=64 Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant