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.

Sign up for GitHub

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

Jump to bottom

EncryptedDateTimeField Causes "can't compare offset-naive and offset-aware datetimes" Error #43

Open
bltravis opened this issue Jul 6, 2014 · 0 comments
Open

EncryptedDateTimeField Causes "can't compare offset-naive and offset-aware datetimes" Error #43

bltravis opened this issue Jul 6, 2014 · 0 comments
Labels
patch-needed
Milestone
v0.3.0

Comments

@bltravis
Copy link
Collaborator

bltravis commented Jul 6, 2014

Using the EncryptedDateTimeField class with Django version >= 1.4 causes a TypeError whenever you try to update the value of the field in the the Django Admin. Django Admin expects timezone-aware datetime objects. Until this is fixed, this field isn't usable in anything newer than 1.3.
@bltravis bltravis added this to the v0.3.0 milestone Jul 6, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
patch-needed
Projects
None yet
Milestone
v0.3.0
Development

No branches or pull requests
1 participant
@bltravis