Matt Davis

I think we want to be able to support pre release versions too like `3.11.0b4`. I haven't looked into `packaging.version.VERSION_PATTERN` yet, but we have it available to us already as...

@jgillich there is no longer the progress bar in pipenv, and the current example looks like: ``` matte@LAPTOP-N5VSGIBD MINGW64 ~/Projects/pipenv (main) $ pipenv install --quiet --dev Loading .env environment variables......

@Siecje `pipenv install` will try to lock from the `Pipfile`. What if you replace that part with `pipenv sync` which installs dependencies from the lock file?

@Siecje I just tested this and it turns out that `pipenv sync` won't install anything without the `Pipfile`, maybe because it doesn't know what is a package and what is...

@Siecje What is the use case for not including the `Pipfile` as well during the build process?

@JDLH I know your offer to help with a PR improving the documentation is a little old by now, but if you are still interested in doing so I think...

@jyoungs Could you provide your sample setup.py that you used to help reproduce this issue?

I believe this was resolved, can you check with `pipenv=2022.8.17`?

@duailibe If you add `editable = "true"` to those Pipfile entries it should work.

I have just made a code change that makes it work without adding the editable flag. https://github.com/pypa/pipenv/pull/5342