Re:Show HN: Update your requirements.txt file with Pur in Py...
by ubernostrum on Monday May 09, 2016 @07:19PM
(#11664046)
Some of my projects have double digits dependencies in their requirements.txt file so upgrading one at a time, even with pip list --outdated, would take too long.
The only solution I know of to this is to "unroll" all those dependencies into your own requirements.txt, and manage them the same way.
For some projects I work with this is actually the only option, since I have to use requirements files with hashes and those are all-or-nothing -- even a single dependency-of-a-dependency that doesn't specify a hash will break the install, so I have to track down all of them and get a hashed entry into my requirements file.
Re:Show HN: Update your requirements.txt file with Pur in Py...
by tedmiston on Monday May 09, 2016 @01:35PM
(#11661566)
My main project has ~30. But still I prefer to go one at a time, especially with a major version bump, for the sake of understanding exactly what breaks. Perhaps it's just a personal preference.
I prefer to upgrade everything and fix things that break. I've always been able to easily figure out which dependency was causing the exception after upgrading all packages, so no point in upgrading them individually for me.
Also, I don't manually update my packages. My build scripts do that for me from my requirements.txt file, so it makes sense to update requirements.txt first.