[Python.NET] Retiring Python 2.7

[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/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, 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 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/b47083a0/attachment.html>