Thulio Ferraz Assis
Thulio Ferraz Assis
The `.so` file is a symlink to the real versioned shared object. ``` lrwxrwxrwx 1 1000 1000 19 Aug 18 14:51 libpython3.9.so -> libpython3.9.so.1.0 -rwxrwxr-x 1 1000 1000 37M Jan...
The breaking change is acceptable. Gazelle can produce the right label for users who rely on it. I have not reviewed the code yet, thought. Will do next.
Sorry, I missed this PR. It ended up getting fixed here https://github.com/bazelbuild/rules_python/commit/2cdad9e18eda451e486737ff3cddc25ddd579c8e as I extracted the fix from the bigger change I was doing in https://github.com/bazelbuild/rules_python/commit/26526a501f5ee67b370744a76a3aa3cf98d212f4.
I still think the approach in the PR is correct. In practical terms, the difference between cc_library and cc_import is that cc_import only takes 1 file, so in the case...
This is related to https://github.com/bazelbuild/rules_python/pull/749. Please, see the related PRs in that description.
Please, reopen if running as non-root doesn't solve your problem.
I reopened. You can just update this PR so we keep the history.
I don't think making these `.pyc` files read-only makes sense as it does with the hermetic toolchain. Probably ignoring them from the glob is better in this case. @mattem what...
@mattem What do you think about this?
Following the decision that rules_python will not be test-framework-specific, this effort landed in https://github.com/aspect-build/rules_py/commit/6b1fcb753ec643d2418d538eb9d1f8a0159f65b5.