[pkg-uWSGI-devel] Bug#1008954: Bug#1008954: uwsgi-plugin-python3: uWSGI uses Python 3.10 which is not yet the default

[Adrien CLERC]

Le 05/04/2022 à 00:03, Jonas Smedegaard a écrit :
>
> Sorry, I am not sure I understand you.
>
> I did a simple rebuild, so if that caused the package to treat Python
> 3.10 as the default then that is because it is the default (at the
> Debian unstable environment where it was built).
>
> If you mean to say that Python 3.10 is not yet the default in testing,
> then that seems like a chicken-and-egg scenario: For Python 3.10 to
> become the default in Debian testing, packages rebuild while Python 3.10
> was the default need to migrate to testing.
>
> If your system is not yet ready for Python 3.10, then I suggest you hold
> back packages as appropriate.

Thanks for your explanation. Indeed, the surprise lies in the socket 
activation of uwsgi. The "apt upgrade" went fine, but since my 
application uses a virtualenv that was created with Python 3.9, uwsgi 
can't find any required dependencies, they were all in the python3.9 
subdirectory, and uwsgi python plugin looked for python3.10. At first 
activation of the application, it failed, and the reason was hard to find.

The main issue for me was that I have to install python3.10 manually to 
upgrade the virtualenv, since it was not installed automatically by any 
package, especially the python3 package. I was expecting somehow that 
the migration was synchronized, but as you mentioned, it might be not 
realistic.

If nothing can be done about this, please close this!

Have a good day,

Adrien
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-uwsgi-devel/attachments/20220405/fa22e913/attachment.htm>