-
Notifications
You must be signed in to change notification settings - Fork 7
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
setuptools==68.2.0 breaks colcon-python-setup-py #56
Comments
Is this a 100% hit rate with |
It's 100% hit rate with |
That makes me think that Any other suggestions? |
Are there backwards-compatible changes that can be made to this package that avoids invoking setup.py as a CLI, as this is a deprecated feature? |
Remove when colcon/colcon-python-setup-py#56 is solved
Remove when colcon/colcon-python-setup-py#56 is solved
Remove when colcon/colcon-python-setup-py#56 is solved
Remove when colcon/colcon-python-setup-py#56 is solved
Remove when colcon/colcon-python-setup-py#56 is solved
Remove when colcon/colcon-python-setup-py#56 is solved (cherry picked from commit d0e63d9)
Remove when colcon/colcon-python-setup-py#56 is solved (cherry picked from commit d0e63d9)
Remove when colcon/colcon-python-setup-py#56 is solved (cherry picked from commit d0e63d9) Co-authored-by: Pablo Garrido <[email protected]>
Remove when colcon/colcon-python-setup-py#56 is solved (cherry picked from commit d0e63d9) Co-authored-by: Pablo Garrido <[email protected]>
Any updates on this? |
The solution is to use a different version of setuptools. The bug only exists in The intermediate issue has to do with the way we're extracting information from setuptools. There are PRs open on this repository with different approaches to that, but I'm not convinced that they would have avoided the 68.2.0 setuptools bug either. |
setuptools==68.2.0 breaks colcon-python-setup-py with the following:
Pinning setuptools==68.1.2 fixed this issue temporarily but doesn't fix the root cause.
There is a discussion on colon-core about setup.py deprecation colcon/colcon-core#454 but doesn't look like its going to happen soon
The text was updated successfully, but these errors were encountered: