3 sd+@sdZddlZddlmZmZmZddlm Z ddl m Z ddl m Z ddlmZddlmZe fd d Zd d Zdd e dddfddZddZdZGdddeZGdddeZddZdS)z Distutils / setuptools helpers N)joinsplitsplitext) ConfigParser) LooseVersion)build_py)install_scripts)logcsGfddd}|S)aZ Return extended build command class for recording commit The extended command tries to run git to find the current commit, getting the empty string if it fails. It then writes the commit hash into a file in the `pkg_dir` path, named ``COMMIT_INFO.txt``. In due course this information can be used by the package after it is installed, to tell you what commit it was installed from if known. To make use of this system, you need a package with a COMMIT_INFO.txt file - e.g. ``myproject/COMMIT_INFO.txt`` - that might well look like this:: # This is an ini file that may contain information about the code state [commit hash] # The line below may contain a valid hash if it has been substituted during 'git archive' archive_subst_hash=$Format:%h$ # This line may be modified by the install process install_hash= The COMMIT_INFO file above is also designed to be used with git substitution - so you probably also want a ``.gitattributes`` file in the root directory of your working tree that contains something like this:: myproject/COMMIT_INFO.txt export-subst That will cause the ``COMMIT_INFO.txt`` file to get filled in by ``git archive`` - useful in case someone makes such an archive - for example with via the github 'download source' button. Although all the above will work as is, you might consider having something like a ``get_info()`` function in your package to display the commit information at the terminal. See the ``pkg_info.py`` module in the nipy package for an example. cseZdZdZfddZdS)z#get_comrec_build..MyBuildPyz6 Subclass to write commit data into installation tree csj|ddl}|jd|j|jdd}|j\}}t|}t}|jtd|j dd|t|j d}|j t |ddS) Nrzgit rev-parse --short HEADT)stdoutstderrshellzCOMMIT_INFO.txtz commit hashZ install_hashwt) run subprocessPopenPIPE communicatestrrreadpjoinset build_libwriteopen)selfrprocZ repo_commit_Z cfg_parserZout_pth) build_cmdpkg_dir//tmp/pip-build-7vycvbft/nibabel/nisext/sexts.pyr4s  z'get_comrec_build..MyBuildPy.runN)__name__ __module__ __qualname____doc__rr)rrrr MyBuildPy2sr%r)rrr%r)rrr get_comrec_builds#r&cCs@||krg||<nt||tr.||g||<||j|dS)z6 Helper for appending dependencies to setuptools args N) isinstancerappend)Zin_dictkeyvaluerrr _add_append_keyGs  r+Fc Csp|dk }t|}|dkr dd}|dkr,i}ddddd} | j|t||||\} } | d krbdS|s| d kr|st| d |tj| d || d dS| d krtd|| dkst|st| d| ||ftj| d| ||f| d dS|rt|t rtd|} |r4| d|7} |r`d|krLi|d<t |d|| dSt |d| dS)a Check if package `pkg_name` is present and has good enough version Has two modes of operation. If `setuptools_args` is None (the default), raise an error for missing non-optional dependencies and log warnings for missing optional dependencies. If `setuptools_args` is a dict, then fill ``install_requires`` key value with any missing non-optional dependencies, and the ``extras_requires`` key value with optional dependencies. This allows us to work with and without setuptools. It also means we can check for packages that have not been installed with setuptools to avoid installing them again. Parameters ---------- pkg_name : str name of package as imported into python version : {None, str}, optional minimum version of the package that we require. If None, we don't check the version. Default is None optional : bool or str, optional If ``bool(optional)`` is False, raise error for absent package or wrong version; otherwise warn. If ``setuptools_args`` is not None, and ``bool(optional)`` is not False, then `optional` should be a string giving the feature name for the ``extras_require`` argument to setup. checker : callable, optional callable with which to return comparable thing from version string. Default is ``distutils.version.LooseVersion`` version_getter : {None, callable}: Callable that takes `pkg_name` as argument, and returns the package version string - as in:: ``version = version_getter(pkg_name)`` If None, equivalent to:: mod = __import__(pkg_name); version = mod.__version__`` messages : None or dict, optional dictionary giving output messages setuptools_args : None or dict If None, raise errors / warnings for missing non-optional / optional dependencies. If dict fill key values ``install_requires`` and ``extras_require`` for non-optional and optional dependencies. NcSst|}|jS)N) __import__ __version__)pkg_namemodrrr version_gettersz%package_check..version_getterz-Cannot import package "%s" - is it installed?zMissing optional package "%s"z; you may get run-time errorsz=You have version %s of package "%s" but we need version >= %s)missingz missing optz opt suffixzversion too old satisfiedr1z missing optz opt suffixz no-versionzCannot find version for z low-versionzversion too oldz'Not-False optional arg should be stringz>=extras_requireinstall_requires) boolupdate_package_status RuntimeErrorr warnAssertionErrorr'rr+) r.versionoptionalcheckerr0messagesZsetuptools_argsZsetuptools_modeZ optional_tfZmsgsstatus have_version dependencyrrr package_checkTsd2           rBcCsly t|Wntk r dSX|s*dSy ||}Wntk rJdSX||||krdd|fSd|fS)Nr1r2 no-versionz low-version)r1N)r2N)rCN)r, ImportErrorAttributeError)r.r;r0r=r@rrr r7s  r7a0@echo off REM wrapper to use shebang first line of {FNAME} set mypath=%~dp0 set pyscript="%mypath%{FNAME}" set /p line1=<%pyscript% if "%line1:~0,2%" == "#!" (goto :goodstart) echo First line of %pyscript% does not start with "#!" exit /b 1 :goodstart set py_exe=%line1:~2% call "%py_exe%" %pyscript% %* c@seZdZdZddZdS)install_scripts_bata Make scripts executable on Windows Scripts are bare file names without extension on Unix, fitting (for example) Debian rules. They identify as python scripts with the usual ``#!`` first line. Unix recognizes and uses this first "shebang" line, but Windows does not. So, on Windows only we add a ``.bat`` wrapper of name ``bare_script_name.bat`` to call ``bare_script_name`` using the python interpreter from the #! first line of the script. Notes ----- See discussion at https://matthew-brett.github.io/pydagogue/installing_scripts.html and example at git://github.com/matthew-brett/myscripter.git for more background. c Cstj|tjdksdSx|jD]}t|d}|j}WdQRX|jdoXd|jksft j dq"t |\}}t |\}}t ||d}tjd|} t j d|d ||jrq"t|d }|j| WdQRXq"WdS) Nntrtz#!pythonz3No #!python executable found, skipping .bat wrapperz.batz{FNAME}zMaking z wrapper for r )rrosname get_outputsrreadline startswithlowerr infopsplitrr BAT_TEMPLATEreplacedry_runr) rfilepathfobj first_linepthfnameZfrootextZbat_fileZ bat_contentsrrr rs&          zinstall_scripts_bat.runN)r!r"r#r$rrrrr rFsrFc@seZdZddZdS)BunchcCs0x*|jD]\}}|jdrq ||j|<q WdS)N__)itemsrN__dict__)rvarsr)rKrrr __init__s zBunch.__init__N)r!r"r#r`rrrr r[sr[c Cs0i}t|d}t|j|WdQRXt|S)a  Read variables from Python text file Parameters ---------- ver_file : str Filename of file to read Returns ------- info_vars : Bunch instance Bunch object where variables read from `ver_file` appear as attributes rHN)rexecrr[)Zver_filensrVrrr read_vars_froms rc)r$rJos.pathrrrrQr configparserrdistutils.versionrZdistutils.command.build_pyr!distutils.command.install_scriptsr distutilsr r&r+rBr7rRrFobjectr[rcrrrr s(      8  f*