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

Documentation: Add link to types-icalendar #762

Open
2 tasks
niccokunzmann opened this issue Dec 31, 2024 · 3 comments
Open
2 tasks

Documentation: Add link to types-icalendar #762

niccokunzmann opened this issue Dec 31, 2024 · 3 comments

Comments

@niccokunzmann
Copy link
Member

niccokunzmann commented Dec 31, 2024

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.

  • link to project
  • describe its purpose
@niccokunzmann niccokunzmann changed the title Add link to types-icalendar Documentation: Add link to types-icalendar Dec 31, 2024
@stevepiercy
Copy link
Member

stevepiercy commented Dec 31, 2024

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?

Refs:

@niccokunzmann
Copy link
Member Author

Your idea is nice. However it takes work, so the proposed change helps for now and if someone wants to take on your idea, it can be implemented! ❤️

@stevepiercy
Copy link
Member

stevepiercy commented Dec 31, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants