News for hackers. Stuff that matters.

A comment on Pipenv: promises a lot, delivers very little. Parent comment

Re:Pipenv: promises a lot, delivers very little by vmchale on Wednesday December 05, 2018 @11:49PM (#18615497)
> Introducing a lockfile is a big step forward for Python dependency management

Huh? I'm not really familiar with the state of dependency management for Python/dynamic languages but... there's much more out there beyond just lockfiles. I'm a bit appalled Python is so far behind.

[ Parent | on HN ]
Re:Pipenv: promises a lot, delivers very little by IvanAnishchuk on Thursday December 06, 2018 @03:58AM (#18616416)
Much more for what? In this context, "lockfile" means a file listing all your project dependencies with exact versions pinned. (Not semaphore-files or anything like that. It's not even a python-specific term, e.g. npm uses package-lock.json for the same purpose.) The need for something to store all dependencies with exact versions pinned exists in any language and infrastructure, are there any better solutions than store them in a file? Files are nice, they are VCS-friendly and everything.
[ Parent | on HN ]
Re:Pipenv: promises a lot, delivers very little by vmchale on Thursday December 06, 2018 @11:52AM (#18619678)
> Much more for what?

Much more in the field of build tooling/package management. Pinning versions is fine, but dependency resolution is another legitimate choice.

[ Parent | on HN ]