Comment 3 for bug 786022

Thanks, Suart.

While I agree there are better ways to represent real timezones, etc timezones are useful for testing (which is how I found the problem) and despite the errors in the Olson database, pytz should provide a correct offset unless the incorrect behavior is relied upon by legacy code, something I believe not be the case. I understand the wish not to insert code to compensate for an incorrect tz table, but, since it's very unlikely to be corrected there, the fix on pytz's side would end up solving the problem forever.

We could, at least, add a deprecation warning telling people that "Etc timezones are deprecated and the Olson tz database presents them incorrectly"