grthtrhthjhtyjytjytkergtrhtrjytjerhrfh4:24 29/09/2026+ `o'brHRt^RIt^RItR RltRtRtRtRtRtRt R#) zShared AIX support functions.Ncr^RIp^RIp\RVP4: 2R4pVP V4;_uu_4pV'dV: RVP : R2pMV: RVP : R2pVP V4'gVP4MRuuRRR4# +'giR#;i)z0Output from successful command execution or NoneNz/tmp/_aix_support.zw+bz >'z' 2>&1z 2>/dev/null >'')os contextlibopengetpidclosingnamesystemread) commandstringcapture_stderrrrfpcmds&& 3/opt/alt/python314/lib64/python3.14/_aix_support.py_read_cmd_outputrs    B   B  2 %2BGG%%&KL **W C ))+  C Cb'R-#c"g,TC AK  ><=>sA??BBcD\4wr\\V4V4#)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 )r3rr()r$rs r aix_platformr5?s&~HD IdOR ((rcl\P!R4pV'g \R4h\VR7#)BUILD_GNU_TYPEzBUILD_GNU_TYPE is not defined)r$) sysconfigget_config_var ValueErrorr()gnu_types r_aix_bgtr<Ws-''(89H 899 ( ##rc\P!R4p\V4p\ \ 4T4# \\3d\RT: 24hi;i)z< Return the platform_tag of the system Python was built on. AIX_BUILDDATEz)AIX_BUILDDATE is not defined or invalid: )r8r9r#r: TypeErrorrr<) build_dates r aix_buildtagrA_sc))/:J,_  HJ ++  ",D&>+, ,,s 7!A)F) __doc__rr8rrr(r3r5r<rArrrDs2# 9$X) *)0$ ,r