How to Install and Uninstall python39-cymem Package on openSuSE Tumbleweed

Last updated: December 25,2024

1. Install "python39-cymem" package

Here is a brief guide to show you how to install python39-cymem on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python39-cymem
            
                    
    
    Copied

2. Uninstall "python39-cymem" package

Here is a brief guide to show you how to uninstall python39-cymem on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python39-cymem
            
                    
    
    Copied

3. Information about the python39-cymem package on openSuSE Tumbleweed

Information for package python39-cymem:
---------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python39-cymem
Version : 2.0.8-1.4
Arch : x86_64
Vendor : openSUSE
Installed Size : 125.7 KiB
Installed : No
Status : not installed
Source package : python-cymem-2.0.8-1.4.src
Upstream URL : https://github.com/explosion/cymem
Summary : Manage calls to calloc/free through Cython
Description :
cymem provides two small memory-management helpers for Cython. They make it
easy to tie memory to a Python object's life-cycle, so that the memory is freed
when the object is garbage collected.
The most useful is `cymem.Pool`, which acts as a thin wrapper around the calloc
function:
```python
from cymem.cymem cimport Pool
cdef Pool mem = Pool()
data1 = mem.alloc(10, sizeof(int))
data2 = mem.alloc(12, sizeof(float))
```
The `Pool` object saves the memory addresses internally, and frees them when the
object is garbage collected. Typically you'll attach the `Pool` to some cdef'd
class. This is particularly handy for deeply nested structs, which have
complicated initialization functions. Just pass the `Pool` object into the
initializer, and you don't have to worry about freeing your struct at all —
all of the calls to `Pool.alloc` will be automatically freed when the `Pool`
expires.