<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>
<blockquote>
<p>Let me add this as a discussion item, though really (my personal opinion) the <em>authors</em> should spend time on coming up with solutions. Part of having things<br>
included in the ET means that they must make some effort in keeping things working with the ET. If they want to do whatever they want then having it in a toolkit used by many and with a statement of supported clusters then they should not include it. "it works for me" is not good enough anymore, it has to work for others.</p>
</blockquote>
<p>Only two in the set {kuibit supports Python 3.6, kuibit supports Python 3.11, the dependency tree of kuibit is vetted and verified consistent and compatible}, so I decided to raise the minimum version required because depends heavily on the NumPy ecosystem, which has a tight support schedule and sometimes introduces breaking changes that ripple through all the downstream packages (for example, in 1.20, NumPy deprecated the names <code>np.int</code>, <code>np.float</code> and so on). </p>
<p>I presented the community with the statement that the next version of kuibit will depend on Python>=3.8, and the problem I raised is “what do we want to do in this situation?”</p>
<p>Among the options are:</p>
<ul>
<li>We require Python 3.8 and build it when it is not available</li>
<li>We require Python 3.8 and claim the clusters that don’t have it “not supported”</li>
<li>We maintain both kuibit 1.3.X and 1.4.X </li>
<li>We require as minimum ET dependency Python 3.7 and reject this kuibit update.</li>
</ul>
<p>Note that the latest Fedora (one of the supported machines) defaults to Python 3.11, so kuibit 1.3.6 cannot be installed there. </p>
<p>That’s why I feel this is more of a policy issue than a technological one (that I could solve myself).</p>
<p></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>