Closed goxofy closed 4 months ago
I also hit this in a windows Docker environment while testing out some recent changes in the python prisma client
A basic reproduction Dockerfile is:
FROM winamd64/python
# FROM python <-- this works on other architectures fine
RUN pip install nodeenv
RUN nodeenv --list
Note, this is when targeting the Windows architecture. Ill try to put up a PR with a reproduction. This works perfectly fine on other architectures as far as I can tell
@goxofy is this still an issue for you? If so, maybe https://bugs.python.org/issue36011 might be helpful to you. Otherwise, after adding a fair amount of robust testing on the associated PR here, I can't reproduce your issue
I came across this issue in a private Gitlab instance, but was unable to reproduce this on gitlab.com as well. For the record, here's the job information: https://gitlab.com/bers/nodeenv-issues/-/jobs/4984422322
The workaround at https://github.com/python/cpython/issues/80192#issuecomment-1093815328 worked great for me on that private Gitlab instance.
I faced the same issue today, trying to create a virtual env. Reproduce: nodeenv .venv