j.>dZddlmZddlZddlZddlZddlZddlZddlm Z m Z ddl m Z ddl mZmZmZmZddlmZe d Gd d Zd!dZd"dZd#dZd$dZd\ZZZe d GddZd%dZd&dZd'd ZdS)(aVIs this distribution an EDITABLE install, and how sure are we? WHY IT IS ITS OWN MODULE. This answer existed twice, in two strengths, and the strong one was in the place that never acts on it: * `__main__.py` had a three-valued detector over four independent signals, refusing on `unknown` - and `__main__` is the CLI, which is forbidden from running pip at all (`INSTALL_RUNNER = _refuse_to_install`). * `_pin.py` had `editable_core_path()`: one file, `direct_url.json`, two values, `None` on any gap - and `_pin` is the module that actually runs `pip install --force-reinstall`, from the first line of a consumer's `__init__`. So the careful check guarded a command that never runs and the careless one guarded the command that overwrites a developer's working tree. That is not hypothetical: on 2026-07-27 it fired THREE times in one session, replacing an editable checkout with the published wheel, and twice it corrupted a measurement rather than just being annoying - three tests went red claiming fixes that were present on disk were missing, and five mutation checks reported SURVIVED against a gate that was sound. The third time it blocked a push in the middle of a release. THE RULE -------- `safe_to_reinstall` is `state == NOT_EDITABLE`, never `state != EDITABLE`. The three ways the old check was defeated all produced an ABSENCE of evidence, and an absence of evidence must not read as a licence to overwrite somebody's work. Stdlib only. `_pin` imports this and `_pin` runs at the first line of a consumer's import, so anything heavy here is paid by every user on every start. ) annotationsN) dataclassfield)Path)ListOptionalSequenceTuple)metadataT)frozenceZdZUdZded<ded<dZded<dZd ed <d Zd ed <d Zded<dZ ded<dZ ded<dZ d ed<dZ d ed<dZ ded<d S) DistFactsaEverything the doctor reads about one distribution. One seam, so the tests never touch the real environment. direct_url_raw is the FILE, kept separately from the parsed object on purpose: "the file is not there" and "the file is there and is garbage" are different findings, and collapsing them into `direct_url is None` is how the editable check used to conclude "not editable" from a truncated file. requires is the raw Requires-Dist list. The doctor does NOT parse it here: the `invisible-core==` question is answered by invisible_core.pin, so the doctor and the consumers' import-time check cannot disagree about the same metadata. It is kept because it is what the environment declares, and the tests feed the shared parser from this same field. strnameboolpresentversionTuple[str, ...]requiresNzOptional[dict] direct_urlz Optional[str]direct_url_raw metadata_dir module_pathlegacy_editableeditable_finder git_worktree)__name__ __module__ __qualname____doc____annotations__rrrrrrrrrrCC:\Projects\Muse2API\.venv\Lib\site-packages\invisible_core/_env.pyrr.s  IIIMMMG "H""""!%J%%%%$(N((((LK')O))))')O))))Lr$rprreturnrc>td|jDS)Nc3K|]}|dvV dS))z site-packagesz dist-packagesNr).0parts r% z'_under_site_packages..Ls(NNdt99NNNNNNr$)anyparts)r&s r%_under_site_packagesr/Ks! NNagNNN N NNr$rc |g|jD]*}|dz rt|cS+n#t$rYnwxYwdS)aThe nearest ancestor holding a .git entry, or "". Only ever consulted for files that are NOT under site-packages. A virtualenv created inside the project (.venv/, the common layout) puts every ordinary index install inside a git working tree, so on its own this signal would call the whole environment editable. Paired with the site-packages test it is what distinguishes `pip install -e .` from `pip install invisible-core`. z.gitr)parentsexistsrOSError)r&ds r%_git_worktree_abover5Osv ai  AF ""$$ 1vv         2s388 AAmodrc t||}|rt|Sn#t$rYnwxYw ddl}|j|}tt|ddpg}|r"tt|dS|-|j r&tt|j j Sn#t$rYnwxYwdS)z8Where do the files that would actually be imported live?rNsubmodule_search_locationsr) r locate_filer2r Exceptionimportlib.utilutil find_speclistgetattroriginparent)r4r6rr& importlibspeclocss r%_locate_modulerEas s## $ $ 88:: q66M         ~'',,GD">EEKLL  &tDG}}%% %   tDK((/00 0      2s+AA AAA!C+;.C++ C87C8rcR tj|}n@#tj$rt|dcYSt$rt|dcYSwxYwd} |d}n#t$rd}YnwxYwd}|A t j|}t|tr|nd}n#t$rd}YnwxYwtj dd|}ttt|ddpd}t|r|jnd}t#|||}g} g} t|rN|jdr4t)|s%| d|jd |j| |d D]`} || jd dvr| | jd a|d D]]} || jd dvr| | j^n#t4$rYnwxYwd} |r8t)t|st7t|} t|d|jpdt;|jpd||t||t;| t;| |  S)NFzdirect_url.jsonz[-.]+__pathr)z .egg-infoz.eggzlegacy z outside site-packages at z *.egg-link-z (a develop-mode link)z __editable__*Tr)rrrrrr)r distributionPackageNotFoundErrorrr: read_textjsonloads isinstancedict ValueErrorresubrrr?rArErendswithr/appendgloblowerstemreplacer3r5rtupler)rr4rawduparsedr6meta_dirsite_dirrlegacyfinderlinkshimworktrees r% _dist_factsrexss&  !$ ' '  (&&&u%%%%% &&&u%%%%%& Ckk+,,  B  Z__F%fd33=BB   BBB  &3 % %CC7B//526677H"%h--9xTH C22KFF 8}}\//0EFF\(22\  Z ZZZZ[[[  l33 H H99;;$)//"3"3";";C"E"EEEMMTY"F"F"FGGG o66 - -99;;$)//"3"3";";C"E"EEEMM$),,, -    D H:/[0A0ABB:&tK'8'899 T4b% 8Hb2I2I2$'c(mm!,eFmm%*6]] K K KKsKAAAA00 A?>A?-B55 CCC)J J J)editablez not-editableunknowncteZdZUdZded<dZded<dZded<eeZ ded <e dd Z d S) EditabilityzEThree answers, not two. `unknown` is the one that used to be missing.rstaterpathwhy)default_factoryrevidencer'rc"|jtkS)a#Only a POSITIVE not-editable finding unlocks an install command. Not `state != EDITABLE`. The three ways this check was defeated all produced an absence of evidence, and an absence of evidence must not read as a licence to overwrite somebody's working tree. )rj NOT_EDITABLE)selfs r%safe_to_reinstallzEditability.safe_to_reinstallsz\))r$N)r'r) rr r!r"r#rkrlrrZrnpropertyrrrr$r%riris{OOJJJDNNNNCMMMM %e < < installed from a local directory, dir_info.editable is not setz'direct_url.json 'dir_info.editable' is ) rUNKNOWNrstriprYgetrOrrprPtyperEDITABLE)rtheadr\rzr{flags r%_pep610_verdictrs #CD D #))++CRC088sCC1(,112 2  B &&-- 2C c3  BsB@AAvvj!!H   ~33 #(9: :QR R h % %KJ!%h!8JJJK K << # #D t||#GHH }c$01 1 SLDLL MMr$c x|jsttddSt|jd|jDz}|jrTtt|js3d|j}|j r |d|j z }| |t|\}}}t|p|j}|tkr(tt||t|g|zS|r>tt|p|jd|t|S|t kr`|jC|jrz _editable_of..s49Z9Z9Z>?19999Z9Z9Zr$z3the importable files are outside site-packages, at z, inside the git working tree z; Nz6no direct_url.json and the files live in site-packages)rrirpr>rrrr/rrrUr _display_pathrrZjoinr~r)rtpositivenoterjrzrlrks r% _editable_ofrs =X<-VWWWu4559Z9ZCHCX9Z9Z9ZZH !5d5;L6M6M!N!NXUEVXX   J IU5GII ID%e,,OE3    2!2D 8T3seh6F0G0GHHHA8T%>U->99X..hAA A    'E,= '(e.?)@)@AA ( |U->WYY Y7D#... |T3 / //r$rzc|sdS|dr8ddlm}ddlm} |||jS#t $r|cYSwxYw|S)Nrzfile:r)urlparse) url2pathname) startswith urllib.parserurllib.requestrrkr:)rzrrs r%rrs r ~~g))))))////// < 233 3   JJJ  JsA AA)r&rr'r)r&rr'r)r6rrrr'r)rrr'r)rtrr'ru)rtrr'ri)rzrr'r) r" __future__rrMosrR subprocesssys dataclassesrrpathlibrtypingrrr r rBr rr/r5rErerrpr~rirrrrr$r%rs>#"""""  ((((((((222222222222 $8OOOO$.4K4K4K4Kn#H, $********$NNNND$0$0$0$0N      r$