Improved NamedTuple declaration

[amogus07]

Description

Utilize a new way of declaring NamedTuples, which allows for typechecking as well. Maybe the latter is now redundant in other places, but I'm not that familiar with the codebase yet, so I just changed the declarations (and hopefully used the correct types). While I was at it, I also ran poetry update, but I'll revert poetry.lock in case I wasn't supposed to do that. This is my first commit here, so I hope I didn't do anything wrong...

To Do

• Documentation.
• Changelog.
• Tests.

[github-actions]

Thank you for the PR! The changelog has not been updated, so here is a friendly reminder to check if you need to add an entry.

[snejus]

I like this update!

Just checked and it seems like there's one replacements that's been left out?

[amogus07]

I like this update!

Just checked and it seems like there's one replacements that's been left out?

Which types should be used here?

[amogus07]

uhhhh… can't reproduce this locally?!

[amogus07]

@snejus What should I do now? Can you reproduce it?

[snejus]

dict is only supported from Python 3.9 onwards, so try using typing.Dict instead. Also, I think you may want to use str type for the key instead of Any, Dict[str, Any].

@snejus What should I do now? Can you reproduce it?

You should be able to reproduce it in Python 3.8.

[snejus]

Ideally we want to keep this PR focused on the namedtuple replacement, so I asked to submit the rest of the type changes as a separate PR.

[snejus]

If you're adjusting this, could you clarify what at index 1 of the NamedTuple means? Can this be replaced by the name of the namedtuple attribute?

[amogus07]

I think the person who wrote this would have to explain what it means…

[amogus07]

@JOJ0 can you help out?

[snejus]

Thanks for making the requested adjustments, it all looks good now!