#35866: Django documentaion style guide on models is unclear what to do with any
other Python dunder methods that the model class might have
--------------------------------------+------------------------------------
Reporter: Hristo Trendafilov | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Natalia Bidart):
* stage: Unreviewed => Accepted
* type: Uncategorized => Cleanup/optimization
* version: => dev
Comment:
Hello Hristo Trendafilov, thank you for taking the time to create this
report. To me, "any custom method" is a method that you "invent" for your
Model, not methods that are already "defined" by Python's base object
class.
So my reading of that is that whatever extra business logic and helpers
that you need are after `get_absolute_url`. I agree we could make this
explicit in the docs though, accepting with that goal.
Would you like to prepare a patch?
--
Ticket URL: <https://code.djangoproject.com/ticket/35866#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 visit
https://groups.google.com/d/msgid/django-updates/01070192c3f29762-ebd0aff8-aa86-435d-b92d-3b1fc24dbb86-000000%40eu-central-1.amazonses.com.
