News for hackers. Stuff that matters.
Re:Pipfile for Python by Animats on Tuesday November 22, 2016 @02:15AM (#13012267)
If you need old-version retrieval on a routine basis, library regression testing has a problem. This gives package developers an excuse to break backwards compatibility. Historically, Python has avoided that, except for the Python 3 debacle.
Re:Pipfile for Python by Groxx on Tuesday November 22, 2016 @03:09AM (#13012506)
I'm a bit confused as well, unless you're referring to "installing libs at any version except HEAD", in which case I vehemently disagree with you. Deterministic builds are a must-have for production systems.
Re:Pipfile for Python by icebraining on Tuesday November 22, 2016 @04:41AM (#13012902)
The question is whether that should be included in the project, or as a configuration of the deployment tool.
Re:Pipfile for Python by yxhuvud on Tuesday November 22, 2016 @05:16AM (#13013037)
There is no question. If it isn't included in the project, then any errors you get are not repeatable.
Re:Pipfile for Python by icebraining on Tuesday November 22, 2016 @05:23AM (#13013064)
Why can't you get the versions in question from the origin of the error (deployment config if it's an internal error, or asking the user if it's an external report)?
Re:Pipfile for Python by yxhuvud on Tuesday November 22, 2016 @05:41AM (#13013142)
It is certainly possible, but adding a manual step for something that has no reason not to be automatic doesn't make sense. Yes, you can certainly choose to do more manual work for no reason, but why would you?

And if you don't want that (for example if you distribute a library), you can still distribute the project without the lockfile, and then have the users distribute the lockfile back to you to get a repeatable error.

Re:Pipfile for Python by civilian on Tuesday November 22, 2016 @02:37AM (#13012352)
Sorry, maybe it's late, but I don't follow. Can you elaborate?
Re:Pipfile for Python by chaosagent on Tuesday November 22, 2016 @04:05AM (#13012759)
They're probably claiming that using a lockfile excessively would put less incentive on library developers to keep backwards compatibility, because nothing would break if the user doesn't explicitly upgrade.