Quantcast

datetime in gmt zone = timezoneNaive?

classic Classic list List threaded Threaded
5 messages Options
johannes raggam johannes raggam
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

datetime in gmt zone = timezoneNaive?

hi all,

i'm not sure if it's an issue or not, but i guess it is:

in a plone 4.1 / datetime 2.12.6 based installation, an event's start
date gives
   obj.timezoneNaive()==True
even when
   obj.timezone()=='GMT+2'
and
   obj.timezoneOffset()=='7200'

is that intentional? normally i would expect that
obj.timezoneNaive()==False in that case - even if GMT+2 isn't a good
zone, because no daylight-saving-changes can be calculated from that
information.

cheers,
hannes

--
johannes raggam / thet,thetet
python plone zope development
mailto: [hidden email]
web:  http://bluedynamics.com


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
johannes raggam johannes raggam
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: datetime in gmt zone = timezoneNaive?

i guess, this behavior has something to do, how the datetime instance is
constructed by archetypes.

another thing: DateTime(obj.startDate) returns a copy, but
DateTime(obj.startDate).timezoneNaive() is None, which shouldn't IMO....

while this statement asserts to True
DateTime(obj.startDate) == obj.startDate
what's totally ok IMO, since microseconds since epoch are compared and
those have the timezone offset included.

cheers,hannes

On 10/10/2011 12:08 PM, Johannes Raggam wrote:

> hi all,
>
> i'm not sure if it's an issue or not, but i guess it is:
>
> in a plone 4.1 / datetime 2.12.6 based installation, an event's start
> date gives
>     obj.timezoneNaive()==True
> even when
>     obj.timezone()=='GMT+2'
> and
>     obj.timezoneOffset()=='7200'
>
> is that intentional? normally i would expect that
> obj.timezoneNaive()==False in that case - even if GMT+2 isn't a good
> zone, because no daylight-saving-changes can be calculated from that
> information.
>
> cheers,
> hannes
>


--
johannes raggam / thet,thetet
python plone zope development
mailto: [hidden email]
web:  http://bluedynamics.com


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Hanno Schlichting-4 Hanno Schlichting-4
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: datetime in gmt zone = timezoneNaive?

On Mon, Oct 10, 2011 at 12:22 PM, Johannes Raggam <[hidden email]> wrote:
> i guess, this behavior has something to do, how the datetime instance is
> constructed by archetypes.

DateTime has two distinct concepts: being timezone naive and having a
timezone set.

This allows you to have DateTime object which is both timezone naive
and has a timezone at the same time. This doesn't make any sense, but
it's the way the API's evolved over time.

Yvo Schubbe (yuppie) showed interest in fixing this for DateTime 3 -
if you want to help him, please do ;)

Hanno

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Radim Novotny-2 Radim Novotny-2
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: datetime in gmt zone = timezoneNaive?

In reply to this post by johannes raggam
Hi,

check this bug http://dev.plone.org/plone/ticket/10141 and
Products.Archetypes 1.7.7 release. Plone 4.1 contains Archetypes 1.7.6

http://pypi.python.org/pypi/Products.Archetypes/1.7.7


--
Radim

Dne 10.10.11 12:08, Johannes Raggam napsal(a):

> hi all,
>
> i'm not sure if it's an issue or not, but i guess it is:
>
> in a plone 4.1 / datetime 2.12.6 based installation, an event's start
> date gives
>     obj.timezoneNaive()==True
> even when
>     obj.timezone()=='GMT+2'
> and
>     obj.timezoneOffset()=='7200'
>
> is that intentional? normally i would expect that
> obj.timezoneNaive()==False in that case - even if GMT+2 isn't a good
> zone, because no daylight-saving-changes can be calculated from that
> information.
>
> cheers,
> hannes
>



------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Eric Steele (esteele) Eric Steele (esteele)
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: datetime in gmt zone = timezoneNaive?

The latest 4.1.x release, 4.1.2, includes this fix.
Eric

On Oct 12, 2011, at 2:45 AM, Radim Novotny wrote:

> Hi,
>
> check this bug http://dev.plone.org/plone/ticket/10141 and
> Products.Archetypes 1.7.7 release. Plone 4.1 contains Archetypes 1.7.6
>
> http://pypi.python.org/pypi/Products.Archetypes/1.7.7
>
>
> --
> Radim
>
> Dne 10.10.11 12:08, Johannes Raggam napsal(a):
>> hi all,
>>
>> i'm not sure if it's an issue or not, but i guess it is:
>>
>> in a plone 4.1 / datetime 2.12.6 based installation, an event's start
>> date gives
>>    obj.timezoneNaive()==True
>> even when
>>    obj.timezone()=='GMT+2'
>> and
>>    obj.timezoneOffset()=='7200'
>>
>> is that intentional? normally i would expect that
>> obj.timezoneNaive()==False in that case - even if GMT+2 isn't a good
>> zone, because no daylight-saving-changes can be calculated from that
>> information.
>>
>> cheers,
>> hannes
>>
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> Plone-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-developers


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Loading...