#20737: Request to ship feedgenerator as package separately of Django's core
------------------------------+--------------------------------------
Reporter: echevemaster | Owner: nobody
Type: New feature | Status: closed
Component: Packaging | Version: 1.5
Severity: Normal | Resolution: needsinfo
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 aaugustin):
* status: new => closed
* needs_better_patch: => 0
* resolution: => needsinfo
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm sorry, but I'm confused by this bug report; I can't figure out what
you're asking for.
I read the wiki page you linked to. But I don't know what you're calling a
"bundled library". While the page goes to great lengths to explain how bad
"bundled libraries" are, it doesn't define what they are, so it doesn't
help me understand the problem you're reporting.
If you're asking to remove the feedgenerator functionality from Django,
the answer is no, for backwards compatibility reasons.
If you're asking to ship the feedgenerator functionality separately from
Django, that already exists, it's the package you mentioned:
https://pypi.python.org/pypi/feedgenerator
--
Ticket URL: <https://code.djangoproject.com/ticket/20737#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.843133e9b2cbd5bd684574f251e8e315%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
