> uv ignores pip’s configuration files entirely. No parsing, no environment variable lookups, no inheritance from system-wide and per-user locations.
Stuff like this sense unlikely to contribute to overall runtime, but it does decrease flexibility.
Astral have been very clear that they have no intention of replicating all of pip. uv pip install was a way to smooth the transition from using pip to using uv. The point of uv wasn't to rewrite pip in rust - and thankfully so. For all of the good that pip did it has shortcomings which only a new package manager turned out capable of solving.
> No bytecode compilation by default. pip compiles .py files to .pyc during installation. uv skips this step, shaving time off every install.
... thus shifting the bytecode compilation burden to first startup after install. You're still paying for the bytecode compilation (and it's serialized, so you're actually spending more time), but you don't associate the time with your package manager.
In most cases this will have no noticeable impact (so a sane default) - but when it does count you simply turn on --compile-bytecode.
I agree that bytecode compilation (and caching to pyc files) seldom has a meaningful impact, but it's nevertheless unfair to tout it as an advantage of uv over pip, because by doing so you've constructed an apples to oranges comparison.
You could argue that uv has a better default behavior than pip, but that's not an engineering advantage: it's just a different choice of default setting. If you turned off eager bytecode compilation in pip you'd get the same result.
> You could argue that uv has a better default behavior than pip, but that's not an engineering advantage: it's just a different choice of default setting. If you turned off eager bytecode compilation in pip you'd get the same result.
Until pip does make the change, this is an engineering advantage for uv. Engineers working on code are part of the product. If I build a car with square wheels and don't change them when I notice the issue, my car still has a bumpy ride, that's a fact.
Haven't heard a word from Vietnam Airlines - my whole family are members. Interesting to see how a Vietnamese organisation handles this type of incident.
Really not sure - my partner is Vietnamese (dual citizenship) but we don't live there. We flew Vietnamese Airlines for 4 flights in the last month (2 international). I'd like to think we'd receive an email about this in any case - so far only an email from HIBP.
Changing your password wouldn't help in this case. They used lastpass to store their crypto wallet seed phrase - this can't be changed. They would have to move to a new wallet and pay transfer fees in the process.
Yeah I guess some people also don’t want to go through the hassle or cost to change the locks on on their actual homes when their keys are compromised/move into a new home
Considering it cost me $750 to rekey all my locks and now one can duplicate keys from just an image, I don't think I would rekey ally locks every time my key is visible in public (which one should consider compromised).
Certainly! Here's the Litany of Fear written phonetically in a Scottish accent:
"Ah maunae fear. Feer is the leel-deeth that brangs total obleetiration. Ah will face mah feer. Ah will pemreet it tae pass ower me an throo me. An when it hus gaun past, Ah will turn the inner ee tae see its path. Whaur the feer hus gaun, there will be naethin'. Only Ah will remain."
There's also not a huge amount of resources for "Scottish written phonetically" except the Scots Wikipedia which was exactly that and written by an American kid.
Very cool - I used a website with a custom qr code generator [1] and some hacky RPA tool about 8 years ago to create custom QR codes for each guest at our wedding. My wife created a wedding logo and we had that in the middle of our QR code - it worked well. The QR code was a personalised URL for each guest's rsvp which used a URL shortener [2] installed on our wedding domain (hosted on a free micro AWS instance).
Was a fun way to do my part for our wedding planning.
Glad I didn't take part in a promotion they offered last week for 25% off giftcards via ShopBack. Looks like a dodgy way to milk money off their customers.
This reminded me of when I started listening to a new podcast and also tried a new podcast app at the same time. The podcaster had this unusual editing style where he'd cut all the pauses out of his podcast and I really grew to love it. It was only when I tried a different podcast that did the same thing that I realised I had set the app to cut out all of the silences.
After that I've been unable to go back to normal speed podcasts - I just don't have the time or patience.
Podcast Addict [0] has that feature but only runs on Android devices. I use that as well as speeding up podcasts to 2x speed which makes things better for me.
Stuff like this sense unlikely to contribute to overall runtime, but it does decrease flexibility.
Astral have been very clear that they have no intention of replicating all of pip. uv pip install was a way to smooth the transition from using pip to using uv. The point of uv wasn't to rewrite pip in rust - and thankfully so. For all of the good that pip did it has shortcomings which only a new package manager turned out capable of solving.
> No bytecode compilation by default. pip compiles .py files to .pyc during installation. uv skips this step, shaving time off every install.
... thus shifting the bytecode compilation burden to first startup after install. You're still paying for the bytecode compilation (and it's serialized, so you're actually spending more time), but you don't associate the time with your package manager.
In most cases this will have no noticeable impact (so a sane default) - but when it does count you simply turn on --compile-bytecode.
reply