notatallshaw

9 ms·

1.
by notatallshaw 16d ago
Fun fact! The original request to add a concurrency variable in uv was requested by me because, among other things, I wanted to measure the difference between uv and pip: https://github.com/astral-sh/uv/issues&#x2F
2.
by notatallshaw 16d ago
That's excellent news for uv, and I think covers one of two major use cases I often see where uv does not cover standard packaging workflows. This one being downloading to an offline wheelhouse and installing from that. The other one b
3.
by notatallshaw 16d ago
> it improved a boto3 case by 3x (30s to 10s) and our "standard" solve benchmark by 2x. It's plausible some of those gains have been reduced by other optimizations in our solver since then though. This makes a lot of sense
4.
by notatallshaw 17d ago
> We can also make low-level optimizations during resolution, e.g., in version parsing, that are not possible in pure Python code. As a complete aside, uv can and does do this, but for this particular optimization I'm not sure how m
5.
by notatallshaw 17d ago
As a pip maintainer, I've long been looking at the tradeoffs of uv's cache, it's the biggest item that makes warm installs faster for uv vs. pip. As pip caches the original distributions and then has to unzip them each time,
6.
by notatallshaw 2mo ago
Or an obscure CalVer that no one realizes - /pip-maintainer
7.
by notatallshaw 2mo ago
FWIW, break-system-packages comes directly from pip's interface, it's not a novel addition from uv. If Astral/OpenAI are willing to support uv pip in the long term, why do you think they should use a stick as well as a carrot
8.
by notatallshaw 3mo ago
> Their infrastructure (pip) getting worse and worse Hi, I'm a pip maintainer, can you please report any issue you think is happening in recent versions of pip: https://github.com/pypa/pip/ I particularly
9.
by notatallshaw 5mo ago
> Running pip install lightning is all that is needed to activate FYI, pip added cooldowns in 26.1: * https://discuss.python.org/t/announcement-pip-26-1-release/107108 * https://ichard26.github.io
10.
by notatallshaw 5mo ago
The note at the end of the post indicates the user asked Claude to review their own chat logs. It's impossible to tell if Claude used or built a a performance harness or just wrote those numbers based on vibes.
11.
by notatallshaw 6mo ago
Pip maintainer here, to do this in pip (26.0+) now you have to manually calculate the date, e.g. --uploaded-prior-to="$(date -u -d '3 days ago' '+%Y-%m-%dT%H:%M:%SZ')" In pip 26.1 (release scheduled for April 2
12.
by notatallshaw 6mo ago
The threat actor was sophisticated enough to spam GitHub issues with dozens of different accounts. I imagine they could completely overwhelm PyPI with unauthenticated reports.
13.
by notatallshaw 6mo ago
> I had no idea how to contact anyone related to PyPI https://pypi.org/security/ : > If you've identified a security issue with a project hosted on PyPI Login to your PyPI account, then visit the project&#x27
14.
by notatallshaw 6mo ago
As a pip maintainer I don't think that's really true. The resolver in both pip and uv are fundamentally sequential and single threaded, you can't really queue up or split out jobs. What uv does is parallelize the final downlo
15.
by notatallshaw 6mo ago
pixi offloads PyPI ecosystem stuff to uv, but pixi is conda first. The team were actually the first to build a Rust based Python package resolver (rip), but after uv was released they migrated to uv's resolver (Python package resolvers
16.
by notatallshaw 6mo ago
On a widely used open source project I maintain I've been seeing PRs in the last month that are a little off (look okayish but are trivial or trying to solve problems in weird ways), and then when I look at their account they started o
17.
by notatallshaw 6mo ago
My understand is Astral's focus for ty has been on making a good experience for common issues, whereas they plan for very high compliance but difficult or rare edge cases aren't are prioritized. Compliance suite numbers are biased
18.
by notatallshaw 7mo ago
AI is somewhat helpful but I'm not interested in a company finding a way for me to pay to do my volunteer OSS work. GitHub Copilot offers a permanent free subscription for OSS maintainers. I previously ignored a free offer when Claude
19.
by notatallshaw 8mo ago
I found the diagrams on the Wikipedia pages help build an intuitive understanding of each step: https://en.wikipedia.org/wiki/Conflict-driven_clause_learnin... Also, the pubgrub-rs guide I find has a gentle ramp in in
20.
by notatallshaw 8mo ago
I assume lock and dependency files are in the training data, so predicting version number tokens have high probabilities associated with them.
21.
by notatallshaw 8mo ago
As a pip maintainer I primarily think about resolution and resolver performance. I got involved when pip introduced it's current resolver around late 2020, and got my first PR landed in mid 2021. I recently became a packaging maintaine
22.
by notatallshaw 9mo ago
> At one company I worked at, we had a system where each deploy got its own folder, and we'd update a symlink to point to the active one. It worked, but it was all manual, all custom, and all fragile. The first time I saw this I tho
23.
by notatallshaw 9mo ago
We're getting there https://pip.pypa.io/en/stable/cli/pip_lock/ ! Pip has been a flag bearer for Python packaging standards for some time now, so that alternatives can implement standards rather tha
24.
by notatallshaw 11mo ago
Unfortunately that was posted 1 month before the Faster CPython project was disbanded by Microsoft, so I imagine things have slowed.
25.
by notatallshaw 11mo ago
Python has about 40 keywords, I say I would regularly use about 30, and irregularly use about another 5. Hardly seems like a "junkyard". Further, this lack of first class support for lazy importing has spawned multiple CPython for
26.
by notatallshaw 11mo ago
> I had been hoping someone would introduce the non-virtualenv package management solution that every single other language has where there's a dependency list and version requirements (including of the language itself) in a manifes
27.
by notatallshaw 11mo ago
> You let people make the mistake and have the library throw an exception if they do that, not through type checking but just through something eventually calling a method that doesn't exist. Exceptions or crashes would be annoying,
28.
by notatallshaw 11mo ago
> I wouldn't mind a codebase where numpy objects created by dependency B can't be shared directly with dependency A without me first running some kind of conversion function on them Given there's no compiler to enforce thi
29.
by notatallshaw 11mo ago
I agree, but as a type checker it is a subjective choice, whether to be explicit and not make assumptions or whether to infer from certain certain patterns as probably correct and not be noisy to the user. Very glad to see they plan to fix
30.
by notatallshaw 11mo ago
I assume in your example if you update the foo declaration to the following it solves the complaint: foo: list[str] = [] If so this a type checking design choice: * What can I infer from an empty collection declaration? * Wha

More ›