Code

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#12059 closed (fixed)

datetime to time conversion incorrect

Reported by: wkornewald Owned by: jezdez
Component: Database layer (models, ORM) Version: master
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

In TimeField.to_python
(db.models.fields: init.py line 838) a datetime is converted to
time via value.time, but it should be value.time() (parenthesis were
missing). Could you please fix that? Thanks!

Attachments (1)

12059.diff​ (1.4 KB) - added by simonz05 4 years ago.

Download all attachments as: .zip

Change History (6)

Changed 4 years ago by simonz05

comment:1 Changed 4 years ago by simonz05

  • Has patch set
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Version changed from 1.1 to SVN

comment:2 Changed 4 years ago by jacob

  • Owner jacob deleted

comment:3 Changed 4 years ago by jezdez

  • Owner set to jezdez
  • Status changed from new to assigned
  • Triage Stage changed from Unreviewed to Accepted

comment:4 Changed 4 years ago by jezdez

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [12137]) Fixed #12059 - Let TimeField.to_python correctly return a datetime.time object when having a datetime object.

comment:5 Changed 4 years ago by jezdez

(In [12237]) [1.1.X] Fixed #12059 - Let TimeField.to_python correctly return a datetime.time object when having a datetime object.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

Attachments ↑
 
Note: See TracTickets for help on using tickets.