Policy on type annotations · Issue #1311 · RDFLib/rdflib (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Description

There are not many changes needed to make to get mypy to pass, and this opens the door to adding more type annotations which makes it easier for users of the library and helps prevents errors.

Are you open to a PR that adds support for mypy to the CI pipelines and makes changes needed in the codebase for it to pass? Any preferences for config and styling (i.e. import typing as t; import typing_extensions as te;)?

Would really make the experience of using rdflib easier IMO.