'zsh: killed python' while executing from virtualenv on macOS Big Sur for Python 2.7 #4502

aberrya · 2020-10-27T20:29:55Z

zsh: killed python while executing from virtualenv on macOS Big Sur (platform: arm64) for Python 2.7
It is working fine for Python 3.8

Expected result

Python Shell should launch from virtual env shell.
On using pipenv sync should install dependencies.

Actual result

zsh: killed python. Python shell is not launched.

Steps to replicate

pipenv install --python 2.7
pipenv shell
python

Using /usr/bin/python2.7 (2.7.16) to create virtualenv...
⠴ Creating virtual environment...created virtual environment CPython2.7.16.final.0-64 in 216ms
  creator CPython2macOsFramework(dest=/Users/ab/.local/share/virtualenvs/demo2-HNdtbnRg, clear=False, global=False)
  seeder FromAppData(download=False, pip=bundle, wheel=bundle, setuptools=bundle, via=copy, app_data_dir=/Users/ab/Library/Application Support/virtualenv)
    added seed packages: pip==20.2.4, setuptools==44.1.1, wheel==0.35.1
  activators PythonActivator,CShellActivator,FishActivator,PowerShellActivator,BashActivator

✔ Successfully created virtual environment! 
Failed to load paths: 
Output: 
Virtualenv location: /Users/ab/.local/share/virtualenvs/demo2-HNdtbnRg
Installing dependencies from Pipfile.lock (3cbc06)...
  🐍   ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 0/0 — 00:00:00
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
 demo2 % pipenv shell
Launching subshell in virtual environment...
 . /Users/ab/.local/share/virtualenvs/demo2-HNdtbnRg/bin/activate                         
demo2 %  . /Users/ab/.local/share/virtualenvs/demo2-HNdtbnRg/bin/activate
demo2 % python 
zsh: killed     python
demo2 % which python
/Users/ab/.local/share/virtualenvs/demo2-HNdtbnRg/bin/python

This works perfectly fine with if I use pipenv install --python 3.8
See details of platform and Python version below (skipped sys env variables)

$ pipenv --support

Pipenv version: '2020.8.13'

Pipenv location: '/Users/ab/Library/Python/2.7/lib/python/site-packages/pipenv'

Python location: '/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python'

Python installations found:

3.8.2: /usr/bin/python3
2.7.16: /usr/bin/python2.7
2.7.16: /usr/bin/python2

PEP 508 Information:

{'implementation_name': 'cpython',
 'implementation_version': '0',
 'os_name': 'posix',
 'platform_machine': 'arm64',
 'platform_python_implementation': 'CPython',
 'platform_release': '20.0.0',
 'platform_system': 'Darwin',
 'platform_version': 'Darwin Kernel Version 20.0.0: Fri Aug 14 00:25:08 PDT 2020; root:xnu-7195.40.44.151.1~4/RELEASE_ARM64_T8020',
 'python_full_version': '2.7.16',
 'python_version': '2.7',
 'sys_platform': 'darwin'}

Pipenv–specific environment variables:

Debug–specific environment variables:

PATH: /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Users/ab/Library/Python/2.7/bin
SHELL: /bin/zsh
LANG: en_US.UTF-8

The text was updated successfully, but these errors were encountered:

frostming · 2020-10-28T03:23:07Z

Sorry but I can't reproduce, does pipenv run python work?

aberrya · 2020-10-28T10:10:31Z

@frostming thanks for reply.
pipenv run python not working and output is : zsh: killed pipenv run python and Python shell not launched.
Big Sur version 11.0 Beta (20A5354i)

uranusjr · 2020-10-28T10:15:18Z

Looks like you have a broken environment or Python installation. Try each of the following steps one by one (run the next if the previous does not fix the issue):

Reboot (this could fix it if you’re simply out of memory)
pipenv --rm and start over
Re-install Python (not the virtual environment; the actual Python interpter)

If none of the above works, you’re likely having a system issue and should seek (physical) technical assistance.

kamilturek · 2020-12-20T00:19:28Z

@aberrya Any update on this? I've come across the same issue.

nilabjodey · 2020-12-23T16:52:41Z

I've come across the same issue as well. I've created a virtual environment running python 2.7, and any command be it pip or python is killed by the zsh. I'm using Rosetta to run x64 based terminal on arm64 Mac. Any updates would be helpful.

aberrya · 2020-12-23T17:49:18Z

@kamilturek @nilabjodey We started using venv and also moved to Python3 now (which was long pending for years). But I saw that even with recent Big Sur update on ARM Mac, issue was still persisting Python2 and pipenv.

kamilturek · 2020-12-23T18:57:32Z

It worked for me after I installed Python 2.7.18 using pyenv.

pxul · 2021-02-06T21:47:48Z

I suspect this is related to: pypa/virtualenv#2023

afit · 2021-02-14T16:33:45Z

Same problem: can't make virtualenv work on any M1-based Mac with 2.7. Tried a few systems, always plays out as @aberrya describes.

lykhatskyi · 2021-02-23T08:45:54Z

solution:

cd ~/.virtualenvs/<your venv name here>/bin
mkdir bk; cp python bk; mv -f bk/python .;rmdir bk
codesign -s - --preserve-metadata=identifier,entitlements,flags,runtime -f python

aberrya · 2021-02-26T21:39:55Z

Same problem: can't make virtualenv work on any M1-based Mac with 2.7. Tried a few systems, always plays out as @aberrya describes.

You can check as suggested by kamilturek above, that Python 2.7.18 using pyenv worked.
I have moved to Python3.8/venv and no issue.

bernardknt · 2021-02-27T08:02:11Z

solution:

cd ~/.virtualenvs/<your venv name here>/bin
mkdir bk; cp python bk; mv -f bk/python .;rmdir bk
codesign -s - --preserve-metadata=identifier,entitlements,flags,runtime -f python

Thanks man this worked for me

oswalgopal · 2021-02-28T16:11:31Z

Thanks It worked on m1

goxofy · 2021-03-03T06:36:28Z

same problem

vasantvohra · 2021-03-27T14:10:53Z

same problem, updating to 2.7.18 solved the issue

goxofy · 2021-03-28T01:29:52Z

@vasantvohra how to update?

vasantvohra · 2021-03-28T10:47:21Z

@vasantvohra how to update?

@goxofy I've installed python 2.7.18 using MacOs installer available on the python website and also used pyscopg2-binary for Postgres v13 as there were some errors installing pyscopg2.

I'm using M1 with the latest Big Sur.

goxofy · 2021-03-29T01:09:04Z

@vasantvohra So there are Python 2.7.18 and 2.7.16 on your Mac?

ameysunu · 2021-05-19T08:55:34Z

I had the same issue on my M1 Mac. You can resolve the same by duplicating your Terminal, and running it with Rosetta. That worked for me.

hein-j · 2021-05-31T19:25:30Z

I had the same issue on my M1 Mac. You can resolve the same by duplicating your Terminal, and running it with Rosetta. That worked for me.

That works for me for the built-in python, but for the python3 installed through homebrew, I had to reinstall by:
brew reinstall $(brew deps python3) python3

ADVALAKI · 2021-07-01T12:56:37Z

If you are on Apple M1, mac sure open terminal with Rosetta enabled. it will works fine.

jesphinpt · 2021-07-28T09:15:47Z

Can anyone explain why it happening and any common workarunds. It failed for me while running a script

pxul · 2021-07-28T10:05:41Z

@jesphinpt details of why this is happening, and workarounds (also mentioned in this thread) can be found here:
pypa/virtualenv#2023

jesphinpt · 2021-07-28T10:26:57Z

Thanks for you reply. But in my case it not failing in Python. It fails in an another script. Could you please let me know common usecase for the zsh killed error in M1 model?

…

On Wed, Jul 28, 2021 at 3:35 PM Paul Jefferson ***@***.***> wrote: @jesphinpt <https://github.com/jesphinpt> details of why this is happening, and workarounds (also mentioned in this thread) can be found here: pypa/virtualenv#2023 <pypa/virtualenv#2023> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4502 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQAIH37NNTQESCGW2OHJA73TZ7JABANCNFSM4TBLJAEQ> .

pxul · 2021-07-28T11:38:57Z

Hi Pypa/Pipenv Thanks for you reply. But in my case it not failing in Python. It fails in an another script. Could you please let me know common usecase for the zsh killed error in M1 model?

(I'm not pypa/pipenv, just a random person but...) As I understand it, the reason this is happening here is because in python2 virtual environments the python (and pip) binaries are copied (rather than symlinked, as is the case in python3) into the virtualenv. This results in a mismatch between the binary and the code signature (required to run binaries on macOS). As a result the process is killed on startup.

For you case, it is a bit off-topic for this thread. Perhaps post a question in Stack Overflow (or similar) but provide as much information about the script and how you are running it as you are able. I would also check logs in /var/log/system.log, or using console.app to see if there is any useful information there which may help with diagnosing the issue. Good luck.

nemoDreamer · 2021-08-05T17:10:22Z

solution:

cd ~/.virtualenvs/<your venv name here>/bin
mkdir bk; cp python bk; mv -f bk/python .;rmdir bk
codesign -s - --preserve-metadata=identifier,entitlements,flags,runtime -f python

Works like a charm, @lykhatskyi , thanks! ❤️

But @pxul , according to your comment, creating the virtualenv with symlinks would be the preferred solution?

virtualenv --symlinks <your env target path>

pxul · 2021-08-05T20:27:49Z

@nemoDreamer sadly not, according to these two comments the limitation comes from the inability to update sys.path of a symlinked interpreter under cpython2, I think:

pypa/virtualenv#2023 (comment)
pypa/virtualenv#2023 (comment)

As such, even when the --symlinks option is passed to virtualenv when creating a python2 virtual environment, a copy of the interpreter is created, rather than a symlink to the original.

nemoDreamer · 2021-08-05T20:42:32Z

😢

carltongibson · 2021-11-22T16:07:40Z

I hit this issue. FWIW dropping back to pip was the simplest way forward:

$ pipenv lock -r > ../requirements.txt
$ cd ..
$ python -m venv venv
$ source venv/bin/activate
$ pip install -r requirements.txt  # And we're off.

matteius · 2021-12-24T10:20:36Z

I question keeping this issue open, given that python 2.7 support has ended and it is not a supported language version any longer on the pipenv pypi page. It would require running old versions of pipenv, which would have whatever behaviors they have. Then you famous people trying to run py2 stuff on M1 macs, I just don't know about it, but it sounds like an awful idea. Happy holidays everyone; I'm glad there is some work arounds for your issues but I am closing this one as it doesn't feel like an actionable pipenv issue.

deni · 2022-01-23T20:10:15Z

Then you famous people

What does that mean?

matteius · 2022-01-23T21:30:41Z

Then you famous people

What does that mean?

Ah sorry -- I had spent too many hours looking at pipenv issues that day, I was amused to see so many names I recognized on this thread but probably didn't need to add that remark.

albertowen999 · 2022-02-23T09:52:44Z

here is the soloution https://youtu.be/dWC4xAdbko8

keerthanmp21 · 2022-02-28T14:00:30Z

If anyone still facing this issue then follow below steps:

enable rosetta in terminal or create new terminal with different name
a)To create new terminal
go to Applications -> Utilities -> double click on terminal -> duplicate
b) To enable rosetta
double click on terminal -> Get Info -> tick open using rosetta checkbox
(check rosetta by typing arch command i386 should appear )

2)create virtual env with python
3)type below commands
cd <virtual_env>/bin
mkdir kmp(can be any name)
cp python kmp
mv -f kmp/python .
codesign -s - --preserve-metadata=identifier,entitlements,flags,runtime -f python

Note:- i386 to execute x86_64 architecture dependencies (where python2.x works on)
arm64 to execute arm architecture dependencies(where python3.x works on)

RavikantSingh0191 · 2022-05-03T18:15:34Z

alias python3="/usr/bin/python3"

Use this in your terminal. It should work now.

WLewington · 2022-07-22T10:49:49Z

Manually updating to python version 2.7.18 also worked for me, don't brew install.

https://www.python.org/downloads/release/python-2718/

matteius closed this as completed Dec 24, 2021

matteius mentioned this issue Jan 4, 2022

Cannot create a 2.7 environment on macOS Monterey #4904

Closed

'zsh: killed python' while executing from virtualenv on macOS Big Sur for Python 2.7 #4502

'zsh: killed python' while executing from virtualenv on macOS Big Sur for Python 2.7 #4502

Comments

aberrya commented Oct 27, 2020

Expected result

Actual result

Steps to replicate

frostming commented Oct 28, 2020

aberrya commented Oct 28, 2020

uranusjr commented Oct 28, 2020 • edited Loading

kamilturek commented Dec 20, 2020

nilabjodey commented Dec 23, 2020

aberrya commented Dec 23, 2020 • edited Loading

kamilturek commented Dec 23, 2020

pxul commented Feb 6, 2021 • edited Loading

afit commented Feb 14, 2021

lykhatskyi commented Feb 23, 2021 • edited Loading

aberrya commented Feb 26, 2021

bernardknt commented Feb 27, 2021

oswalgopal commented Feb 28, 2021

goxofy commented Mar 3, 2021

vasantvohra commented Mar 27, 2021 • edited Loading

goxofy commented Mar 28, 2021

vasantvohra commented Mar 28, 2021

goxofy commented Mar 29, 2021

ameysunu commented May 19, 2021

hein-j commented May 31, 2021

ADVALAKI commented Jul 1, 2021

jesphinpt commented Jul 28, 2021

pxul commented Jul 28, 2021

jesphinpt commented Jul 28, 2021 via email • edited Loading

pxul commented Jul 28, 2021

nemoDreamer commented Aug 5, 2021

pxul commented Aug 5, 2021

nemoDreamer commented Aug 5, 2021

carltongibson commented Nov 22, 2021

matteius commented Dec 24, 2021

deni commented Jan 23, 2022

matteius commented Jan 23, 2022

albertowen999 commented Feb 23, 2022

keerthanmp21 commented Feb 28, 2022 • edited Loading

RavikantSingh0191 commented May 3, 2022

WLewington commented Jul 22, 2022

uranusjr commented Oct 28, 2020 •

edited

Loading

aberrya commented Dec 23, 2020 •

edited

Loading

pxul commented Feb 6, 2021 •

edited

Loading

lykhatskyi commented Feb 23, 2021 •

edited

Loading

vasantvohra commented Mar 27, 2021 •

edited

Loading

jesphinpt commented Jul 28, 2021 via email •

edited

Loading

keerthanmp21 commented Feb 28, 2022 •

edited

Loading