#22639: Fix inconsistency with imports in documentation
-------------------------------------+-------------------------------------
Reporter: niclas.ahden | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Documentation | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timo):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I don't mind the current state of things. There was a couple of patches a
while back that added a lot of imports, e.g.
1fe587d80bfcf062a94252fb532c8ac035c833b9
08b501e7d314e9c45dd51d3ba27b2ecb0287df3b
1d543949d7acc93a172e8a2c9272d8b983a421ef.
The first time a concept is introduced in a section, it probably makes
sense to include all imports, but if the example is tweaked later, I don't
think the imports need to be repeated.
If there are spots that bother you right now, feel free to send a PR.
Otherwise, I don't think we need to keep a ticket open for this.
We'll never be able to make all code snippets safe to copy and paste
because examples have example dependencies like `from myapp.models import
Article`.
--
Ticket URL: <https://code.djangoproject.com/ticket/22639#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 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/070.0fb9ac34060f575362c366da53f5f085%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
