Hmm oddly, using a PEX lockfile when locking `absl...
# development
b
Hmm oddly, using a PEX lockfile when locking
absl-py
it uses
absl-py==0.10
instead of
absl-py==0.10.0
. https://pypi.org/project/absl-py/0.10.0 lists
0.10.0
and the wheel's
METADATA
lists
0.10.0
🧐
Not breaking anything but my diff is funky
e
I'd think https://github.com/pantsbuild/pex/pull/1951 would address that.
b
Ah that's likely the case. will confirm tomorrow
Looks like I was on 2.1.113
Upgrading to 114 doesn't change it
e
Ok. If you can file an issue I can take a look. The short of it is though that both project names and versions are normalized per PEP 440 and 508 internally for all comparisons. Clearly there are external leaks. These should never be substantive, since they are just normalized, but it would be good to meet reasonable expectations.
b
Will do
e
And if you can drill down on diff is funky, that would be helpful - namely including a diff and explicating what would be better.
b
That part is easy.
pip-compile
puts
0.10.0
in my
requirements.txt
, now using
pex
I get
0.10
, so my diff says that line changed, when it did, but the requirement didnt
It's a slightly annoying red herring
e
Ok, that's where explication will be very helpful, You say lockfile, I'll be nowhere near the exported requirements.txt. If you just explain all your steps and where you arrive at funk, in detail, that will be appreciated.
b
Yeah sorry, mismatched terminology.
requirements.txt
is also a lockfile in this case 🙂 Issue incoming