Re: [Python.NET] pythonnet development

2019-06-14 Thread Li Amos
Interesting for it, count me in. _ Python.NET mailing list - PythonDotNet@python.org https://mail.python.org/mailman/listinfo/pythondotnet

Re: [Python.NET] Retiring Python 2.7

2019-06-14 Thread 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 versi

Re: [Python.NET] Retiring Python 2.7

2019-06-14 Thread Victor “LOST” Milovanov
I do have a change, that removes all defines for Python 3.x, replacing them with a initialization-time reflection work. It also drops PYTHON2, but it is possible to make it work for Python 2.7 as well with some effort. See here: https://github.com/losttech/pythonnet/commit/705358e7c97338b3d6f5f

Re: [Python.NET] Retiring Python 2.7

2019-06-14 Thread Benedikt Reinartz
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

2019-06-14 Thread Denis Akhiyarov
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

2019-06-14 Thread Denis Akhiyarov
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

2019-06-14 Thread Ivan Cronyn
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

2019-06-14 Thread David Lassonde
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