Skip to content

Add basic Pyrefly configuration to pyproject.toml#4494

Merged
svartkanin merged 1 commit intoarchlinux:masterfrom
correctmost:cm/add-pyrefly-config
Apr 29, 2026
Merged

Add basic Pyrefly configuration to pyproject.toml#4494
svartkanin merged 1 commit intoarchlinux:masterfrom
correctmost:cm/add-pyrefly-config

Conversation

@correctmost
Copy link
Copy Markdown
Contributor

PR Description:

This makes it easier to use the Pyrefly type checker with various IDEs.

This makes it easier to use the Pyrefly type checker with various
IDEs.
@correctmost correctmost requested a review from Torxed as a code owner April 28, 2026 13:00
@svartkanin
Copy link
Copy Markdown
Collaborator

I'm not against different type checkers, but I'd be good to settle on one. Currently we're using mypy heavily, but there is ty as well (not sure how mature it is at this point). Would it make sense to evaluate them properly on the code base and stick to one?

@correctmost
Copy link
Copy Markdown
Contributor Author

I think it's best to stick with mypy for now:

  • mypy - stable and actively maintained
  • Pyright - stable, but less actively maintained
  • Pyrefly, ty, and zuban - still in beta

The newer type checkers have language server features, so I would expect more developers to start using them while working on archinstall. I use them with VS Code and thought it would be helpful to add configs that reduce warning noise.

I think it's okay to commit basic configs for tools like Pyright and Pyrefly to support local development, even if the tools don't end up running on CI.

@svartkanin svartkanin merged commit 05560d2 into archlinux:master Apr 29, 2026
9 checks passed
@correctmost correctmost deleted the cm/add-pyrefly-config branch April 29, 2026 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants