Open eirnym opened 5 years ago
Hmm, we still search for Homebrew in src/MacVim/src/vimrc
though so it will still work. I would be hesitant to break behaviors for Mojave users, and we have had a lot of Python compatibiliy issues over the years already… I guess I'm not even sure if Travis CI will be able to build it correctly. Need to think more about it.
if MacVim have found version from Homebrew, it uses it, if we build agains Homebrew by default, then if we haven't found it, we use from system. will it work?
Since python 2 will be end of support on Jan 1 2020, seems like a good idea to move to 3.7
@adudek16 I don't think MacVim and Vim users will be happy atm. It will be removed at some point, but not now. If you really want to learn more reasons why it's bad idea to do it now, you should ask in upstream (vim/vim)
Seems like it shouldn't be a problem https://github.com/vim/vim/issues/5028#issuecomment-539574733
@adudek16 meant that you can't resign completely from python2 even it is won't supported. The sunsetting process will be quite long, I think, so I won't rush with complete removal of python2 support.
@ychin How the linking and the if-order will affect users? I see it only with resign from MacVIm initialization.
Oh I miss understood entirely.
On Tuesday, October 8, 2019, Arseny Nasokin notifications@github.com wrote:
I meant that you can't resign completely from python2 even it is won't supported. The sunsetting process will be quite long, I think, so I won't rush with complete removal of python2 support.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/macvim-dev/macvim/issues/939?email_source=notifications&email_token=ADXODGLAEU3YATS3AAFEMDLQNTIR5A5CNFSM4IURPIZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAVGOWY#issuecomment-539649883, or mute the thread https://github.com/notifications/unsubscribe-auth/ADXODGM6OCXAPAFB7C6MSTDQNTIR5ANCNFSM4IURPIZA .
@adudek16 meant that you can't resign completely from python2 even it is won't supported. The sunsetting process will be quite long, I think, so I won't rush with complete removal of python2 support.
The sunsetting has been going on for a long time as it is. Too many people are still in denial about it. Python has been saying for a few years now that python 2 is going EOL. Many major modules no longer support it in their newer versions. It's also not difficult to upgrade 80+% of code
according to Apple Developer Release Notes, there will be no Python installed in system by default.
We need to consider to starting to switch default python 2.7 build versions to Homebrew, then to the MacPorts and then system as we do with Python 3.7