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
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
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
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 <
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
lostfreeman@gmail.com> wrote: 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
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@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@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
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@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@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 <
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
lostfreeman@gmail.com> wrote: 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
_________________________________________________ Python.NET mailing list - PythonDotNet@python.org https://mail.python.org/mailman/listinfo/pythondotnet
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@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@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@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@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
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
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 someone demonstrates that it significantly simplfies the code and build process. Python 2.7 is currently just one target out of five, so first priority to me should be to trim down the need of individual PYTHON3x defines to a single PYTHON3, as this is where change is happening. Python 2 is a static target. Of course it would be nice to provide fewer packages, I've outlined my ideas on this at https://github.com/pythonnet/pythonnet/wiki/Plan, but I don't see it as an improvement if we just run a -DPYTHON3 over all code. Regards Benedikt
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/705358e7c97338b3d6f5f26d06ae10a... // 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, 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 someone demonstrates that it significantly simplfies the code and build process. Python 2.7 is currently just one target out of five, so first priority to me should be to trim down the need of individual PYTHON3x defines to a single PYTHON3, as this is where change is happening. Python 2 is a static target. Of course it would be nice to provide fewer packages, I've outlined my ideas on this at https://github.com/pythonnet/pythonnet/wiki/Plan, but I don't see it as an improvement if we just run a -DPYTHON3 over all code. Regards Benedikt _________________________________________________ Python.NET mailing list - PythonDotNet@python.org https://mail.python.org/mailman/listinfo/pythondotnet
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
participants (7)
-
Benedikt Reinartz -
Carl Trachte -
David Lassonde -
Denis Akhiyarov -
Ivan Cronyn -
Jason Sachs -
Victor “LOST” Milovanov