<html>#2696: Update kuibit to 1.4.0
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Gabriele Bozzola</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td>ET_2023_05</td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td></td></tr>
</table>
<p>Comment (by Gabriele Bozzola):</p>
<p>In that case, kuibit 1.3.6 will still work.</p>
<p>Unfortunately, it is pretty much impossible to support at the same time Python 3.7 and Python 3.11 if I want to ensure that all the dependencies are satisfied and known to be compatible. </p>
<p>I am acutely aware of how clusters are stuck back in time, and I tried hard to see if I could squeeze in at least Python 3.7. Given <a data-is-external-link="true" href="https://numpy.org/neps/nep-0029-deprecation_policy.html" rel="nofollow">NEP29</a>, that meant hard-coding a several versions of packages specifically for Python 3.7, and the result was that the dependency solver wouldn’t even convergence. (At the moment, the usage of features available only in Python>3.7 is either 0 or very minimal, so the main problem is with the dependencies.)</p>
<p>We can discuss how to handle this, but form a technical point of view the only solution is to forgo any check on the dependency tree and cross fingers that things will install and work (as 80% of the Python world routinely does anyway).</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2696/update-kuibit-to-140'>https://bitbucket.org/einsteintoolkit/tickets/issues/2696/update-kuibit-to-140</a></p>
</html>