<div dir="ltr">OT, but....<br><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Assuming your dependencies have version agnostic wheels (either manylinux or pure python), what would be the advantage to you of putting everything together in a single file?<br><br></div><div>That being said, I suppose it would be possible to create your own manylinux wheels that include all the necessary dependencies, but that would make building more difficult and opens up the possibility that the installed modules will conflict with users' existing installed packages.<br></div></div></div></div></blockquote><div><br></div><div>which is why conda exists -- conda can package up many things besides python packages, and you WILL need things besides python pacakges.<br><br></div><div>building conda packages for everything you need, and then creating an environment.yaml file, and you can create a consistent environment very easy across systems (even across OSs) There is even a project (I forgot what its called -- "collections" maybe?) that bundles up a bunch of conda packages for you.<br><br></div><div>and with conda-forge, there are an awful lot of packages already to go.<br><br></div><div>If you need even more control over your environment, then Docker is the way to go -- you can even use conda inside docker...<br><br></div><div>-CHB<br><br></div><div><br><br><br><br><br></div><div><br><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>Another possibility would be to use docker to create a container [2] that includes everything you need to run the code in an isolated environment that won't conflict<br></div><div><br>[1] <a href="https://github.com/pypa/manylinux" target="_blank">https://github.com/pypa/<wbr>manylinux</a><br>[2] <a href="https://www.digitalocean.com/community/tutorials/docker-explained-how-to-containerize-python-web-applications" target="_blank">https://www.digitalocean.com/<wbr>community/tutorials/docker-<wbr>explained-how-to-containerize-<wbr>python-web-applications</a><br><br></div></div></div></div>
<br>______________________________<wbr>_________________<br>
Python-ideas mailing list<br>
<a href="mailto:Python-ideas@python.org">Python-ideas@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/python-ideas" rel="noreferrer" target="_blank">https://mail.python.org/<wbr>mailman/listinfo/python-ideas</a><br>
Code of Conduct: <a href="http://python.org/psf/codeofconduct/" rel="noreferrer" target="_blank">http://python.org/psf/<wbr>codeofconduct/</a><br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><br>Christopher Barker, Ph.D.<br>Oceanographer<br><br>Emergency Response Division<br>NOAA/NOS/OR&R (206) 526-6959 voice<br>7600 Sand Point Way NE (206) 526-6329 fax<br>Seattle, WA 98115 (206) 526-6317 main reception<br><br><a href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a></div>
</div></div>