<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>open</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 Roland Haas):</p>
<p>Sure. Note that the <code>numpy</code> ↔︎ Python compatibility issue does not directly arise with those clusters I would claim. The old clusters only providing old Python will provide an equally old (and compatible to Python) <code>numpy</code>. So the issue would be more whether <code>kuibit</code> can support both old and new <code>numpy</code> versions. From previous discussion about this my understanding is that supporting both numpy versions is (basically) impossible in kuibit. So faced with the choice of having to drop support for some version of <code>numpy</code> dropping support for the older one rather than dropping support for all newer versions makes sense. </p>
<p>This has been an issue with old HPC clusters all the time, they just offer quite old software stacks.</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>