pipenv 2021.11.5 regresses back to issue #2961

Issue description

It appears that issue https://github.com/pypa/pipenv/issues/2961 has returned. This is occurring on a mac.

Expected result

pipenv should operate without throwing an exception.

Actual result

Traceback (most recent call last):
  File "/Users/buildgimp/.new_local/bin/pipenv", line 5, in <module>
    from pipenv import cli
  File "/Users/buildgimp/.new_local/lib/python/site-packages/pipenv/__init__.py", line 22, in <module>
    from pipenv.vendor.vistir.compat import ResourceWarning, fs_str
  File "/Users/buildgimp/.new_local/lib/python/site-packages/pipenv/vendor/vistir/__init__.py", line 4, in <module>
    from .compat import (
  File "/Users/buildgimp/.new_local/lib/python/site-packages/pipenv/vendor/vistir/compat.py", line 13, in <module>
    from .backports.tempfile import NamedTemporaryFile as _NamedTemporaryFile
  File "/Users/buildgimp/.new_local/lib/python/site-packages/pipenv/vendor/vistir/backports/__init__.py", line 6, in <module>
    from .tempfile import NamedTemporaryFile
  File "/Users/buildgimp/.new_local/lib/python/site-packages/pipenv/vendor/vistir/backports/tempfile.py", line 15, in <module>
    from backports.weakref import finalize
ImportError: No module named weakref

Steps to replicate

Pipenv is deeply embedded in a jhbuild install, so not able to extract to exactly reproduce. But it appears that pipenv is simply not functioning at all.

“Workaround”

pip install --upgrade --user pipenv==2021.5.29

[majg0]

yank the release of that problematic release

Does this mean that things will start working again during builds without the workaround?

If you could please ping us when it’s out, that would be great.

Thank you for your help! 🙏🏼

[lukaso]

I’m not using the workaround anymore. I think the issue has been fixed (but I’m not quite sure what I did so I’m not certain).