Hacker News Reader

Comment by vforgione | Hacker News Reader

Twine[0] is the tool I've been using for PyPI archive management and Pipenv[1] is looking promising as the next iteration of pip.

Twine makes the packaging process _slightly_ easier, although setuptools is still a bit of a pain.

Pipenv handles a lot of project cruft for you: setting up a virtualenv, distinguishing dev and prod packages, locking them down and deterministic building.

[0]: https://github.com/pypa/twine

[1]: https://github.com/kennethreitz/pipenv

View on HN

Oh man, how have I not known about pipenv? This addresses a huge amount of my complaints with pip. Thanks for sharing!

The downside to pipenv is that there aren't any good docker images to work with it. I've tried a few times, but I've never given enough time to learning the guts of Docker to make anything stable enough to run with it.

That shouldn't be too much of a problem. I'll have to port an image over later to use pipenv, so I'll share a gist to a minimal Dockerfile.

have you tried https://github.com/VaultVulp/pipenv-alpine/blob/master/Docke...?

I did, but something about Alpine rubs me the wrong way. I know it's probably irrational, but my gut always goes to Debian. I really can't justify it. Maybe I should give it a better chance.

Here's my Dockerfile: https://gist.github.com/dfee/388c3f270fdfc4f31aba906770f9313...

Very cool. I'll have to give it a whirl. I haven't taken a stab at a custom image in a while. Thanks!

Reply on news.ycombinator.com