Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Announcing the Beta release of ty

astral.sh

Post reply on HN
Print view View original

31–40 of 181 posts

Re: Announcing the Beta release of ty

#31

Post by syiblet »

The codebase has none of the rust code. In fact even the python code in the code base is mostly just scripts for updating version tags and etc...

Seems like the code isn't actually open source which to me is a bit concerning. At the very least, if ya'll want to release it like this please be clear that you're not open source. The MIT license in the repo gives the wrong impression.

Re: Announcing the Beta release of ty

#32

Post by woodruffw »

syiblet wrote: post #31

The codebase has none of the rust code. In fact even the python code in the code base is mostly just scripts for updating version tags and etc... Seems like the code isn't actually open source which to me is a bit concerning. At the very least, if ya'll want to release it like this please be clear that you're not open source. The MIT license in the repo gives the wrong impression.

The ty repo contains the ruff repo[1] as a submodule, where the remainder of the code is. It is indeed open source, the layout is just indirect at the moment because of code-sharing between the tools.

[1]: https://github.com/astral-sh/ruff

Re: Announcing the Beta release of ty

#33

Post by bobthecowboy »

syiblet wrote: post #31

The codebase has none of the rust code. In fact even the python code in the code base is mostly just scripts for updating version tags and etc... Seems like the code isn't actually open source which to me is a bit concerning. At the very least, if ya'll want to release it like this please be clear that you're not open source. The MIT license in the repo gives the wrong impression.

At least as of a couple months ago, `ty` was actually being developed in the `ruff` repo (per an pdocast interview the devs did on Talk Python), so that might be why the `ty` repo looks empty (and pulls in ruff as a git submodule).

Re: Announcing the Beta release of ty

#34

Post by simonw »

syiblet wrote: post #31

The codebase has none of the rust code. In fact even the python code in the code base is mostly just scripts for updating version tags and etc... Seems like the code isn't actually open source which to me is a bit concerning. At the very least, if ya'll want to release it like this please be clear that you're not open source. The MIT license in the repo gives the wrong impression.

I think that's because most of the code for `ty` is tucked away in the `ruff` codebase: https://github.com/astral-sh/ruff/tree/main/crates/ty - it's all MIT licensed.

Re: Announcing the Beta release of ty

#35

Post by selcuka »

0cf8612b2e1e wrote: post #29

Without digging too deep- what is the Django story? Django does a bunch of magic which is challenging for the type checkers to handle well.

Ty doesn't support Django yet, and it doesn't have a plugin system, so third party developers can't improve it. If you need Django support, it is better to stick to mypy or pyright for the time being.

Re: Announcing the Beta release of ty

#36

Post by shrumm »

Thanks Astral team! We use Pydantic heavily, and it looks like first class support from Ty is slated for the stable release, we'd love to try it.

While we wait... what's everyone's type checking setup? We run both Pyright and Mypy... they catch different errors so we've kept both, but it feels redundant.

https://htmlpreview.github.io/?https://github.com/python/typ... suggests that Pyright is a superset, which hasn't matched our experience.

Though our analysis was ~2 years ago. Anyone with a large Python codebase successfully consolidated to just Pyright?

Re: Announcing the Beta release of ty

#37

Post by zanie »

woodruffw wrote: post #32
syiblet wrote: post #31

The codebase has none of the rust code. In fact even the python code in the code base is mostly just scripts for updating version tags and etc... Seems like the code isn't actually open source which to me is a bit concerning. At the very least, if ya'll want to release it like this please be clear that you're not open source. The MIT license in the repo gives the wrong impression.

The ty repo contains the ruff repo[1] as a submodule, where the remainder of the code is. It is indeed open source, the layout is just indirect at the moment because of code-sharing between the tools. [1]: https://github.com/astral-sh/ruff

This is also documented at https://github.com/astral-sh/ty?tab=readme-ov-file#contribut... and https://github.com/astral-sh/ty/blob/main/CONTRIBUTING.md#re...

Re: Announcing the Beta release of ty

#38

Post by collinmcnulty »

I am so pleased by ty’s stance that I should not have to add annotations to satisfy the type checker. I ripped out last type checker out because it was constantly nagging us about technicalities, but ty immediately found issues where we annotated that a duct was an acceptable input, but actually doing so would break things.

Re: Announcing the Beta release of ty

#40

Post by ocamoss »

modeless wrote: post #3

The title of this story should be "Announcing the Beta release of ty". A lot of people have been waiting for the beta specifically. I've been using Pyrefly and loving it compared to Pyright, but they recently shipped some updates with crash bugs that forced me to pin to a previous version, which is annoying. Unfortunately my first impression of ty isn't great either. Trying to install the ty extension on the current…

(pyrefly maintainer here) If you haven't already, please file an issue for that crash on the [Pyrefly repo](https://github.com/facebook/pyrefly) as well :)
Post reply on HN