<html>#2736: consider using git+https together with a branch name or kuibit install
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></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>trivial</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Other</td></tr>
</table>
<p>Comment (by Gabriele Bozzola):</p>
<p>I can see another drawback to this. When you install kuibit with <code>pip install kuibit</code>, you are served the wheels from PyPI. These are very small files (460 kB) and are supposed to work immediately on all the supported architectures/versions.</p>
<p>When you install kuibit from git, you have to download the entire repo (along with the tests, some data files, and so on, and the entire git history), which can be 100s of MBs - 1 GB. Moreover, you have to recompile the package locally. This should not be a problem for 99 % of the cases, but I would not be surprised if there were incompatibilities in some cases.</p>
<p>So, as developer, I would prefer sticking with PyPI for the slightly better user experience, but I do not feel strongly about this.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2736/consider-using-git-https-together-with-a'>https://bitbucket.org/einsteintoolkit/tickets/issues/2736/consider-using-git-https-together-with-a</a></p>
</html>