Fix: git subdirectory dependencies fail to resolve with a TypeError on name #5479
Conversation
This file contains 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
FAILED tests/puzzle/test_provider.py::test_search_for_vcs_hyphenated_name - TypeError: expected string or bytes-like object
Closed
|
master branch has resolved this issue |
|
@skairunner happy for a test case to be added. :) |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Pull Request Check List
Resolves: #4678
This is a resurrection of #4922, fixing an issue with package name discovery on git repos with subdirectories. All I've done is merge master and clean up some dust.
It appears that the test written by steved works correctly, as disabling the fix causes it to fail. I also am unsure whether _pep517_metadata is actually related to the bug, I took a cursory look and it seemed unrelated. If the current unit test is unacceptable please tell me.