-
Notifications
You must be signed in to change notification settings - Fork 27
fix type annotation #58
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
base: master
Are you sure you want to change the base?
Conversation
Thanks! You're right, but I believe that the fix should be in line 146
(str is a valid input too) |
Right, I missed that. Changed to allow string as well. |
Ah, sorry, I missed your point. I guess any iterable of strings OR string should be accepted, then the code you copied will convert it to a tuple. |
Yes, sounds good.
…On Fri, Jan 10, 2025 at 17:40 Marcell Kovács ***@***.***> wrote:
Ah, sorry, I missed your point. I guess any iterable of strings OR string
should be accepted, then the code you copied will convert it to a tuple.
—
Reply to this email directly, view it on GitHub
<#58 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFSSSEFD5P43JPDNDI24YD2J7ZZJAVCNFSM6AAAAABU6V7LPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBTGIYTSNZSHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I also adjusted |
Sorry, my code should have been |
I also missed that |
Ok, I think None has a special meaning, and converting None to () messes it up down the line. Sorry, it's been a while since I worked on this code, so I forgot the nuances. If you prefer, I can try to finish the PR myself. But you're of course welcome to do it yourself. |
The type annotation is wrong here, it is expected to be a tuple