RARavencentric·Sep 12, 2026Submission
notatallshaw/nab: PubGrub-based dependency resolver for Python packages
2 points · Open discussionnotatallshaw
nab
Python2026–2026
notatallshaw / nab
nab
PubGrub-based dependency resolver for Python packages
2Distinct people
2Mentions
0Explicit recommenders
32GitHub stars
What to know before exploring
What it is
PubGrub-based dependency resolver for Python packages
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by day2 dated mentions
Observed mentions: 2026-08-31 16:00:39 UTC to 2026-09-12 04:34:43 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Aug 31 | 2026-08-31 00:00:00 UTC | 2026-09-01 00:00:00 UTC | 1 | 0 | 1 |
| Sep 1 | 2026-09-01 00:00:00 UTC | 2026-09-02 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2 | 2026-09-02 00:00:00 UTC | 2026-09-03 00:00:00 UTC | 0 | 0 | 0 |
| Sep 3 | 2026-09-03 00:00:00 UTC | 2026-09-04 00:00:00 UTC | 0 | 0 | 0 |
| Sep 4 | 2026-09-04 00:00:00 UTC | 2026-09-05 00:00:00 UTC | 0 | 0 | 0 |
| Sep 5 | 2026-09-05 00:00:00 UTC | 2026-09-06 00:00:00 UTC | 0 | 0 | 0 |
| Sep 6 | 2026-09-06 00:00:00 UTC | 2026-09-07 00:00:00 UTC | 0 | 0 | 0 |
| Sep 7 | 2026-09-07 00:00:00 UTC | 2026-09-08 00:00:00 UTC | 0 | 0 | 0 |
| Sep 8 | 2026-09-08 00:00:00 UTC | 2026-09-09 00:00:00 UTC | 0 | 0 | 0 |
| Sep 9 | 2026-09-09 00:00:00 UTC | 2026-09-10 00:00:00 UTC | 0 | 0 | 0 |
| Sep 10 | 2026-09-10 00:00:00 UTC | 2026-09-11 00:00:00 UTC | 0 | 0 | 0 |
| Sep 11 | 2026-09-11 00:00:00 UTC | 2026-09-12 00:00:00 UTC | 0 | 0 | 0 |
| Sep 12 | 2026-09-12 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
2 sources> 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 much absolute time it ends up saving compared to pure Python in real world resolution scenarios.
uv's total memory usage isn't that much leaner than pip's, and for parsing speed it turned out that the library pip uses, packaging, was just very unoptimized at the time uv launched. This has been significantly addressed since then:
* We did a lot of work to make version parsing twice as fast: https://iscinumpy.dev/post/packaging-faster/
* Since that blog post I made typical version parse three times faster on top of that: https://github.com/pypa/packaging/pull/1082
* Also since that blog post version filtering has
Read the rest
gone through multiple optimizations and in some cases will be more than 30x faster e.g. https://github.com/pypa/packaging/pull/1105,
https://github.com/pypa/packaging/pull/1111, https://github.com/pypa/packaging/pull/1120
At this point large dependency resolves in pip are spending very little of their time doing things in packaging, like version parsing. The main non-IO time spent in large resolves is now in the core resolver, resolvelib, which I hope to one day replace with my experimental resolver nab: https://github.com/notatallshaw/nab. Nab scales to large resolves much more efficiently than resolvelib (in fact I've cross-ported some of the algorithmic efficiency gains to uv already ;o)).