3 ms·
It's hard for me to name a problem domain that doesn't have 3 different python packages doing the same thing three different ways, each more clever and less und
by BobbyJo 3y ago
It's hard for me to name a problem domain that doesn't have 3 different python packages doing the same thing three different ways, each more clever and less understandable than the last.
- psunavy03 3y agoWhy TF would you name an HTML parser BeautifulSoup?
- nijave 3y agoI Googled it, apparently it comes from this https://en.m.wikipedia.org/wiki/Tag_soup https://en.m.wikipedia.org/wiki/Tag_soup
- psunavy03 3y agoOK, I get it, but when I'm trying to write automation for a shop that isn't natively Python-savvy (long story short, it made sense when I started a side project which evolved), if I use that library and ever move on, I now have to document in comments or somewhere WTF "BeautifulSoup" means. Because of some rando's inside joke they thought was funny.
- Lammy 3y agoThis is actually one reason I prefer the Ruby ecosystem — whimsy is still welcome. The world has enough Noun Manager projects.
- psunavy03 3y agoWhen I'm trying to figure out how to build a side project for my team and simultaneously fighting company bureaucracy who reflexively stonewalls things on the order of "no one's done that before, we need permission," I don't also want to deal with some immature idiot's stupid namespace. I want a damned Noun Manager for my own sanity's sake.
- benji-york 3y agoThe name is also a reference to Alice in Wonderland.
- raverbashing 3y agofor real If it's not on the stdlib, I'd go with the most popular one, or just DIY No, it is not "best practice" to use a barely tested module with half the bugs affecting its main functionality just because someone thinks it is Unfortunately package abandonment is a thing and they don't even bother fixing needed bugs (which, coupled with 'the urge to deprecate' makes things annoying)