Hacker News: zanie

New comment by zanie in "Open source security at Astral"

zanie — Thu, 09 Apr 2026 12:16:43 +0000

We do address this in the article! It's defense in depth, not theater.

We audit all of our actions, check if they pull in mutable dependencies, contribute upstream fixes, and migrate off using any action when we can.

(I work at Astral)

New comment by zanie in "Astral to Join OpenAI"

zanie — Thu, 19 Mar 2026 14:42:57 +0000

A brief note, your numbers are way off here — Astral subsequently raised a Series A and B (as mentioned in the blog post) but did not announce them. We were doing great financially.

(I work at Astral)

New comment by zanie in "Announcing the Beta release of ty"

zanie — Wed, 17 Dec 2025 19:10:33 +0000

Ruff wasn't named after the bird, we just think it's funny that Charlie didn't know it was a bird. He made up the word :)

New comment by zanie in "Announcing the Beta release of ty"

zanie — Tue, 16 Dec 2025 23:21:15 +0000

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

New comment by zanie in "Announcing the Beta release of ty"

zanie — Tue, 16 Dec 2025 22:21:19 +0000

As noted in the linked issue

> At time of writing, many of the remaining rules require type inference and/or multi-file analysis, and aren't ready to be implemented in Ruff.

ty is actually a big step in this direction as it provides multi-file analysis and type inference.

(I work at Astral)

New comment by zanie in "Uv is the best thing to happen to the Python ecosystem in a decade"

zanie — Thu, 30 Oct 2025 16:57:27 +0000

You're upset that uv doesn't yet support something that no other tool in the ecosystem supports?

I'd love for uv to lock build dependencies, but due to the dynamic nature of Python package metadata it's quite a hard problem. It'll be supported eventually though.

(I work on uv)

New comment by zanie in "Code formatting comes to uv experimentally"

zanie — Fri, 22 Aug 2025 17:44:17 +0000

It's intentionally distinct from the `uv tool` interface — it won't change `ruff` or `uv tool run` behaviors.

New comment by zanie in "PYX: The next step in Python packaging"

zanie — Thu, 14 Aug 2025 12:44:12 +0000

Thanks that's helpful.

Did you try reducing the concurrency limit?

New comment by zanie in "PYX: The next step in Python packaging"

zanie — Thu, 14 Aug 2025 03:58:07 +0000

Please open an issue with some details about the memory usage. We're happy to investigate and feedback on how it's working in production is always helpful.

(I work on uv)

New comment by zanie in "PYX: The next step in Python packaging"

zanie — Wed, 13 Aug 2025 23:21:54 +0000

Thanks for the feedback!

New comment by zanie in "PYX: The next step in Python packaging"

zanie — Wed, 13 Aug 2025 22:58:53 +0000

Yes, we let you override our detection of your hardware. Though we haven't implemented dumping detected information on one platform for use on another, it's definitely feasible, e.g., we're exploring a static metadata format as a part of the wheel variant proposal https://github.com/wheelnext/pep_xxx_wheel_variants/issues/4...

New comment by zanie in "PYX: The next step in Python packaging"

zanie — Wed, 13 Aug 2025 19:39:31 +0000

It's actually not powered by Wheel Variants right now, though we are generally early adopters of the initiative :)

New comment by zanie in "PYX: The next step in Python packaging"

zanie — Wed, 13 Aug 2025 19:38:11 +0000

We're hoping that building a commercial service makes it clear that we have a sustainable business model and that our tools (like uv) will remain free and permissively licensed.

(I work at Astral)

New comment by zanie in "I'm switching to Python and actually liking it"

zanie — Wed, 16 Jul 2025 21:43:10 +0000

If you open even a brief issue and tag me @zanieb I'm happy to take a look!

New comment by zanie in "The uv build back end is now stable"

zanie — Thu, 03 Jul 2025 17:24:59 +0000

We consider it a breaking change to switch the default, so that's coming a bit later.

New comment by zanie in "Switching Pip to Uv in a Dockerized Flask / Django App"

zanie — Tue, 24 Jun 2025 15:42:16 +0000

Installation in Docker just looks like

    COPY --from=ghcr.io/astral-sh/uv:latest /uv /uvx /bin/

https://docs.astral.sh/uv/guides/integration/docker/#using-u...

(We'd recommend pinning the version or SHA in production)

New comment by zanie in "Pyrefly: A new type checker and IDE experience for Python"

zanie — Sun, 18 May 2025 03:52:09 +0000

ty doesn't invoke a Python interpreter to discover imports yet — so you need to either set `VIRTUAL_ENV` or pass `--python` to configure your target environment. We'll expand support here in the future, but this part of ty's interface is intentionally minimal while we focus on core type checking features.

New comment by zanie in "Ty: A fast Python type checker and language server"

zanie — Thu, 08 May 2025 18:32:09 +0000

The plan remains the same as when the company was announced (https://astral.sh/blog/announcing-astral-the-company-behind-...) — paid services that build on and integrate with the free tooling.

New comment by zanie in "Ty: A fast Python type checker and language server"

zanie — Wed, 07 May 2025 19:52:10 +0000

ditto! but we gave impressively non-overlapping answers

New comment by zanie in "Ty: A fast Python type checker and language server"

zanie — Wed, 07 May 2025 19:49:24 +0000

As in, how are we parsing the Python code into an AST?

CPython uses a generated parser. The grammar is defined in https://github.com/python/cpython/blob/main/Grammar/python.g... which is used to generate the specification at https://docs.python.org/3/reference/grammar.html#full-gramma...

We use a hand-written parser, in Rust, based on the specification. We've written that previously at https://astral.sh/blog/ruff-v0.4.0#a-hand-written-parser