Matt Davis

This won't be possible unless the pip resolver supported the pre option on a per-package level instead of a global level.

@mungojam My understanding is `pipenv requirements` was built to only consider the existing `Pipfile.lock` whereas the old `install -r` regenerated the lock file.

@mungojam That could be, I just checked the implementation and in fact, the original feature requests and author wanted the requirements command to be generated from the lock file, and...

I spent some time on this last night studying what is happening with respect to the current pip resolver, and basically the platform marker transitive dependencies get filtered out --...

Can this issue be rechecked on the latest `pipenv` version?

Can you check if this is still an issue on latest `pipenv` version? I believe this has been solved for.

@nikoskaramo The issue appears to be that you are getting a newer version of Python in your docker deploy. I got this same error trying to install `pipenv install backports-zoneinfo`...

FWIW I get the same error on `pipenv==2022.8.5` when trying to do the system install on the latest ubuntu, because it pulls in my python 3.10 What does your base...

@jkueloc You did not provide complete data but likely the problem is one of the setup.py packages you are installing depends on being able to import one of the other...

@jkueloc I just tried the `Pipfile` from that repository and made a fresh lock file and it worked -- was this an issue with the `--system` flag you experienced? ```...