Alyssa Ross
6e732d98d8
As far as I can tell, the released version of django-mailman3 is not affected by any of the issues that have required further fixes for newer allauth, since they're all for the Fedora provider, which in this version doesn't use allauth at all.
35 lines
1.0 KiB
Nix
35 lines
1.0 KiB
Nix
{
|
|
python3,
|
|
lib,
|
|
overlay ? (_: _: { }),
|
|
}:
|
|
|
|
lib.fix (
|
|
self:
|
|
python3.override {
|
|
inherit self;
|
|
packageOverrides =
|
|
lib.composeExtensions
|
|
(self: super: {
|
|
/*
|
|
This overlay can be used whenever we need to override
|
|
dependencies specific to the mailman ecosystem: in the past
|
|
this was necessary for e.g. psycopg2[1] or sqlalchemy[2].
|
|
|
|
In such a large ecosystem this sort of issue is expected
|
|
to arise again. Since we don't want to clutter the python package-set
|
|
itself with version overrides and don't want to change the APIs
|
|
in here back and forth every time this comes up (and as a result
|
|
force users to change their code accordingly), this overlay
|
|
is kept on purpose, even when empty.
|
|
|
|
[1] 72a14ea563a3f5bf85db659349a533fe75a8b0ce
|
|
[2] f931bc81d63f5cfda55ac73d754c87b3fd63b291
|
|
*/
|
|
django = super.django_5;
|
|
})
|
|
|
|
overlay;
|
|
}
|
|
)
|