Opened 16 years ago

Closed 16 years ago

#8953 closed (duplicate)

Timezone support at the model level

Reported by: simon Owned by: nobody
Component: Uncategorized Version: 1.0
Severity: Keywords: djangocon
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by simon)

This should probably rely on dateutil and/or pytz - so you wouldn't be able to use DateTimeTzField without having those installed.

Change History (5)

comment:1 by simon, 16 years ago

Description: modified (diff)

comment:2 by Brian Rosner, 16 years ago

I would like to point out http://code.google.com/p/django-timezones/ as something that was created for Pinax. It tries to be as unintrusive as possible. There are some less than ideal ways of accomplishing things, but it certainly is a start and hopefully heading down the right direction with cleanups for Django proper.

comment:3 by jhenry, 16 years ago

There is another implementation of this in use on http://chicago.decider.com/ on launchpad.

https://code.launchpad.net/~theonion/bulbs/trunk

comment:4 by korpios, 16 years ago

What jhenry said; also see my comment:

http://code.djangoproject.com/ticket/2626#comment:13

In a nutshell, we have it working without needing to hack up Django core.

comment:5 by Jacob, 16 years ago

Resolution: duplicate
Status: newclosed

This is a duplicate of #2626.

Note: See TracTickets for help on using tickets.
Back to Top