HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
duriantaco
fyn
Rust2026–2026
duriantaco / fyn

fyn

Fyn is a fork of uv for fast Python package management, dependency resolution, virtual environments, and pyproject.toml workflows.

4Distinct people
4Mentions
0Explicit recommenders
359GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Fyn is a fork of uv for fast Python package management, dependency resolution, virtual environments, and pyproject.toml workflows.

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, 3:56:07 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 hour4 dated mentions

Observed mentions: 2026-03-23 12:37:39 UTC to 2026-03-24 16:22:30 UTC.

012026-03-23 12:00:00 UTC to 2026-03-23 13:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 23, 12:002026-03-23 13:00:00 UTC to 2026-03-23 14:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-03-23 14:00:00 UTC to 2026-03-23 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-23 15:00:00 UTC to 2026-03-23 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-23 16:00:00 UTC to 2026-03-23 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-23 17:00:00 UTC to 2026-03-23 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-23 18:00:00 UTC to 2026-03-23 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-23 19:00:00 UTC to 2026-03-23 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-23 20:00:00 UTC to 2026-03-23 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-23 21:00:00 UTC to 2026-03-23 22:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-03-23 22:00:00 UTC to 2026-03-23 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-23 23:00:00 UTC to 2026-03-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 00:00:00 UTC to 2026-03-24 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 01:00:00 UTC to 2026-03-24 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 02:00:00 UTC to 2026-03-24 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 24, 02:002026-03-24 03:00:00 UTC to 2026-03-24 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 04:00:00 UTC to 2026-03-24 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 05:00:00 UTC to 2026-03-24 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 06:00:00 UTC to 2026-03-24 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 07:00:00 UTC to 2026-03-24 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 08:00:00 UTC to 2026-03-24 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 09:00:00 UTC to 2026-03-24 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 10:00:00 UTC to 2026-03-24 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 11:00:00 UTC to 2026-03-24 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 12:00:00 UTC to 2026-03-24 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 13:00:00 UTC to 2026-03-24 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 14:00:00 UTC to 2026-03-24 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 15:00:00 UTC to 2026-03-24 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-24 16:00:00 UTC to 2026-03-24 17:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 24, 16:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 23, 12:002026-03-23 12:00:00 UTC2026-03-23 13:00:00 UTC110
Mar 23, 13:002026-03-23 13:00:00 UTC2026-03-23 14:00:00 UTC101
Mar 23, 14:002026-03-23 14:00:00 UTC2026-03-23 15:00:00 UTC000
Mar 23, 15:002026-03-23 15:00:00 UTC2026-03-23 16:00:00 UTC000
Mar 23, 16:002026-03-23 16:00:00 UTC2026-03-23 17:00:00 UTC000
Mar 23, 17:002026-03-23 17:00:00 UTC2026-03-23 18:00:00 UTC000
Mar 23, 18:002026-03-23 18:00:00 UTC2026-03-23 19:00:00 UTC000
Mar 23, 19:002026-03-23 19:00:00 UTC2026-03-23 20:00:00 UTC000
Mar 23, 20:002026-03-23 20:00:00 UTC2026-03-23 21:00:00 UTC000
Mar 23, 21:002026-03-23 21:00:00 UTC2026-03-23 22:00:00 UTC101
Mar 23, 22:002026-03-23 22:00:00 UTC2026-03-23 23:00:00 UTC000
Mar 23, 23:002026-03-23 23:00:00 UTC2026-03-24 00:00:00 UTC000
Mar 24, 00:002026-03-24 00:00:00 UTC2026-03-24 01:00:00 UTC000
Mar 24, 01:002026-03-24 01:00:00 UTC2026-03-24 02:00:00 UTC000
Mar 24, 02:002026-03-24 02:00:00 UTC2026-03-24 03:00:00 UTC000
Mar 24, 03:002026-03-24 03:00:00 UTC2026-03-24 04:00:00 UTC000
Mar 24, 04:002026-03-24 04:00:00 UTC2026-03-24 05:00:00 UTC000
Mar 24, 05:002026-03-24 05:00:00 UTC2026-03-24 06:00:00 UTC000
Mar 24, 06:002026-03-24 06:00:00 UTC2026-03-24 07:00:00 UTC000
Mar 24, 07:002026-03-24 07:00:00 UTC2026-03-24 08:00:00 UTC000
Mar 24, 08:002026-03-24 08:00:00 UTC2026-03-24 09:00:00 UTC000
Mar 24, 09:002026-03-24 09:00:00 UTC2026-03-24 10:00:00 UTC000
Mar 24, 10:002026-03-24 10:00:00 UTC2026-03-24 11:00:00 UTC000
Mar 24, 11:002026-03-24 11:00:00 UTC2026-03-24 12:00:00 UTC000
Mar 24, 12:002026-03-24 12:00:00 UTC2026-03-24 13:00:00 UTC000
Mar 24, 13:002026-03-24 13:00:00 UTC2026-03-24 14:00:00 UTC000
Mar 24, 14:002026-03-24 14:00:00 UTC2026-03-24 15:00:00 UTC000
Mar 24, 15:002026-03-24 15:00:00 UTC2026-03-24 16:00:00 UTC000
Mar 24, 16:002026-03-24 16:00:00 UTC2026-03-24 17:00:00 UTC101

What Hacker News says

4 sources
> where any AI must be AI slop, and no AI is the only solution Yep, also a huge factor. Why publish something you built with an AI assistant if you know it's going to be immediately dunked on not because the quality may be questionable, but because someone sees an em-dash, or an AI coauthor, and immediately goes on a warpath? Heck I commented[0] on the attitude just a few hours ago. I find it really irritating. [0] https://github.com/duriantaco/fyn/issues/4#issuecomment-4117...
In So where are all the AI apps?
> There was no "telemetry" in uv to begin with. They're just aiming for an emotional response. Read about the "telemetry" they removed and you'll find it funny. I would personally prefer it be spelled out better, but I assume we're looking at this: https://github.com/duriantaco/fyn/blob/main/MANIFESTO.md#no-... > uv was sending a surprising amount of info to package indexes every time you installed something. These things include your OS, py version, CPU architecture, Linux distro, whether you're in CI. All baked into the User-Agent header via something called "linehaul". We ripped that out. Now it just sends fyn/0.10.13. That's it. Unless you're disputing the factual angle (I confess I tried to look at the commits, saw that the first couple commits in the repo changed over a thousand files, and gave up)... yes? I would describe sending O
Read the rest
S, python version, CPU arch, and CI yes/no as telemetry. I guess we can quibble about whether there's a more precise term for this particular form of sending information about your machine to a remote target without asking, but the description seems fair enough.
In Fyn: An uv fork with new features, bug fixes, stripped telemetry
The telemetry they removed here isn't unique to uv, and it's not being sent back to Astral. Here's the equivalent code in pip itself: https://github.com/pypa/pip/blob/59555f49a0916c6459755d7686a... It's providing platform information to PyPI to help track which operating systems and platforms are being used by different packages. The result is useful graphs like these: https://pypistats.org/packages/sqlite-utils and https://pepy.tech/projects/sqlite-utils?timeRange=threeMonth... The field that guesses if something is running in a CI environment is particularly useful, because it helps package authors tell if their package is genuinely popular or if it's just being installed in CI thousands of times a day by one heavy user who doesn't cache their requirements. Honestly, stripping this data and then implying that it was collected by Astral/
Read the rest
OpenAI in a creepy way is a bad look for this new fork. They should at least clarify in their documentation what the "telemetry" does so as not to make people think Astral were acting in a negative way. Personally I think stripping the telemetry damages the Python community's ability to understand the demographics of package consumption while not having any meaningful impact on end-user privacy at all. Here's the original issue against uv, where the feature was requested by a PyPI volunteer: https://github.com/astral-sh/uv/issues/1958 Update: I filed an issue against fyn suggesting they improve their documentation of this: https://github.com/duriantaco/fyn/issues/1
In Fyn: An uv fork with new features, bug fixes, stripped telemetry

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.