1 7  m _I|Mdv &K Index of /FSS-BCZ/root/sys/devices/system/cpu/cpu3/node0/memory37

Index of /FSS-BCZ/root/sys/devices/system/cpu/cpu3/node0/memory37

 NameLast modifiedSizeDescription
 Parent Directory   -  
 node0/ 2026-10-21 14:32 -  
 subsystem/ 2026-10-21 14:32 -  
 online 2026-10-22 17:51 4.0K 
 phys_device 2026-10-22 17:51 4.0K 
 phys_index 2026-10-22 17:51 4.0K 
 power/ 2026-10-22 17:51 -  
 uevent 2026-10-22 17:51 4.0K 
 valid_zones 2026-10-22 17:51 4.0K 
 removable 2026-10-22 17:51 4.0K 
 state 2026-10-22 17:51 4.0K 
" lY>d h~.\i1h  Metadata-Version: 1.1 Name: gpg Version: 1.15.1 Summary: Python bindings to the GPGME API of the GnuPG cryptography library. Home-page: https://www.gnupg.org Author: The GnuPG hackers Author-email: gnupg-devel@gnupg.org License: LGPL2.1+ (the library), GPL2+ (tests and examples) Description: Dynamically generated bindings to the C API of the GNU Privacy Guard. The GPG Made Easy (GPGME) library provides a high-level API in C to all the component software and libraries in the GnuPG Project, including GPG itself (the GnuPG OpenPGP implementation), libgcrypt, libgpg-error, libassuan and more. The official CPython bindings to GPGME are generated during the compiling process of GPGME itself and built for the specific C header and include files produced when GPGME is compiled using SWIG. This provides access to over two thousand functions, methods and values via both the lower level dynamically generated bindings and a more intuitively pythonic higher level layer. While the lower level, dynamically generated bindings provide access to everything which GPGME itself provides; the higher level layer is easier to use by Python developers, provides access to the vast majority of functionality developers would want from GnuPG and is extensively documented. GPGME and thes