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

invalid literal for int() with base 10: 'unknown' with 3.8.0 rel #2047

Open
chenrui333 opened this issue Feb 23, 2025 · 3 comments
Open

invalid literal for int() with base 10: 'unknown' with 3.8.0 rel #2047

chenrui333 opened this issue Feb 23, 2025 · 3 comments
Milestone

Comments

@chenrui333
Copy link

chenrui333 commented Feb 23, 2025

Summary

While regression building ansible for homebrew, seeing some setuptools build failure as

      File "/private/tmp/pip-build-env-4sd8ymlv/normal/lib/python3.13/site-packages/wheel/_bdist_wheel.py", line 66, in <module>
        setuptools_major_version = int(setuptools.__version__.split(".")[0])
    ValueError: invalid literal for int() with base 10: 'unknown'
@Kami
Copy link
Member

Kami commented Mar 2, 2025

Thanks for reporting this.

I'm working on 3.9.0 release as we speak. I will start a voting thread on our mailing list by EOD and then hopefully we will get enough votes to publish the release by end of the week.

In the mean time, would it be possible for you to test latest trunk version and ensure the issue is fixed there?

Additionally, I would also like to add some safe guards to our CI to check issues like that automatically (we already have various dist and install checks in our pipeline, but it looks like they didn't catch this issue).

@Kami
Copy link
Member

Kami commented Mar 2, 2025

Here are dist + install checks we run today with all the supported versions on CI:

I'm just working on improving 1) to also use python -m build to create the dist tarball, but besides that, it's not yet clear to me how they haven't caught this issue.

@Kami Kami added this to the v3.9.0 milestone Mar 2, 2025
@Kami
Copy link
Member

Kami commented Mar 2, 2025

Per @chenrui333, a2114923adcaee6b022b43410 should fix the issue.

Additionally, I've included various improvements and additional build + dist + install checks (we already had a bunch, but sadly they some how diidn't catch this issue) as part of #2024 and other PRs.

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

No branches or pull requests

2 participants