Closed to175 closed 1 month ago
Hi, the error is correct, that time technically doesn't exist. Since the winter time started at 2 o clock and 2 o clock bacame 3 o clock there never was 2.30 in 1983 in France. Here a reference:
https://www.timeanddate.com/time/change/france/paris-department?year=1983
Hope I was enough clear!
Oh I understand now, thanks! However my date is 25 Sept and I can see on the link you shared that we are in the second case "Back 1 hour" so we are supposed to be twice on 2:55
So the time can be ambiguous because we don't know if we are in the first or the second 2:55 but this time has existed! So what to do in this case please? @g-battaglia We should have some automatic thing to pick either first or second but not run into this error
@g-battaglia this seems easily solvable since line 254 of astrological_subject.py
is already explicitly setting is_dst
to None
:
local_datetime = local_time.localize(naive_datetime, is_dst=None)
If you simply add is_dst
as a named argument to the constructor and pass this through to the above call to localize
instead of None
then the user can decide which side of Daylight Savings their time belongs to & the problem should be solved.
Hey @theriftlab @to175, can you check if now this issue is fixed it and write here if now it's ok? Thanks
Fixed in v4.13.0
Hello,
I have this issue both with version 4.2.4 and 3.4.1
It works with 1:30 but not with 2:30 for example because of wierd error...
Code
Output
Same issue with 3.4.1