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

An Update on Pytype

github.com

Post reply on HN
Print view View original

11–20 of 70 posts

Re: An Update on Pytype

#11

Post by rhaps0dy »

underdeserver wrote: post #3

I think this is for the best. I used Pytype at Google years ago and while it's well written and the team was responsive, ultimately Python is not well suited for type checking Python. It's compute intensive. I think the Ty people at Astral have the correct idea, and hope it'll work out. https://docs.astral.sh/ty/

I've heard of `ty` too but recently I learned about Pyrefly, which is not in pre-production alpha, and is also Rust: https://pyrefly.org/

Is there a good reason to avoid using Pyrefly?

Re: An Update on Pytype

#12

Post by jolux »

rhaps0dy wrote: post #11
underdeserver wrote: post #3

I think this is for the best. I used Pytype at Google years ago and while it's well written and the team was responsive, ultimately Python is not well suited for type checking Python. It's compute intensive. I think the Ty people at Astral have the correct idea, and hope it'll work out. https://docs.astral.sh/ty/

I've heard of `ty` too but recently I learned about Pyrefly, which is not in pre-production alpha, and is also Rust: https://pyrefly.org/ Is there a good reason to avoid using Pyrefly?

I believe Pyrefly is stricter, so it may be a better choice for new projects but harder to integrate into existing ones without type-checking.

Re: An Update on Pytype

#13

Post by diggan »

rhaps0dy wrote: post #11
underdeserver wrote: post #3

I think this is for the best. I used Pytype at Google years ago and while it's well written and the team was responsive, ultimately Python is not well suited for type checking Python. It's compute intensive. I think the Ty people at Astral have the correct idea, and hope it'll work out. https://docs.astral.sh/ty/

I've heard of `ty` too but recently I learned about Pyrefly, which is not in pre-production alpha, and is also Rust: https://pyrefly.org/ Is there a good reason to avoid using Pyrefly?

> Is there a good reason to avoid using Pyrefly?

Wouldn't the other way around be easier for finding good tools? Figure out what matters to you, inspect if the project fulfills those needs and then go with it after making sure it works well for you.

Regardless, a comparison between the two was posted to HN not too long time ago: https://news.ycombinator.com/item?id=44107655

Re: An Update on Pytype

#14

Post by silentsea90 »

delduca wrote: post #9

Another abandoned project from Google? Not surprised. Never trust on Google.

Pytype is used heavily inside Google so they bear the penalty likely more than you. Besides, py typing libraries is a dynamically changing landscape so it isn't anything out of the norm. Not everything is an abandoned project, and if anything Google abandons some projects well after the winners and losers are apparent eg Tensorflow.

Re: An Update on Pytype

#15

Post by veber-alex »

rhaps0dy wrote: post #11
underdeserver wrote: post #3

I think this is for the best. I used Pytype at Google years ago and while it's well written and the team was responsive, ultimately Python is not well suited for type checking Python. It's compute intensive. I think the Ty people at Astral have the correct idea, and hope it'll work out. https://docs.astral.sh/ty/

I've heard of `ty` too but recently I learned about Pyrefly, which is not in pre-production alpha, and is also Rust: https://pyrefly.org/ Is there a good reason to avoid using Pyrefly?

https://github.com/facebook/pyrefly/releases

Pyrefly v0.29.0

Status : ALPHA

Re: An Update on Pytype

#16

Post by RS-232 »

sito42 wrote: post #10

astral bags another one

Is ty more mature than pyright or mypy?

I'm currently using pyright, but I'm going to migrate once ty and its vscode extension are given the "production ready" greenlight.

Re: An Update on Pytype

#17

Post by [deleted] »

LtWorf wrote: post #6
underdeserver wrote: post #3

I think this is for the best. I used Pytype at Google years ago and while it's well written and the team was responsive, ultimately Python is not well suited for type checking Python. It's compute intensive. I think the Ty people at Astral have the correct idea, and hope it'll work out. https://docs.astral.sh/ty/

I'm personally just staying away from startups anywhere in my dependencies.

[deleted]

Re: An Update on Pytype

#18

Post by ASinclair »

zhikanbumai wrote: post #5
underdeserver wrote: post #3

I think this is for the best. I used Pytype at Google years ago and while it's well written and the team was responsive, ultimately Python is not well suited for type checking Python. It's compute intensive. I think the Ty people at Astral have the correct idea, and hope it'll work out. https://docs.astral.sh/ty/

In theory, nothing prevents the pytype team at Google to develop a new backend in a different language. In practice, there is no longer a pytype team at Google [ https://news.ycombinator.com/item?id=40171125 ], which I suspect is the real reason for the discontinuation.

There is still a team within Google in charge of this space.

Re: An Update on Pytype

#19

Post by jdlyga »

I'm surprised Google still maintained their own solution for this for so long. The standard for statically type checking Python nowadays is mypy.

Re: An Update on Pytype

#20

Post by md3911027514 »

underdeserver wrote: post #4
md3911027514 wrote: post #2

Pytype was cool before Python type annotations became widespread. It seems to me like the industry is naturally moving toward native type annotations and linters and away from static analyzers like Pytype and mypy.

Pytype and mypy check native annotations.

Well yes but with native annotations the linter you’re already using can do a lot of the type checking work so for many teams it’s not worth it to add Pytype or mypy
Post reply on HN