News for hackers. Stuff that matters.

A comment on Hypermodern Python. Parent comment

Re:Hypermodern Python by im3w1l on Thursday May 28, 2020 @10:16AM (#23337498)
The "production version" of your script should be running in your system environment with system packages. pyenv and friends should be used for testing with different versions and making sure you don't accidentally depend on idiosyncrasies of your box.

The exception is if your python thingy is "the main thing" running on a server, i.e. your customer facing webapp.

My $.10 anyway

[ Parent | on HN ]
Re:Hypermodern Python by jalons on Thursday May 28, 2020 @10:21AM (#23337581)
I tend to agree with you that pyenv|pipenv|etc shouldn't be used for actual production usage.

This of course leads to other issues to solve, now that your development environment doesn't actually mirror production.

[ Parent | on HN ]
Re:Hypermodern Python by ses1984 on Thursday May 28, 2020 @10:23AM (#23337610)
How do you package your entire pyenv as one or more system packages?
[ Parent | on HN ]
Re:Hypermodern Python by im3w1l on Thursday May 28, 2020 @11:18AM (#23338340)
This isn't exactly what you are asking, but https://askubuntu.com/questions/90764/how-do-i-create-a-deb-...
[ Parent | on HN ]
Re:Hypermodern Python by hprotagonist on Thursday May 28, 2020 @11:02AM (#23338111)
pyinstaller, shiv, pex, docker: depending on use case, any of these may be appropriate.
[ Parent | on HN ]