Skip to content

Fix: force Python 3.10 in environment.yml to avoid PySide2 incompatibility #1023

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+10 −7
Open

Fix: force Python 3.10 in environment.yml to avoid PySide2 incompatibility #1023

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion README_developers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,13 @@ Once you are in the folder that contains the `environemnt.yml` file, execute the
```sh
conda env create -n <env_name> environment.yml
conda activate <env_name>
pip install pyside2==5.15.2.1
pip install gmsh==4.11.1
pip install pyepr-quantum==0.8.5.7
pip install pyaedt==0.6.46
python -m pip install --no-deps -e .
```
Note the use of `--no-deps`. Indeed the `environment.yml` already instructs conda to install all the necessary package dependencies. We therefore prevent `setup.py` from overwriting them with the pip-equivalent packages, which might not be compatible with conda.
Note the use of `--no-deps` in the final step. Indeed the `environment.yml` already instructs conda to install most necessary package dependencies. However, some packages (pyside2, gmsh, pyepr-quantum, and pyaedt) need to be installed manually via pip after the conda environment setup to avoid version conflicts. We therefore prevent `setup.py` from overwriting them with potentially incompatible packages.

This creates a new environment with name `<env_name>` with all the necessary library dependencies.
Then it activates the new environment.
Expand All @@ -54,6 +58,10 @@ If convenient, you can instead try to install directly in an existing conda envi
```
conda env update -n <env_name_exist> environment.yml
conda activate <env_name_exist>
pip install pyside2==5.15.2.1
pip install gmsh==4.11.1
pip install pyepr-quantum==0.8.5.7
pip install pyaedt==0.6.46
python -m pip install --no-deps -e .
```

Expand Down
7 changes: 1 addition & 6 deletions environment.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ name: qiskit-metal
channels:
- conda-forge
dependencies:
- python>=3.9
- python=3.10
- addict==2.4.0
- descartes==1.1.0
- gdspy==1.6.12
Expand All @@ -12,9 +12,7 @@ dependencies:
- numpy==1.24.2
- pandas==1.5.3
- pint==0.20.1
- pyepr-quantum==0.8.5.7
- pygments==2.14.0
- pyside2==5.15.8
- qdarkstyle==3.1
- qutip==4.7.1
- scipy==1.10.0
Expand All @@ -24,6 +22,3 @@ dependencies:
- pyyaml==6.0
- pip==23.0
- cython<3.0.0
- pip:
- pyaedt==0.6.46
- gmsh==4.11.1