Open wimglenn opened 2 years ago
Likely another problem with using --copies
with the virtual environment.
What does it look like when you create a virtual environment with --copies
? e.g.
$ mypython -m venv --copies testenv
$ testenv/bin/python
You are right. I get:
Error: Command '['/path/to/testenv/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 127.
Hmm, okay, so this is the same root cause #24, but with differing circumstances. Copies are quite useful as it prevents Poetry breaking when you upgrade your system Python interpreter, without duplicating shared objects... I'll have to consider whether we can preserve this feature and test for support in a robust/maintainable way, or if we just have to drop it and let users deal with the consequences of upgrading their Python.
Thanks for the info. For what it's worth, I would totally expect having to reinstall poetry if upgrading system interpreter.
Yep, for anyone else stumbling on this issue - for me it was because I was using pyenv
and I uninstalled the version of Python that I'd used to install poetry. So similar to @wimglenn, changing Python versions could require a re-install of poetry.
I'm using the CPython configure flags
--enable-shared
with an rpath interpolation (LDFLAGS). Linux platform (RHEL 8.3).The interpreter's stdlib venv works just fine, but poetry installer doesn't like something about that config
The log: