Allowing Python.Net to run with latest Python version
Hello, I work on a commercial Python package which I am currently enhancing to use Python.Net in order to access some .Net libraries. Before using Python.Net we specified to end users that the requirement for running our package was "Python 3 installed". Now that we are using Python.Net we can't say that statement because Python.Net 2.5.1 supports Python 3.8 but not Python 3.9. Since our package is not a stand-alone application, but it instead provides a Python API for users Python scripts to call, it's not an option for us to convert the whole delivery into an exe using something like PyInstaller. So I'm looking for advice about the best option: 1. Specify that end users install a specific version of Python (3.8) in order to use our application. 2. Include Python 3.8 in our installer and install this if it's not already installed. Is this a good idea? 3. Any other ideas? Many thanks, DareDevilDenis
Hi, Python 3.9 support has been merged upstream on master as well as the 2.5 branch (https://github.com/pythonnet/pythonnet/tree/backports-2.5). I'll try to make a new maintenance release (2.5.2) with Python 3.9 support this weekend. Benedikt
Thanks Benedikt, that's good to hear that Python 3.9 is coming very soon :) My concern was that there will always be a period of time where a new Python version is released, but Python.Net has not yet been updated to support it, so on a fresh PC my customer might install the latest version of Python3 without thinking about the version, and then get frustrated when my application doesn't run. I appreciate that this is not a Python.Net issue, but would love to hear if you have any thoughts on my options 1,2 in my original post. Regards, DareDevilDenis
participants (3)
-
Benedikt Reinartz
-
Vince Luff
-
vinceluff@hotmail.com