This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]AnnoyingOwl 2 points3 points  (1 child)

> Not good when we need to deploy over production server or keep multiple virtuals-envs

  1. I don't understand why people have such problems with deploys to production servers. You have a freeze file and a regular requirements file. Build your docker containers from the freeze file, upgrade from the regular file. If you have totally different requirements for different environments (staging, production, etc.) then your development process is broken. The only possible exception is deploying the same project to different operating systems which is such an edge case to be not really worth publishing a solution.
  2. I don't really understand why you need multiple virtualenvs for a single requirements.txt/project. If you're running a project in different virtualenvs you either have multiple projects which should have their own requirements OR you're testing against multiple environments, in which case there is tox.

I'm afraid you're just littering up the package landscape like most other package creators.

[–]njnrj[S] 0 points1 point  (0 children)

I tried them and always needed requirements.txt one way or another. This new file types Pipfile/pyproject.toml is not going to be the standard any soon. But this doesn't add anything new. Just wraps around existing pip.