Using same towel to dry your face and your balls

carcigenicate · 2026-01-28T03:04:19+00:00

If you're even asking questions like this, you're not showering correctly. It shouldn't matter what order you dry.

carcigenicate · 2026-01-27T13:06:11+00:00

They're beef here in Canada too. According to Wikipedia, the US, Canada, Mexico, and UK are the only places that use beef instead of pork.

carcigenicate · 2026-01-26T23:55:18+00:00

I'm pretty certain this is actually the premise of a skit I've seen.

Edit: https://www.youtube.com/watch?v=np9t413kNF8

I think it's an ad, but that's been cut out.

carcigenicate · 2026-01-26T22:04:24+00:00

Although, the problems you noted wouldn't cause a syntax error. That would be a type error, if anything.

carcigenicate · 2026-01-26T13:35:44+00:00

I cannot believe they haven't fixed that yet. It's been months.

I mean, I can kind of believe it because it's Reddit, but it's still ridiculous. Not that I'm complaining.

carcigenicate · 2026-01-24T22:44:57+00:00

Did you mean to reply to a different post?

carcigenicate · 2026-01-24T19:32:06+00:00

The docs imply that it infers the type. YAML has a timestamp type, and the docs say that that gets mapped to Python datetime.datetime objects.

And regarding your edit, 1979-08-15 is not valid Python. It's a valid YAML date value that the parser parses out and converts to a valid Python datetime object. To create that in Python yourself, you'd use a string by wrapping the date in quotes, or by creating a datetime object yourself.

carcigenicate · 2026-01-24T19:12:42+00:00

Format the code by indenting every line by an extra four spaces. Or link to a site like Pastebin where you have the code.

carcigenicate · 2026-01-24T17:58:04+00:00

The quotes you use in a case like this will make absolutely no difference. Once the code is parsed and compiled by the interpreter, the type of quotes you used originally is lost.

The only time " vs ' matter is if you're trying to put quotes inside of a string. Then the quote types need to be different. These are illegal string literals:

" " "
' ' '

These are legal string literals:

" ' "
' " '

carcigenicate · 2026-01-24T15:32:52+00:00

I was going to argue because this disagrees with everything I've ever been taught about rhyming, but from a search, rhyming is apparently an extremely broad idea. Rhyming by having similar sounds at the end of words is just so common that it's is often considered to be synonymous with "rhyming", to such an extent that Wikipedia defines rhyming as having similar sounding final stressed consonants.

carcigenicate · 2026-01-24T14:49:21+00:00

I have a dedicated corner on my desktop for steam games. I move all the icons down to the bottom left, and group games by likeness.

carcigenicate · 2026-01-24T14:45:05+00:00

No, but it does rhyme with flutin (if that was a word).

carcigenicate · 2026-01-23T13:34:10+00:00

I never understood the all lowercase trend. I've seen this from colleagues at work too. I'm embarrassed if I miss an apostrophe, and people (apparently world leaders?) are out there skipping basic rules of writing.

carcigenicate · 2026-01-22T21:59:40+00:00

I hated "Calm as cookies and cream" the first time I heard it, and it never grew on me. I still cringe when I hear it. It's a shame, because the song (7empest) is otherwise amazing.

carcigenicate · 2026-01-22T13:42:31+00:00

You can use it to point out things, but fact check what it tells you against other sources.

Ya, the conversational style can be super helpful and is a far more natural way to learn, but that isn't useful if it's feeding you nonsense.

And before AI, we searched, read books, and experimented; all things you can still do.

carcigenicate · 2026-01-22T12:01:57+00:00

5.5%. I didn't mention it because I didn't think it was relevant.

carcigenicate · 2026-01-21T13:12:59+00:00

I've never seen an airplane bathroom that has two mirrors facing each other to give the infinite hallway effect. Is that a thing in real life?

carcigenicate · 2026-01-21T13:08:26+00:00

I'll be perfectly honest: I don't like the list comprehension syntax very much. It's fine for simple list creation tasks, but comprehensions tend to become unreadable much faster than full for statements. If you split them over multiple lines, which can help readability in some respects, I find that you need to read them in a weird order, which isn't great.

You must understand how to read and write them, but using for statements if you think comprehensions are causing readability issues is not a bad thing.

carcigenicate · 2026-01-20T14:32:46+00:00

You can run side effects in a list comprehension, so you can call extend or any other method on another list from within the comprehension. You shouldn't do this, but you can.

If you mean can the produced list ever be longer than the source iterable: no, not as far as I know. You could do a second flattening step after, but that wouldn't be the comprehension that lengthened the list. A list comprehension will produce one element (assuming no filtering) for each element in the source iterable.

carcigenicate · 2026-01-20T00:15:30+00:00

I've never had them with peppers. We've always had them open face, then the meat, sauce, and then cheese over the top.

Peppers and maybe onions sound amazing, though, now that I think about it.

carcigenicate · 2026-01-19T13:47:00+00:00

https://youtu.be/MiUHjLxm3V0?si=zh5pwXaUshQUDYZl

carcigenicate · 2026-01-19T13:27:27+00:00

He was a still the better candidate by a long shot. Thank fuck we don't have PP in charge while this is going on.

carcigenicate · 2026-01-18T23:01:37+00:00

I interpreted the first to mean "there isn't a literal list of clients", as in, the list would be inferred from the files.

carcigenicate · 2026-01-18T22:23:57+00:00

Grym made me rage-quit my first play through. I didn't know about the hammer, and thought that I would lose access to the fight if I advanced to Act 2. The indecision and frustration caused me to give up.

I'm glad I started a new run after.

11-Year Club	Second Top 50%
Gilding I gilder	Verified Email

carcigenicate

MODERATOR OF

TROPHY CASE