Timestamp inconsistency between the services about berserk HOT 6 CLOSED

Ultimately this is a consistency issue with the API. I'll see if there's any hope of fixing the API itself by asking the devs in the discord chat. If not then instead perhaps I can perform some sort of detection and convert them all into proper datetime objects.

from berserk.

Unfortunately it seems this is either somewhat by design or changing it would be troublesome without sacrificing backwards compatibility. I've got a somewhat elegant solution on the develop branch that I'll be releasing soon.

from berserk.

@sentrworks feel free to give it a whirl if you can and let me know if you find any issues before I release it :)

from berserk.

@rhgrant10 unfortunately it doesn't work. Despite I upgraded to berserk 0.1.2 to 0.2.1, in both versions the api "lichess.games.export_by_player(username=username,as_pgn=False,max=how_many_games,rated='true',moves='false')" returns 'createdAt' field in a timestamp format which needs to divide by 1000.

from berserk.

Yeah it's still on the develop branch. I haven't released it yet. I should be able to get to it this weekend though.

from berserk.

It's available now on the PyPI at v0.3.0 @sentrworks.

from berserk.