Bug located in launch_mapdl.py #4162
Description
🤓 Before submitting the issue
- I have visited the Troubleshooting section.
- I have searched among the existing issues.
- I am using a Python virtual environment.
- I am using the latest version of PyMAPDL and its dependencies (fully updated virtual environment). You can update them using
pip install --upgrade --upgrade-strategy eager ansys-mapdl-corein your activated virtual environment.
🔍 Description of the bug
when calling launch_mapdl with exec_file, it checks whether the exec_file version is registred from the version number found in its path, which is an issue because exec_file would be used to call an exec file of an Ansys prelease such as currently 261. Can we suggest not checking the version when using an exec_file ?
🕵️ Steps To Reproduce
launch_mapdl(exec_file=/ansys_inc/v261/ansys/bin/ansys261)💻 Which Operating System are you using?
Linux
🐍 Which Python version are you using?
3.10
💾 Which MAPDL version are you using?
26.1
📝 PyMAPDL Report
Show the Report!
# PASTE HERE THE OUTPUT OF `python -c "from ansys.mapdl import core as pymapdl; print(pymapdl.Report())"` here
📝 Installed packages
Show the installed packages!
# PASTE HERE THE OUTPUT OF `python -m pip freeze` here
📝 Logger output file
Show the logger output file.
# PASTE HERE THE CONTENT OF THE LOGGER OUTPUT FILE.