9 Commits

Include renames

Author	SHA1	Message	Date
Aman Sharma	3edad21b41	Write test for tmp_fname to check if it accepts Path-like and str objects	2019-11-18 11:49:40 +05:30
Aman Sharma	204cfcb879	Ensure makedirs accepts str and Path-like objects	2019-11-08 20:37:32 +05:30
Aman Sharma	d4aa27d6ab	Ensure copyfile accepts str and Path-like objects	2019-11-08 01:51:49 +05:30
Aman Sharma	34a868b420	Ensure file_md5 accept str and Path-like objects	2019-11-06 09:25:35 +05:30
Ruslan Kuprieiev	95fe1578bb	dvc: automatically reorder imports	2019-11-05 02:34:40 +02:00
Ruslan Kuprieiev	132de572af	run: improve pyenv PATH modification criteria ... https://discordapp.com/channels/485586884165107732/485596304961962003/628766062472724510 Related to #2506	2019-10-02 06:33:01 +03:00
Ruslan Kuprieiev	43975c8618	dvc: remove PATH prefixes appended by pyenv ... Unlike PyInstaller, pyenv doesn't leave backups of original env vars when it modifies them. If we look into the shim, pyenv and pyenv-exec, we can figure out that the PATH is modified like this: PATH=$PYENV_BIN_PATH:${bin_path}:${plugin_bin}:$PATH where PYENV_BIN_PATH - starts with $PYENV_ROOT, see pyenv-exec source code. bin_path - might not start with $PYENV_ROOT as it runs realpath on it, see pyenv source code. plugin_bin - might contain more than 1 entry, which start with $PYENV_ROOT, see pyenv source code. So having this, we can make a rightful assumption about what parts of the PATH we need to remove in order to get the original PATH. Fixes #2506	2019-09-23 04:25:42 +03:00
pared	7f8da34cf2	utils: extend to_chunks functionality, can specify number of chunks or length of chunk	2019-06-28 13:52:59 +02:00
pared	3d5c42e2fe	state: test: refactor existing state test to pytest	2019-06-28 13:52:59 +02:00