Possible Easy Fix for Int / Enum Problem Mentioned in Readme about zospy

[LucVV]

Hi @julian-irwin-tfs,

Thank you for this report. Am I correct in assuming you are using Python.NET 3.0?
I ran into the same problem when updating to pythonnet 3.0. I started recoding several parts of the package but ran into similar problems with other calls to the API that were not fixable on the ZosPy side. Furthermore, the Zemax Staff recommended not using pythonnet 3.0.

Since I ran into things I could not fix, I decided to wait until further updates from Zemax OpticStudio or Python.Net before changing the code and rather made Python.Net 2.5.2 required.

Could you let me know which Python.Net version you are on?

[julian-irwin-tfs]

I am indeed using pythonnet 3.0.1.

I will work harder to get an older version of pythonnet up and running. Thanks so much for letting me know that Zemax Staff believe 3.0 is not supported.

Also, thanks for the very nice python wrapper of ZOS API. It is a rather confusing API and I can tell that ZOSpy is going to get me up and running very quickly!

[julian-irwin-tfs]

There is only pythonnet==2.5.2 support up through Python 3.8. I had only tried down to 3.9 when I submitted these issues. Everything seems to be working now. Sorry to bother you even though you had this exact advice posted on the front page!

[LucVV]

No worries! I hope the use of 3.8 does not hamper you too much! I'll update the readme to state this requirement more specifically for now

[crnh]

The Int to Enum conversion issue is already fixed in most of the code base, and will be fully fixed in an upcoming version of ZOSPy.

We updated the documentation to point to a more relevant problem caused by Python.NET 3.x (which we also hope to fix soon).