-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate validation of RECORD
#147
Conversation
Thanks for this PR @BlueGlassBlock, and appreciate your patience on this. I'm doing a brain-dump TBH, so apologies for the somewhat unpolished phrasing. Instintively, I feel like it's valuable to have validation live outside of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for filing this PR @BlueGlassBlock! I really appreciate it.
I do have a few suggestions.
I think this is my first review on a PR by you so I'll clarify that any comment starting with nit:
is something that I don't consider being worth an extended discussion. It's more of a nit-pick and I don't think it's worth having an extended discussion on that -- if you disagree with my suggestion or don't really wanna bother with that suggestion, please feel welcome to mark it as resolved without a discussion. :)
Add corresponding doc to `WheelSource.validate`
switch to `validation_error` property Fix `RECORD.jws`
Modified quite a bit. Please review and tell me what to change :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One last thing!
Synced and changed. :) |
Oh, maybe the CLI should be updated too? But I think that should be separated into another PR. |
Could you remove 14cefe1? I'd prefer to handle that in a separate PR. :) |
Force pushed. That commit is saved on another branch. |
This PR adds
validate_record
method toWheelSource
and a boolean parametervalidate_record
toinstall
function.Currently,
validate_record
implementation ofWheelFile
checks the presence ofRECORD
, entries of files in the wheel, and whether there's a corresponding hash for the entry. (RECORD.p7s
andRECORD.jwt
are ignored from here)validate_record
parameter ofinstall
indicates whetherWheelSource.validate_record
will be called during installation.I've already modified the
fancy_wheel
builder fromconftest.py
to include hashes (and sizes) of files.The names and places are quite different from #100 and #105, please inform me about what I need to change.
Please review and request changes so that I can push this PR forward 😄
The line ending seems messed up, so please squash when it's ready for merge