#36555: Allow null for LogEntry.user
-------------------------------+--------------------------------------
Reporter: Siburg | Owner: (none)
Type: New feature | Status: closed
Component: contrib.admin | Version: dev
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 Sarah Boyce):
* resolution: => wontfix
* status: new => closed
Comment:
Hi Siburg, thank you for the suggestion!
When suggesting a new feature for Django, the feature idea should first be
proposed and discussed with the community. To do that, please raise this
on the [https://github.com/django/new-features/issues new feature
tracker].
I'll close the ticket for now, but if the community agrees with the
proposal, please return to this ticket and reference the forum discussion
so we can re-open it. For more information, please refer to
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features the documented guidelines for requesting
features].
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/36555#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/01070198acfa098e-aaa6b5e7-63e2-41f5-9b0d-f8fe9445edfb-000000%40eu-central-1.amazonses.com.
