#23884: Consider moving FlatPageSitemap to contrib.flatpages
--------------------------------------+--------------------
Reporter: kezabelle | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.sitemaps | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
The FlatPageSitemap currently exists within the 'core'
`django.contrib.sitemaps` namespace, though it's specific to
`django.contrib.flatpages`. Given a number of modules and moves have
happened recently, I'm floating the idea of:
* Moving `FlatPageSitemap` to `django.contrib.flatpages.sitemaps`, which
would better reflect it's dependencies (though it still has one to
`django.contrib.sites`), and is more inline with how sitemaps would be
packaged in third-party apps (and would allow spinning out flatpages to an
external app with less work, if ever desired)
* Raising a deprecation warning for a release, if importing from the old
namespace (like the ContentTypes move and form.util moves)
The documentation currently says ''The sitemap framework provides a couple
convenience classes for common cases'', and I'd argue that flatpages isn't
all *that* common, these days, though it may have been in the past (before
richer packages either built on it or supplanted it, because the ecosystem
was smaller)
--
Ticket URL: <https://code.djangoproject.com/ticket/23884>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.d434f251d3af7fdb2bde3962b8d05f0a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
