time.localtime still uses original timezone information about freezegun HOT 5 OPEN

#348
#204
#89

All seem like basically the same thing?

#89 specifically has a long discussion where we try to figure out what it SHOULD be doing. I would welcome someone tackling this and I will argue to spulec that any such person be given commit/merge access.

I personally don't use freezegun anymore and have switched totally to time-machine, so I won't be spending more time with this.

from freezegun.

If you're not using pypy, I strongly recommend you switch to time-machine. It's quite easy to switch in my experience.

from freezegun.

Yes #204 is indeed the exact same issue.

Well, for my usecase i don't really care whether the passed time is utc or something else.
The problem is, that datetime.datetime.now() returns the utc time once frozen and time.localtime() doesn't. That is really inconsistent.
For my usecase, I need datetime.datetime.now() and time.localtime()to return the same time.

from freezegun.

Yes, thats what i have done now.
Thanks for the suggestion!

from freezegun.

For folks migrating to time-machine because of this, you might wanna be aware of adamchainz/time-machine#325 (comment)

from freezegun.