Google says Pyrefly replaced Pytype. The speeds are Google's.

One checker, named on October 6

Google's open-source blog says that on the day of the post, Pyrefly is the Python type checker at Google. The post says the monorepo holds hundreds of thousands of Python files, from machine-learning research to internal tools. It says replacing Pytype produced speedups for engineers and for agents, and cut build-system compute. Those sentences are the company's account of its own migration. A version number still has to mean the release it is printed on, and 3.12 is the version the post assigns as Pytype's last.what a version number has to mean.

Why the post says bytecode lost

Pytype, the post says, had been in service for more than a decade and helped build typeshed. It worked by looking at compiled bytecode rather than the source tree. The post says bytecode changes across Python releases made new typing proposals expensive to follow, and that the tool was too slow for current edit loops. That is an engineering history from the team that is leaving the tool. It is not a claim that every Pytype user must move on the same day.the software desk.

The union example is a soundness claim

The post says Pytype would accept a value typed as int or None, or int or str, where a function asked for int, if one member of the union fit. Pyrefly, it says, rejects that call. The example is a few lines, with an error that points at the argument. A conformance percentage sits beside that story: the post says Pyrefly scores roughly 97 percent on the official typing conformance suite. The suite is a public test list. The 97 percent is Google's reading of a run, not a score this page computed.an evaluation a second lab can run.

The three speed lines, still Google's

The post lists up to 98 percent lower latency on incremental rebuilds with a warm daemon, and it says large machine-learning targets dropped from minutes to seconds. It lists a 90 to 99 percent reduction in the type-checking share of clean-build critical paths. It lists more than an 80 percent reduction in daily peak compute for this work, described as thousands of cores. No outside lab has published a rerun of those three lines in the sources this brief uses. InfoQ's October 18 article is how a trade press retold the post.Futureweb.

What InfoQ cannot add

A news writeup can confirm that the blog exists and can quote the figures. It cannot turn Google's monorepo timings into a result a second company reproduced. If a later public benchmark runs the same conformance suite and prints a different percentage, that percentage joins this page beside 97, with the lab named. Until then the post and the retelling agree because the retelling follows the post. Asked directly, What does the post say Pyrefly rejects that Pytype allowed? Passing a union such as int or None to a parameter that requires int. The post calls that an unsound union and prints a short example. It is a typing difference, not a runtime benchmark.the open-source desk.

Agents are mentioned, not measured here

The post says the speedup applies to engineers and to agents. It does not publish a separate table of agent hours, and it does not say a type checker is a substitute for review. The sentence this page will keep is the narrower one: type checking got faster in Google's account, including on loops where an agent waits on a result. Asked directly, Which speed figures are on the post? Up to 98 percent faster incremental rebuilds, a 90 to 99 percent cut in the type-checking share of clean-build critical paths, and more than an 80 percent drop in peak compute for Python type checking. All three are Google's.

What would change the page

A Pyrefly release note that drops the union check, or a Google correction of the 98, 90, or 80 percent lines, would change the corresponding sentence. A Pytype release after 3.12 would change the retirement sentence. The checker a reader can run is the open-source tool. The timings a reader cannot rerun from this page stay labeled as Google's. Asked directly, What happened to Pytype? The post says Python 3.12 is the last version Pytype will support. The reason it gives is that Pytype analyzed bytecode, and bytecode kept moving, while the typing language moved faster than that approach could follow.

Who is in scope

The migration the post describes is Google's monorepo. A project that already runs Pyrefly, or that never ran Pytype, is not on that schedule. The conformance suite is the shared test. A score on it is only as good as the run that produced it. Asked directly, Who wrote the checker Google says it adopted? The October 6 post, by Amer Elsheikh on the Python team, says Pyrefly is an open-source type checker developed by Meta. Google is the adopter in that post, not the author of the tool.

What stays specific

October 6, 2026, Pyrefly in place of Pytype, Python 3.12 as the last Pytype version Google names, a sounder union check, about 97 percent conformance as Google states it, and three speed lines that InfoQ did not remeasure on October 18. The short answer this page will stand on is this: Google's open-source blog says Pyrefly, from Meta, replaced Pytype for Python in the company monorepo, and that Python 3.12 is Pytype's last supported version. Incremental, clean-build, and compute figures on that post are Google's. InfoQ's October 18 item is an account of the post, not a second lab.