Log file Viewer

[11:32:46] <MrJones> I dumped the output of pip freeze into a constraints.txt and specified it with -c, to pretty much pin the status quo and only allow new packages to be installed

[11:32:58] <MrJones> now I'm getting this error: Could not find a version that satisfies the requirement reportlab==3.4.16 (from -c constraints.txt (line 7)) (from versions: 2.3, 2.4, 2.5, 2.6, 2.7, 3.0, 3.1.8, 3.1.44, 3.2.0, 3.3.0, 3.4.0, 3.5.0, 3.5.1, 3.5.2, 3.5.4, 3.5.5, 3.5.6, 3.5.8, 3.5.9, 3.5.10, 3.5.11, 3.5.12, 3.5.13)

[11:33:15] <MrJones> but reportlab==3.4.16 is a literal quote from pip freeze. is this a pip bug? I just don't understand at all why I would say that

[11:33:54] <MrJones> what is there to satisfy from any external version download if 3.4.16 is already installed? why is it even looking for that, when it's already there? this makes no sense to me at all

[11:35:04] <MrJones> it also redownloads & reinstalls Pillow 5.2.0 for some reason, even though it's already listed in pip freeze

[11:35:37] <MrJones> (these are all dependencies from a "pip install ." call of a project of mine with a setup.py, so it's not like I ran "pip install Pillow" or anything which I would expect it to prompt to force a reinstall)

[11:55:16] <MrJones> basically, why would an install_requires dependency ever be installed again if it's already listed in pip freeze in that exact same version? that is my question

[12:05:39] <MrJones> do I need --no-build-isolation to prevent that, maybe?

[12:24:09] <MrJones> hmmm didn't help. https://paste.fedoraproject.org/paste/aHCckWssprpt4qaPQkj4NQ/raw I mean look at this, isn't that at least a little weird? like, why would it be bothered if it's already around & installed? is this really intended behavior, and is there a way to change it?