[im3w1l]

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

[jalons]

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.

[ses1984]

How do you package your entire pyenv as one or more system packages?

[im3w1l]

This isn't exactly what you are asking, but https://askubuntu.com/questions/90764/how-do-i-create-a-deb-...

[hprotagonist]

pyinstaller, shiv, pex, docker: depending on use case, any of these may be appropriate.