Poetry installation gets linked with native python 2.7 in macOS, instead of using python3

[tropxy]

• I am on the latest Poetry version.
• I have searched the issues of this repo and believe that this is not a duplicate.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• OS version and name: <Darwin 19.6.0 Darwin Kernel Version 19.6.0: Sun Jul 5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64 x86_64; macOS 10.15.6 (19G73)>
• Poetry version: <^1.0.5>
• Link of a Gist with the contents of your pyproject.toml file:

Issue

Hi,

My problem started with version 1.0.5 and in an attempt to try to solve it, I have uninstalled this version and installed the most recent one, however the problem described below persisted. I have uninstalled 1.0.5 poetry version by issuing

/System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 get-poetry.py --uninstall

After that, I have installed poetry using the recommended command in the docs, specifying python3:

curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py | python3 -

The installation successfully finishes as expected.

However, poetry gets linked to the native python 2.7 distribution on Mac, instead of getting linked to the python3 version installed:

The correct python version gets linked to the poetry installation only if I install it using pip:

> pip3 install poetry 

Thus, now everything works, but still, I assume the way I have tried to install it should have worked as well. I have checked other issues that were similar, like this one:
#655

But here the problem was more about poetry not picking up the correct virtual env, which is not an issue, in my case.

Thank you all!

[finswimmer]

Hello @tropxy,

this is intended behavior and was discussed before (#3184, #3288) Please see my comments about the why: #3184 (comment) , #3288 (comment)

fin swimmer

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.