#2896 NORM Untriag: sugar.date API review

[Zarro Boogs per Child]

#2896: sugar.date API review
-------------------------------+--------------------------------------------
  Reporter:  marco             |       Owner:  Eben      
      Type:  defect            |      Status:  new       
  Priority:  normal            |   Milestone:  Untriaged 
 Component:  interface-design  |     Version:            
Resolution:                    |    Keywords:  api-review
  Verified:  0                 |  
-------------------------------+--------------------------------------------
Changes (by marco):

  * owner:  marco => Eben
  * component:  sugar => interface-design

Comment:

 Replying to [comment:2 tomeu]:
 > Why do we need to store the timezone in every entry?

 I was not saying we need... I was just trying to figure out the
 requirements.

 The reason I run into this is that python datetime objects are all
 timezone relative. It's tricky (but possible) to convert from a Date to a
 timestamp.

 > I think we should display all dates relative to the local time zone,
 right?
 >
 > Another alternative would be showing the timezone next to the date, but
 that seems a bad idea to me.

 I don't have a strong feeling. Reassigning to Eben to figure out the user
 interface requirements.

-- 
Ticket URL: <https://dev.laptop.org/ticket/2896#comment:3>
One Laptop Per Child <http://laptop.org/>