Pipenv: consider locking after every install
kennethreitz42
👍2
All 4 comments
+1 on this. npm updates its shrinkwrap.json if installing/saving the package.json and yarn does the same with yarn.lock.
I think it might be a good rule that if we're updating the Pipfile, we also update the Pipfile.lock, instead of having the user do so everytime. I could tackle this.
jpadilla
on 23 Jan 2017
👍2
the only downside is that currently locking is a rather expensive (time-wise) operation.
kennethreitz42
on 23 Jan 2017
👍1
How about an optional parameter to check for locking after install?
rmad17
on 24 Jan 2017
@rmad17 done!
kennethreitz42
on 25 Jan 2017
👍2
Was this page helpful?
0 / 5 - 0 ratings
Related issues
jerzyk
·
3Comments
marc-fez
·
3Comments
randName
·
3Comments
bgjelstrup
·
3Comments
xi
·
3Comments
Most helpful comment
@rmad17 done!