[Python.NET] Retiring Python 2.7

[Ivan Cronyn]

According to MS the future of .NET is .NET Core, so it would make sense to at least begin to think about this as the future target, with Mono in the picture too.

I currently run a slightly icky port of Pythonnet on CentOS 7, targeting Python 2.7 on .NET Core 2.1. It builds and runs on all versions of 2.1 and 2.2 and I’m sure it will work with 3.0.

With this build I’m loading about 80 large In-house .NET framework libraries, from 3.5 to 4.8, and run successful tests on 95% of the functionality (WCF clients, database calls, maths, pricing models, etc). 

I’d like nothing better than to work to be able to get rid of my port, and build straight from master. I’m prepared to spend a serious amount of time this year and 2020 working on the whole project to get this. 😎

> On 14 Jun 2019, at 17:08, Denis Akhiyarov <denis.akhiyarov at gmail.com> wrote:
> 
> Ivan, I just noticed your message. My opinion still applies and should work for you, if the release in 2019 includes at least partial .NET Core support. Note that .NET runtimes are also moving fast and hence may require a separate discussion about which versions should be supported for .NET Framework, .NET Core, Mono, .NET Standard.
> The amount of combinations for runtimes and platforms is not sustainable in the long term.
> 
>> On Fri, Jun 14, 2019, 10:41 AM Ivan Cronyn <ivan.cronyn at gmail.com> wrote:
>> I think it’s much too early to drop 2.7 - I’m on a mix of 2.7 and 3.6 at work
>> Also, if we’re going to spend some cycles changing the build, let’s get 2.4.0 eggs out and get .NET Core properly working? 😎
>> 
>>> On 14 Jun 2019, at 14:22, David Lassonde <david.lassonde at 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. 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 at 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 at 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 at 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 at python.org
>>>> >> https://mail.python.org/mailman/listinfo/pythondotnet
>>>> >
>>>> > _________________________________________________
>>>> > Python.NET mailing list - PythonDotNet at python.org
>>>> > https://mail.python.org/mailman/listinfo/pythondotnet
>>>> _________________________________________________
>>>> Python.NET mailing list - PythonDotNet at python.org
>>>> https://mail.python.org/mailman/listinfo/pythondotnet
>>> _________________________________________________
>>> Python.NET mailing list - PythonDotNet at python.org
>>> https://mail.python.org/mailman/listinfo/pythondotnet
>> _________________________________________________
>> Python.NET mailing list - PythonDotNet at python.org
>> https://mail.python.org/mailman/listinfo/pythondotnet
> _________________________________________________
> Python.NET mailing list - PythonDotNet at python.org
> https://mail.python.org/mailman/listinfo/pythondotnet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pythondotnet/attachments/20190614/19e1a361/attachment-0001.html>