Backend (and sometimes frontend) software engineer working on sports data at Elias Sports Bureau.
Experience with: Python, Django, Typescript/JS, infrastructure, databases
Find me:
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.
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
This proved to be a fair amount of work, absent a bot of some sort that I haven’t had time to create yet.
So, I failed toward just including events in the sidebar, with a link to python.org’s Event Calendar.
I took a look around over at programming.dev, but couldn’t find a C-specific community. Although we do have these (semi-) related communities:
You can also request new communities in !community_request@programming.dev . Oh man, I was totally wrong. Check out !c_lang@programming.dev !
There’s also !data_engineering@programming.dev , over at programming.dev, which is a software engineering/prorgramming/computer science focused instance.
Ha! Great catch. Yeah, I’ll get that sorted.
Ugh, my apologies folks. Clearly still figuring out how to do this Lemmy/Mastodon federation thing.
Also trying out Today in Python!. I accidentally launched the first one early, in that I posted about 20 June 2023 on 19 June 2023. Whoops.
Next experiment is Talk Tuesday where each top-level comment is about a particular conference talk that a commenter liked and why they like it.
Thought I would also keep track of things we experiment with here. The first is Media Mondays where we track podcast and video episode from the community over the last week.
I’m personally still loving Regolith Desktop on top of Ubuntu/Debian.
@db0@lemmy.dbzer0.com posted a new Python wrapper for Lemmy that he’s started working on over at !python@programming.dev : https://programming.dev/post/39578
Reported as spam. I tend to agree. Removing.