Wrong daylight saving time calculation

Bug #314622 reported by Simon Csaba Endre on 2009-01-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Pelle van der Scheer

Bug Description

Daylight saving time was not in use every year. For example I was born in May, 1969 in Romania. In that time there was no DST in effect and the program calculates wrong horoscope. See: http://en.wikipedia.org/wiki/Daylight_saving_time_around_the_world#Romania
Zet8 and StarFisher will take in account this fact but OpenAstro.org not.

These result I get for Bucharest, Romania

20 may 1932 [+2:00] (correct, no daylight saving time yet)
29 may 1932 [+3:00] (correct, start of first daylight saving time)
20 may 1969 [+2:00] (correct, no daylight saving time)
20 may 1996 [+3:00] (correct, with daylight saving time)

Could please tell me the location? It might be a problem with a wrong timezone.
Could you also try the above results and compare?

Changed in openastro.org:
assignee: nobody → pellesimon
Simon Csaba Endre (secsaba) wrote :

With Bucharest I got the same results. The faulty city is Cluj-Napoca (Kolozsvár).

Bucharest, 28 may 1969 [+2:00] (correct, no daylight saving time)
Cluj-Napoca, 28 may 1969 [+3:00] (wrong)

It's nice that the program can understand the Hungarian names for the cities, also. Thanks for this.

Changed in openastro.org:
importance: Undecided → Medium
status: New → Confirmed
milestone: none → 1.1.7
Vladislav Muravyev (rex-lux) wrote :

It has also particularity for post-soviet union territories, or maybe somewhere else: while the current time is daylight-saving (e.g. UTC+4 at June in Moscow), it calculates for all dates, even for thoses that occured in non-daylight-saving period (e.g. UTC+3 at January in Moscow) as though it occured in daylight-saving period (for our example is UTC+4 and it substruct 4 hours, not 3 for UTC time).

Todd Carnes (toddcarnes) wrote :

This is an issue for Ohio in the USA also....

For example, for the date and time 9 Oct 1966 @ 14:52 your program erroneously sets the timezone to Eastern Daylight Time [-04:00]. It should be Eastern Standard Time [-05:00]. I have to adjust my birth time an hour in order to get the correct chart.

Timezones are notoriously difficult to get correct. I would recommend allowing the user to specify if DST is to be used or not. A simple checkbox that allows the user to turn DST on or off would go a long ways toward alleviating the issue.

Todd Carnes (toddcarnes) wrote :

I forgot to mention I am using version 1.1.24.

Todd Carnes (toddcarnes) wrote :

Well... it might be version 1.1.25. The info box off the help menu says 24, but my package manager says I have 25.

Perhaps you forgot to update the version number in the info box when you released version 25?


Could anyone concerned please check his issue using the newest version 1.1.37?

Changed in openastro.org:
status: Confirmed → In Progress
Simon Csaba Endre (secsaba) wrote :

The newest version 1.1.37 for Cluj-Napoca gives the correct result.

Not related to this but the package is not dependent on python-tz and after installation the program does not start until python-tz is not installed also.

I'm marking it as resolved. If anyone still has the problem, please comment.

Changed in openastro.org:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers