Skip to content
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

Ignore vendored .dist-info folders. #1972

Merged
merged 2 commits into from
Aug 27, 2024

Conversation

freakboy3742
Copy link
Member

Fixes #1970.

setuptools has always included vendored downstream libraries; however, as of 73.0, they started including a vendored copy of the .dist-info folder as well. This breaks Briefcase's binary package search mechanism.

This PR modifies binary package search to do a shallow search, rather than a deep search.

PR Checklist:

  • All new features have been tested
  • All new features have been documented
  • I have read the CONTRIBUTING.md file
  • I will abide by the code of conduct

Copy link
Member

@rmartin16 rmartin16 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good; small suggestion for changenote but works for me.

Two notes:

  • I have a list of scenarios I want to include in some future build-bot system; I'll add packaging the top XXX number of PyPI packages with Briefcase to the list. Should probably just open a proper issue.
  • Also, it may be good to annotate these warnings with some kind of explanation...just given that I expect most users may not fully understand everything that is happening and what these messages are trying to communicate.
    image

changes/1970.bugfix.rst Outdated Show resolved Hide resolved
Co-authored-by: Russell Martin <russell@rjm.li>
@freakboy3742
Copy link
Member Author

  • I have a list of scenarios I want to include in some future build-bot system; I'll add packaging the top XXX number of PyPI packages with Briefcase to the list. Should probably just open a proper issue.

Agreed this would be good to thing to verify - if not "top XXX", then at least "packages we know are common and/or problematic".

  • Also, it may be good to annotate these warnings with some kind of explanation...just given that I expect most users may not fully understand everything that is happening and what these messages are trying to communicate.

Yeah - agreed these messages aren't especially clear. Some of them we could possibly even put into an ignore list - .h files, for example, won't be used in a bundled app; and .a files are just taking up space, and can almost certainly be deleted without impact. At the very least, we can improve the message that is output, possibly with a link to a FAQ in the macOS guide about what is going on.

@freakboy3742
Copy link
Member Author

@rmartin16 FYI I've opened #1973 and #1974 to track these two ideas.

@freakboy3742 freakboy3742 merged commit af1430a into beeware:main Aug 27, 2024
52 checks passed
@freakboy3742 freakboy3742 deleted the shallow-distinfo branch August 27, 2024 04:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot package setuptools>=73.0.0 for universal builds for macOS
2 participants