Let me know if you have things to add!

Reported as spam. I tend to agree. Removing.

Hey Ulrik, apologies for not responding sooner.

I’m more than happy to talk about adding one (or more!) mods for any of the communities I mod for right now, including c/python. I have at least one person in mind, who has been pretty active both in c/python and c/django. I’d also like to talk more about mod expectations, particularly with regard to reported posts/comments.

They changed the licensing: https://redis.com/blog/redis-adopts-dual-source-available-licensing/

I haven’t had a chance to look yet, but I’m using a pretty similar stack at, although with React instead of Nuxt/Vue. I definitely love using Docker, at least as a dev platform, because of the way it evens the field across OS’s and makes it easy to onboard new contributors. Will definitely take a closer look when I get more time.

Buuut … I do mod the !django@programming.dev community, which you might be interested in checking out. There’s also the !docker@programming.dev, which is also worth checking out.

Reading the docs and I’m a little disappointed to see that disabling telemetry is opt-in: https://bruin-data.github.io/ingestr/getting-started/telemetry.html#disabling-telemetry.

Looking at the docs, it looks like it’s an instance of ID3Tags, which appears to be based on couple of helper classes mutagen._util.DictProxy and mutagen._tags.Tags, where DictProxy (and its base DictMixin) provides the dict-like interface. Underneath that, it looks like it’s storing the actual values in a simple dict (DictProxy.__dict) and proxying to that.

I’m not seeing anything obvious that would muck with the incoming lookup key anywhere in ID3Tags or DictProxy.__getitem__ or any of the other base classes.

I have to jump off to pack for a trip, but might try this out later in a live shell session to see if there’s something odd going on with the API.

In the meantime, OP, are you positive you were looking at the same file each time? Was this in a script or in a live Python shell session?

Includes pytest integration: https://github.com/adamchainz/time-machine#pytest-plugin

Ha! Great catch. Yeah, I’ll get that sorted.

This is my favorite/most horrifying part:

The control flow is so labyrinthine that some of the code is actually indented by 23 tabs. Forget the 80-column rule – these lines don’t even start until column 92! Even if we discard the inline data tables, then the longest line in the codebase is still a whopping 387 characters long (you’ll have to scroll to the right to read it)