-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
1.0.10 NameError exception 'PosixPath' is not defined when creating virtual envrionment #2742
Comments
Duplicate of #2711 |
I should have searched closed issues, thanks for referencing #2711 I installed the preview version with |
Can this be backported? Or can a release be made? The lockfile does not seem to be backwards compatible. |
* poetry first run: RuntimeWarning: The _posixsubprocess module is not being used. Child process reliability may suffer if your program uses threads. "program uses threads. Need to hack into ~/.poetry/bin/poetry to change the shebang line to use Python 3 instead of Python 2... (thanks python-poetry/poetry#1257 (comment)) * poetry second run: NameError exception 'PosixPath' is not defined when creating virtual environment Need to upgrade to the preview version of poetry (thanks python-poetry/poetry#2742 (comment)) * poetry third run: installing black Resolving dependencies... (76.5s) (ノಠ益ಠ)ノ彡┻━┻
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. |
-vvv
option).make build-1.0.10
should show the errorIssue
I noticed today when poetry was used in a centos image to install dependencies, it failed (output will be below). It looks like an exception is thrown when creating the virtual environment, which fails, but then poetry tries to install dependencies:
Curious if anyone else is running into this. I typically use poetry on my mac, but I have some projects where I'll use it to install dependencies on centos based images like in the example project linked above.
Hope this is helpful, thank you for your consideration!
The text was updated successfully, but these errors were encountered: