How to Install and Uninstall python36-python-gflags Package on openSuSE Tumbleweed

Last updated: November 27,2024

Deprecated! Installation of this package may no longer be supported.

1. Install "python36-python-gflags" package

In this section, we are going to explain the necessary steps to install python36-python-gflags on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python36-python-gflags
            
                    
    
    Copied

2. Uninstall "python36-python-gflags" package

Please follow the instructions below to uninstall python36-python-gflags on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python36-python-gflags
            
                    
    
    Copied

3. Information about the python36-python-gflags package on openSuSE Tumbleweed

Information for package python36-python-gflags:
-----------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python36-python-gflags
Version : 3.1.2-2.14
Arch : noarch
Vendor : openSUSE
Installed Size : 420,8 KiB
Installed : No
Status : not installed
Source package : python-python-gflags-3.1.2-2.14.src
Summary : Google Commandline Flags Module
Description :
This project is the python equivalent of google-gflags, a Google commandline
flag implementation for C++. It is intended to be used in situations where a
project wants to mimic the command-line flag handling of a C++ app that uses
google-gflags, or for a Python app that, via swig or some other means, is
linked with a C++ app that uses google-gflags.
The gflags package contains a library that implements commandline flags
processing. As such it's a replacement for getopt(). It has increased
flexibility, including built-in support for Python types, and the ability to
define flags in the source file in which they're used. (This last is its major
difference from OptParse.)