You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This option of supporting types in a separate repo has the most overhead. How do you test the types? How do you keep them in sync with the icalendar repo? How do you synch releases between the the two repos?
Did you consider shipping the stub files with the icalendar distribution?
Oops, I omitted an important clause. I meant to say "This option of supporting types in a separate repo has the most overhead.
Anyway, there is a good discussion about the various options in the Python Typing docs. If you choose to use stub files, I don't see how keeping them in the same repo takes more work than in a separate repo. The latter sounds like more work to me.
This project adds the typing information for icalendar:
https://pypi.org/project/types-icalendar/
I think, we should document this in the installation section or related work if people are interested.
The text was updated successfully, but these errors were encountered: