You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if that is saying it is Nov 2nd at 1:65 (65?)
OR if it is saying it is more likely saying Nov 2nd at 16:05 (more likely)
I could try adding separators just to see what it was intending to say, but all of those scenarios have flaws regardless
If you get the time, could you make it so that months, days, hours, & minutes have the preceding zero? So that January 7th @ 8:05am would be 2022 01 07 0805
{year}{month}{day}{hour}{minute}
produced:
2021112165
I don't know if that is saying it is Nov 2nd at 1:65 (65?)
OR if it is saying it is more likely saying Nov 2nd at 16:05 (more likely)
I could try adding separators just to see what it was intending to say, but all of those scenarios have flaws regardless
If you get the time, could you make it so that months, days, hours, & minutes have the preceding zero? So that January 7th @ 8:05am would be 2022 01 07 0805
datetime.today().strftime('%Y-%m-%d-%H:%M:%S')
'2022-01-07-08:05:59'
Could even add those seconds in if you wanted, if it's not too much trouble =]
EDIT:
I looked at the source, & I think that would fix it... also added the julian date, abbreviated months & days, and short year
EDIT2: fixed my errors
I edited my local file and tested... works great!!
EDIT3:
I fumbled my way through my first pull request on Github. I think I tripled the number of steps it should have taken ¯_(ツ)_/¯
The text was updated successfully, but these errors were encountered: