Log file Viewer

[12:49:05] <exarkun> Anyone know what the deal is here? https://gist.github.com/exarkun/4ddd30f1e2ca585c86a77d963f318be1

[13:05:06] <tos9> exarkun: usually IIRC that tends to be bad cache state

[13:05:21] <tos9> exarkun: is it repeatable?

[13:05:26] <tos9> (for you, not me)

[13:52:58] <jenner> heya

[13:53:19] <jenner> guys, are there any docs on how to run warehouse without docker?

[13:58:09] <jenner> nvm, I just follow the commands in Dockerfile

[17:32:26] <kushal> when we do pip install PackageA, will pip install the dependencies based on the requirements.txt of ProjectA?

[17:42:13] <dude-x> kushal no, based on what's in install_requires in setup.py

[17:43:27] <kushal> dude-x, Okay, thanks.

[17:43:53] <kushal> dude-x, we (in a project) were discussing if we should pin the versions on the install_requires or not.

[17:49:31] <dude-x> kushal the recommendation is not to pin versions, unless necessary

[17:50:01] <kushal> yes, I remember that part.

[17:50:04] <kushal> https://packaging.python.org/discussions/install-requires-vs-requirements/

[18:29:30] <GothAlice> On my own side, we pin everything, though we try to range pin rather than pin to specific versions. E.g. if a package has guaranteed that patch releases (1.0.x) and single feature releases (1.x) will not break compatibility, if the current version is 1.2.3, we pin <1.3 in setup.py.

[18:29:41] <GothAlice> kushal: ^

[18:30:05] <GothAlice> Er, <1.4, rather.

[18:31:41] <GothAlice> At 1.2.3, 1.3 may introduce deprecation warnings, but won’t actually eliminate the deprecated material until the subsequent major or feature release. (2.0 or 1.4 respectively.)