Python Packages and Slackware Packages
Posted: 26. Apr 2013, 09:58
Python's official package installer, pip, handles dependencies and supports upgrades and uninstalls. The root user can use pip to install packages under /usr/lib/python2.x/, and pip allows a normal user to install under their home directory.
Many "pure" Python packages are available, including libraries and apps, from a centralized, official repo. This Python Package Index (PyPI) has a complete searchable index at https://pypi.python.org/pypi/.
PyPI is kept up-to-date so, in many cases, newer versions are available there than via slapt-get / GSlapt, or even via slapt-src / Sourcery.
The only disadvantage I can think of would be during a Slackware / Salix upgrade. Packages installed by pip might get lost or damaged in the shuffle. Since pip can easily provide a list of all packages that it has installed, its seems simple enough to reconstruct the Python "site packages."
So for pure Python packages, are there any other reasons to install a Salix/Slackware package, rather than one from PyPI?
Many "pure" Python packages are available, including libraries and apps, from a centralized, official repo. This Python Package Index (PyPI) has a complete searchable index at https://pypi.python.org/pypi/.
PyPI is kept up-to-date so, in many cases, newer versions are available there than via slapt-get / GSlapt, or even via slapt-src / Sourcery.
The only disadvantage I can think of would be during a Slackware / Salix upgrade. Packages installed by pip might get lost or damaged in the shuffle. Since pip can easily provide a list of all packages that it has installed, its seems simple enough to reconstruct the Python "site packages."
So for pure Python packages, are there any other reasons to install a Salix/Slackware package, rather than one from PyPI?