-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Poetry Install crashes for python-preview branch. #116
Comments
@alexchaomander , can you take a look please? |
@Codie-Petersen Hmm I'm not able to reproduce this on my side. Can you clear your pypoetry cache and try again?
|
Same problem for python 3.11.2 |
@alexchaomander For other people who want to try on windows (@richardk53 maybe): Should give you this:
Then you can try manually deleting the pypoetry folder with the cache-dir. |
I can reproduce this now! (I run an ubuntu desktop and WSL normally, but setup on regular Windows to reproduce this.) This issue seems to be the culprit: microsoft/debugpy#1246 For now, it seems the workaround is: poetry config installer.modern-installation false --local After that, you should be able to complete: poetry install
poetry shell
python And, in the python terminal, do something like |
@jjhenkel Nice, that worked. Thanks. @richardk53 Solution if you are on windows. |
Bumps [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) from 18.2.17 to 18.2.18. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Describe the bug
The poetry install command fails at debugpy installation. Possibly due to hashing error on 'debugpy/_vendored/pydevd/pydevd_attach_to_process/run_code_on_dllmain_x86.dll'.
To Reproduce
Steps to reproduce the behavior:
git checkout python-preview
cd python
pip install poetry
poetry install
Expected behavior
I was walking through the README.md tutorial for python setup in the branch. Expected the install to go through nicely.
Log
This is the log after a second install attempt.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: