[issue35385] time module: why not using tzname from the glibc?

STINNER Victor added the comment: This issue isn't really a bug. The current code just works. I close the issue. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue35385] time module: why not using tzname from the glibc?

STINNER Victor added the comment: See also bpo-28108. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35385] time module: why not using tzname from the glibc?

Change by Paul Ganssle : -- nosy: +p-ganssle ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35385] time module: why not using tzname from the glibc?

Alexey Izbyshev added the comment: See #28108 and https://sourceware.org/bugzilla/show_bug.cgi?id=23859 (for msg276123). -- nosy: +izbyshev ___ Python tracker ___

[issue35385] time module: why not using tzname from the glibc?

STINNER Victor added the comment: Ah, context of this question: I modified get_gmtoff() in bpo-35373 to fix compiler warnings :-) (see my first commit 503ce5c482cb267b0770bc46c315d5cf822bdca9) -- ___ Python tracker

[issue35385] time module: why not using tzname from the glibc?

Change by STINNER Victor : -- nosy: +belopolsky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35385] time module: why not using tzname from the glibc?

New submission from STINNER Victor : Currently, the time module uses tm_zone and tm_gmtoff of struct tm with localtime_r() to get the timezone (name and offset) on my Fedora 29. But it seems like glibc provides "tzname", "daylight" and "timezone" variables. Why not using them? Python also