-
Notifications
You must be signed in to change notification settings - Fork 543
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
Heads up: setuptools
contain files with whitespaces in their names
#617
Comments
Thanks for reaching out @abravalheri. In rules python we ignore files from installed packages that have spaces in them, which is what caused the runtime error with the Lorem file. We are aware of the issue but there ins't much we can do without upstream support for input files with spaces in bazel bazelbuild/bazel#4327 |
@hrfuller out of curiosity, where does rules_python ignore files with spaces in them. I'm noticing an issue where there's a directory of an installed package with spaces in it and that is causing a failure. Actually, I found it here: rules_python/python/repositories.bzl Line 209 in 0aa5ea4
Seems like we'd want to glob exclude directories as well |
Cross referencing pypa/setuptools#4605. As previously noted the workaround introduced by setuptools was not bulletproof and there was no guarantee that similar problems would not happen again due the limitation in |
Is there any workaround we can apply to be able to upgrade setuptools? |
Fixes #617. Modern `setuptools` versions contain files critical to setuptools functionality loaded proactively on module load that contain spaces. Bazel 7.4.0+ now supports files with spaces in their names. --------- Co-authored-by: Richard Levasseur <[email protected]> Co-authored-by: Richard Levasseur <[email protected]>
Hello, I would like to thank the authors, maintainers and all contributors for making such a cool project 😄
The reason why I was brought here is that recently we received a issue in the setuptools repository (pypa/setuptools#3072) that seems related to the fact that
bazel
does not support whitespaces in file names, and this might generate problems for people usingrules_python
.As noted in of the issue's comment, even before the recent changes,
setuptools
already had files containing whitespaces.My main objective here is just to give you guys a heads up, so you are aware about potential problems that might arise. (I understand that it might be a very complicated problem to solve and that it will take a long time...)
For the time being
setuptools
' lead developer have kindly provided a patch with a workaround, but it is difficult to guarantee that in the future other files containing whitespace in their names will not be added (specially via vendored dependencies).The text was updated successfully, but these errors were encountered: