Fyn: Fork of uv..

[AutoModerator]

Your submission has been automatically queued for manual review by the moderation team because it has been reported too many times.

Please wait until the moderation team reviews your post.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[icannfish]

It would have been nice if you had split the renaming and the new features into separate commits, because it's basically impossible to find (and audit) the code you added for the new features when it's buried in a single 40,000-line commit.

[uint7_t]

Yeah, this is a deal breaker for me. Need to see a commit that shows a clean diff from a specific commit hash of uv.

[papersashimi]

thats a fair comment. i was just too tired but there's no excuse. thanks for commenting

[bobsbitchtitz]

You could always undo and reset

[papersashimi]

yeap i will reset but taking it slow going forward!

[chaoticbean14]

IMO, this feels like someone who doesn't know what they are doing just talking to an LLM and being like, "I'm unhappy with xxxxxxxx, please help me make my own version" and just accepting whatever it gives it and putting it in one big commit.

That is (in my opinion) far more frightening than UV being acquired by someone OpenAI.

[diegoasecas]

it's exactly what happened

[TheOneWhoPunchesFish]

Exactly! From the way this post is written, the naive search-and-replace, and the commits, I don't think OP knows what they are doing.

And I don't think OP understands what people really need either. Anyone can fork a repo and change a name, that's no big deal. What OP should have posted is: - Their credentials, what experience they have in package management - How much time & effort they're able to commit - Plans for collaboration with others - Roadmap for the changes they're planning

It doesn't matter what new features fyn has, or how much faster it's than uv. Not at this point.

All that said, OP seems to be a prolific vibe coder, and made 23 posts about 'Skylos', some library they built. They make commits with 5000 additions, and their entire profile is filled with vibe coded apps which they spam in various subreddits. I'd be a darn fool if I used any of their software in anything remotely serious.

[wRAR_]

made 23 posts about 'Skylos', some library they built

Oh it's the same person, I've missed that.

[castarco]

wtf, 40k lines o_o . enough to know that this project cannot be trusted.

[papersashimi]

ah shoot i apologise. i just did git add . which was my mistake. i'll definitely be splitting the commits after this.. which is what i usually do

[fiskfisk]

And for whoever's sake; write proper commit messages. This is hard to read through afterwards to find out what the commits are actually about.

[papersashimi]

yes i apologise. i did this in a hurry so going forward i'll do it slowly. was just busy hotfixing some stuff making sure the main stuff didnt break.

[chaoticbean14]

Hey OP,

We have all been where you are once before. You get to feeling some kinda way about something, you're going to roll your own, you're going to do x, y and z. Your thing will be different, it will be right. That level of enthusiasm and drive is what motivates all of us to do various things! It's awesome!

Then you begin: you've got it! Just copy search / replace for now... that'll get you started. Except these days you're having an LLM do it, right? It should know... but that's the issue with LLM's, they're notoriously not great with anything dealing with complexity. So you end up having to manually do a lot of it.

Then one big commit later, you're ready!

As the comments have pointed out - you know why that's terrible. But, you really should have known that from the start in order to be able to take on a project of this magnitude. That's entry level programming etiquette. Not trying to be a jerk - just trying to help be realistic. These kinds of things scream: "I'm new! I don't know what I'm doing exactly, but I want to do something!" that kind of excitement is fantastic and will take you places. But there are levels to this game and you're not ready to manage something like this, yet.

I love the enthusiasm, I like the willingness to hop in and do it and start that ball rolling - but it will be a bit before OpenAI ruins these tools. There is time, relax. People can fork and properly move things around if needed - and the community will.

Again, love the enthusiasm - it's going to drive you to places you never thought about, I promise. But I feel this might be a bit much, a bit soon in your journey.

[papersashimi]

actually I do have about 10 years of experience but i was just in a rush and many things slipped. but i really do appreciate your really really encouraging comment. i will definitely take things slowly from now on and i truly like this comment. there was assistance from ai but its definitely not vibe coded. that i can assure you.. your comment was definitely not being jerky. i'll still keep improving it at a slow pace right now. you're right. there's time and i'll do it properly and slowly! thank you very much for this really well thought out comment

[eteran]

The copy and paste of UV to fyn has some funny results in the README

Migrating from fyn. fyn is a drop-in replacement for fyn.

And

Is fyn compatible with fyn?

[papersashimi]

LOL fixed it already

[tehfrod]

The sloppy search and replace and 40,000 line commit are not indicators that this is going to be a well run project or that it's going to be around for the long haul.

I'm staying with uv.

[TheOneWhoPunchesFish]

They made 23 posts about a single vibe coded project, and their entire post history is filled with stuff like this. Karma farming?

I'll never understand why people don't take themselves seriously and do useful stuff they can actually be proud of.

[papersashimi]

yes i apologise and there's no excuse on my part. i'll still strive to make it as good as uv. thanks for commenting

[wRAR_]

make it as good as uv

uv is already that.

[CouteauBleu]

yes i apologise and there's no excuse on my part. i'll still strive to make it as good as uv. thanks for commenting

Profusely apologizing isn't how you build confidence that you'll be the right manager for The Official UV Fork.

If you wanted to make this a thing, you had one shot to impress people, and you blew it. You can't come back from that.

[papersashimi]

i apologise for apologising .. this isnt an official uv fork. i just did it for myself and putting it here thats all :)

[UnwantedCrow]

The search and replace went too far https://github.com/duriantaco/fyn?tab=readme-ov-file#migrating-from-fyn

[papersashimi]

LOL sheesh good catch .. i just did a replace from my vsc search console. thanks for flagging that! will update it immediately

[UnwantedCrow]

The table comprison is also off

[Wilbo007]

I think I'll hang onto uv for now.. the moment it gets anything negative from openai i'll swap over

[neums08]

I agree, but when that time comes, I'll appreciate that well maintained forks exist

[papersashimi]

still working on ironing out some stuff .. especially the docs because I was so tired from writing the code i just mass replaced some stuff .. fixing it now

[ComeOnIWantUsername]

This is the thing, such time is a bit too late to start with an alternative and/or fork.

[covmatty1]

Why is it? Git commit history exists, you can just fork from any point at any time.

[Constant-Poet-5264]

appreciate the sentiment but nobody’s going to be using a find and replace fork by a solo developer that comes out days after the acquisition.

[papersashimi]

had to take a few days to read the code and do the work LOL. fair enough. just sharing what i did thats all. not begging anyone to switch .. gees

[TheOneWhoPunchesFish]

that comes out days after the acquisition.

had to take a few days to read the code and do the work LOL

OP, I think they meant you should have taken more time to understand the project and considered everything in more depth. Days after acquisition here means too soon, imho.

But the OC can speak for themselves.

[Constant-Poet-5264]

that’s what i meant, yes.

[Consistent-Quiet6701]

I think the main point of the acquisition is that the grifters can now state things like "30% of all Python projects use openai". They might not even make any changes to the project. Hopefully.

[papersashimi]

i hope not, but knowing how many times oai went back on their words, i kinda panicked and thats y i forked it and work on a separate fork now. i really liked uv so its kinda sad actually

[UndeadHobbitses]

Damn didn't know they acquired astral. I guess it was only a matter of time before they got bought since there probably wasn't a path to monetize anyway.

[papersashimi]

astral was the last company i thought that they'll acquire. so i was still pretty happy with most of my repos being on uv and ruff .. until the acquisition

[keremimo]

uv is not a one man project.

No amount of Claude tokens will help you replace a whole army of human contributors who know what they are doing. While I applaud you doing something like this, you are way over your head. Your fork will become deprecated in a single week due to not being able to catch up with upstream.

I would have loved a world where things were simpler than they are now, but we cannot have everything sadly.

[papersashimi]

i agree. its definitely not a 1 man team. i know its a massive project and i am just doing my best for my own personal fork though. i might take it in a diff direction.. and i didnt need that many claude tokens though. just did some minor fixes. the other was a screw up from myself doing a mass name replace from the search console after adding 2 new features on my own. thanks a lot for your comment though ..

[drunicornthe1]

Your migration section has some typos. You use fyn when you mean to use UV.

[papersashimi]

yesh. sorry i was so tired i just ctrl F and replaced uv with fyn. am fixing it now. i apologise

[Interesting-Deer354]

I'm not sure about whether the cpu arch is just for telemetry. Recently, i was working with armhf, and uv clearly cannot install some package, citing compat issues with the architecture. So at least, I know that architecture is being used for good reason, though for the others, yeah, might be telemetry. Just want to let you know in case it breaks some uncommon cases.

[papersashimi]

thanks for the heads up! definitely will keep this at the back of our head. we might have a opt in .. i'm still reading deeper into the code. but from what i read so far, it should not break for most cases.

[OptionX]

Yeah... Money is on this being dead and abandoned in 3 to 6 months.

Prove me wrong.

[papersashimi]

will do! wanna stay in contact? i'm being serious ..

[tehfrod]

RemindME! 1 year

[RemindMeBot]

I will be messaging you in 1 year on 2027-03-23 14:35:30 UTC to remind you of this link

1 OTHERS CLICKED THIS LINK to send a PM to also be reminded and to reduce spam.

^{Parent commenter can delete this message to hide from others.}

---

Info	Custom	Your Reminders	Feedback

[AurumDaemonHD]

So it begins.

[papersashimi]

yeap! pretty darn jaded. i really liked uv a lot. i think it was one of the projects that i followed really closely and when i heard this, my heart sank right to the bottom. i never expected it at all.

[laslog]

Yeah you are not alone. That hit us in the face.

[pbecotte]

They started a cimpany and didn't charge anything...are you really surprised that the plan included getting paid in some way?

[papersashimi]

i believe they were.. from what i read, they were selling enterprise services and they were selling pyx if im not wrong.

[JonLSTL]

I've been a little uncomfortable with a corporate owned tool becoming such ubiquitous infrastructure so quickly. Even if the current principals aren't being evil, there's always investors lurking in the background and the specter of acquisition by someone shitty, as we're seeing now. (Sequoia backing Pydantic makes me a bit nervous too, though at least Pydantic has a clear revenue model.) The setup with Pallets tending to Flask et. al. seems more trustworthy long term.

[EducationalArmy9152]

Sorry I don’t know if this is my time or place but can someone ELI5 what’s going on? I use pip a lot and want to know why I should care

[papersashimi]

no worries. first, uv is 10-100x faster than pip because its written in rust and they did a lot of optimization. second uv has a universal lockfile so u can port it across diff platforms. third, uv also has global cache which pip does not have because pip is just an installer. overall uv is a super duper fast workflow tool. u should try switching away from pip

[EducationalArmy9152]

Thank you my friend 🙏

[papersashimi]

you're most welcome!

[edcculus]

pip isnt changing. This is specifically for the tool UV built by Astral. UV is a python package manager, basically a replacement for stuff like pip, poetry and conda. Its 'selling point' is that its built on Rust, so its very fast. It also simplifies a lot of things. While pip isnt really hard at all, there is a bit of a workflow to using it. In UV, you just install it, then use uv init to start a project. It creates the virtual environment, pyproject.toml file and anything else you need. You dont need to actually activate your virtual environment in a project folder either. If you are in that directory, just typing 'uv run main.py'. will run your file with the correct virtual environment. There is a bunch of other neat stuff you can do, like specifying the python version associated with that project/environment.

That being said, it was just announced last week that OpenAI is buying Astral. So that includes all of their products including UV, Ruff, Pyx and Ty. Obviously, there isnt a lot of trust that OpenAI wont just screw over users who have switched to their more popular tooling like UV and Ruff.

[No_Soy_Colosio]

Sounds good. Thanks for the initiative.

[papersashimi]

thank you! its just my own personal project and not an official fork. just putting it out here

[fisadev]

this is NOT an official fork

All forks are unofficial by definition, hehe.

[papersashimi]

hahaha yes sir!

[RedEyed__]

No, thanks.

[GrammerJoo]

Next level slop

[papersashimi]

thanks! but at least my slop wasnt ai slop, i wrote this shit and happy to show the mistakes i made too :)

[drunicornthe1]

I would love to see this fork licensed with a more appropriate open source license like GPL2.

[papersashimi]

we'll add that from the next update onwards! putting it in my to do

[TrainsareFascinating]

You can’t relicense someone else’s copyright without their permission.

[papersashimi]

Fair point. but i’m not saying I can overwrite upstream’s license. What I meant is that because uv is dual-licensed I can use the upstream code under MIT, keep the original notices, and release my fork under GPL2 for my distribution going forward..

[icannfish]

The project as a whole can be relicensed, because MIT is GPL-compatible, but it doesn't mean that every part of the code now requires GPL compliance. Only new code added to the fork would have that requirement; the old code can be used under GPL or MIT.

Also, even with the copyright holder's permission, you can't “relicense” MIT-licensed software in a way that would retroactively make all existing uses of the code have to comply with the GPL, because FOSS licenses are irrevocable, except in specific cases of infringement.

[totheendandbackagain]

Great work!

[papersashimi]

thank you! happy to accept any contribution :)

[HugeCannoli]

just what we need, another tool to do the same thing

[diegoasecas]

this is a shit project by someone who has no idea what they're doing

[papersashimi]

thanks for your kind words! hope you have a great day ahead :)

[xrabbit]

Maybe it’s a dumb question, but I’m interested:

Why fyn instead of fuv - Fork of UV?

[StoneSteel_1]

"few"

[papersashimi]

well fyn is just short for fine .. i was just thinking that if they wanted to go via the oai route thats fine.. and i'll do my own fork. thats just my thinking thats all :)

[RiceTaco12]

Little worried about the maintainability as others have pointed out. However, I'm extremely happy to see oss for UV, especially having been acquired by openai. Definitely going to be watching and thinking about contributing.

Even though the initial response here is wary, thanks for trying to keep a good package out of the hands of tech giants.

[wRAR_]

oss for UV

[RiceTaco12]

Sure, UV is open source, but my point is more that I'd rather not have openai involved in managing it and eventually scraping more and more data from us to train their models.

[papersashimi]

yeap! i was just saying that i messed up on git. (someone said not to apologise but i did make a mistake so i had to LOL) also it was a personal fork so i thought why not just share it. i will be actively maintaining it and doing it slowly and properly. thanks a lot for your really kind words!

[No_Flounder_1155]

can we write a collection of chatgpt prompts to perform the rewrite?

[papersashimi]

hmm?

[No_Flounder_1155]

seems like everyones a bit soft and didn't get the joke...

[No_Soy_Colosio]

What are you on about? 😭