Sander Van Balen

As far as I can tell, the state that gets rejected is the same as the final one. It is child=1 that is considered as a candidate, and it appears...

So, I've been thinking about the possible implications of this some more. The example I gave above does not result in an undesired end state, so it might not be...

> This way, the latest compatible `child` will always be skipped in preference of the second latest. Actually, it's even worse: suppose there exist many newer versions of child between...

I've extended the test case a bit more, adding a check for what I believe to be the undesired behavior. I've also added a POC fix. I can't comment on...

I'm cleaning up my fix to open up a pull request. I'm wondering about the last two comments. If I understand the situation correctly `pip` fails here because in its...

If I understand correctly, there is actually already a workaround for this, though it is not documented yet. I added documentation in #261, which is still in review.

I have encountered this issue when trying to convert a project from `datetime` to `pendulum`. Our code base is full of `datetime.now().astimezone()` in order to work with timezone aware datetimes....

I would love to see this feature, so I thought I'd make an attempt to implement it. From the comments above I understood that it was only the UI that...

Thanks for your response. I feel like your proposal would be a good compromise. I don't mind so much having to select 6 players and getting the warning once, it's...

I'm on Linux but I can try building from source from the `check-player-config-once` branch if you want? It'll probably be for next week though.