Mark, thanks for your response.
It is perhaps non-fatal, but we do have a different number of templates processed. This is from a successful run with django-allauth==0.57.0. Note the different count of templates from the “failed” processing and this one.
(venv) [mailman@rubytears ~]$ mailman-web compress Compressing... done Compressed 2 block(s) from 124 template(s) for 1 context(s).
Is this compression of web content that will served to clients? Compressed data would be preferred over non-compressed to decrease data volume, but non-compressed will be served if compressed isn’t available?
Michael SandersonOn Nov 7, 2023, at 7:46 PM, Mark Sapiro <mark@msapiro.net> wrote:
[CAUTION: Non-UBC Email]
On 11/7/23 16:26, Michael.Sanderson@ubc.ca wrote:
Despite earlier comments that django-allauth 0.58.1 has been released to fix this issue (and presumably 0.58.2 would have the fix as well), there appears to still be an issue. As Odhiambo indicated with django-allauth==0.57.0, mailman-web compress completes without errors. With django-allauth 0.58.1 and 0.58.2, I still get (venv) $ mailman-web compress Compressing... Error parsing template socialaccount/signup.html: socialaccount/base.html done Compressed 2 block(s) from 78 template(s) for 1 context(s).
I don't think this is fatal, but I have reported it at https://github.com/pennersr/django-allauth/issues/3513
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to michael.sanderson@ubc.ca