<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:ming.v.hua@qq.com" title="Ming Hua <ming.v.hua@qq.com>"> <span class="fn">Ming Hua</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Add numpy to LibreOffice\program\python"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=143980">bug 143980</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>ming.v.hua@qq.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Add numpy to LibreOffice\program\python"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=143980#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Add numpy to LibreOffice\program\python"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=143980">bug 143980</a>
from <span class="vcard"><a class="email" href="mailto:ming.v.hua@qq.com" title="Ming Hua <ming.v.hua@qq.com>"> <span class="fn">Ming Hua</span></a>
</span></b>
<pre>While I would welcome addition of Numpy to LibreOffice's bundled Python, I
don't see it happening without a dramatic change of the current practice of
python module packaging.
We don't even ship the full core library of Python. To use the Windows
installer as an example (I assume TDF's RPM and DEB packages are similar), I
think we build python without Tcl/Tk and the accompanying tkinter graphic UI
module, and we strip a lot of modules LO doesn't use when bundling python into
the installer.
As a result, the whole program\python-core-3.8.10\lib directory (with .pyc
cache files generated) for installed 7.2.0 on my system is 28 MB with 1,225
files. As a comparison, the official python.org installation's python38\Lib
directory here (excluding subdirectory site-packages\) is 115 MB with 7,183
files, also with .pyc files generated.
And Numpy alone on my system is 56 MB. It also links to BLAS/LAPACK and maybe
many other C/C++ libraries, so building it correctly is going to be tricky,
too. And by adding it we are more and more like shipping a custom python
distribution, instead of an office suite bundling python.
Without discouraging anyone who want to work on this, I personally feel the
developers' efforts would be better put into making installing external modules
from PyPI and building virtual environments easier with LO's bundled python.
Then we can avoid frustrated users like in <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Python Implementation Poorly Conceived with No Package Installation Process"
href="show_bug.cgi?id=143867">bug 143867</a>. Maybe starting with
adding "ensurepip" module into our bundle, and writing a good tutorial about
setting up PIP and installing packages from PyPI with LO-bundled python?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>