You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 19, 2024. It is now read-only.
I would like to run peep in a way that acquires all the tarballs from the requirements file, possibly by downloading them or pulling from a cache, hashes them, and reports if everything matches, but doesn't actually install them. It would be nice if this additionally checked that the requirements tree was complete. This would be a great check to put in a CI job, and would give me confidence that I didn't break something when I changed the requirements file.
PS: It would be ever better (especially for the CI job) if running peep check (or whatever it is called) followed by peep install wouldn't download everything twice somehow.
The text was updated successfully, but these errors were encountered:
@mythmon - Maybe if it put all the files in checks in /tmp, then checks there before re-downloading you could avoid an extra download? For the rest, this sounds like a new command such as ./peep check-reqs or something.
That's exactly what I want, a new command. In a normal installation, Peep will only download things once right now. This Issue is for a check command (or a dry run flag, or something), that will just check requirements.
The second part is that once these are all downloaded it would be a shame if they got downloaded a second time if I proceeded to actually install them. The pip download cache can probably deal with that.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would like to run peep in a way that acquires all the tarballs from the requirements file, possibly by downloading them or pulling from a cache, hashes them, and reports if everything matches, but doesn't actually install them. It would be nice if this additionally checked that the requirements tree was complete. This would be a great check to put in a CI job, and would give me confidence that I didn't break something when I changed the requirements file.
PS: It would be ever better (especially for the CI job) if running
peep check
(or whatever it is called) followed bypeep install
wouldn't download everything twice somehow.The text was updated successfully, but these errors were encountered: