#1232: dabo.settings.dateFormat '%m/%d/%y' not accepting full century
---------------------+------------------------------------------------------
Reporter: johnf | Owner: paul
Type: defect | Status: assigned
Priority: major | Milestone: 0.9.2
Component: ui | Version: 0.9.1
Resolution: | Keywords: dateFormat wrong century
---------------------+------------------------------------------------------
Changes (by paul):
* owner: somebody => paul
* status: new => assigned
Old description:
> When using dabo.settings.dateFormat '%m/%d/%y' the dDateTextBox control
> does not respect the user adding the century as in '1970'. It converts
> '1970' to '2070'
New description:
When using dabo.settings.dateFormat '%m/%d/%y' the dDateTextBox control
does not respect the user adding the century as in '1970'. It converts
'1970' to '2070'
Steps to repro:
1) start an app that instantiates a dTextBox with a date value of
datetime.date.today(), or any date.
2) open a command window, and get an object reference to the textbox.
3) type:
{{{
#!python
import datetime
dabo.settings.dateFormat = "%m/%d/%y"
textbox.Value = datetime.date(1972, 5, 11)
print textbox.Value
}}}
The textbox.Value will be
{{{
#!python
datetime.date(2072, 5, 11)
}}}
even though you explicitly gave the century.
Comment:
It isn't just dDateTextBox - it also happens in dTextBox. I changed the
description of the ticket a little to be more specific.
--
Ticket URL: <http://trac.dabodev.com/ticket/1232#comment:1>
Dabo Trac <http://trac.dabodev.com>
Trac Page for Dabo
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message:
http://leafe.com/archives/byMID/[email protected]
