Re: [Django] #12139: forms.fields.DateTimeField and TimeField so not accept stringified datetimes

2015-03-21 Thread Django
#12139: forms.fields.DateTimeField and TimeField so not accept stringified
datetimes
-+-
 Reporter:  mattbennett  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  datetime, forms, | Triage Stage:  Accepted
  datetimefield, timefield   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 I don't think this is a problem any longer nowadays.
 See #9459/[dce278673a409a10c1f74f597035b737bbf6a017]
 and #19917 [384c180e414a982a6cc5ccabc675bcfb4fd80988]

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.01d4b6281393586956c8ca9f6d56af44%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #12139: forms.fields.DateTimeField and TimeField so not accept stringified datetimes

2011-04-01 Thread Django
#12139: forms.fields.DateTimeField and TimeField so not accept stringified
datetimes
-+-
   Reporter: |Owner:  nobody
  mattbennett|   Status:  new
   Type:  New|Component:  Forms
  feature| Severity:  Normal
  Milestone: | Keywords:  datetime, forms,
Version:  SVN|  datetimefield, timefield
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  1
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by mattmcc):

 * type:   => New feature
 * severity:   => Normal


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.



Re: [Django] #12139: forms.fields.DateTimeField and TimeField so not accept stringified datetimes

2010-10-07 Thread Django
#12139: forms.fields.DateTimeField and TimeField so not accept stringified
datetimes
--+-
  Reporter:  mattbennett  | Owner:  nobody  
 
Status:  new  | Milestone:  
 
 Component:  Forms|   Version:  SVN 
 
Resolution:   |  Keywords:  datetime, forms, 
datetimefield, timefield
 Stage:  Accepted | Has_patch:  1   
 
Needs_docs:  0|   Needs_tests:  1   
 
Needs_better_patch:  1|  
--+-
Comment (by mk):

 This patch not only needs tests, but also other improvements. It will fall
 on the face with dates f.e. in german format. The stupid check for '.' in
 the string representation will not do the right thing with "03.11.2009
 12:21:10".

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.



Re: [Django] #12139: forms.fields.DateTimeField and TimeField so not accept stringified datetimes

2010-02-05 Thread Django
#12139: forms.fields.DateTimeField and TimeField so not accept stringified
datetimes
--+-
  Reporter:  mattbennett  | Owner:  nobody  
 
Status:  new  | Milestone:  
 
 Component:  Forms|   Version:  SVN 
 
Resolution:   |  Keywords:  datetime, forms, 
datetimefield, timefield
 Stage:  Accepted | Has_patch:  1   
 
Needs_docs:  0|   Needs_tests:  1   
 
Needs_better_patch:  1|  
--+-
Changes (by russellm):

  * needs_better_patch:  => 1
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 1
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.



[Django] #12139: forms.fields.DateTimeField and TimeField so not accept stringified datetimes

2009-11-03 Thread Django
#12139: forms.fields.DateTimeField and TimeField so not accept stringified
datetimes
---+
 Reporter:  mattbennett|   Owner:  nobody   
 
   Status:  new|   Milestone:   
 
Component:  Forms  | Version:  SVN  
 
 Keywords:  datetime, forms, datetimefield, timefield  |   Stage:  
Unreviewed
Has_patch:  1  |  
---+
 When you stringify a datetime.datetime or datetime.time object, it
 includes fractional seconds e.g. '2009-11-03 12:21:10.800641'. The default
 input formats for DateTimeField and TimeField do not expect the fractional
 seconds part.

 This is irritating when using a ModelForm and populating directly without
 preprocessing the datetimes, for example in a REST API where the form data
 is generated automatically.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---