Open zlatko-minev opened 4 years ago
Here is a summary of the things I tried to make pyEPR work on Linux
Thank you @nmaterise,
I am going through the same issue.
In the code base there is a comment at pyEPR/ansys.py
try:
# TODO: Replace `win32com` with Linux compatible package.
# See Ansys python files in IronPython internal.
from win32com.client import Dispatch, CDispatch
except (ImportError, ModuleNotFoundError):
pass #raise NameError ("win32com module not installed. Please install.")
Are there any updates on this ?
cc/ @zlatko-minev @DanielCohenHillel
Would it not be possible to interface to Ansys EDT using PyAEDT?
https://github.com/ansys/pyaedt
I know that most of the rest of the qiskit metal code base has moved away from using win32 COM calls to using the official ansys interfacing API via PyAEDT. In fact, I think the only dependence left in qiskit metal that prevents it from running on linux is PyEPR?
That’s right That would be great indeed Any chance anyone here wants to help set this up with some guidance and input from me?Sent from my iPhoneOn Nov 6, 2024, at 12:56 PM, Gary Steele @.***> wrote: Would it not be possible to interface to Ansys EDT using PyAEDT? https://github.com/ansys/pyaedt I know that most of the rest of the qiskit metal code base has moved away from using win32 COM calls to using the official ansys interfacing API via PyAEDT. In fact, I think the only dependence left in qiskit metal that prevents it from running on linux is PyEPR?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Nick Materise will add notes here on what he has tried.