Thanks for the new PR! I edited the PR description, so beth the issue and the old PR will be closed, when merging.
Can you please merge from master? Besides resolving the conflicts that should fix the tests, so we can see better what's going on :)

Okay. I've just rebased the branch to current master and fixed the conflicts.
I see the monthly job tests are fixed already. I've just started to fix them.
The only thing left is to add tests for new "if-else" branches.

About changing the implementation. When we started to take Tuple, some calls to external libs became mypy-invalid because some of them require only List. So i converted tuples to lists where possible.
And do you actually think that a list passed to __init__() should ever be preserved as-is when assigned to instance attr? It's understandable that property setters preserve them. But __init__() makes a brand-new instance with brand-new attrs. Preserving lists may lead to bad side-effects that would be hard to find.

"STL" sounds too "Std Template Lib", so i chose "SLT".
Pyliint doesn't like T, so i had to use RT.

About changing the implementation. When we started to take Tuple, some calls to external libs became mypy-invalid because some of them require only List. So i converted tuples to lists where possible.

Frankly, compatibility with 3rd party libs shouldn't be the first priority when making changes. If they need a list, convert the input yourself, that's not PTBs job ;)

And do you actually think that a list passed to __init__() should ever be preserved as-is when assigned to instance attr? It's understandable that property setters preserve them. But __init__() makes a brand-new instance with brand-new attrs. Preserving lists may lead to bad side-effects that would be hard to find.

You have a point here. However, changing

def __init__(self, some_list: List):
    self.some_list = some_list

to

def __init__(self, some_list: List):
    self.some_list = list(some_list)

everywhere in the code is a largely independent issue. As of now the aim of this PR is just to make type hinting a bit more generous. So please either only change signatures or go the full way and adjust the behaviour of every __init__ in the lib ;)

I'll try to have a closer look at the new changes soon.

MyPy check fails on third-party lib calls inside PTB. If you still can merge such PR, so okay.

or go the full way

You know how to convince people (at least my kind). If you could ignore MyPy or loosen its checks, then say it, and i'll roll the implementation changes back. Even the generator optimization.

MyPy check fails on third-party lib calls inside PTB. If you still can merge such PR, so okay.

Okay, apparently I misunderstood that. I had understood that mypy becomes invalid when using the changes with some 3rd party libs used in one of your projects. But in this case, I'll resort to "Basically the changes in this PR should not cause mypy to be unhappy. "

Are there any change requests left?

The only unnecessary change here was the generator optimization. I've removed it.

About rendering thingies. Could not find a way to render them as hyperlinks and maintain readability of the remainder.

@Poolitzer could you review this PR too?

Hi. I'm glad the PRs are merged. But they still don't count for Hacktoberfest for some reason. Could you please add "hacktoberfest-accepted" label to both PRs?

Thank you @Bibo-Joshi. But it didn't work. Hacktoberfest still doesn't count them. May be this is because i submitted these PRs too late (in the evening of 31th of October). Let's pretend this time i contibuted not for the tee)).