Backend (and sometimes frontend) software engineer working on sports data at Elias Sports Bureau.
Experience with: Python, Django, Typescript/JS, infrastructure, databases
Find me:
Crap, now I need to know about competitive Jenga …
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.
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?
I don’t have much to say besides, good job. We all believe in you.
Looking at the thinkTank website, I think you’re talking about the Secure Pocket Rocket model, but I’m not sure.
Anecdata here in the US, but my local mom and pop pharmacy (which I love) currently would lose $200/mo on my vyvanse because of my insurance and the whole generic vyvanse nonsense. This system sucks.
For the time being, I fill my vyvanse at Walgreens and hope they’re losing $200/mo on it. I fill everything else at the mom and pop, until they let me know the situation is better.
Includes pytest integration: https://github.com/adamchainz/time-machine#pytest-plugin
The installed packages themselves won’t be faster, but they will install faster, sometimes much faster.
Yes, I believe wheels will generally be preferred by pip
.
My latest is Fresh Off The Boat
@allinalllearners@lemmy.world you seem to have linked to just an image.
Care to update this post?
The other thing to remember is that post IDs are relative to the Lemmy server you’re working with. So post/12345
is almost surely not post/12345
on another server.
I mod a couple of communities on another server and this caught me off guard when trying to share what I thought were good URLs.
OP, you could even use a local file/sqlite database in the repo and just update and commit it when the script runs.
Simon Willison has a cool approach for this that runs in GitHub Actions and keeps the versioned state in git itself: https://simonwillison.net/2020/Oct/9/git-scraping/
Let me know if you have things to add!