.DS_Store files are created by the system for every directory on MacOS. However, I would not expect them to exist within a wheel. Yet, after building a wheel of my package (which we'll call foobar), I end up with the following file structure within the root of the wheel:
- foobar/
- Foobar-3.1.dist-info/
- .DS_Store
Note that .DS_Store files do not exist in any of the sub-directories, only in the root directory. The only other mention of .DS_Store in the wheel is an entry in Foobar-3.1.dist-info/RECORD which lists the file along with all other files included in the wheel:
.DS_Store,sha256=OfLZLRvDHtaZ3tF9i25UoJtjltEuP1xdggL5XdUtokg,6148
I wondered if I had perhaps inadvertently added the file by inspecting the wheel after creating it. However, the file being listed in RECORD suggests is was added by the build tool. Of course, as .DS_Store files are hidden on MacOS, I didn't notice the file when inspecting the wheel. It was only after a user reported an issue that it came to my attention. According to the user, "This triggers an error during installation because we are blocking this file name on our storage system."
Wouldn't it make sense for the wheel builder to exclude .DS_Store files?
Or, is there a way I can tell the wheel builder to exclude them?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4