+ 4j Rt^RIHt^RIt^RIt^RIHt^RIHt]'d^RI H t .ROt ] !]P]P04tRRlt!R R]4tR R ltR R ltRRltR#)zGPath resolution, plus presence checks that tell absent from unreadable.) annotationsN)Enum) TYPE_CHECKING)Path PathStatec V^8dQhRRRR/#)excOSErrorreturnbool)formats"b/home/user/pdf2html-billing-ledger-validate/.venv/lib/python3.14/site-packages/nab_python/paths.py __annotate__rs'''T'c(VP\9#)zWhether ``exc`` from a stat or an open means nothing is at the path. ``ENOTDIR`` is a non-directory component part-way along the path, which leaves nothing at the path just as surely as ``ENOENT`` does. )errno_ABSENT_ERRNOS)r s&ris_absent_errorrs 99 &&rcD]tRt^!tRtRtRtRtRtRt ] RRl4t R t R #) rzWhat a stat of a path found.absentfile directoryother unreadablecV^8dQhRR/#)rr r r )rs"rrPathState.__annotate__+s>>T>rc HV\P\P39#)zWhether the caller should go on and open the path. True for a regular file, and for one whose stat failed: what an unreadable path means is the reader's call. )rFILE UNREADABLE)selfs&r should_readPathState.should_read*s  (<(<===rr N) __name__ __module__ __qualname____firstlineno____doc__ABSENTr DIRECTORYOTHERr propertyr"__static_attributes__r rrrr!s0& F DI EJ >>rc V^8dQhRRRR/#)rpathrr rr )rs"rrr4sTircVP4p\P!TP4'd\P#\P!TP4'd\P#\P# \d\Pu#\dAp\ T4'd\PuRp?#\P uRp?#Rp?ii;i)aClassify ``path`` without raising, keeping the stat failures apart. ``Path.exists``/``is_file``/``is_dir`` answer with a bool, so an absent path and a stat that failed collapse into one answer. An unsearchable parent directory fails the stat with ``EACCES``, which those methods re-raise on Python 3.13 and below and report as absent on 3.14. :data:`PathState.UNREADABLE` keeps that case separate, so the caller can hand the path to the read that names the errno. N) stat ValueErrorrr)r rr S_ISREGst_moderS_ISDIRr*r+)r/str s& r path_stater74s $ YY[ ||BJJ~~ ||BJJ""" ??   $ 3  ## ####$s5BC5+C54C55 C0C5C0*C50C5c V^8dQhRRRR/#)rentrystrr r r )rs"rrrQsstrc RV9#)zWhether the filesystem can carry ``entry`` as a name. An embedded NUL has to be tested for rather than caught: building a ``Path`` never raises on one, and a non-strict resolve keeps it in the path on Windows. r )r9s&ris_usable_path_namer=Qs  rc$V^8dQhRRRRRR/#)rbaserr9r:r z Path | Noner )rs"rrr[s!  t C K rcz\V4'gR#W, P4# \dR#i;i)zResolve ``entry`` against ``base``, or ``None`` for an unusable name. Unencodable names other than a NUL raise from the resolve itself. N)r=resolver2)r?r9s&&r resolve_pathrB[s: u % % %%'' s + ::)rrr=r7rB)r( __future__rrr1enumrtypingrpathlibr__all__ frozensetENOENTENOTDIRrrrr7r=rBr rrrKs]M"   ELL%--89'>>&: r