#34501: Revert CICharField deprecation
----------------------------------+--------------------------------------
Reporter: Johannes Maron | Owner: (none)
Type: Bug | Status: closed
Component: contrib.postgres | Version: 4.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* type: Uncategorized => Bug
* resolution: => wontfix
Comment:
Thanks Joe, unfortunately, I'm forced to close it as "wontfix" based on
current replies on the [https://groups.google.com/g/django-
developers/c/nDMnO98nexY mailing list]. We can reconsider this decision
when there are more replies in favor of revert or we reach a consensus.
I hope that makes sense.
--
Ticket URL: <https://code.djangoproject.com/ticket/34501#comment:2>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/0107018793718a11-6cd87441-a766-4def-9d68-0d2cd3963824-000000%40eu-central-1.amazonses.com.
