-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All my [packages] are ignored, only my [dev-packages] are locked #4866
Comments
So, I probably found what's wrong:
in Pipenv. When moved before
it seems to be ok too. So, it probably errs somewhere because of this, but no error indication is shown. |
@janmpeterka You are my hero for accurately describing the same bug I encountered with the newer versions released in November and the private Pipfile we have at my place of employment. I just verified from the report you filed that when I remove from the Pipfile a block at the bottom similar to yours, it generates the full lock file.
I knew dependencies were missing, what I hadn't figured out is the other thing you said that "only my [dev] are locked" which seems to be the case in my example, too. However one discrepancy -- It was only fixed in my case when I deleted the block, I tried to verify what you said that moving that block above the [requires] python version block also resolves the issue, but for me the lock file only had the dev requirements in that case as well. This affects the latest version of |
This bug seems to have been fixed in: |
All my [packages] are ignored, only my [dev] are locked
Running on:
Pipfile:
Pipfile.lock
Here is terminal, it seems like it skipped/erred on packages
The text was updated successfully, but these errors were encountered: