unified time handling might be a good idea about yt-dlp-rajiko HOT 5 CLOSED

need:

• url format: 20230607062200 - YYYYMMMDDhhmmss - 29-hour time is valid - handled in ShareIE
• iso format: for noa (tracklist), already handled by datetime.isoformat() - handled in _extract_chapters()
• timetable api: YYYYMMDD, 0 midnight - 5 am is included in previous day - handled in _unfuck_day()
• unix timestamp

timezone handled in:

• _timestring_to_datetime with datetime.timezone
• _get_programme_meta with +0900 in unified_timestamp

from yt-dlp-rajiko.

• url format: 20230607062200 - YYYYMMMDDhhmmss - 29-hour time is valid - handled in ShareIE

bit more complicated than that

on the site, seconds and minutes get clamped to 59, hours get clamped to 24
but share urls do indeed just go on forever

from yt-dlp-rajiko.

just to comment a bit on the current solution:

it's definitely not perfect, there's still some jank etc etc
but its a hell of a lot better than what i had before lol

i think ideally i'd've liked to extend upon datetime.datetime, so id still get all the nice functions it has that i have to do some jank to get to
but i couldn't figure out how and i just wanted to get on with it, so i have the current solution of doing passthrough for the couple of things i need that are in datetime.datetime
again, not perfect, but much better than what came before

from yt-dlp-rajiko.

hm, here's a hack for handling the days in the share time
take away any days above 28 (lowest month end), then add them back in the datetime

not sure if it'll work yet, just noting down so i don't forget

from yt-dlp-rajiko.

days above the end of the month dont work on the site
wasnt able to check before because it wasnt quite the end of the month yet

from yt-dlp-rajiko.