Closed SchrodingersStruggle closed 2 months ago
Thanks! That is a solution, however it installs the whole environment twice which makes the container bigger and it takes longer to set up. I merge this now since it works but I will keep the issues open till there is a solution that figures out how to determine how to keep the python3 command consistent.
@laserlab So based on this, we can now use the 3.12.6 kernel without running into error on our codespace? Once it is synced with the change, that is.
@ojha-aditya Yes, a codespace should be able to run python 3.12.6 without issue now.
Great! Will give that a try then.
These edits allow codespaces on vscode to run on startup with no need for manual installations by specifying the locations of the initial setup in the devcontainer.json.
They also allow the codespace to use other interpreters than the python 3.9 interpreter which worked. This includes the python 3.12 interpreters.
I created a few entirely fresh codespaces to test, and with these two changes these has been absolutely no issues on startup, and it can create a Jupyter file, import qiskit, and run code with no issues.