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

Multiple python interpreters in dev container cause issues #1033

Open
Donaim opened this issue Nov 9, 2023 · 4 comments
Open

Multiple python interpreters in dev container cause issues #1033

Donaim opened this issue Nov 9, 2023 · 4 comments
Assignees
Labels
bug config change Requires a configuration change during release.
Milestone

Comments

@Donaim
Copy link
Member

Donaim commented Nov 9, 2023

Our docker image is based on python:3.8, which includes two versions of python.
One comes from the underlying distribution, and another one from the image maintainers.

As a result, when python packages are install during docker build, they are not immediately visible to vscode.

@Donaim Donaim added bug config change Requires a configuration change during release. labels Nov 9, 2023
@Donaim Donaim self-assigned this Nov 9, 2023
@Donaim
Copy link
Member Author

Donaim commented Nov 9, 2023

Simply removing the "incorrect" python binary fixes the problem.

@Donaim
Copy link
Member Author

Donaim commented Nov 11, 2023

Removing the whole incorrect python3.9 package does not work because apt remove fails with a dependency related error.

@Donaim
Copy link
Member Author

Donaim commented Nov 15, 2023

We hope that the cleaner solution will be available after we switch to a more recent python version, like python 3.12.

However, an outstanding issue with minimap is currently preventing us from upgrading.

@Donaim
Copy link
Member Author

Donaim commented Nov 15, 2023

Another alternative is to configure virtualenv for MiCall as it seems that editors default to the python version set in the .venv/pyvenv.cfg.

This requires more investigation.

@Donaim Donaim added this to the 7.18 milestone May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug config change Requires a configuration change during release.
Projects
None yet
Development

No branches or pull requests

1 participant