-
Notifications
You must be signed in to change notification settings - Fork 130
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
dist info folder follows dist name if one is supplied
- Loading branch information
Showing
1 changed file
with
2 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
639e622
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.
It may be possible to write .dist-info always and never bother with .egg-info
639e622
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.
I had a look at a few dist-info and egg-info folders on my own machine, and it looked easier to create the
installed-files.txt
file in a .egg-info folder than theRECORD
file in a .dist-info. E.g. RECORD includes sha256 hashes and file sizes, and I'm not sure what to do with those for a symlink. But I would like to write .dist-info directories if we can work it out.639e622
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.
It should be OK to just leave the hash and file sizes empty. https://www.python.org/dev/peps/pep-0376/#record
639e622
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, that PEP was the reference I was missing. I've had a go at implementing it: 1f4c9e4