h!SrSSKrSSKJr SSKJrJrJrJr SSK J r SSK J r J r JrJrJr SS KJrJrJrJrJrJr S rS rS rS \S\S\S\3r\R8"\5\"\R:"5SSSS9\"SS\S3S9\"SSSSS9\"SSSSS9\"SSSS S94S!\S"\\S#\S$\S%\4 S&jj5r S0SSSS'.S!\S"\\S#\S$\S%\S(S4 S)jjjr!S1S*\S+\\\4S"\\S#\S$\S%\S(\4S,jjr"S0S-\\S"\\S(S4S.jjr#S!\S(S4S/jr$g)2ztThis module contains helpers and subcommands for integrating Weasel with Data Version Control (DVC). https://dvc.orgN)Path)AnyDictListOptional)msg)get_hash join_commandload_project_config run_command working_dir)COMMANDNAME PROJECT_FILEArgOptappzdvc.yaml.dvcdvcz6# This file is auto-generated by Weasel based on your z. If you've # edited your z-, you can regenerate this file by running: #  zELocation of project directory. Defaults to current working directory.TF)helpexists file_okayzName of workflow defined in z(. Defaults to first workflow if not set.)r --verbosez-VzPrint more info--quietz-qzPrint less infoz--forcez-FzForce update DVC config project_dirworkflowverbosequietforcec[XX#US9 g)ajAuto-generate Data Version Control (DVC) config. A DVC project can only define one pipeline, so you need to specify one workflow defined in the project.yml. If no workflow is specified, the first defined workflow is used. The DVC config will only be updated if the project.yml changed. DOCS: https://github.com/explosion/weasel/tree/main/docs/cli.md#repeat-dvc r r!r"N)project_update_dvc)rrr r!r"s H/home/james-whalen/.local/lib/python3.13/site-packages/weasel/cli/dvc.pyproject_update_dvc_clir's${gRWXr$returnc [U5n[XXX4S9nSnU(a[R"S[3U5 g[R "S[S3U5 g)aUpdate the auto-generated Data Version Control (DVC) config file. A DVC project can only define one pipeline, so you need to specify one workflow defined in the project.yml. Will only update the file if the checksum changed. project_dir (Path): The project directory. workflow (Optional[str]): Optional name of workflow defined in project.yml. If not set, the first workflow will be used. verbose (bool): Print more info. quiet (bool): Print less info. force (bool): Force update DVC config. r$z0To execute the workflow with DVC, run: dvc reprozUpdated DVC config from zNo changes found in z, no update neededN)r update_dvc_configrgoodrinfo)rrr r!r"configupdatedhelp_msgs r&r%r%)sY&! -FXeGBH +L>:HE ' ~5GH(Sr(pathr.c J[U5 URS05n[UR55n[ Xr5 U(dUSn[ U5nUR 5nU[- n U R5(aeU RSSS9n U R5R5RSS5n SSS5 W U:XaU(dg U R5 /n URS /5V s0sHoS U _M nn /nU(aURS 5 U(aURS 5 XbGHZnUUnURS/5nURS/5nURS/5nU(dU(d U(dMVSS[SSU/nUVs/sHnSU/PM snVVs/sHnUHnUPM M nnnUVs/sHnSU/PM snVVs/sHnUHnUPM M nnnUVs/sHnSU/PM snVVs/sHnUHnUPM M nnnS/UQSPUPSP[!U5PSPnURS5(aURS5 /UQUQUQUQUQnU R[#U55 GM] U (d[$R&"SSS9 [)U5 U HnS U-n[+U5 M SSS5 U RS!SS9n U R-5nU R/SS5 U R1SUS"[2S"U35 SSS5 g#!,(df  GN=fs sn fs snfs snnfs snfs snnfs snfs snnf!,(df  N=f!,(df  g#=f)$aVRe-run the DVC commands in dry mode and update dvc.yaml file in the project directory. The file is auto-generated based on the config. The first line of the auto-generated file specifies the hash of the config dict, so if any of the config values change, the DVC config is regenerated. path (Path): The path to the project directory. config (Dict[str, Any]): The loaded project.yml. verbose (bool): Whether to print additional info (via DVC). quiet (bool): Don't output anything (via DVC). force (bool): Force update, even if hashes match. RETURNS (bool): Whether the DVC config file was updated. workflowsrrutf8)encodingz# NFcommandsnamerrdepsoutputsoutputs_no_cachepythonz-mprojectrunz-dz-oz-Oz-nz-wz --no-execno_skipz--always-changedzhNo usable commands for DVC found. This can happen if none of your commands have dependencies or outputs.rexitszdvc zr+ T) ensure_dvcgetlistkeyscheck_workflowsr resolve DVC_CONFIGropenreadlinestripreplaceunlinkappendrstrr rfailrr readseekwriteDVC_CONFIG_COMMENT) r1r.rr r!r"r3workflow_names config_hashdvc_config_pathfref_hash dvc_commandscmdconfig_commandsflagsr9commandr:r;r< project_cmdpclcdeps_cmd outputs_cmdoutputs_nc_cmddvc_cmdfull_cmd dvc_commandcontents r&r+r+Gsf(t ;+I)..*+NN- !!$6"K <<>DZ'O  ! !# ! 71zz|))+33D"=H8 { "5 L39::j"3MN3MC6{C'3MON E [!  Y#!$'{{62&++i,";;'92>G,<  tYtD 48 9Dq$D 9F 9"2aA2A 9F7>#?w!T1Iw#?L#?RAqq#? L:J&K:JQay:J&KX&KUWPQ!UW!&KXK5K$KKdKCIK{K ;;y ! ! NN- .UWUxU+UUUL23%$(   5 T A 1*K  $    dV  4&&( q!  "[M$6#7r'CD 5 i8 7 O&!:F#?L&KX"   5 4 sO/M M/M"M' M-4M2M8%M=NAN M N N"r3c U(d[R"S[S3SS9 Ub6X;a1[R"SUS[SS RU53SS9 U(d%[R"S [S US S 35 gg)zValidate workflows provided in project.yml and check that a given workflow can be used to generate a DVC config. workflows (List[str]): Names of the available workflows. workflow (Optional[str]): The name of the workflow to convert. zNo workflows defined in zA. To generate a DVC config, define at least one list of commands.rrANz Workflow 'z' not defined in z. Available workflows: z, zLNo workflow specified for DVC pipeline. Using the first workflow defined in z: 'r')rrRrjoinwarn)r3rs r&rHrHs  &|n54 5  9  "3L>B$$(IIi$8#9 ;  &s9Q<. ;  r(c[R"SS/[RS9 US- R 5(d[R "S S SS9 g g ![a [R "SSSS9 NRf=f) zqEnsure that the "dvc" command is available and that the current project directory is an initialized DVC project. rz --version)stdoutztTo use Weasel with DVC (Data Version Control), DVC needs to be installed and the 'dvc' command needs to be availablezYou can install the Python package from pip (pip install dvc) or conda (conda install -c conda-forge dvc). For more details, see the documentation: https://dvc.org/doc/installrrArz(Project not initialized as a DVC projectzTo initialize a DVC project, you can run 'dvc init' in the project directory. For more details, see the documentation: https://dvc.org/doc/command-reference/initN) subprocessr?DEVNULL ExceptionrrRr)rs r&rDrDs  {+J4F4FG & ( ( * *  6 9   +    J 9   s%A A:9A:)N)NFFF)%__doc__rrpathlibrtypingrrrrwasabirutilr r r r rmainrrrrrrrJDVC_DIRUPDATE_COMMANDrVr`cwdrQboolr'r%r+rHrDr(r&rs&4,,XX<<  OP\~^n )1^   ^DHHJ-t~BNST!$/KL>ZB.CD{D7HIeY3DEeY3LM YYsmY Y  Y  YY,#T TTsmT T  T  T TB# S S cNSsmS S  S  S Sl tCy HSM T 4 D T r(