Rebase pylock paths for nested exports#133
Closed
zaniebot wants to merge 1 commit into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Exporting a lock to
locks/pylock.*.tomlcan preserve a project-relativedeppath, so a consumer resolveslocks/depand fails. Rebase relative directory and archive paths against the output lockfile's directory.See the
pylock.tomldirectory-path and archive-path rules.This is related to the portability report uv#16299: rebase existing relative paths without converting deliberately absolute paths, preserving the intent established in uv#18176.
Moved to: astral-sh/uv-dev#131.