Skip to content

Handle long filenames on Windows in a few more places.#2781

Merged
jayconrod merged 1 commit intobazel-contrib:masterfrom
pmuetschard:win_fix
Jan 11, 2021
Merged

Handle long filenames on Windows in a few more places.#2781
jayconrod merged 1 commit intobazel-contrib:masterfrom
pmuetschard:win_fix

Conversation

@pmuetschard
Copy link
Copy Markdown
Contributor

C.f. #1382

What type of PR is this?
Bug fix

What does this PR do? Why is it needed?
Makes rules_go work on Windows with long filenames.

Copy link
Copy Markdown
Collaborator

@jayconrod jayconrod 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, thanks.

@jayconrod jayconrod merged commit c403e77 into bazel-contrib:master Jan 11, 2021
@pmuetschard pmuetschard deleted the win_fix branch January 12, 2021 00:50
yushan26 pushed a commit to yushan26/rules_go that referenced this pull request Jun 16, 2025
This PR moves the parsing of `Requires-Dist` to the loading phase
within the `whl_library_targets_from_requires` macro. The original
`whl_library_targets` macro has been left unchanged so that I don't have
to reinvent the unit tests - it is well covered under tests.

Before this PR we had to wire the `target_platforms` via the
`experimental_target_platforms` attr in the `whl_library`, which means
that whenever this would change (e.g. the minor Python version changes),
the wheel would be re-extracted even though the final result may be the
same.

This refactor uncovered that the dependency graph creation was incorrect
if we had multiple target Python versions due to various heuristics that
this had. In hindsight I had them to make the generated `BUILD.bazel`
files more readable when the unit test coverage was not great. Now this
is unnecessary and since everything is happening in Starlark I thought
that having a simpler algorithm that does the right thing always is the
best way.

This also cleans up the code by removing left over TODO notes or code
that no longer make sense.

Work towards bazel-contrib#260, bazel-contrib#2319
yushan26 pushed a commit to yushan26/rules_go that referenced this pull request Jun 16, 2025
…#2831)

This just adds the code back at the original state before the following
PRs have been made to remove them: bazel-contrib#2629, bazel-contrib#2781. This has not been
hooked up yet in `evaluate_markers` and `whl_library` yet and I'll need
extra PRs to do that.

No CHANGELOG entries for now, will be done once the integration is back.

Work towards bazel-contrib#2830
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants