How to Install and Uninstall python2-smmap Package on openSUSE Leap
Last updated: December 25,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "python2-smmap" package
This is a short guide on how to install python2-smmap on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
python2-smmap
Copied
2. Uninstall "python2-smmap" package
This tutorial shows how to uninstall python2-smmap on openSUSE Leap:
$
sudo zypper remove
python2-smmap
Copied
3. Information about the python2-smmap package on openSUSE Leap
Information for package python2-smmap:
--------------------------------------
Repository : Main Repository
Name : python2-smmap
Version : 3.0.2-bp153.1.15
Arch : noarch
Vendor : openSUSE
Installed Size : 174,6 KiB
Installed : No
Status : not installed
Source package : python-smmap-3.0.2-bp153.1.15.src
Summary : A pure git implementation of a sliding window memory map manager
Description :
When reading from many possibly large files in a fashion similar to random
access, it is usually the fastest and most efficient to use memory maps.
Although memory maps have many advantages, they represent a very limited
system resource as every map uses one file descriptor, whose amount is
limited per process. On 32 bit systems, the amount of memory you can have
mapped at a time is naturally limited to theoretical 4GB of memory, which
may not be enough for some applications.
The documentation can be found here: http://packages.python.org/smmap
--------------------------------------
Repository : Main Repository
Name : python2-smmap
Version : 3.0.2-bp153.1.15
Arch : noarch
Vendor : openSUSE
Installed Size : 174,6 KiB
Installed : No
Status : not installed
Source package : python-smmap-3.0.2-bp153.1.15.src
Summary : A pure git implementation of a sliding window memory map manager
Description :
When reading from many possibly large files in a fashion similar to random
access, it is usually the fastest and most efficient to use memory maps.
Although memory maps have many advantages, they represent a very limited
system resource as every map uses one file descriptor, whose amount is
limited per process. On 32 bit systems, the amount of memory you can have
mapped at a time is naturally limited to theoretical 4GB of memory, which
may not be enough for some applications.
The documentation can be found here: http://packages.python.org/smmap