Python 2 will be replaced with Python 3 in the next RHEL major release

Re:Python 2 will be replaced with Python 3 in the next RHEL ... by mhd on Wednesday April 11, 2018 @04:10AM (#16809023)

Wasn't there a big brouhaha over the change from VB6 to VB.Net? The big difference there is that if it's ordained from your corporate overlords, you have little choice, whereas you feel like you've got a bigger right to complain when it's "just" coming from the BDFL.

[ Parent | on HN ]

Re:Python 2 will be replaced with Python 3 in the next RHEL ... by umanwizard on Wednesday April 11, 2018 @05:57AM (#16809542)

VB.NET is a totally new language almost unrelated to VB6. That’s like talking about C vs C++, not py2 vs py3.

[ Parent | on HN ]

Re:Python 2 will be replaced with Python 3 in the next RHEL ... by toyg on Wednesday April 11, 2018 @07:57AM (#16810212)

Calling it a “New language” flatters Vb.net. In reality, it was a “marketing compatibility shim” on top of C# to help VB developers acclimatise to the CLR.

[ Parent | on HN ]

Re:Python 2 will be replaced with Python 3 in the next RHEL ... by michaelt on Wednesday April 11, 2018 @06:11AM (#16809602)

As VB6 is compiled, you don't need your users to have a particular interpreter version installed.

[ Parent | on HN ]

Re:Python 2 will be replaced with Python 3 in the next RHEL ... by ajdlinux on Wednesday April 11, 2018 @06:16AM (#16809618)

I do remember the good old days of having to make sure you had MSVBVM50.DLL or MSVBVM60.DLL in the right place...

[ Parent | on HN ]

Re:Python 2 will be replaced with Python 3 in the next RHEL ... by pjmlp on Wednesday April 11, 2018 @07:16AM (#16809934)

It is no different than ensuring you have the right libc.so in place.

[ Parent | on HN ]