<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">Le 05/04/2022 à 00:03, Jonas Smedegaard
a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:164910978802.1943.12598328062636209565@auryn.jones.dk"><br>
<pre class="moz-quote-pre" wrap="">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.</pre>
</blockquote>
<p>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.</p>
<p>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.<br>
</p>
<p>If nothing can be done about this, please close this!</p>
<p>Have a good day,</p>
<p>Adrien<br>
</p>
<div id="grammalecte_menu_main_button_shadow_host" style="width:
0px; height: 0px;"></div>
</body>
</html>