Incorrect Pathing on Windows Powershell causes poetry to fail to install build cpp dependencies.

[skewballfox]

• Poetry version: 1.3.2
• Python version: 3.10.8
• OS version and name: Windows 10 Education Version 10.0.19045 Build 19045
• pyproject.toml: sanitized gist

• I am on the latest stable Poetry version, installed using a recommended method.
• I have searched the issues of this repo and believe that this is not a duplicate.
• I have consulted the FAQ and blog for any relevant entries or release notes.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below.

Issue

I believe this issue may be related to an upstream issue with virtualenv. It seems that path isn't set correctly causing installation of dependencies to fail when wheels need to be built.

the windows compiler is installed, the headers stored in the python modules do not seem to be on the search path. I think it's looking at .venv/ rather than .venv/lib, the way I resolved it with just venv directly was to switch to the scripts directory before activating Activate.ps1.

link to debug output for poetry install on powershell

[dimbleby]

if you've already diagnosed this as not a poetry issue, I'm not sure why you've raised it here?

you should be able to double-confirm that it's not a poetry problem with something like pip install --use-pep517 --no-cache-dir pyfastnoisesimd - which I expect to fail in the same way, without poetry being anywhere near it.

[skewballfox]

if you've already diagnosed this as not a poetry issue, I'm not sure why you've raised it here?

partially because it's still an issue that affects poetry whether the cause is upstream. partially because I'm not sure that specific upstream issue is the root cause.

you should be able to double-confirm that it's not a poetry problem with something like pip install --use-pep517 --no-cache-dir pyfastnoisesimd - which I expect to fail in the same way, without poetry being anywhere near it.

yeah that failed. I'll go ahead and close this. Quick question though, you think that linked issue is the cause of this?

[skewballfox]

sorry, didn't realize you couldn't comment on closed issues

[dimbleby]

you think that linked issue is the cause of this?

No, I think not. It's definitely not a poetry problem, but I'd guess that also it's nothing to do with the virtualenv issue that you mentioned.

Most likely you want to be raising this with pyfastnoisesimd and asking them to support PEP517 builds.

[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.