Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
zanie
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
zanie
16d ago
> FYI: The extraction of files is largely python code that doesn't release the GIL. (cf. the zipfile class from the python interpreter has large layers of abstraction with a massive overhead in python code). TIL. I ran some benchmar
2.
▲
by
zanie
16d ago
You might be interested in taking a look at the `uv download` sketch I started on last week https://github.com/astral-sh/uv-dev/pull/875
3.
▲
by
zanie
16d ago
We didn't compare to pip at the time, but it saved a lot of absolute time for us as reported in the benchmarks from the pull request ( https://github.com/astral-sh/uv/pull/789 ) it improved a boto3 case by
4.
▲
by
zanie
16d ago
I haven't done the comparison but it shouldn't be so hard - https://docs.astral.sh/uv/reference/environment/#uv_concurre... - https://docs.astral.sh/uv/reference/environmen
5.
▲
by
zanie
16d ago
I'm a bit confused. pdm hit 1.0 in 2021, 3 years before uv was released.
6.
▲
by
zanie
16d ago
(I work on uv) > The only advantage of uv is to have support for parallel async extraction. This isn't true, the biggest speed ups are for the warm cases where we've already unpacked the files into the cache, as notatallshaw me
7.
▲
by
zanie
16d ago
If you want to open an issue with verbose logs (`-vv`) I'd be happy to look into it. You can set `UV_LOG_CONTEXT=1` to emit timing information. If you're running Python scripts, I'd recommend using `uv lock --script <path&
8.
▲
by
zanie
19d ago
That project looks owned by https://github.com/karpetrosyan who has contributed to httpx but is not the owner / maintainer in question
9.
▲
by
zanie
2mo ago
We want to support that workflow / experience but we want to design it differently because there are a lot of nuances to pip's interface and the pip maintainers have encouraged us to rethink it. It's also non-trivial to imple
10.
▲
by
zanie
2mo ago
Yes! It's in progress — it's already there, just hidden as we iterate on it. (but as a note, the initial `uv lock` will already attempt to choose the highest possible versions and `uv lock --upgrade` will do so again, requests for
11.
▲
by
zanie
2mo ago
It makes `uv run <project-name>` work by default, I expect most projects to need an entry point.
12.
▲
by
zanie
2mo ago
So far the maintenance burden has been quite bearable and extending pip provides us with an opportunity to explore and encourage improvements upstream which are still beneficial to a lot of people.
13.
▲
by
zanie
2mo ago
I hadn't considered that, it's an interesting idea. We generally hold a very high bar for nagging users or gating behaviors. It's possible we'll reach a point someday where this is appropriate! I think you're right
14.
▲
by
zanie
2mo ago
Unfortunately dynamic metadata is not efficient for package resolution, so we don't want to encourage it. Instead, we want to design a better workflow for using source control for versioning, but haven't had the time to do so.
15.
▲
by
zanie
2mo ago
Pixi is very focused on the Conda ecosystem and implements a sort of bridge across the Conda and PyPI ecosystems. I am very interested in solving the problems that motivated creation of the Conda ecosystem, but I want to do so by driving fo
16.
▲
by
zanie
2mo ago
Yes! We've been working on this for quite some time as it's one of the worst experiences in Python packaging today. There are two PEPs that we're involved with that will provide the components for the ecosystem to properly de
17.
▲
by
zanie
2mo ago
I think we're doing what we should making isolated environments easy to use. I don't think we should take options away from people that need them.
18.
▲
by
zanie
2mo ago
We have the interface because we care a lot about meeting people where they are. We keep the interface because we care a lot about long-term support and compatibility. I cannot imagine removing it. We generally want to add features to the t
19.
▲
by
zanie
4mo ago
I don't think it's true at all that "dropping features" makes uv fast. As an author of uv, I think that particular section of the article is way off base.
20.
▲
by
zanie
4mo ago
(I work on uv) As a note, you can set the default bounds for `uv add` in persistent configuration — no need to provide it every time. See https://docs.astral.sh/uv/reference/settings/#add-bounds We prefer not
21.
▲
by
zanie
4mo ago
I'm a bit confused, `uv run --with $package main --help` should do what you say with very little overhead. We won't reinstall it every time, `--with` environments are stored in the cache and retained. Even if the environment is ca
22.
▲
by
zanie
4mo ago
fwiw `uv upgrade` is on the roadmap — we just haven't done it yet because it's hard to build a great experience for it (there are far more nuances than people expect) and we're a small team with a lot of priorities.
23.
▲
by
zanie
5mo ago
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)
24.
▲
by
zanie
6mo ago
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)
25.
▲
by
zanie
9mo ago
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 :)
26.
▲
by
zanie
9mo ago
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...
27.
▲
by
zanie
9mo ago
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 pro
28.
▲
by
zanie
11mo ago
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 prob
29.
▲
by
zanie
1y ago
It's intentionally distinct from the `uv tool` interface — it won't change `ruff` or `uv tool run` behaviors.
30.
▲
by
zanie
1y ago
Thanks that's helpful. Did you try reducing the concurrency limit?
More ›