Frost Ming
Frost Ming
We have implemented a full validation mechanism for both Pipfile and Pipfile.lock in `plette`, but it is not rolled into pipenv yet.
Rather than throwing an error, I prefer to normalize it silently for users.
The change in my PR is: when installing wildcard versions from CLI, Pipfile won't be modified. With the proposal here, when we do `pipenv install mypkg --pre`, we are willing...
This seems not true regarding #3751
@bkemmer Your Pipfile is not valid, ``[[source]]`` is for PyPI index, not VCS repo.
This is because this https://github.com/pypa/pipenv/blob/29af360d34a9e89dec59a8fa93b45eb33ef8e4ca/pipenv/project.py#L132 You may argue that is not reasonable to cd to the project root. But that line has been there for 4 years and there is...
The resolution goes too deep from the project initialization, and it is run in a subprocess. I think it is much easier to change your workflow to using a path...
@matteius Yes, the root directory doesn't contain a `setup.py` and is thus not recognized as a valid local requirement. The requirement parsing is performed after changing root to the project...
@matteius I agree with you but unfortunately, I don't have the bandwidth in fixing bugs in either Pipenv or vendored packages. requirementslib does too many things, which makes it hard...
It typically happens when your dependencies include some scientific packages, read #3830 for knowledge of why it is difficult to improve. What you can do at the best now, is...