σ @K7]c@`sΈddlmZmZmZddlZddlZddlZddlmZddl m Z m Z ddl m Z ddl mZejdejƒd„Zd „Zd „ZdS( i(tabsolute_importtdivisiontprint_functionN(tapi(tCONDA_TARBALL_EXTENSIONSton_win(tget_render_parser(texecutetlevelcC`sUtƒ}d|_|jdddƒ|jddddƒ|jdd dd ƒ|jd d d dddƒ|jddg|jD]}|jdgkrƒ|^qƒdfgƒ|jddg|jD]}|jdgkrΘ|^qΘdfgƒ|jddg|jD]}|jdgkr |^q dfgƒ|j|ƒ}||fS(NsQ Set up environments and activation scripts to debug your build or test phase. trecipe_or_package_file_paththelpsτPath to recipe directory or package file to use for dependency and source information. If you use a recipe, you get the build/host env and source work directory. If you use a package file, you get the test environments and the test_tmp folder.s-ps--paths‘root path in which to place envs, source and activation script. Defaults to a standard conda-build work folder (packagename_timestamp) in your conda-bld folder.s-os --output-idsψfnmatch pattern that is associated with the output that you want to create an env for. Must match only one file, as we don't support creating envs for more than one output at a time. The top-level recipe can be specified by passing 'TOPLEVEL' heres-as--activate-string-onlytactiont store_truesuOutput only the string to the used generated activation script. Use this for creating envs in scripted environments.s--outputis --bootstraps--old-build-string(Rt descriptiont add_argumentt_handle_conflict_resolvetNonet_actionstoption_stringst parse_args(targstpt_((s9lib/python2.7/site-packages/conda_build/cli/main_debug.pyRs"  EE)c`s`t|ƒ\}‰t}yt‡fd†tDƒƒsRt|dtƒ}t}n ˆj}tj|dˆj ˆj }ˆj s±t ddƒ|r€t dƒq±t dƒnt |ƒˆj s(|rςt rΦdnd}t d j |ƒƒn%t rώd nd }t d j |ƒƒt ddƒnWn0tk r[}t t|ƒƒtjd ƒnXdS(Nc3`s.|]$}tjjˆjƒd|kVqdS(iN(tostpathtsplitextR (t.0text(t_args(s9lib/python2.7/site-packages/conda_build/cli/main_debug.pys @st print_resultstverboset#iPsKTest environment created for debugging. To enter a debugging environment: sYBuild and/or host environments created for debugging. To enter a debugging environment: sconda_test_runner.shsDTo run your tests, you might want to start with running the {} file.sconda_build.batsconda_build.shsDTo run your build, you might want to start with running the {} file.i(RtTruetanyRtrender_executetFalseR Rtdebugtactivate_string_onlyt__dict__tprintRtformatt ValueErrortstrtsystexit(RRttesttthing_to_debugtactivation_stringt test_filet build_filete((Rs9lib/python2.7/site-packages/conda_build/cli/main_debug.pyR;s0       cC`sttjdƒS(Ni(RR+targv(((s9lib/python2.7/site-packages/conda_build/cli/main_debug.pytmain]s(t __future__RRRtloggingRR+t conda_buildRtconda_build.utilsRRtconda_build.cli.main_renderRRR"t basicConfigtINFORR4(((s9lib/python2.7/site-packages/conda_build/cli/main_debug.pyts    # "