Same as Mr. Sachs. I've left the job since, but we used pythonnet with a python 2.7 distro. As long as the current version is available for download, the script can get done what it needs to where it is deployed locally.
Sorry for noise is this is not on topic. On Thu, Jun 13, 2019 at 2:46 PM Jason Sachs <jmsa...@gmail.com> wrote: > > As long as I can still download Python.NET for Python 2.7, I don't care about > future development. > > My use case is a legacy Python 2.7 application that works with a data > acquisition system that has .NET drivers. I'm not currently developing it, > but we are still actively using it. > > On Thu, Jun 13, 2019 at 2:10 PM Victor “LOST” Milovanov > <lostfree...@gmail.com> wrote: >> >> Python 2.7 end of life is set to Jan 1st 2020, which is just a bit over 6 >> months now. https://pythonclock.org/ Major packages, like numpy are planning >> to drop support too. >> >> >> >> I think we should have some kind of plan to retire Python 2.x support in >> Python.NET. >> >> >> >> First of all, it would be good to know if there are anyone actually using >> Python 2.7 via Python.NET, and what is your plan going forward past EoL. >> >> >> >> Regards, >> >> Victor Milovanov >> >> >> >> _________________________________________________ >> Python.NET mailing list - PythonDotNet@python.org >> https://mail.python.org/mailman/listinfo/pythondotnet > > _________________________________________________ > Python.NET mailing list - PythonDotNet@python.org > https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet@python.org https://mail.python.org/mailman/listinfo/pythondotnet
