Closed chrisg564 closed 1 month ago
Hmm that might be because you are using conda I guess... Using pip directly installation works fine, you can check this in the wheelhouses we build. So it is installable in Linux as well - see for example https://github.com/ansys/pyansys/actions/runs/9874700254/job/27269666702
Nonetheless I agree this problem has to be solved - however I think it is a PyWorkbench issue. Transferring it to them.
See https://github.com/ansys/pyansys/actions/runs/9874700254/job/27269665551#step:4:519 specifically where this wmi
package gets installed in Python 3.9
I guess this may lie in the way poetry resolves package dependencies. My build action doesn't even try to download wmi
, it tries to get pywin32
before and fails to find any versions that work for my environment.
The fix is part of release 0.5.0.
🔍 Before submitting the issue
🐞 Description of the bug
This might be a user error on my end, but I am trying to update from pyansys
2024.1.7
to2024.2.0
for Ansys Notebook. We are using poetry to manage our packages, but2024.2.0
fails because I thinkpyworkbench
relys onwmi
which requirespywin32
. I don't think this will work on linux, which is what our notebook image is based on using python3.9.12
.Most packages that have pywin32 as a requirement with the sys_platform being windows like this:
However, wmi adds the dependency like this:
If this is just an issue on my end, please just close the issue.
📝 Steps to reproduce
💻 Which operating system are you using?
Linux
📀 Which ANSYS version are you using?
No response
🐍 Which Python version are you using?
3.9
📦 Installed packages