#36820: Date Parsing Modernization
-------------------------------------+-------------------------------------
     Reporter:  Varun Kasyap         |                    Owner:  Varun
  Pentamaraju                        |  Kasyap Pentamaraju
         Type:  New feature          |                   Status:  assigned
    Component:  Utilities            |                  Version:  dev
     Severity:  Normal               |               Resolution:
     Keywords:  dateparse,           |             Triage Stage:
  timesince                          |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Description changed by Varun Kasyap Pentamaraju:

Old description:

> I have been analyzing django.utils.dateparse and django.utils.timesince.
> Currently, developers have to write custom logic for many very common use
> cases.
>
> Maybe we should add built-in support for these common cases:
> Please correct me if i am wrong
>
> 1) parse_datetime relies on regex and does not support partial dates (for
> example, providing "2024" returns None instead of a datetime like
> 2024-01-01 12:00).
> 2) timesince forces long-form output such as "1 year, 2 months" using
> hard-coded joins, while modern UIs prefer compact formats like "1y 2mo"
> or "2w".
> 3) Support a customizable “Just now” threshold instead of returning "0
> minutes" for very small time differences.

New description:

 I have been analyzing django.utils.dateparse and django.utils.timesince.
 Currently, developers have to write custom logic for many very common use
 cases.

 Maybe we should add built-in support for these common cases:
 Please correct me if i am wrong

 1) parse_datetime relies on regex and does not support partial dates (for
 example, providing "2024" returns None instead of a datetime like
 2024-01-01 12:00).
 2) timesince forces long-form output such as "1 year, 2 months" using
 hard-coded joins, while modern UIs prefer compact formats like "1y 2mo" or
 "2w".
 3) Support a customizable “Just now” threshold instead of returning "0
 minutes" for small time differences.

--
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36820#comment:1>
Django <https://code.djangoproject.com/>
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 [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/0107019b47228311-a1158a0f-3c02-4339-9b57-e87ac4831f96-000000%40eu-central-1.amazonses.com.

Reply via email to