Skip to content
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

Handles name == None case (re: issue #4311, #3628) #4702

Closed
wants to merge 1 commit into from

Conversation

aalok-sathe
Copy link

@aalok-sathe aalok-sathe commented Nov 2, 2021

Addresses issue #4311 and others, related to canonicalize_name throwing TypeError because a str or bytes like object was expected.

Pull Request Check List

Resolves: #4311, #3628

  • Added tests for changed code.
  • Updated documentation for changed code.

Addresses issue python-poetry#4311 and others, related to `canonicalize_name` throwing TypeError because a str or bytes like object was expected.
@aalok-sathe aalok-sathe changed the title Handles name == None case (re: issue #4311) Handles name == None case (re: issue #4311, #3628) Nov 3, 2021
Copy link
Member

@neersighted neersighted left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure this is the best way to solve this problem -- one one hand, poetry should probably be more resilient to unexpected problems like empty egg/dist-info. On the other hand, if this is a poetry-managed environment, it's likely that poetry is creating these problems for itself.

I'll have to think about this one personally, after doing some digging and reproduction work.

At the very least, to be merge-able, we need to create a reproduction and regression test for this change.

@aalok-sathe
Copy link
Author

@neersighted You're probably right; I was looking for a quick fix at the time to remove a blockade in a project. Unfortunately I am not able to spend enough time on this at the moment to come up with a better solution.

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

got a expected string or bytes-like object when running install
2 participants