Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Timezone support #2391

Closed
wants to merge 6 commits into from
Closed

[WIP] Timezone support #2391

wants to merge 6 commits into from

Conversation

mkurek
Copy link
Contributor

@mkurek mkurek commented Apr 20, 2016

Successor of #2263 (i needed to add one more commit/fix)

We are using the following settings regarding timezone:

TIME_ZONE = 'Europe/Warsaw'
USE_TZ = False
When USE_TZ is False, Django would store timestamps in the timezone of TIME_ZONE, and this is how ralph is storing time. After I realised I should change TIME_ZONE, even if I changed TIME_ZONE to 'Asia/Beijing', the stored time are still in the old timezone (GMT+1). How about it that we change USE_TZ to True, to make sue time is always saved as UTC? This is also recommended by Django.

@mkurek mkurek mentioned this pull request Apr 20, 2016
@mkurek mkurek changed the title Timezone support [WIP]Timezone support Jun 13, 2016
@mkurek mkurek changed the title [WIP]Timezone support [WIP] Timezone support Jun 13, 2016
@mkurek mkurek closed this Oct 24, 2016
@romcheg
Copy link
Contributor

romcheg commented Jul 5, 2018

I think we should actually revive this.

@romcheg romcheg reopened this Jul 5, 2018
@romcheg
Copy link
Contributor

romcheg commented Jul 5, 2018

I have realized it's not possible for me to push commits to the same pull request. I will create a new one

@romcheg romcheg closed this Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants