You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"env use" fails with "NameError: name 'PosixPath' is not defined" #2711
I guess it will be fixed by replacing venv to str(venv) so I tried to fix, but the commit above is replacing str(venv) to venv and I can't understand the purpose to do so. I can't fix it.
@elferia appreciate the bug report and the analysis. As you have already identified, the preview version will resolve this. And since we recently released the last 1.0.z release and next release is expected soon, resolving this.
I had the same issue, upgrading to the latest preview version fixed it for me - thanks!
$ poetry self update --preview
Updating to 1.1.0b2
Reacted by Tony Narlock, elferia, Patrick, Andrii Skoryk, Niklas Krolovitsch, luckymice, Logan Yang, Mikaël Gourlaouen, Dustin Engstrom, Chitradeep Dutta Roy and 25 more
Reacted by A.G, Meshack Mwaura, Zane Dufour, Charles Dorner, Evan E. Baird, Sam Korn, Loki Wijnen and JakobSchubert
Since my poetry installation gave me this warning: Poetry was not installed with the recommended installer. Cannot update automatically.
Reacted by Kyu Chul Kim, Eino Gourdin, Caio Fleury, Mike Boyle, Timothée Mazzucotelli, Wasitpon Sinthuphon, Jason Goldfine-Middleton, Bogdan Daragan, Charles Dorner and Shakeeb
Isn't there a chance to get a patch release for this bug for the 1.0 line? Seems a few dependencies still block upgrading things like the archlinux package and user there are then stuck with this broken version.
Reacted by Wil Thomason, Никита, Tom Howard, German Lashevich, Tony Narlock, Kevin Languasco and esztermarton
Is there any way around this upgrading to 1.1 (I can't do that - I have projects depending on 1.0 and it's the team's choice whether poetry upgrades, the lockfiles aren't compatible to my knowledge between 1.0 and 1.1)
Is this something that could be backported into 1.0? (I am on 1.0.10)
What was the fix for this in 1.1? Is it a trivial one?
I don't believe it's solved by 5487069, which is in 1.0.10, since I still get the issue. The PR at #2742 doesn't specify what change fixed it in 1.1 at the time
Any workarounds aside from upgrading anyone know of? This sorta breaks my setup.
Activity
elferia commentedon Jul 24, 2020
version 1.1.0a3 not include 5487069
poetry/poetry/utils/env.py
Line 664 in a50d87d
So workaround is installing preview version.
abn commentedon Jul 24, 2020
@elferia appreciate the bug report and the analysis. As you have already identified, the preview version will resolve this. And since we recently released the last
1.0.zrelease and next release is expected soon, resolving this.alexlouden commentedon Jul 26, 2020
I had the same issue, upgrading to the latest preview version fixed it for me - thanks!
tony commentedon Jul 26, 2020
Thanks @alexlouden
I had to do :
pip install --user --pre poetry -USince my poetry installation gave me this warning:
Poetry was not installed with the recommended installer. Cannot update automatically.goodcheer commentedon Jul 28, 2020
Thanks @tony
if you're using
pipxas install manager, you can get pre-release by :pipx install --pip-args='--pre' poetry(confimred working)or upgrade exisiting one
pipx install --pip-args='--pre -U' poetry(haven't tried this one, but might work)Fix for Poetry 1.0.10
CI: Use preview version of Poetry
An issue in poetry is only available in preview mode. python-poetry/p…
jrgoldfinemiddleton commentedon Sep 5, 2020
I had to use this instead:
pipx upgrade --pip-args='--pre' poetryInstall prerelase poetry in CI script
gavinbeatty commentedon Sep 29, 2020
Still running into this issue when doing
poetry shellon mac latest stable, works on preview 1.1.0rc1.abn commentedon Sep 29, 2020
@gavinbeatty #2711 (comment)
languitar commentedon Jan 7, 2021
Isn't there a chance to get a patch release for this bug for the 1.0 line? Seems a few dependencies still block upgrading things like the archlinux package and user there are then stuck with this broken version.
tony commentedon Jan 30, 2021
@abn Hi there! I got a a question (echo'ing) @languitar at #2711 (comment)
Is there any way around this upgrading to 1.1 (I can't do that - I have projects depending on 1.0 and it's the team's choice whether poetry upgrades, the lockfiles aren't compatible to my knowledge between 1.0 and 1.1)
Is this something that could be backported into 1.0? (I am on 1.0.10)
What was the fix for this in 1.1? Is it a trivial one?
I don't believe it's solved by 5487069, which is in 1.0.10, since I still get the issue. The PR at #2742 doesn't specify what change fixed it in 1.1 at the time
Any workarounds aside from upgrading anyone know of? This sorta breaks my setup.
github-actions commentedon Mar 2, 2024
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.