Delays due to moon launch responsibilities are acceptable I guess 
5 Likes
As long as heâs not saying Laika ate his homework I guess thatâs a good enough excuse.
3 Likes
Any update?
Hey @CAM-Gerlach congrats for sending the rocket towards the Moon and not crashing it!
@thatch and I are back on the saddle and willing to help usher this through the finish line.
You have done an enormous amount of work there!
What can we do to help?
What is your latest PR?
3 Likes
One thing that came up in hatchâs issue tracker: Custom files under `dist-info` as part of a build hook ¡ Issue #620 ¡ pypa/hatch ¡ GitHub
Currently, this PEP defines a directory for storing license files under the .dist-info folder, in a sub-folder. In the discussions back when installerâs scope/API was being figured out, @dholth pointed out that (at least, by design) the files in dist-info should be treated like a dictionary of name-of-file: text-contents-of-file with no directories expected in there (and, that was somewhat baked-into the API design of installer).
Iâm mentioning this to elevate from those discussions that this is a semantic change weâd be making to how dist-info works, which could lock us out of potential data structures for storing metadata info in that, and other stuff like that, in the future.
I donât personally have strong opinions on this; the pip/installer side of this is relatively straightforward to deal with, and Iâm fairly certain that they already do â but Iâm not sure if everyone is fine with making this change for tooling. Itâs certainly worth calling out in the PEP as well. 
I also donât have a strong opinion here, beyond that we shouldnât just make assumptions, we should agree and document a position, one way or another.
The spec for the .dist-info directory says âAdditional installer-specific files may be presentâ. That doesnât explicitly prohibit directories, but it could be viewed as implying âfiles only, no directoriesâ. The wheel spec says nothing about this, as far as I can tell.
Does anyone know of any existing wheels or installed projects that have subdirectories in .dist-info? My database of PyPI data doesnât currently include wheel contents, so I canât check this myself.
If weâre allowing custom (whether backend or user defined) files in .dist-info, then we have a potential backward compatibility issue whenever we add new files. For example, the proposal here for a licenses directory would be incompatible with a custom file called licenses. This isnât mentioned in the PEPâs âBackward compatibilityâ section, by the way⌠A way round this would be to reserve all top level names (maybe explicitly noting that setuptools adds a number of non-standard names, which will remain for compatibility) and require all non-standard metadata files to go in a custom subdirectory. That means accepting that subdirectories are allowed.
2 Likes
Directories would be fine.
I would like to see new keys in the .data/ directory to mark categories of files.
2 Likes
Hey all, is there any update on this? Iâve now ran into multiple situations where having this PEP active would be helpful.
1 Like