Hi Hans,

I kinda want to know as well now.

I’ve read about the match case statement in Python 3.10. What else are you interested in this combo?

Take care,

David

Hi David,

Yes, match-case statement is very interesting.

But as someone who’s switching from 30 years with Matlab to Python, better error syntax and typing syntax is much appreciated. After all, 3.8 was released 3 years ago :)

/Hans

Hi Hans,

It makes sense.

Kudos to you for switching programming langage after 30 years. It speaks about your open-mindeness.

Good luck on your Python journey,

David

Hi David and Hans

I checked with our developers. The ZOS-API is a .NET 4.8-based library.
So if Python.net 3.0 supports .NET 4.8, then it should work without any issues. And Python.NET is compatible and tested with Python releases 3.7 - 3.10.

But we haven’t done any specific tests.

Thanks Sandrine and David,

Seems like it’s best to wait a bit and let things converge first.

Cheers, Hans

Hi David! Thank you for pointing this. I had missed it.

All I can see that it says Python.NET gives “a nearly seamless integration with the .NET 4.0+ Common Language Runtime (CLR)”.

I’d like to add that @Asuku also had an issue with the most recent Pythonnet version in this thread with the FFT MTF diffraction data. Since this is the third user I see that had this problem, I think it would be good to have a note on the community somewhere visible to warn people against using Pythonnet 3.0 for now. What do you think @Allie and @Sandrine Auriol ?

Take care,

David

Hi @David.Nguyen ! Yes fully agree. I have done one below. I also had issues when testing last week with Pythonnet 3.0. 
Thank you all on this forum thread for starting this conversation.
 

• Python 3.10 not recommended to use for ZOSAPI-Python Interactive or Standalone application

One more thread with an issue using Pythonnet 3.0: 

• Specifying a UDA file to a Surface Aperture as an Aperture file using Python

Take care,

David