5
[-] jnovinger@programming.dev 6 points 2 weeks ago

Crap, now I need to know about competitive Jenga ...

17
24
6
39
[-] jnovinger@programming.dev 1 points 1 month ago

Reported as spam. I tend to agree. Removing.

27
5
14
2
7

Via https://mastodon.cloud/@radiac/112641898082821618

In my experience flask is great until it isn't - I've seen quite a few projects which outgrew it, and the lack of django's batteries and guard rails left a maintenance nightmare. Not sure if it'll be helpful, but as a result I wrote nanodjango, which lets you write a django site in a single file, then convert it to a full project if you outgrow it.

3

DEFNA: Django Events Foundation North America

Via Django News #238

15
[-] jnovinger@programming.dev 1 points 3 months ago

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.

[-] jnovinger@programming.dev 1 points 3 months ago

That's the way I read the proposal, which I definitely like.

[-] jnovinger@programming.dev 3 points 6 months ago

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.

[-] jnovinger@programming.dev 6 points 6 months ago

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.

[-] jnovinger@programming.dev 2 points 6 months ago

Thanks, I appreciate the reply and openness to doing things besides just video.

[-] jnovinger@programming.dev 15 points 6 months ago

Do you have a written version?

I really dislike having to watch an entire video to catch the one bit of useful information. I wish I had the time to watch entire videos, but honestly, I don't. On top of that, my brain has often wandered off well before I get to the interesting bit.

[-] jnovinger@programming.dev 2 points 8 months ago

Love it. Thanks for the improvement!

[-] jnovinger@programming.dev 3 points 8 months ago

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?

view more: next ›

jnovinger

joined 1 year ago
MODERATOR OF