[masklinn]

> Ok, I don't understand though why the bug hasn't been fixed and is there any other widely used time localization library that makes the same mistake

Because the issue is in the way datetime interacts with timezone objects (it assumes timezone objects are dumb and there's no co-dependency, which is incorrect), and fixing that would require changing the protocol, which would break existing libraries.