home.social

#pyrefly — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pyrefly, aggregated by home.social.

fetched live
  1. @Reuven
    I expect a similar post about , and or soon ;-D

  2. I wanted to migrate one of my #Python packages from #mypy to #ty and #pyrefly. I handed this task over to #Claude, and at the end I asked it to write out some guidance on how to perform it most efficiently. So what follows is AI-generated 'slop'.

    #aicodingagents
    dev.to/ldrscke/migrate-from-my

  3. I wanted to migrate one of my packages from to and . I handed this task over to , and at the end I asked it to write out some guidance on how to perform it most efficiently. So what follows is AI-generated 'slop'.


    dev.to/ldrscke/migrate-from-my

  4. I wanted to migrate one of my #Python packages from #mypy to #ty and #pyrefly. I handed this task over to #Claude, and at the end I asked it to write out some guidance on how to perform it most efficiently. So what follows is AI-generated 'slop'.

    #aicodingagents
    dev.to/ldrscke/migrate-from-my

  5. Lessons from #Pyre that Shaped #Pyrefly

    "Building a #typechecker is ultimately a deeply pragmatic exercise. It is easy to get lost in the weeds of type theory, but at the end of the day, we are building a tool that developers have to live with every single day. We chose usability over absolute soundness, and we built an architecture that embraces #Python's dynamism instead of fighting it."

    pyrefly.org/blog/lessons-from-

    @pythonbytes @mkennedy

  6. Lessons from that Shaped

    "Building a is ultimately a deeply pragmatic exercise. It is easy to get lost in the weeds of type theory, but at the end of the day, we are building a tool that developers have to live with every single day. We chose usability over absolute soundness, and we built an architecture that embraces 's dynamism instead of fighting it."

    pyrefly.org/blog/lessons-from-

    @pythonbytes @mkennedy

  7. Lessons from #Pyre that Shaped #Pyrefly

    "Building a #typechecker is ultimately a deeply pragmatic exercise. It is easy to get lost in the weeds of type theory, but at the end of the day, we are building a tool that developers have to live with every single day. We chose usability over absolute soundness, and we built an architecture that embraces #Python's dynamism instead of fighting it."

    pyrefly.org/blog/lessons-from-

    @pythonbytes @mkennedy

  8. 🔍💥 Welcome to the #Python #type checker showdown nobody asked for! Watch as the nerds at #Pyrefly unleash a flood of #buzzwords, promising type-checking utopia while drowning developers in a sea of overly-complicated syntax. 🤯 Spoiler: nobody cares about your #type #completeness score, Pyrefly. 🙄
    pyrefly.org/blog/typing-confor #Checking #Developer #Struggles #HackerNews #ngated

  9. 🔍💥 Welcome to the #Python #type checker showdown nobody asked for! Watch as the nerds at #Pyrefly unleash a flood of #buzzwords, promising type-checking utopia while drowning developers in a sea of overly-complicated syntax. 🤯 Spoiler: nobody cares about your #type #completeness score, Pyrefly. 🙄
    pyrefly.org/blog/typing-confor #Checking #Developer #Struggles #HackerNews #ngated

  10. 🔍💥 Welcome to the #Python #type checker showdown nobody asked for! Watch as the nerds at #Pyrefly unleash a flood of #buzzwords, promising type-checking utopia while drowning developers in a sea of overly-complicated syntax. 🤯 Spoiler: nobody cares about your #type #completeness score, Pyrefly. 🙄
    pyrefly.org/blog/typing-confor #Checking #Developer #Struggles #HackerNews #ngated

  11. 🚀 Pyrefly: the trailblazing type checker that'll make your #IDE shine like a supernova! If you're eagerly waiting to compare empty containers while flying through type hints at light speed, #Pyrefly has got you covered. 💫 Who knew #debugging #Python could be this thrilling? 🙄
    pyrefly.org/blog/container-inf #TypeChecker #Innovation #HackerNews #ngated

  12. 🚀 Pyrefly: the trailblazing type checker that'll make your #IDE shine like a supernova! If you're eagerly waiting to compare empty containers while flying through type hints at light speed, #Pyrefly has got you covered. 💫 Who knew #debugging #Python could be this thrilling? 🙄
    pyrefly.org/blog/container-inf #TypeChecker #Innovation #HackerNews #ngated

  13. 🚀 Pyrefly: the trailblazing type checker that'll make your #IDE shine like a supernova! If you're eagerly waiting to compare empty containers while flying through type hints at light speed, #Pyrefly has got you covered. 💫 Who knew #debugging #Python could be this thrilling? 🙄
    pyrefly.org/blog/container-inf #TypeChecker #Innovation #HackerNews #ngated

  14. Pyrefly giới thiệu 4 mẫu thu hẹp loại dữ liệu giúp kiểm tra kiểu trong Python trực quan hơn qua: 1. hasattr/getattr, 2. tagged unions, 3. kiểm tra độ dài tuple, 4. lưu điều kiện trong biến. Pyrefly hiện là trình kiểm tra kiểu duy nhất hỗ trợ đầy đủ các mẫu này. Tìm hiểu thêm tại trang chủ hoặc GitHub. #Python #TypeChecking #Pyrefly #LậpTrình #KiểmTraKiểu

    reddit.com/r/programming/comme

  15. With high-performance #Python type checkers like #Pyright, #Pyrefly, and #ty now available, what's the value proposition of #Mypy? Is it the reference implementation? Or does Mypy still have the most features? I'm not trying to knock Mypy, I'm genuinely asking because I don't know.

  16. With high-performance #Python type checkers like #Pyright, #Pyrefly, and #ty now available, what's the value proposition of #Mypy? Is it the reference implementation? Or does Mypy still have the most features? I'm not trying to knock Mypy, I'm genuinely asking because I don't know.

  17. With high-performance #Python type checkers like #Pyright, #Pyrefly, and #ty now available, what's the value proposition of #Mypy? Is it the reference implementation? Or does Mypy still have the most features? I'm not trying to knock Mypy, I'm genuinely asking because I don't know.

  18. Let's say you want to do good type-checking for the #Python project you're working on. You pick a tool, maybe you use it as an #LSP also (so your editor can show you errors, too). As an example, I'm using #Ty at the moment. There's three places this might be installed: globally (e.g., `brew install ty`), as a dev-only dependency inside your project (e.g., `uv add --dev ty`), or -- and this one might surprise you -- it might only be used and installed by `pre-commit`, which builds a separate environment for each needed tool (which is great for instance where I use `codespell` as a `pre-commit` check, which seems to need some higher version of Python than my actual project).

    Where should you install it?

    If you're the only one on your team running it, globally is fine. If more than just you, then absolutely as a dev-only dependency inside your project ... and **maybe** globally as well.

    The only real problem is updates. If you use a reasonable global install scheme, updates will be easy. They're less easy inside your project or in `pre-commit`. And you might care one way or the other! I **don't** want updates! I **do** want updates!

    As for Python type-checking, `ty` seems good so far, but not enough experience with it yet. `basedpyright`, `pyrefly`, and `ruff` all good. These four are my favorites.

    #BasedPyright #Pyrefly #Ruff #PreCommit #CodeSpell #Homebrew

  19. Let's say you want to do good type-checking for the project you're working on. You pick a tool, maybe you use it as an also (so your editor can show you errors, too). As an example, I'm using at the moment. There's three places this might be installed: globally (e.g., `brew install ty`), as a dev-only dependency inside your project (e.g., `uv add --dev ty`), or -- and this one might surprise you -- it might only be used and installed by `pre-commit`, which builds a separate environment for each needed tool (which is great for instance where I use `codespell` as a `pre-commit` check, which seems to need some higher version of Python than my actual project).

    Where should you install it?

    If you're the only one on your team running it, globally is fine. If more than just you, then absolutely as a dev-only dependency inside your project ... and **maybe** globally as well.

    The only real problem is updates. If you use a reasonable global install scheme, updates will be easy. They're less easy inside your project or in `pre-commit`. And you might care one way or the other! I **don't** want updates! I **do** want updates!

    As for Python type-checking, `ty` seems good so far, but not enough experience with it yet. `basedpyright`, `pyrefly`, and `ruff` all good. These four are my favorites.

  20. Let's say you want to do good type-checking for the #Python project you're working on. You pick a tool, maybe you use it as an #LSP also (so your editor can show you errors, too). As an example, I'm using #Ty at the moment. There's three places this might be installed: globally (e.g., `brew install ty`), as a dev-only dependency inside your project (e.g., `uv add --dev ty`), or -- and this one might surprise you -- it might only be used and installed by `pre-commit`, which builds a separate environment for each needed tool (which is great for instance where I use `codespell` as a `pre-commit` check, which seems to need some higher version of Python than my actual project).

    Where should you install it?

    If you're the only one on your team running it, globally is fine. If more than just you, then absolutely as a dev-only dependency inside your project ... and **maybe** globally as well.

    The only real problem is updates. If you use a reasonable global install scheme, updates will be easy. They're less easy inside your project or in `pre-commit`. And you might care one way or the other! I **don't** want updates! I **do** want updates!

    As for Python type-checking, `ty` seems good so far, but not enough experience with it yet. `basedpyright`, `pyrefly`, and `ruff` all good. These four are my favorites.

    #BasedPyright #Pyrefly #Ruff #PreCommit #CodeSpell #Homebrew

  21. Well … I get symbol renaming if I use as my

  22. It seems like my #Pyrefly problem isn’t related to my #AdventOfCode project. Before pyrefly, I could rename a symbol throughout the project. With pyrefly, I can’t. More investigation needed.

  23. It seems like my problem isn’t related to my project. Before pyrefly, I could rename a symbol throughout the project. With pyrefly, I can’t. More investigation needed.

  24. Working on #AdventOfCode. My plan was to solve each day in both #Python and #RustLang. I thought I would be further by now. Yes, my Python answer to day 1 solves both parts, but I'm trying to be exemplary: good names, docstrings, comments-where-needed, tests, project structure, all the things.

    For some reason, #HelixEditor keeps complaining about the #LSP (using both #Pyrefly and #Ruff, as usual). I'm concerned I haven't set things up right somehow, but I don't yet see where I've gone wrong.

    Once this is working, further days will be easy. At least ... I hope!

  25. Working on . My plan was to solve each day in both and . I thought I would be further by now. Yes, my Python answer to day 1 solves both parts, but I'm trying to be exemplary: good names, docstrings, comments-where-needed, tests, project structure, all the things.

    For some reason, keeps complaining about the (using both and , as usual). I'm concerned I haven't set things up right somehow, but I don't yet see where I've gone wrong.

    Once this is working, further days will be easy. At least ... I hope!

  26. Working on #AdventOfCode. My plan was to solve each day in both #Python and #RustLang. I thought I would be further by now. Yes, my Python answer to day 1 solves both parts, but I'm trying to be exemplary: good names, docstrings, comments-where-needed, tests, project structure, all the things.

    For some reason, #HelixEditor keeps complaining about the #LSP (using both #Pyrefly and #Ruff, as usual). I'm concerned I haven't set things up right somehow, but I don't yet see where I've gone wrong.

    Once this is working, further days will be easy. At least ... I hope!

  27. PyreFly: Because who needs Python in Python when you can overengineer it in Rust? 🚀✨ Just pip-install this glorified type checker and bask in the glow of 166 cores and 228 GB RAM, because... why not? 🤖💻
    pyrefly.org/?featured_on=talkp #PyreFly #Rust #Overengineering #TypeChecker #TechInnovation #HackerNews #ngated

  28. PyreFly: Because who needs Python in Python when you can overengineer it in Rust? 🚀✨ Just pip-install this glorified type checker and bask in the glow of 166 cores and 228 GB RAM, because... why not? 🤖💻
    pyrefly.org/?featured_on=talkp #PyreFly #Rust #Overengineering #TypeChecker #TechInnovation #HackerNews #ngated

  29. PyreFly: Because who needs Python in Python when you can overengineer it in Rust? 🚀✨ Just pip-install this glorified type checker and bask in the glow of 166 cores and 228 GB RAM, because... why not? 🤖💻
    pyrefly.org/?featured_on=talkp #PyreFly #Rust #Overengineering #TypeChecker #TechInnovation #HackerNews #ngated

  30. I think #astral may want to consider marketing #ty a bit more.

    After a bunch of my coworkers and I got back from Pycon I'm hearing WAY more from them about #pyrefly - which confuses me because while Meta has made MASSIVE contributions to FLOSS and we should all thank them for that, Astral has consistently produced outstanding #python tooling.

    I know there's plenty of room in the pool and that competition is good, I'd just hate to see a great tool get overlooked because its competitor was giving away free Espresso :) :P

  31. I think #astral may want to consider marketing #ty a bit more.

    After a bunch of my coworkers and I got back from Pycon I'm hearing WAY more from them about #pyrefly - which confuses me because while Meta has made MASSIVE contributions to FLOSS and we should all thank them for that, Astral has consistently produced outstanding #python tooling.

    I know there's plenty of room in the pool and that competition is good, I'd just hate to see a great tool get overlooked because its competitor was giving away free Espresso :) :P

  32. I think #astral may want to consider marketing #ty a bit more.

    After a bunch of my coworkers and I got back from Pycon I'm hearing WAY more from them about #pyrefly - which confuses me because while Meta has made MASSIVE contributions to FLOSS and we should all thank them for that, Astral has consistently produced outstanding #python tooling.

    I know there's plenty of room in the pool and that competition is good, I'd just hate to see a great tool get overlooked because its competitor was giving away free Espresso :) :P

  33. Introducing #Pyrefly: Meta's new #opensource #Python type checker, crafted in Rust for maximum performance!

    Pyrefly is intended to replace the OCaml-based Pyre type checker previously used for Instagram’s codebase.

    Find out more: bit.ly/4kIsRpu

    #InfoQ #Meta #RustLang #TypeChecking

  34. Introducing #Pyrefly: Meta's new #opensource #Python type checker, crafted in Rust for maximum performance!

    Pyrefly is intended to replace the OCaml-based Pyre type checker previously used for Instagram’s codebase.

    Find out more: bit.ly/4kIsRpu

    #InfoQ #Meta #RustLang #TypeChecking

  35. Introducing : Meta's new type checker, crafted in Rust for maximum performance!

    Pyrefly is intended to replace the OCaml-based Pyre type checker previously used for Instagram’s codebase.

    Find out more: bit.ly/4kIsRpu

  36. 🐍🔧 #Rust fanboys rejoice! We've got not one, but TWO new #Python type checkers to argue about: #Pyrefly and #Ty. Because obviously what the Python ecosystem really needed was more esoteric tools nobody asked for. 😅🔍
    blog.edward-li.com/tech/compar #TypeCheckers #DeveloperCommunity #HackerNews #ngated

  37. 🐍🔧 #Rust fanboys rejoice! We've got not one, but TWO new #Python type checkers to argue about: #Pyrefly and #Ty. Because obviously what the Python ecosystem really needed was more esoteric tools nobody asked for. 😅🔍
    blog.edward-li.com/tech/compar #TypeCheckers #DeveloperCommunity #HackerNews #ngated

  38. 🐍🔧 #Rust fanboys rejoice! We've got not one, but TWO new #Python type checkers to argue about: #Pyrefly and #Ty. Because obviously what the Python ecosystem really needed was more esoteric tools nobody asked for. 😅🔍
    blog.edward-li.com/tech/compar #TypeCheckers #DeveloperCommunity #HackerNews #ngated