future-oxygen-10553
06/15/2023, 2:42 PM{
"artifacts": [
{
"algorithm": "sha256",
"hash": "72264f1594e547c6ac986c694a0c7617b62bd45fb6e806d81ddb5c46b538dfec",
"url": "git+<https://github.com/photocrowd/django-cursor-pagination@master>"
}
],
"project_name": "django-cursor-pagination",
"requires_dists": [],
"requires_python": null,
"version": "0.2.1"
},
For reasons, I’m using pex3 lock export
to turn this into a pip-style requirements.txt with hashes. The corresponding output in the export file is:
django-cursor-pagination==0.2.1 \
--hash=sha256:72264f1594e547c6ac986c694a0c7617b62bd45fb6e806d81ddb5c46b538dfec
which then pulls the file from our Artifactory index (which has a different hash) than the branch from the repo. Is this intentional on the part of pex to omit the URL? How can I tell Pex to include that part?curved-television-6568
06/15/2023, 2:47 PMfuture-oxygen-10553
06/15/2023, 2:48 PMcurved-television-6568
06/15/2023, 2:49 PMfuture-oxygen-10553
06/15/2023, 2:49 PMcurved-television-6568
06/15/2023, 2:49 PMcurved-television-6568
06/15/2023, 2:50 PMenough-analyst-54434
06/15/2023, 2:58 PMenough-analyst-54434
06/15/2023, 2:59 PM@master
?enough-analyst-54434
06/15/2023, 2:59 PMfuture-oxygen-10553
06/15/2023, 3:00 PMfuture-oxygen-10553
06/15/2023, 3:03 PMCollecting git+<https://github.com/photocrowd/django-cursor-pagination@master> (from -r python-reqs.txt (line 756))
ERROR: Can't verify hashes for these requirements because we don't have a way to hash version control repositories:
git+<https://github.com/photocrowd/django-cursor-pagination@master> (from -r python-reqs.txt (line 756))
future-oxygen-10553
06/15/2023, 3:03 PMenough-analyst-54434
06/15/2023, 3:18 PMenough-analyst-54434
06/15/2023, 3:19 PMfuture-oxygen-10553
06/15/2023, 3:19 PMfuture-oxygen-10553
06/15/2023, 3:20 PMfuture-oxygen-10553
06/15/2023, 3:21 PMenough-analyst-54434
06/15/2023, 3:37 PMfuture-oxygen-10553
06/15/2023, 3:39 PMenough-analyst-54434
06/15/2023, 3:39 PMpex3 venv create --lock my-lock [reqs] -d right-here.venv
,enough-analyst-54434
06/15/2023, 3:40 PMenough-analyst-54434
06/15/2023, 3:41 PMenough-analyst-54434
06/15/2023, 3:43 PMWe’re not actually installing directly with URL requirements, just curious if that should be a supported feature and whether I should file an issue to fix this.It might be possible, but I think its not an appropriate feature. I used pip-compile as a point of comparison since it's ~industry standard for Pip workflows that want to lock with hashed requirements files.
future-oxygen-10553
06/15/2023, 3:44 PMfuture-oxygen-10553
06/15/2023, 3:44 PMpip
versionsfuture-oxygen-10553
06/15/2023, 3:45 PMenough-analyst-54434
06/15/2023, 3:45 PMfuture-oxygen-10553
06/15/2023, 3:46 PMfuture-oxygen-10553
06/15/2023, 3:52 PMfuture-oxygen-10553
06/15/2023, 3:53 PMenough-analyst-54434
06/15/2023, 3:55 PM--help
, but try --python
.enough-analyst-54434
06/15/2023, 3:56 PMfuture-oxygen-10553
06/15/2023, 3:56 PM