OwlCyberSecurity - MANAGER
Edit File: _aix_support.cpython-313.pyc
� ���g� � �F � S r SSKrSSKrS S jrS rS rS rS rS rS r g) z Shared AIX support functions.� Nc �V � SSK nSSKn[ SUR 5 < 3S5 nUR U5 nU( a U < SUR < S3nOU < SUR < S3nUR U5 ( d UR 5 OSsSSS5 $ ! , ( d f g= f) z0Output from successful command execution or Noner Nz/tmp/_aix_support.zw+bz >'z' 2>&1z 2>/dev/null >'�')�os� contextlib�open�getpid�closing�name�system�read)� commandstring�capture_stderrr r �fp�cmds �3/opt/alt/python313/lib64/python3.13/_aix_support.py�_read_cmd_outputr sy � � �� � � � � �� � �B� � � �B� �2� �%2�B�G�G�<�C�,9�2�7�7�C�C� "� � �#���r�w�w�y�D� � � �s �AB� B(c � � [ R S:X a SOSnUS:w a UOSnSR U S U S U S X25 $ ) Ni���� �@ r �' z aix-{:1x}{:1d}{:02d}-{:04d}-{}� � )�sys�maxsize�format)�vrtl�bd�_sz�_bds r �_aix_tagr sF � � � � ��(�"�b�C��a��"�T�C� +� 2� 2�4��7�D��G�T�!�W�c� W�W� c �v � U R S5 S S u pn[ US 5 [ U5 [ U5 /$ )N�.� ���)�split�int)�vrmf�v�r�tls r � _aix_vrtlr, $ s7 � ��z�z�#��r��"�H�A�"� ��"��J��A���B�� (�(r! c � � SSK n U R / SQ5 nUR S5 nUR 5 R S5 nUS S:w a [ US 5 OS n[ US 5 U4$ ! [ a [ S5 n Npf = f) a Return a Tuple[str, int] e.g., ['7.1.4.34', 1806] The fileset bos.rte represents the current AIX run-time level. It's VRMF and builddate reflect the current ABI levels of the runtime environment. If no builddate is found give a value that will satisfy pep425 related queries r N)z/usr/bin/lslppz-Lqczbos.rtez/usr/bin/lslpp -Lqc bos.rtezutf-8�:r% � r r ) � subprocess� check_output� ImportErrorr �decode�stripr& r' �str)r0 �outr s r � _aix_bos_rter7 * s� � �>���%�%�&K�L�� �*�*�W� �C� �)�)�+� � �C� �C� �b�'�R�-�#�c�"�g�,�T�C� ��A��K�� � �� � >� � <�=��>�s �A2 �2B � B c �D � [ 5 u p[ [ U 5 U5 $ )ap AIX filesets are identified by four decimal values: V.R.M.F. V (version) and R (release) can be retrieved using ``uname`` Since 2007, starting with AIX 5.3 TL7, the M value has been included with the fileset bos.rte and represents the Technology Level (TL) of AIX. The F (Fix) value also increases, but is not relevant for comparing releases and binary compatibility. For binary compatibility the so-called builddate is needed. Again, the builddate of an AIX release is associated with bos.rte. AIX ABI compatibility is described as guaranteed at: https://www.ibm.com/ support/knowledgecenter/en/ssw_aix_72/install/binary_compatability.html For pep425 purposes the AIX platform tag becomes: "aix-{:1x}{:1d}{:02d}-{:04d}-{}".format(v, r, tl, builddate, bitsize) e.g., "aix-6107-1415-32" for AIX 6.1 TL7 bd 1415, 32-bit and, "aix-6107-1415-64" for AIX 6.1 TL7 bd 1415, 64-bit )r7 r r, )r( r s r � aix_platformr9 ? s � �& �~�H�D� �I�d�O�R� (�(r! c �d � [ R " S5 n U ( d [ S5 e[ U S9$ )N�BUILD_GNU_TYPEz BUILD_GNU_TYPE is not defined)r( )� sysconfig�get_config_var� ValueErrorr, )�gnu_types r �_aix_bgtr@ W s- � ��'�'�(8�9�H� ��8�9�9� �(� #�#r! c � � [ R " S5 n [ U 5 n [ [ 5 U 5 $ ! [ [ 4 a [ SU < 35 ef = f)z< Return the platform_tag of the system Python was built on. � AIX_BUILDDATEz)AIX_BUILDDATE is not defined or invalid: )r< r= r' r> � TypeErrorr r@ )� build_dates r � aix_buildtagrE _ sc � � �)�)�/�:�J�,���_� � �H�J� � +�+�� � � "� ,��D� &�>�+� ,� ,�,�s � 7 � A)F) �__doc__r r< r r r, r7 r9 r@ rE � r! r �<module>rH s2 �� #� � �9�$X�)� �*)�0$� ,r!