Skip to content

Update Requirements #5

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

Open
sandorstormen opened this issue Apr 3, 2025 · 8 comments · May be fixed by #6
Open

Update Requirements #5

sandorstormen opened this issue Apr 3, 2025 · 8 comments · May be fixed by #6
Labels
bug Something isn't working

Comments

@sandorstormen
Copy link

sandorstormen commented Apr 3, 2025

Right now the mal-gui points to a version of PySide6 which I cannot get. Can we update requirements for this package?

Logs from pip
~ pipenv run pip install "PySide6==6.9.0"

Courtesy Notice:
Pipenv found itself running within a virtual environment,  so it will automatically use that environment, instead of  creating its own for any project. You can set
PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create  its own instead.
You can set PIPENV_VERBOSITY=-1 to suppress this warning.
Requirement already satisfied: PySide6==6.9.0 in ./.venv/lib/python3.13/site-packages (6.9.0)
Requirement already satisfied: shiboken6==6.9.0 in ./.venv/lib/python3.13/site-packages (from PySide6==6.9.0) (6.9.0)
Requirement already satisfied: PySide6-Essentials==6.9.0 in ./.venv/lib/python3.13/site-packages (from PySide6==6.9.0) (6.9.0)
Requirement already satisfied: PySide6-Addons==6.9.0 in ./.venv/lib/python3.13/site-packages (from PySide6==6.9.0) (6.9.0)

~ pipenv run pip install "mal-gui"       

Courtesy Notice:
Pipenv found itself running within a virtual environment,  so it will automatically use that environment, instead of  creating its own for any project. You can set
PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create  its own instead.
You can set PIPENV_VERBOSITY=-1 to suppress this warning.
Collecting mal-gui
  Using cached mal_gui-0.0.7-py3-none-any.whl.metadata (1.7 kB)
Collecting networkx==3.2.1 (from mal-gui)
  Using cached networkx-3.2.1-py3-none-any.whl.metadata (5.2 kB)
Collecting numpy==1.26.4 (from mal-gui)
  Using cached numpy-1.26.4.tar.gz (15.8 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
INFO: pip is looking at multiple versions of mal-gui to determine which version is compatible with other requirements. This could take a while.
Collecting mal-gui
  Using cached mal_gui-0.0.6-py3-none-any.whl.metadata (1.2 kB)
  Using cached mal_gui-0.0.5-py3-none-any.whl.metadata (1.2 kB)
  Using cached mal_gui-0.0.4-py3-none-any.whl.metadata (1.2 kB)
  Using cached mal_gui-0.0.3-py3-none-any.whl.metadata (1.2 kB)
  Using cached mal_gui-0.0.2-py3-none-any.whl.metadata (1.2 kB)
  Using cached mal_gui-0.0.1-py3-none-any.whl.metadata (1.2 kB)
ERROR: Cannot install mal-gui==0.0.1, mal-gui==0.0.2, mal-gui==0.0.3, mal-gui==0.0.4, mal-gui==0.0.5, mal-gui==0.0.6 and mal-gui==0.0.7 because these package versions have conflicting dependencies.

The conflict is caused by:
    mal-gui 0.0.7 depends on PySide6==6.7.0
    mal-gui 0.0.6 depends on PySide6==6.7.0
    mal-gui 0.0.5 depends on PySide6==6.7.0
    mal-gui 0.0.4 depends on PySide6==6.7.0
    mal-gui 0.0.3 depends on PySide6==6.7.0
    mal-gui 0.0.2 depends on PySide6==6.7.0
    mal-gui 0.0.1 depends on PySide6==6.7.0

To fix this you could try to:
1. loosen the range of package versions youve specified
2. remove package versions to allow pip to attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
~ pipenv run pip install "PySide6==6.7.0"

Courtesy Notice:
Pipenv found itself running within a virtual environment,  so it will automatically use that environment, instead of  creating its own for any project. You can set
PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create  its own instead.
You can set PIPENV_VERBOSITY=-1 to suppress this warning.
ERROR: Could not find a version that satisfies the requirement PySide6==6.7.0 (from versions: 6.8.0.2, 6.8.1, 6.8.1.1, 6.8.2, 6.8.2.1, 6.8.3, 6.9.0)
ERROR: No matching distribution found for PySide6==6.7.0

```

</details>
@andrewbwm
Copy link
Collaborator

I received an e-mail from some researchers also running into similar issues, but I do think they were able to eventually just install that version. And they had a similar request for a newer version of it to be supported.

They also mentioned that python3.12 should be included as a requirement.

@sandorstormen
Copy link
Author

They also mentioned that python3.12 should be included as a requirement.

I'm running Python 3.13 so outdated python is not the problem for me at least.

@mrkickling
Copy link
Contributor

Interesting. I can install pyside on both 3.10 and 3.12.

@sandorstormen
Copy link
Author

I can install PySide6 itself, but not the specific version pinned for the latest mal-gui.

@mrkickling
Copy link
Contributor

Yes, I meant that it worked for me on 6.7.0.

@sandorstormen
Copy link
Author

Okay, that did it. May be we can change this line to exclude python 3.13. I don't know how other packages infer python version restrictions like this?

@mrkickling
Copy link
Contributor

So you were able to install it with python 3.12 but not 3.13? Yes, then we should make sure the requirements match that.
Other option would be to see if newer version of pysides library supports 3.13 and if it breaks anything. I will try to sort it out.

@mrkickling
Copy link
Contributor

mrkickling commented Apr 7, 2025

https://forum.qt.io/topic/159278/cannot-install-pyside6-on-python-3-13-0

Looks like 6.8.1 should support it. Created a branch now that seems to work without any issues on 3.13. Please try it out.

@mrkickling mrkickling linked a pull request Apr 7, 2025 that will close this issue
@sandorstormen sandorstormen added the bug Something isn't working label Apr 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants