It is possible to write code that targets both Python 2 and Python 3 runtimes and do testing while still using legacy Python 2 as the runtime in production. There are plenty of tools and examples from large tech companies to support the transition. IMO: all efforts to support legacy Python 2 runtime in 2020 should be based on commercial agreement in a separate "bug-fix only" branch due to the effort to maintain both runtimes. For example, release one last Python 2.7 compatible version late 2019 on PYPI and keep that branch on GitHub. But all backports from master branch to that legacy branch and releases of Python 2 binaries/wheels to PYPI should be supported by commercial users. Note that binaries for *Nix architectures is still not feasible with Mono or .NET Core. Thanks, Denis On Fri, Jun 14, 2019, 8:23 AM David Lassonde < david.lassonde@imaginary-spaces.com> wrote:
In our field (film/tv/games), pipelines are only using Python 2.7. Our customers, partners and us try to follow the vfx reference platform <https://vfxplatform.com/>. The table says that studios and vendors have until the end of CY 2020 to drop Python 2.7.
It is too soon to tell if this will really happen that fast, because the transition will be hard, it will take time and money. Pixels will not look better after the investment.
All that to say that for us, as long as there is a "last Python for .NET" GitHub release/tag, we will be fine. We can always fork the repo and fix bugs on our own, or merge to a special branch that you could keep open in the repo.
David
On Thu, Jun 13, 2019 at 6:31 PM Carl Trachte <ctrachte@gmail.com> wrote:
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 <jmsachs@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 <
lostfreeman@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
_________________________________________________ Python.NET mailing list - PythonDotNet@python.org https://mail.python.org/mailman/listinfo/pythondotnet