Re: [Python.NET] Retiring Python 2.7

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 versi

Re: [Python.NET] Retiring Python 2.7

/705358e7c97338b3d6f5f26d06ae10a601241ef0 // Victor From: Benedikt Reinartz Sent: Friday, June 14, 2019 10:49 AM To: A list for users and developers of Python for .NET Subject: Re: [Python.NET] Retiring Python 2.7 Hi, > 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,

Re: [Python.NET] Retiring Python 2.7

Hi, > 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? 😎 Just to get this straight, I have no intention of dropping Python 2 support until

Re: [Python.NET] Retiring Python 2.7

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 Framewo

Re: [Python.NET] Retiring Python 2.7

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 runti

Re: [Python.NET] Retiring Python 2.7

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 > wrote: > > In our field (film/tv/games), pipel

Re: [Python.NET] Retiring Python 2.7

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 reall

Re: [Python.NET] Retiring Python 2.7

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

Re: [Python.NET] Retiring Python 2.7

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, 20

[Python.NET] Retiring Python 2.7

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 kno