The Steering Council is on the case. They'll impose a lifetime ban, a forced public self-criticism and ten lashes with a whip, all of which has been suggested by the totally independent CoC troika.

confused why coc is okay, dong is not okay.

Some animals are more equal than others. If you point out that CoC can be pronounced "cock", they'll say you are not "acting" "in good faith" and ban you.

The Steering Council makes up rules as it goes along.

You Sir are a genius! This will be my pronunciation of "coc" from now on.

Serious answers are flagged, so it shall remain a mystery.

oh no

I remember that I wanted to implement a python module that would improve upon the builtin Django groups. So following a tradition of adding ex to the end of the existing name, I named my module "groupsex".

After taking a peek at it I decided to rename it to groups2 instead :)

Not python but literally yesterday I had do a double take when I saw https://github.com/janestreet/sexplib

I was introduced to S-Expressions a few decades ago yet it is still the case that 100% of the time I pronounce 'SEXP' as 'SEX-P'

I occasionally run across something called K8-Sexecutor, or at least that's how I pronounce it.

Ah the traditional lispish naming for predicate functions, applied to questions of an amorous nature!

the children's exchange dot com drops the s, just in case.

Let's not forget this fine contribution to the Python's nest. https://github.com/ajalt/fuckitpy

> The web devs tell me that fuckit's versioning scheme is confusing, and that I should use "Semitic Versioning" instead. So starting with fuckit version ה.ג.א, package versions will use Hebrew Numerals.

Big lol

And this: https://github.com/Roger/escrotum

There are also seeeeeveral LOVE2D libraries with overtly sexual names. The most egregious example that comes to mind is the (now defunct compat library) "AnAL." There's also HUMP, Pölygamy, Swingers, Adult Lib (debatable but close enough), Gspöt, Möan.lua, fLUIds (also debatable, but there's a clear theme here), and yaoui.

Let’s not forget https://web.archive.org/web/20210308033218/https://github.co....

> https://github.com/ajalt/fuckitpy

10 years ago this was just a joke, but today, now that we're finally agile enough so that any disorganized jumble of completely unreviewed and unversioned notebooks might suddenly become a production pipeline? Why let a little thing like critical errors halt the execution of that perfect nightmare you've been working on! The only problem is that the database still won't let you shove a string into an integer slot, but data-science is looking forward to switching over to spreadsheets completely as soon as we can migrate the data from redshift.

I'm sure this tiny inconvenience can be taken care of with the help ofhttps://github.com/ostafen/viperdb or, if we want to stick to the juvenile innuendo, https://pythonhosted.org/pickleDB/

You can always ask the folks at Experts Exchange for guidance on naming things.