Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#20737 closed New feature (needsinfo)

Request to ship feedgenerator as package separately of Django's core

Reported by: echevemaster Owned by: nobody
Component: Packaging Version: 1.5
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Hi, I'm Fedora packager, a colleague and me we want to package pelican, this package depends of a standalone version of feedgenerator,

due to our packaging policies we can not do that. the reason is this

because that, i want to ask you if you can ship feedgenerator as separately package of Django's core

Thanks for advance

Change History (4)

comment:1 Changed 5 years ago by Aymeric Augustin

Resolution: needsinfo
Status: newclosed

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:

comment:2 Changed 5 years ago by echevemaster

Actually, isn't a problem of Django or a bug from you, "bundled library" in fedora refer it at if a package or lib exist in the system-wide, not should exist in a new package, given that, feedgenerator is part of the Django's core, my question refer to ship feedgenerator as a functionality separately from Django, question that has been answered; and it gives me to understand would not be possible. Anyway thanks a lot

comment:3 Changed 4 years ago by Aurélien Bompard

OK, let me try to clarify the bug report again. The proposed solution would be to replace the django.utils.feedgenerator module with an import from the external feedgenerator package (and an additional dependency of course). Unless I'm missing something, that would remove the system-wide duplicate functionality while keeping backwards compatibility.
Am I clear? Is it something that the Django project would consider doing?

comment:4 Changed 4 years ago by Tim Graham

It seems that would make changes where we need to modify it like a269ea4fe0a9a7195f1bd8bf5d462f48c226d525 much more difficult as we'd need to submit changes to an external project, require them to do a new release, and update Django's dependency.

Note: See TracTickets for help on using tickets.
Back to Top