News for hackers. Stuff that matters.
Re:What to do about GPU packages on PyPI? by kortex on Thursday May 20, 2021 @07:08PM (#27228586)
Yeet them into the sun. I say that as someone whose job benefits greatly from the convenience of easy to pip-install GPU wheels, and has fought many hours compiling GPU libraries from scratch.

I think it's the wrong abstraction. It encourages ridiculous amounts of bloat and duplication, of bandwidth, file systems, virtual environments, and docker images. It's really not actually that portable.

It encourages blindly installing unauditable giant binary blobs which run with all kinds of leaky abstractions. But boy howdy are they convenient.

I think "Allow external hosting" is the best case here. The first point of user expectation on PEP 470 is:

> Easily allow external hosting to "just work" when appropriately configured at the system, user or virtual environment level.

That's already out of the window once GPGPU is involved. The ecosystem is much better than it used to be, but there is still no plug-and-play GPGPU on linux without hiccups.

Let PyPI be the namespace, registry and lookup, and let users pass an --allow-external again, or (less optimal imho) do something like Conda channels. Improve the user experience for integrating with external hosts.

Pip is unlike NPM, Cargo, go get, etc because Python is much more intimate with linked libraries. It's unlike Brew because it's way more cross-platform. It's much closer to apt-get in this regard, and its challenges are different. Apt-get has sources lists, and I think that makes some sense for Python as well.

Re:What to do about GPU packages on PyPI? by tgamblin on Friday May 21, 2021 @10:30AM (#27234430)
This is why Spack supports external packages. For any package, you can tell spack the prefix where it lives and build with that install prefix instead of a spack-built version:

https://spack.readthedocs.io/en/latest/build_settings.html#e...

People use this the tell Spack where the system cuda libs or system MPI are.

Re:What to do about GPU packages on PyPI? by dataflow on Thursday May 20, 2021 @07:15PM (#27228652)
> Yeet them into the sun

Wow, gen Z lingo has come into HN faster than I expected. Can someone translate this to traditional English? The definition I find for 'yeet' ("an exclamation of excitement") isn't particularly enlightening...

Update: I see, thanks all!

Re:What to do about GPU packages on PyPI? by kortex on Thursday May 20, 2021 @07:19PM (#27228683)
As I am solidly a millenial, I guess I'll take it that I'm keeping hip to the lingo of kids these days :)

My definition of "Yeet" is to fling/throw/hurl something, typically with great vigor. Urban Dictionary defines it as "To discard an item at a high velocity." Derives from the Latin Iacio, From Proto-Italic jakjō‎, from Proto-Indo-European (H)yeh₁-‎ ("to throw, let go"). JK I just made that up, but it's actually plausible.

Never heard the "exclamation of excitement" definition.

Re:What to do about GPU packages on PyPI? by duskwuff on Thursday May 20, 2021 @07:58PM (#27228967)
From another milliennial: the only detail I'd add is that "yeet" is less about pure force and more about the impulsive, imprecise nature of the action. Throwing a basketball into a hoop wouldn't be described as "yeeting", except perhaps if it were by complete accident.
Re:What to do about GPU packages on PyPI? by sp332 on Thursday May 20, 2021 @10:04PM (#27229736)
Right, if precision is involved, it's "LeBron".
Re:What to do about GPU packages on PyPI? by shortj on Friday May 21, 2021 @12:19AM (#27230464)
Yeet is for distance/power. Kobe is for accuracy/precision.
Re:What to do about GPU packages on PyPI? by jszymborski on Thursday May 20, 2021 @07:39PM (#27228830)
Also worth mentioning that the past tense of yeet is widely agreed to be yote or yoted as in:

"The first empty soda can was yote many moons ago"

Re:What to do about GPU packages on PyPI? by rackjack on Thursday May 20, 2021 @08:00PM (#27228988)
"widely agreed upon" is debated.

According to Wiktionary:

"yeeted

1. simple past tense and past participle of yeet" [1]

Worth noting there is a fair amount of discussion on whether the past tense is "yeeted" or "yote", or even "yaught": https://en.wiktionary.org/wiki/Talk:yeet

See also: https://linguistics.stackexchange.com/questions/28300/what-i...

[1]: https://en.wiktionary.org/wiki/yeeted#English

(I do think it would be pretty funny if the past tense ended up as "yote", though.)

Re:What to do about GPU packages on PyPI? by kortex on Friday May 21, 2021 @07:38AM (#27232759)
The ablaut conjugation yeet/yote/yitten is hilarious and gets my vote but it seems like yeeted will win out.
Re:What to do about GPU packages on PyPI? by FridgeSeal on Friday May 21, 2021 @09:40AM (#27233868)
I particularly enjoy “yote” as it sounds so formal/medieval.
Re:What to do about GPU packages on PyPI? by collegeburner on Thursday May 20, 2021 @10:28PM (#27229878)
Nahh it's definitely yeeted.
Re:What to do about GPU packages on PyPI? by ZephyrBlu on Thursday May 20, 2021 @11:08PM (#27230059)
I've never seen a zoomer say yote. Yeeted on the other hand...
Re:What to do about GPU packages on PyPI? by JCharante on Friday May 21, 2021 @05:54AM (#27232145)
I've seen and heard yoted many times before, because double past tensening a word adds comedic effect.
Re:What to do about GPU packages on PyPI? by StavrosK on Friday May 21, 2021 @06:22AM (#27232282)
> Derives from the Latin Iacio, From Proto-Italic jakjō‎, from Proto-Indo-European (H)yeh₁-‎ ("to throw, let go"). JK I just made that up, but it's actually plausible.

I think you're way overestimating the people who come up with new words :P

Re:What to do about GPU packages on PyPI? by tome on Friday May 21, 2021 @03:01AM (#27231268)
A derivation from iacio via jettison doesn't sound too implausible.
Re:What to do about GPU packages on PyPI? by dataflow on Thursday May 20, 2021 @07:23PM (#27228705)
Hahaha I see, thanks. It reminds me of defenestration!
Re:What to do about GPU packages on PyPI? by sudosysgen on Thursday May 20, 2021 @07:17PM (#27228661)
To yeet is to throw enthusiastically, happily and without care.
Re:What to do about GPU packages on PyPI? by sirsinsalot on Thursday May 20, 2021 @07:19PM (#27228681)
My 20 girlfriend informs me it means to fling or throw but with a comical or exuberant effort.
Re:What to do about GPU packages on PyPI? by jhrmnn on Friday May 21, 2021 @06:59AM (#27232518)
FWIW, it already made it in the Oxford dictionary:

https://www.lexico.com/definition/yeet

Re:What to do about GPU packages on PyPI? by hawthornio on Thursday May 20, 2021 @11:04PM (#27230036)
I believe Yeet! Vine is the source usage.

https://m.youtube.com/watch?v=qYWl5ou6R4g

Re:What to do about GPU packages on PyPI? by dataflow on Thursday May 20, 2021 @11:12PM (#27230078)
Amazing. Thanks!
Re:What to do about GPU packages on PyPI? by kstrauser on Thursday May 20, 2021 @07:18PM (#27228671)
s/yeet/toss dramatically/
Re:What to do about GPU packages on PyPI? by swiley on Friday May 21, 2021 @08:39AM (#27233249)
Unpopular opinion: wheels are a bad idea in general for the same reasons.