ocamoss

6 ms·

1.
Pyrefly v1.3: More configurability and composable tensor shapes(pyrefly.org)
1 points by ocamoss 2d ago|0 comments
2.
by ocamoss 19d ago
https://news.ycombinator.com/item?id=49486172
3.
LSPs for LLMs(ianbarber.blog)
2 points by ocamoss 19d ago|0 comments
4.
What's type-coverage, and why should I care?(pyrefly.org)
2 points by ocamoss 22d ago|0 comments
5.
Cognition CEO denies report that SpaceX tried to acquire the startup(techcrunch.com)
4 points by ocamoss 28d ago|1 comments
6.
by ocamoss 1mo ago
I'm not impressed, it's an AI-generated apology. A quick skim of their code or commit history makes that obvious that this project's development methodology was clearly flawed, and only someone who turned their brain off woul
7.
Pyrefly 1.2 is here – feat. Bazel support, attrs, and type coverage checking(pyrefly.org)
5 points by ocamoss 1mo ago|0 comments
8.
2026 Python Type System and Tooling Survey(discuss.python.org)
2 points by ocamoss 1mo ago|0 comments
9.
by ocamoss 2mo ago
Maybe it's like Meta not releasing the big version of Llama 4 a year or two ago
10.
Define less, check more: Pyrefly now supports attrs(pyrefly.org)
6 points by ocamoss 2mo ago|0 comments
11.
Making Type Coverage Visible in Dify's CI(pyrefly.org)
1 points by ocamoss 3mo ago|0 comments
12.
Pyrefly v1.1 is here 27% faster, refactoring tools, tensor shapes(pyrefly.org)
5 points by ocamoss 3mo ago|0 comments
13.
How to get your agent to use Pyrefly for type checking [video](youtube.com)
4 points by ocamoss 3mo ago|0 comments
14.
Talk: Python Type Checking in Agentic Workflows [video](youtube.com)
2 points by ocamoss 3mo ago|0 comments
15.
Tensor Shapes in the Python Type System – Avik Chaudhuri – PyCon Typing Summit(pyrefly.org)
3 points by ocamoss 3mo ago|0 comments
16.
Type Checking in Agentic Workflows – Conner Nilsen – PyCon US 2026 Typing Summit(pyrefly.org)
3 points by ocamoss 3mo ago|0 comments
17.
Thoughts on Python Typing – Guido van Rossum – PyCon US 2026 Typing Summit [video](youtube.com)
9 points by ocamoss 3mo ago|0 comments
18.
by ocamoss 3mo ago
Everything? The blog post and PEP have almost nothing to do with each other lol
19.
by ocamoss 3mo ago
> commented/documented code at best Machine-checked documentation is always valuable, IMO
20.
by ocamoss 3mo ago
Running more type checkers isn't really about strictness. The main benefit to library maintainers is to make sure that their APIs are compatible with whatever tools their users run. This wouldn't really be an issue for most other
21.
Are you expected to run five Python type-checkers now?(pyrefly.org)
168 points by ocamoss 3mo ago|208 comments
22.
by ocamoss 4mo ago
There's an `implicit-any` error code
23.
by ocamoss 4mo ago
Maintainer here: that's not the expected experience. If you're able to share details about the project & file an issue on our Github, we can try to reproduce it and figure out what's going on.
24.
by ocamoss 4mo ago
thanks! :-)
25.
Pyrefly v1.0 is here (fast type checker and language server for Python)(pyrefly.org)
41 points by ocamoss 4mo ago|9 comments
26.
Right Types, Wrong Code: Surprising Bugs a Python Type Checker Catches(pyrefly.org)
3 points by ocamoss 4mo ago|0 comments
27.
Adding Pyrefly Type Checking to Your Agentic Loop(pyrefly.org)
2 points by ocamoss 4mo ago|0 comments
28.
Python Type Checker Comparison: Speed and Memory Usage(pyrefly.org)
2 points by ocamoss 5mo ago|0 comments
29.
How to Support Notebooks in a Language Server(pyrefly.org)
3 points by ocamoss 5mo ago|0 comments
30.
We chose Positron's Python type checker(positron.posit.co)
1 points by ocamoss 6mo ago|0 comments

More ›