-
-
Notifications
You must be signed in to change notification settings - Fork 683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating to snapshot 160 breaks Python support #979
Comments
Have the same issues. Any workarounds? |
@RStankov I worked around the issue by rolling back to snapshot 159. I'll wait and see for snapshot 161. |
This will be fixed in snapshot 161 which will come out in a day or so. The cause of this was that snapshot-160 turned on hardened runtime for app notarization requirements but it messed with Python and other scripting languages. For now, Apple allows using much more lenient restrictions so I'm going to work around the issue and get the app notarized, but they are going to tighten up what they allow to be notarized soon (Janurary 2020) so I'll need to find a real solution for this problem. |
Vim patch 8.1.2234 Fixes: - Fix scripting languages not working (e.g. Python) in binary releases by using the correct entitlements. #979 Targets macOS 10.9+ Script interfaces have compatibility with these versions: - Lua 5.3 - Perl 5.18 - Python2 2.7 - Python3 3.7 - Ruby 2.6
Describe the bug
The Python interface no longer works after updating MacVim from snapshot 159 to snapshot 160.
To Reproduce
Detailed steps to reproduce the behavior:
Put the lines below in
/tmp/pythontest.vim
to tell Vim where to find Python 3.7:Start the TUI with:
or the GUI with:
Do
:echo has('python3')
.Get a
0
.Do
:py3 print(1)
.Get the following errors:
Expected behavior
Both commands should echo
1
, without throwing errors.Environment:
First reported:
https://www.reddit.com/r/vim/comments/dotqki/macvim_black_and_python_version_problem/
The text was updated successfully, but these errors were encountered: