home.social

#ty — Public Fediverse posts

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

  1. @me @krypt3ia wow. Mona for Mastodon keeps doing that in threads. #ty i'll fix now

    #ty
  2. #python peeps: If you assume, as I did, that #astral #ty's LSP JUST provides the type checking ty is known for, you'd be wrong :)

    It's an all around IDE like LSP like pyright/basedpyright but is missing some of pyright's features like codelens, inlay hints and call/type hierarchies, in exchange for being much faster.

    If you use both, don't be puzzled as I was when you hit your Goto Definition key mapping and get a list of 2 identical definitions.

    Just pick one or the other and things will work how you expect.

    I'm sticking with basedpyright for now but I'm putting myself on probation in that if I don't actually start using code lens and hint inlays I'll switch to ty for speed :)

  3. RE: fedi.simonwillison.net/@simon/

    I like what Simon is writing in his blog about this. In particular about the forkability of the tools. Backed up by quoting Armin Ronacher:

    - "even in the worst possible future this is a very forkable and maintainable thing"

  4. I don't trust anything that say or promise. Now they're buying openai.com/index/openai-to-acq - and gains control over , and .

    That the "Astral team will join the Codex team at OpenAI and over time, we’ll explore deeper integrations" - makes me wonder how well these really great tools will keep functioning stand alone in the future.

    Can I keep being depended on them for managing my :python: projects?

    AI companies are gaining al the more control of the toolchain!

  5. Yesterday was just a fantastic day for me. I planned to post on it. Just overjoyed. Strongly tempered today by the acquisition of Astral, and therefore the uncertain future of #uv and #ty (and transitively, #pixi).

    I’m gonna focus on yesterday.

  6. Yesterday was just a fantastic day for me. I planned to post on it. Just overjoyed. Strongly tempered today by the acquisition of Astral, and therefore the uncertain future of #uv and #ty (and transitively, #pixi).

    I’m gonna focus on yesterday.

  7. Yesterday was just a fantastic day for me. I planned to post on it. Just overjoyed. Strongly tempered today by the acquisition of Astral, and therefore the uncertain future of and (and transitively, ).

    I’m gonna focus on yesterday.

  8. Yesterday was just a fantastic day for me. I planned to post on it. Just overjoyed. Strongly tempered today by the acquisition of Astral, and therefore the uncertain future of #uv and #ty (and transitively, #pixi).

    I’m gonna focus on yesterday.

  9. @kevin @Techmeme OMG! I’m pretty sure this is horrible and frightening news; though (counter example) GitHub is still doing okay. I’m a superfan of #uv and #ty. Please don’t make me switch!

  10. I use #ruff as my #Python linter for the speed #flake8 lacked (with a foot still in the other camp for custom rules), was looking at #ty, but hadn’t had any incentive to try #uv.

    Others in the #Python ecosystem might be getting rather more nervous… Looks like the venture capitalists backing #Astral will get their payoff: openai.com/index/openai-to-acq 💰

  11. Well, fuck. Will my favorite Python development tooling smell like pipi now? 🫣

    astral.sh/blog/openai

    #python #uv #ty #ruff

  12. OMG openai.com/index/openai-to-acq

    #openai is acquiring Astral, the author's of #uv, #ruff and #ty

    Well, I'll probably now defer adopting more of the astral tech stack. Or at least until openAI fixes their insane cash burn rate

  13. When installing dependencies, formatting code, linting it, type-checking it, and building docs with or , , , and would previously take from 2min to several more, it now takes less than 15 seconds for the whole thing, thanks to , , and .

    This is for 5 versions (3.10 to 3.15).

    The DX got much better 🥰

  14. When installing dependencies, formatting code, linting it, type-checking it, and building docs with #Poetry or #PDM, #Black, #Flake8, #Mypy and #MkDocs would previously take from 2min to several more, it now takes less than 15 seconds for the whole thing, thanks to #uv, #Ruff, #ty and #Zensical.

    This is for 5 #Python versions (3.10 to 3.15).

    The DX got much better 🥰

  15. When installing dependencies, formatting code, linting it, type-checking it, and building docs with #Poetry or #PDM, #Black, #Flake8, #Mypy and #MkDocs would previously take from 2min to several more, it now takes less than 15 seconds for the whole thing, thanks to #uv, #Ruff, #ty and #Zensical.

    This is for 5 #Python versions (3.10 to 3.15).

    The DX got much better 🥰

  16. When installing dependencies, formatting code, linting it, type-checking it, and building docs with #Poetry or #PDM, #Black, #Flake8, #Mypy and #MkDocs would previously take from 2min to several more, it now takes less than 15 seconds for the whole thing, thanks to #uv, #Ruff, #ty and #Zensical.

    This is for 5 #Python versions (3.10 to 3.15).

    The DX got much better 🥰

  17. OK WHICH ONE OF YOU IS TAKING DOWN ALL THE COMMS INFRASTRUCTURE IN THE US RIGHT NOW?!?

    Guys…I got stuff to do…

    Pause for a sec mebbe?

    #ty

    #ty
  18. @neurovagrant #ty for reading the toxic positivity site so i do not have to 🙃

    and i def tip my hat to those threat actors. brilliant emotional manip!

    #ty
  19. I wrote up how I set up #ty with #helix, with a focus on finding third-party packages (a.k.a. virtualenvs, which I keep on a central location!)

    blog.lanzani.nl/2026/using-ty-

    #HelixEditor #python

  20. @scottwilson heh. #ty, but I will always defer accolades to @huntress b/c of epic knowledge, skills, sharing, & community support like they did during the Kaseya debacle reddit.com/r/msp/comments/ocgg (I remind my CISO classes abt that every cohort).

    They're also one of a tiny handful of MDRs that do not treat their customers like production honeypot bait (like one I know very very well) and, who deliver what they promise.

    A very rare gem.

    #ty
  21. 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.

  22. ty: революция в тайп-чекинге

    Всем привет! За последние пару лет компания Astral буквально разрывает Python-мир своими инструментами. Даже если вы не слышали это имя напрямую, с большой вероятностью вы уже пользовались их продуктами — ruff или uv . И это не преувеличение. И ruff , и uv сегодня фактически стали стандартом индустрии. Например, в свежем релизе PyCharm 2025.3 при создании нового проекта по умолчанию инициализируется именно окружение uv , а не привычный venv . Для open source-проекта — это очень серьёзный показатель доверия со стороны экосистемы. Открытый исходный код и массовое принятие инструментов Python-разработчиками дали Astral тот самый «кредит доверия», который компания, судя по всему, пока что уверенно оправдывает. И вот буквально на днях Astral объявили, что их новый «революционный» тайп-чекер ty переходит в стадию бета-тестирования. А если учитывать, что и uv , и ruff формально тоже всё ещё находятся в бете, то можно считать, что ty уже фактически вышел в релиз. Собственно, о нём и поговорим дальше. Если вам интересны подобные материалы — подписывайтесь на Telegram-канал «Код на салфетке» . Там я делюсь гайдами для новичков и полезными инструментами. А прямо сейчас у нас ещё и проходит новогодний розыгрыш.

    habr.com/ru/articles/979752/

    #uv #ruff #ty #mypy #type_checking #python #rust #astral

  23. 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

  24. 🚀🎉 Hold onto your keyboards, folks! #Astral has unleashed "ty," a lightning-fast #Python #type #checker, because, of course, we needed another one. Written in #Rust, because Python apparently wasn't fast enough for checking itself, "ty" is now in #Beta and ready to bravely enter a market already saturated with the likes of #mypy, #Pyright, and other tools you didn't know you couldn't live without. 🌪️🔧
    astral.sh/blog/ty #ty #HackerNews #ngated