[moin-devel] Debian packages problem: traceback in themes/__init__.py" line 831: AttributeError

[Paul Boddie]

On Wednesday, 10 July 2024 21:06:39 CEST Ulrich B. wrote:
> 
> If you still need support, may I ask you to send me more details on how
> to reconstruct this error?

I haven't really looked into this since April, given that my level of 
motivation dropped below the necessary threshold to keep looking at it.

> What version of Debian are you using and where can I find the moin
> package for testing?

I have been using the unstable version of Debian because this is where 
packaging efforts are directed when software is not yet available in the 
Debian software distribution. I previously made packages available here:

https://salsa.debian.org/moin-team/moin/-/jobs/4925860/artifacts/browse/aptly/

My message from 10th September 2023 with the subject...

[moin-devel] Debian packages (Re: moin2 release with core functionality)

...describes the considerations when using packages published in this way.

Since reading your message, I have looked again at the packaging and have 
finally managed to make setuptools_scm work with the Debian package building 
mechanisms. Despite this being hugely irritating, resolving this only has the 
benefit of avoiding a small amount of work when fixing up the Moin sources.

In any case, trying Moin out in the Debian unstable environment has 
highlighted some places that probably need fixing. First of all, in moin/
utils/send_file.py, in the send_file function, there is usage of 
current_app.use_x_sendfile which may not be compatible with Flask 3.0.

Having eliminated this usage, albeit without fixing the problem, I then 
encounter the previous issue with request.view_args. From what I understand of 
the Request initialisation in flask/wrappers.py, this is initially set to 
None. (I see that enthusiasm for type annotations is slowly turning Python 
into C++.)

It seems that view_args is set in flask/ctx.py, in the match_request method of 
RequestContext by unpacking a result tuple from a URL adapter. The URL adapter 
is apparently created for the context using the create_url_adapter method of 
Flask in flask/app.py.

I imagine that there must be some kind of difference between the 
initialisation of the mod_wsgi application and that of the built-in server, 
but I think that it might be quicker for someone more familiar with the code 
to locate where that difference might be.

Thanks for following up.

Paul