News for hackers. Stuff that matters.

A comment on You shouldn't invoke setup.py directly. Parent comment

Re:You shouldn't invoke setup.py directly by notatoad on Tuesday October 19, 2021 @09:11PM (#28925682)
if you can use docker, that solves pretty much all the python packaging mess and makes deploying your challenge of deploying random python application to a random VPS pretty simple.

i'm not saying that python packaging isn't a mess. but it can be largely mitigated.

[ Parent | on HN ]
Re:You shouldn't invoke setup.py directly by robomartin on Wednesday October 20, 2021 @01:26AM (#28927072)
As someone else said, Docker introduces yet another level of crazy to having to deploy a Python/Django app. I've looked into and used all of these technologies. We have developed internal "How To" documents on how to deploy different types of apps into a variety of environments. Reading through the Python/Django "How To" is a sobering experience.

This coming from someone who would truly like to use Python/Django exclusively. I hate, hate, hate telling people to just use WP or go a different route. I do not enjoy touching PHP. And yet...

[ Parent | on HN ]
Re:You shouldn't invoke setup.py directly by selfhoster11 on Tuesday October 19, 2021 @11:49PM (#28926533)
Docker takes away some problems and creates other, smaller problems. It also results in more complexity. That complexity is a problem.

I can teach a slightly technical person to deploy WordPress on a shared host with a pre-installed shared LAMP stack. I cannot do this with Docker, not to to the extent it's sustainable without ongoing help from me.

[ Parent | on HN ]