o {g@sdZgdZddlZddlZddlZddlmZddlZddlm Z ddl m Z ddl Z ddlZddlZddlmZddlmZddlmZmZddlmZdd lmZmZmZmZdd lm Z m!Z!m"Z"m#Z#m$Z$dd l%m&Z&dd l'm(Z(m)Z)m*Z*m+Z+m,Z,m-Z-m.Z.m/Z/d dl0m1Z1m2Z2m3Z3m4Z4m5Z5m6Z6m7Z7m8Z8d dl9m:Z:m;Z;mZ>m?Z?m@Z@mAZAddlBmCZCmDZDmEZEmFZFmGZGmHZHmIZImJZJmKZKmLZLmMZMmNZNmOZOmPZPddlQmRZRmSZSeNrddl mTZTddlUmVZVddlWmXZXePe$e!eYeZfZ[ej\deSdeGeYddffddZ]Gddde)ej^e&Z_dS)zModule containing :class:`IndexFile`, an Index implementation facilitating all kinds of index manipulations such as querying and merging.) IndexFile CheckoutError StageTypeN)BytesIO)S_ISLNK)IStream)MemoryDB)defenc force_bytes)rGitCommandErrorGitErrorInvalidGitRepositoryError)BlobCommitObject SubmoduleTree) Serializable)Actor LazyMixinLockedFDjoin_path_nativefile_contents_roto_native_path_linux unbare_repo to_bin_sha) S_IFGITLINKaggressive_tree_merge entry_key read_cacherun_commit_hookstat_mode_to_index_mode write_cachewrite_tree_from_cache)BaseIndexEntry IndexEntryr)TemporaryFileSwappost_clear_cache default_indexgit_working_dir)AnyBinaryIOCallableDict GeneratorIOIterableIteratorListNoReturnSequence TYPE_CHECKINGTupleUnion)LiteralPathLike)Popen) Reference)Repo directoryreturnc cstjdkr%tj|d\}}t|z |VWt|dSt|wtj|d }|jVWddS1s;wYdS)a$Create a named temporary file git subprocesses can open, deleting it afterward. :param directory: The directory in which the file is created. :return: A context manager object that creates the file and provides its name on entry, and deletes it on exit. win32)dirN) sysplatformtempfilemkstemposcloseremoveNamedTemporaryFilename)r>fdrJctxrMk/var/www/bot.gig.net.ua/public_html/telegram/P1/HellBot/venv/lib/python3.10/site-packages/git/index/base.py$_named_temporary_file_for_subprocessWs   "rOcseZdZdZdZdZ eZ ddddeedfddfd d Z d e ddffd d Z defddZ e defddZdddZdeddfddZdeefddZddededdfddZ  ddedefdeddfddZeedded edefddfd!d"Zeddd#ee efddfd$d%Zeddd&ed'eddfd(d)Z e!d*dd+e"ede#efd,d-Z$ .dd/d0d1ed2ed3e%d4e&fd5e%eeegdfd6edede ffd7d8Z'd9d:fd;e%e(e)e*fgefde#e(e)e*ffdd?Z-ed@ee.ee)fde(ee)ffdAdBZ/dCe#e*ddfdDdEZ0ddFdGZ1defdHdIZ2dJeeedKfdeeedKffdLdMZ3dNedefdOdPZ4dQeee"eee*e.dRffde(eeee.ffdSdTZ5d1ed5e%de.fdUdVZ6e!e7d+ee dWee%dfd5e%dXee.dee.f dYdZZ8d.d[d:dd.dfdQeee"eee*e.dRffd\ed5e%dWee%d4efdfd]ed^edee.fd_d`Z9dQeee"eee.e*e:ffdeefdadbZ;ee ddQeee"eee*e.dRffdced'edee fdddeZdfdkedlede?fdmede?fdnee@j@e dfdoee@j@e dfdpede>fdqdrZAdie ddfdsdtZBddudvZCde fdwdxZDde fdydzZEdd/d{d|edeFfd}d~ZGedddd:fd+edeHefd\ed5e%d'edede#ee"eff ddZIe   ddee>de fdced+edeHefdked'eddf ddZJeKjLddfdeeMeKjNjLdde dfd+eeeee(ed4fdfded'edeKjOeKjPf fdd ZQZRS)raAn Index that can be manipulated using a native implementation in order to save git command function calls wherever possible. This provides custom merging facilities allowing to merge without actually changing your index or your working tree. This way you can perform your own test merges based on the index only without having to deal with the working copy. This is useful in case of partial working trees. Entries: The index contains an entries dict whose keys are tuples of type :class:`~git.index.typ.IndexEntry` to facilitate access. You may read the entries dict or manipulate it using IndexEntry instance, i.e.:: index.entries[index.entry_key(index_entry_instance)] = index_entry_instance Make sure you use :meth:`index.write() ` once you are done manipulating the index directly before operating on it using the git command. )repoversionentries_extension_data _file_pathNrPr= file_pathr?cCs&||_|j|_d|_|p||_dS)aInitialize this Index instance, optionally from the given `file_path`. If no `file_path` is given, we will be created from the current index file. If a stream is not given, the stream will be initialized from the current repository's index on demand. N)rP_VERSIONrQrS _index_pathrT)selfrPrVrMrMrN__init__szIndexFile.__init__attrc s|dkr8z t|jtj}Wn tyi|_YdSwzt|ddd}Wt|nt|w||dSt |dS)NrRT)stream allow_mmap) rFopenrTO_RDONLYOSErrorrRrrG _deserializesuper _set_cache_)rZr\rKr] __class__rMrNrds zIndexFile._set_cache_cCs|jjr t|jjdStd)Nindexz)No git directory given to join index path)rPgit_dirrr rZrMrMrNrYszIndexFile._index_pathcCs|jS)z3:return: Path to the index file we are representing)rTrirMrMrNpathszIndexFile.pathcCs z|`WdStyYdSw)z6Safely clear the entries cache so it can be recreated.N)rRAttributeErrorrirMrMrN_delete_entries_caches   zIndexFile._delete_entries_cacher]cCst|\|_|_|_}|S)zFInitialize this instance with index values read from the given stream.)r rQrRrS)rZr] _conten_sharMrMrNrbszIndexFile._deserializecCst|jdddS)zK:return: List of entries, in a sorted fashion, first by path, then by stagecSs |j|jfSNrjstageerMrMrN z+IndexFile._entries_sorted..)key)sortedrRvaluesrirMrMrN_entries_sortedszIndexFile._entries_sortedFignore_extension_datacCs&|}|j}|r d}t||||Srn)rxrSr#)rZr]ryrRextension_datarMrMrN _serializes  zIndexFile._serializecCsj|jt|p|j}|jddd}z|||Wn ty%|w||dur3||_dSdS)aWrite the current state to our file path or to the given one. :param file_path: If ``None``, we will write to our stored file path from which we have been initialized. Otherwise we write to the given file path. Please note that this will change the `file_path` of this index to the one you gave. :param ignore_extension_data: If ``True``, the TREE type extension data read in the index will not be written to disk. NOTE that no extension data is actually written. Use this if you have altered the index and would like to use :manpage:`git-write-tree(1)` afterwards to create a tree representing your written changes. If this data is present in the written index, :manpage:`git-write-tree(1)` will instead write the stored/cached tree. Alternatively, use :meth:`write_tree` to handle this case automatically. T)writer]N)rRrrTr_r{ BaseExceptionrollbackcommit)rZrVrylfdr]rMrMrNr|s  zIndexFile.writerhsbasecCs6gd}|dur |||||jj||S)aMerge the given `rhs` treeish into the current index, possibly taking a common base treeish into account. As opposed to the :func:`from_tree` method, this allows you to use an already existing tree as the left side of the merge. :param rhs: Treeish reference pointing to the 'other' side of the merge. :param base: Optional treeish reference pointing to the common base of `rhs` and this index which equals lhs. :return: self (containing the merge and possibly unmerged entries in case of conflicts) :raise git.exc.GitCommandError: If there is a merge conflict. The error will be raised at the first conflicting path. If you want to have proper merge resolution to be done by yourself, you have to commit the changed index (or make a valid tree from it) and retry with a three-way :meth:`index.from_tree ` call. ) --aggressivez-iz-mN)appendrPgit read_tree)rZrrargsrMrMrN merge_trees   zIndexFile.merge_treetree_shacGsNdd|D}t|j|}||}ttdd|Ddd|D}||_|S)aMerge the given treeish revisions into a new index which is returned. This method behaves like ``git-read-tree --aggressive`` when doing the merge. :param repo: The repository treeish are located in. :param tree_sha: 20 byte or 40 byte tree sha or tree objects. :return: New :class:`IndexFile` instance. Its path will be undefined. If you intend to write such a merged Index, supply an alternate ``file_path`` to its :meth:`write` method. cSsg|]}tt|qSrM)rstr).0trMrMrN 4z!IndexFile.new..css|] }|j|jfVqdSrnrorrrrMrMrN ;sz IndexFile.new..css|]}t|VqdSrn)r& from_baserrMrMrNr<s)rodbdictziprR)clsrPrtree_sha_bytes base_entriesinstrRrMrMrNnew#s   z IndexFile.newtreeishkwargsc Ost|dks t|dkrtdt|g}t|dkr&|d|dt|jG}|d|||tt|jd"|jj |i||||}|j |Wd Wd S1sewYWd d S1suwYd S) aMerge the given treeish revisions into a new index which is returned. The original index will remain unaltered. :param repo: The repository treeish are located in. :param treeish: One, two or three :class:`~git.objects.tree.Tree` objects, :class:`~git.objects.commit.Commit`\s or 40 byte hexshas. The result changes according to the amount of trees: 1. If 1 Tree is given, it will just be read into a new index. 2. If 2 Trees are given, they will be merged into a new index using a two way merge algorithm. Tree 1 is the 'current' tree, tree 2 is the 'other' one. It behaves like a fast-forward. 3. If 3 Trees are given, a 3-way merge will be performed with the first tree being the common ancestor of tree 2 and tree 3. Tree 2 is the 'current' tree, tree 3 is the 'other' one. :param kwargs: Additional arguments passed to :manpage:`git-read-tree(1)`. :return: New :class:`IndexFile` instance. It will point to a temporary index location which does not exist anymore. If you intend to write such a merged Index, supply an alternate ``file_path`` to its :meth:`write` method. :note: In the three-way merge case, ``--aggressive`` will be specified to automatically resolve more cases in a commonly correct manner. Specify ``trivial=True`` as a keyword argument to override that. As the underlying :manpage:`git-read-tree(1)` command takes into account the current index, it will be temporarily moved out of the way to prevent any unexpected interference. rz.Please specify between 1 and 3 treeish, got %irz--resetrz--index-output=%srgN) len ValueErrorrrOrhextendr'rrrrR)rrPrrarg_list tmp_indexrgrMrMrN from_treeCs$'      "zIndexFile.from_treerZpathsc csPdtdtfdd}t|jj}|tj}|D]}t|}t|s(t ||}zt |}Wn t y8Ynwt |j rF||dVqtj|svd|vsXd|vsXd|vrvt|}||vrv|t|D] } t| |dVqiqztj||d D]\} } } | D] } t | |d| Vqq~Wqt y||dVYqwd S) a=Expand the directories in list of paths to the corresponding paths accordingly. :note: git will add items multiple times even if a glob overlapped with manually specified paths or if paths where specified multiple times - we respect that and do not prune. rrr?cSs|rnrMrqrMrMrN raise_excsz/IndexFile._iter_expand_paths..raise_exc?*[)onerrorN) Exceptionr4rrPworking_tree_dirrFsepospisabsjoinlstatrarst_modereplacerjexistsglob_iter_expand_pathswalk)rZrrrrsrjabs_pathstresolved_pathsfroot_dirsfiles rela_filerMrMrNrs@      $  zIndexFile._iter_expand_pathsTprocr;filepathitemfmakeexc. fprogressread_from_stdoutc Cs||d|d}|jdur0z |jd|tWnty*}z||d}~ww|j|r>|jdur>|j}||d||S)aWrite path to ``proc.stdin`` and make sure it processes the item, including progress. :return: stdout string :param read_from_stdout: If ``True``, ``proc.stdout`` will be read after the item was sent to stdin. In that case, it will return ``None``. :note: There is a bug in :manpage:`git-update-index(1)` that prevents it from sending reports just in time. This is why we have a version that tries to read stdout and one which doesn't. In fact, the stdout is not important as the piped-in files are processed anyway and just in time. :note: Newlines are essential here, git's behaviour is somewhat inconsistent on this depending on the version, hence we try our best to deal with newlines carefully. Usually the last newline will not be sent, instead we will close stdin to break the pipe. FNz%s T) stdinr|encoder IOErrorflushstdoutreadlinestrip) rZrrrrrrrvalrrrMrMrN_write_path_to_stdins    zIndexFile._write_path_to_stdincCsdS)NTrMrrMrMrNrszIndexFile. predicateccsB|jD]}||j}|j|_|j|f}||r|VqdS)a :return: Iterator yielding tuples of :class:`~git.objects.blob.Blob` objects and stages, tuple(stage, Blob). :param predicate: Function(t) returning ``True`` if tuple(stage, Blob) should be yielded by the iterator. A default filter, the `~git.index.typ.BlobFilter`, allows you to yield blobs only if they match a given list of paths. N)rRrwto_blobrPsizerp)rZrentrybloboutputrMrMrN iter_blobss  zIndexFile.iter_blobscCsRdd}i}||D]\}}||jg||fq |D]}|q |S)a :return: Dict(path : list(tuple(stage, Blob, ...))), being a dictionary associating a path in the index with a list containing sorted stage/blob pairs. :note: Blobs that have been removed in one side simply do not exist in the given stage. That is, a file removed on the 'other' branch whose entries are at stage 3 will not have a stage 3 entry. cSs |ddkS)NrrMrrMrMrNrsrtz*IndexFile.unmerged_blobs..)r setdefaultrjrrwsort)rZis_unmerged_blobpath_maprprlinerMrMrNunmerged_blobs s   zIndexFile.unmerged_blobsrcGst|Srn)r)rrrMrMrNrszIndexFile.entry_keyrc Csr|D]4}|jdf}||jvrtdt|jdD]}z |j|j|f=Wqty-Yqwt||j|<q|S)amResolve the blobs given in blob iterator. This will effectively remove the index entries of the respective path at all non-null stages and add the given blob as new stage null blob. For each path there may only be one blob, otherwise a :exc:`ValueError` will be raised claiming the path is already at stage 0. :raise ValueError: If one of the blobs already existed at stage 0. :return: self :note: You will have to write the index manually once you are done, i.e. ``index.resolve_blobs(blobs).write()``. rz!Path %r already exists at stage 0)rrUr)rjrRrrKeyErrorr& from_blob)rZrrstage_null_keyrprMrMrN resolve_blobs#s   zIndexFile.resolve_blobscCs ||S)aReread the contents of our index file, discarding all cached information we might have. :note: This is a possibly dangerous operations as it will discard your changes to :attr:`index.entries `. :return: self )rlrirMrMrNupdateJs zIndexFile.updatecCsVt}|}t||tdt|\}}|||jjt |j|dd}||_ |S)aOWrite this index to a corresponding :class:`~git.objects.tree.Tree` object into the repository's object database and return it. :return: :class:`~git.objects.tree.Tree` object representing this index. :note: The tree will be written even if one or more objects the tree refers to does not yet exist in the object database. This could happen if you added entries to the index directly. :raise ValueError: If there are no entries in the cache. :raise git.exc.UnmergedEntriesError: rrrj) rrxr$slicer stream_copysha_iterrPrr_cache)rZmdbrRbinsha tree_items root_treerMrMrN write_treeYszIndexFile.write_treerzgit_diff.DiffablecCs,z |||W|StyY|Swrn)poprg IndexError)rZrrMrMrN_process_diff_argsys zIndexFile._process_diff_argsrjcCs`t|s|S|jjrtdtt|t|jjs't d||jjft j ||jjS)z :return: Version of path relative to our git directory or raise :exc:`ValueError` if it is not within our git directory. :raise ValueError: zrequire non-bare repositoryz/Absolute path %r is not in git repository at %r) rrrPbarer normpathr startswithrrrFrjrelpath)rZrjrMrMrN_to_relative_paths zIndexFile._to_relative_pathitemsrcCsg}g}t|ttjfr|g}|D]3}t|ttjfr$|||qt|ttfr4|t |qt|tr?||qt d|||fS)z?Split the items into two lists of path strings and BaseEntries.zInvalid Type: %r) isinstancerrFr:rrrrr%r TypeError)rZrrrRrrMrMrN_preprocess_add_itemss   zIndexFile._preprocess_add_itemscst}t|jrfdd}nfdd}|!}|d|jjttj |j |}|dWdn1s>wYt t |j|j dtfS)zStore file at filepath in the database and return the base index entry. :note: This needs the :func:`~git.index.util.git_working_dir` decorator active! This must be ensured in the calling code. csttttdS)N)encoding)rr rFreadlinkr rMrrMrNrssz'IndexFile._store_path..cs tdSNrb)r_rMrrMrNrss FTNr)rFrrrrPrstorerrtypest_sizer%r"rr)rZrrr open_streamr]istreamrMrrN _store_paths    zIndexFile._store_path path_rewriterrRc Csg}|rK|D]?}t|r|}|tt|jjdd}n|}|jjr,t|jj|}t|jtjt t |j t |} |t| q|dd=t|dksSJ||D] } ||| |qX|S)Nrr)rrrrrPrrr NULL_BIN_SHAr"rFstatrrrr%rrr) rZrrrrR entries_addedrjabspathgitrelative_pathrrrMrMrN_entries_for_pathss*   zIndexFile._entries_for_pathscGdSrnrMrrMrMrNrsrforcer|write_extension_datacs,||\}g}|r||||r{ddD} | r%tdddtDr?tdfd d } | ||rYtD]\} } t| j| j| j || f| <qEtD]\} } | v}|su| j d | | j d | q]||D] } t | |j | j d f<q}|r|j| d|S)aAdd files from the working tree, specific blobs, or :class:`~git.index.typ.BaseIndexEntry`\s to the index. :param items: Multiple types of items are supported, types can be mixed within one call. Different types imply a different handling. File paths may generally be relative or absolute. - path string Strings denote a relative or absolute path into the repository pointing to an existing file, e.g., ``CHANGES``, `lib/myfile.ext``, ``/home/gitrepo/lib/myfile.ext``. Absolute paths must start with working tree directory of this index's repository to be considered valid. For example, if it was initialized with a non-normalized path, like ``/root/repo/../repo``, absolute paths to be added must start with ``/root/repo/../repo``. Paths provided like this must exist. When added, they will be written into the object database. PathStrings may contain globs, such as ``lib/__init__*``. Or they can be directories like ``lib``, which will add all the files within the directory and subdirectories. This equals a straight :manpage:`git-add(1)`. They are added at stage 0. - :class:~`git.objects.blob.Blob` or :class:`~git.objects.submodule.base.Submodule` object Blobs are added as they are assuming a valid mode is set. The file they refer to may or may not exist in the file system, but must be a path relative to our repository. If their sha is null (40*0), their path must exist in the file system relative to the git repository as an object will be created from the data at the path. The handling now very much equals the way string paths are processed, except that the mode you have set will be kept. This allows you to create symlinks by settings the mode respectively and writing the target of the symlink directly into the file. This equals a default Linux symlink which is not dereferenced automatically, except that it can be created on filesystems not supporting it as well. Please note that globs or directories are not allowed in :class:`~git.objects.blob.Blob` objects. They are added at stage 0. - :class:`~git.index.typ.BaseIndexEntry` or type Handling equals the one of :class:~`git.objects.blob.Blob` objects, but the stage may be explicitly set. Please note that Index Entries require binary sha's. :param force: **CURRENTLY INEFFECTIVE** If ``True``, otherwise ignored or excluded files will be added anyway. As opposed to the :manpage:`git-add(1)` command, we enable this flag by default as the API user usually wants the item to be added even though they might be excluded. :param fprogress: Function with signature ``f(path, done=False, item=item)`` called for each path to be added, one time once it is about to be added where ``done=False`` and once after it was added where ``done=True``. ``item`` is set to the actual item we handle, either a path or a :class:`~git.index.typ.BaseIndexEntry`. Please note that the processed path is not guaranteed to be present in the index already as the index is currently being processed. :param path_rewriter: Function, with signature ``(string) func(BaseIndexEntry)``, returning a path for each passed entry which is the path to be actually recorded for the object created from :attr:`entry.path `. This allows you to write an index which is not identical to the layout of the actual files on your hard-disk. If not ``None`` and `items` contain plain paths, these paths will be converted to Entries beforehand and passed to the path_rewriter. Please note that ``entry.path`` is relative to the git repository. :param write: If ``True``, the index will be written once it was altered. Otherwise the changes only exist in memory and are not available to git commands. :param write_extension_data: If ``True``, extension data will be written back to the index. This can lead to issues in case it is containing the 'TREE' extension, which will cause the :manpage:`git-commit(1)` command to write an old tree, instead of a new one representing the now changed index. This doesn't matter if you use :meth:`IndexFile.commit`, which ignores the 'TREE' extension altogether. You should set it to ``True`` if you intend to use :meth:`IndexFile.commit` exclusively while maintaining support for third-party extensions. Besides that, you can usually safely ignore the built-in extensions when using GitPython on repositories that are not handled manually at all. All current built-in extensions are listed here: https://git-scm.com/docs/index-format :return: List of :class:`~git.index.typ.BaseIndexEntry`\s representing the entries just actually added. :raise OSError: If a supplied path did not exist. Please note that :class:`~git.index.typ.BaseIndexEntry` objects that do not have a null sha will be added even if their paths do not exist. cSsg|] }|jdkr|qS)r)moderrMrMrNryz!IndexFile.add..zXAt least one Entry has a null-mode - please use index.remove to remove files for claritycSs g|] \}}|jtjkr|qSrM)rrr)rirrrMrMrNrs rZrr?Ncs@D]}|}||j}t|j|j|j|jf|<qdSrn)rrjr%rrrp)rZei null_entry new_entryrRrnull_entries_indicesrMrNhandle_null_entriess z*IndexFile.add..handle_null_entriesFTr)ry)rZrr?N)rrr r enumerater*r%rrrprjr&rrRr|)rZrrrrr|rrrnull_mode_entriesrrrrr progress_sentrMrrNadds>  z IndexFile.addcCszg}t|ttjfr |g}|D]+}t|tttffr$|||j qt|ttjfr5|||qt d||S)z}Returns a list of repo-relative paths from the given items which may be absolute or relative paths, entries or blobs.zInvalid item type: %r) rrrFr:r%rrrrrjr)rZrrrrMrMrN_items_to_rela_pathss zIndexFile._items_to_rela_paths working_treecKsPg}|s |d|d||}|jjj||fi|}dd|DS)a&Remove the given items from the index and optionally from the working tree as well. :param items: Multiple types of items are supported which may be be freely mixed. - path string Remove the given path at all stages. If it is a directory, you must specify the ``r=True`` keyword argument to remove all file entries below it. If absolute paths are given, they will be converted to a path relative to the git repository directory containing the working tree The path string may include globs, such as ``*.c``. - :class:~`git.objects.blob.Blob` object Only the path portion is used in this case. - :class:`~git.index.typ.BaseIndexEntry` or compatible type The only relevant information here is the path. The stage is ignored. :param working_tree: If ``True``, the entry will also be removed from the working tree, physically removing the respective file. This may fail if there are uncommitted changes in it. :param kwargs: Additional keyword arguments to be passed to :manpage:`git-rm(1)`, such as ``r`` to allow recursive removal. :return: List(path_string, ...) list of repository relative paths that have been removed effectively. This is interesting to know in case you have provided a directory or globs. Paths are relative to the repository. z--cachedz--cSsg|]}|ddqS)rM)rprMrMrNr rz$IndexFile.remove..)rrrPrrm splitlines)rZrrrrr removed_pathsrMrMrNrHs/   zIndexFile.remove skip_errorsc Ksg}|r |d||}t|dkrtd|d|dd}d|d<g}|jjj||fi|}t t t|dt|D]&} ||  d} t| dksZJd || || d d d| d fqC|rn|S|d|jjj||fi||S) aRename/move the items, whereas the last item is considered the destination of the move operation. If the destination is a file, the first item (of two) must be a file as well. If the destination is a directory, it may be preceded by one or more directories or files. The working tree will be affected in non-bare repositories. :param items: Multiple types of items are supported, please see the :meth:`remove` method for reference. :param skip_errors: If ``True``, errors such as ones resulting from missing source files will be skipped. :param kwargs: Additional arguments you would like to pass to :manpage:`git-mv(1)`, such as ``dry_run`` or ``force``. :return: List(tuple(source_path_string, destination_path_string), ...) A list of pairs, containing the source file moved as well as its actual destination. Relative to the repository root. :raise ValueError: If only one item was given. :raise git.exc.GitCommandError: If git could not handle your request. z-krUzLPlease provide at least one source and one destination of the move operationdry_runnNTz to zToo many tokens in %sr r) rrrrrrPrmvr#rangeintsplit) rZrr%rrr was_dry_runoutmvlineslntokensrMrMrNmove s&*     zIndexFile.movemessageparent_commitsheadauthor committer author_date commit_date skip_hooksc Csp|std|||td|||}||} tj|j| |||||||d } |s6td|| S)aCommit the current default index file, creating a :class:`~git.objects.commit.Commit` object. For more information on the arguments, see :meth:`Commit.create_from_tree `. :note: If you have manually altered the :attr:`entries` member of this instance, don't forget to :meth:`write` your changes to disk beforehand. :note: Passing ``skip_hooks=True`` is the equivalent of using ``-n`` or ``--no-verify`` on the command line. :return: :class:`~git.objects.commit.Commit` object representing the new commit z pre-commitz commit-msg)r6r7r8r9z post-commit) r!_write_commit_editmsg_commit_editmsg_filepath_read_commit_editmsg_remove_commit_editmsgrrcreate_from_treerP) rZr3r4r5r6r7r8r9r:treerrMrMrNr[s*   zIndexFile.commitcCsDt|d}||tWddS1swYdS)Nwb)r_r<r|rr )rZr3commit_editmsg_filerMrMrNr;s"zIndexFile._write_commit_editmsgcCst|dSrn)rFrHr<rirMrMrNr>sz IndexFile._remove_commit_editmsgcCs@t|d}|tWdS1swYdSr)r_r<readdecoder )rZrBrMrMrNr=s $zIndexFile._read_commit_editmsgcCst|jjdS)NCOMMIT_EDITMSG)rrrP common_dirrirMrMrNr<sz"IndexFile._commit_editmsg_filepath Popen[bytes] ignore_stdoutcCsN|j}|r ||d}|s|jr|j}|jr%|j||S)NrW)rrrGrrCwait)rrrHstdin_IOrrMrMrN_flush_stdin_and_waits   zIndexFile._flush_stdin_and_waitcGr rnrMr rMrMrNrsrc sdg|r dgggdddttddffdd }|durYd d |d <|dd d|jjji||ddddd|jD}|||St |t ra|g}|jdd|d <t j |d<|jjjfi|fdd}g}|D]b} t || } d } z |j| dfWn;tyt | } | ds| d7} |jD]} t | j| r| j}|j||||d d||d} qYnw| s|j| | ||d d|| qz |jddWntytdgw|||S)aCheck out the given paths or all files from the version known to the index into the working tree. :note: Be sure you have written pending changes using the :meth:`write` method in case you have altered the entries dictionary directly. :param paths: If ``None``, all paths in the index will be checked out. Otherwise an iterable of relative or absolute paths or a single path pointing to files or directories in the index is expected. :param force: If ``True``, existing files will be overwritten even if they contain local modifications. If ``False``, these will trigger a :exc:`~git.exc.CheckoutError`. :param fprogress: See :meth:`IndexFile.add` for signature and explanation. The provided progress information will contain ``None`` as path and item if no explicit paths are given. Otherwise progress information will be send prior and after a file has been checked out. :param kwargs: Additional arguments to be passed to :manpage:`git-checkout-index(1)`. :return: Iterable yielding paths to files which have been checked out and are guaranteed to match the version stored in the index. :raise git.exc.CheckoutError: * If at least one file failed to be checked out. This is a summary, hence it will checkout as many files as it can anyway. * If one of files or directories do not exist in the index (as opposed to the original git command, which ignores them). :raise git.exc.GitCommandError: If error lines could not be parsed - this truly is an exceptional state. :note: The checkout is limited to checking out the files in the index. Files which are not in the index anymore and exist in the working tree will not be deleted. This behaviour is fundamentally different to ``head.checkout``, i.e. if you want :manpage:`git-checkout(1)`-like behaviour, use ``head.checkout`` instead of ``index.checkout``. z--indexz--forcerrGiter_checked_out_filesr?Nc s`|j}|sdS|}|t}d}|D]|}|dsu|dsud}d}d} ||r?|dt| |n5||rX|t|| d|n|| ro|dt|  | n|q|D]} || r|dt|  | nqwqrt d d |rt t |t } t d | dS) N)z already existsz is not in the cachez does not exist at stagez is unmergedzgit checkout-index: zgit-checkout-index: z is a directoryzunable to unlink old 'z already exists, no checkout'zgit-checkout-indexzMSome files could not be checked out from the index due to local modifications)stderrrCrDr r#rendswithrrrfindr listsetr) rrL stderr_IO stderr_bytesrQendingsris_a_dir unlink_issuealready_exists_issuerr valid_files) failed_filesfailed_reasons unknown_linesrMrN handle_stderrsP            z)IndexFile.checkout..handle_stderrz--allr as_processFTcss|]}|jVqdSrnrrrMrMrNr(sz%IndexFile.checkout..z--stdinrcstdtdjS)NrOrP)r tuplerQrCrM)rrrMrNrs9rz$IndexFile.checkout..r/)r)rHzWSome files could not be checked out from the index, probably because they didn't exist.)rr1r:rPrcheckout_indexrIrRrwrr subprocessPIPErrrrRrjrrrKr r)rZrrrrr` rval_itermake_excchecked_out_filesrjco_pathpath_is_directoryfolderrr!rM)rr]r^rr_rNcheckoutsx7 "7            zIndexFile.checkoutHEADrr<c Kst||j|}|s|j|_n4|j}|D].}||}zt|d} || |j| <WqtyCz|j| =Wn ty@YnwYqw||rQ|j|dd|rb|jj j |j |d|d|S)a[Reset the index to reflect the tree at the given commit. This will not adjust our HEAD reference by default, as opposed to :meth:`HEAD.reset `. :param commit: Revision, :class:`~git.refs.reference.Reference` or :class:`~git.objects.commit.Commit` specifying the commit we should represent. If you want to specify a tree only, use :meth:`IndexFile.from_tree` and overwrite the default index. :param working_tree: If ``True``, the files in the working tree will reflect the changed index. If ``False``, the working tree will not be touched. Please note that changes to the working copy will be discarded without warning! :param head: If ``True``, the head will be set to the given commit. This is ``False`` by default, but if ``True``, this method behaves like :meth:`HEAD.reset `. :param paths: If given as an iterable of absolute or repository-relative paths, only these will be reset to their state at the given commit-ish. The paths need to exist at the commit, otherwise an exception will be raised. :param kwargs: Additional keyword arguments passed to :manpage:`git-reset(1)`. :note: :meth:`IndexFile.reset`, as opposed to :meth:`HEAD.reset `, will not delete any files in order to maintain a consistent working tree. Instead, it will just check out the files according to their state in the index. If you want :manpage:`git-reset(1)`-like behaviour, use :meth:`HEAD.reset ` instead. :return: self rT)rrz%s: Updating HEAD)logmsg) rrrPrRrrrr|rmr5 set_commitr) rZrrrr5rnew_instnierjrurMrMrNresetes.6       zIndexFile.resetotherrr create_patchc s|j|krtd|||jurtSt|tr#|j |}t|t r?| dd}| |d<|j|j||fi|S|durIt d|tj|||fi|S)aDiff this index against the working copy or a :class:`~git.objects.tree.Tree` or :class:`~git.objects.commit.Commit` object. For documentation of the parameters and return values, see :meth:`Diffable.diff `. :note: Will only work with indices that represent the default git index as they have not been initialized with a stream. zECannot call %r on indices that do not represent the default git indexRFNzr=r<bytesrKr1rmrsrzryr9 DiffConstantsr{Diffrx __classcell__rMrMrerNrns       ($# E B   1 "& '     * M :Q    3  :  _     r)`r__all__ contextlibrriorrFos.pathrjrrrrerBrD gitdb.basergitdb.dbr git.compatr r git.diffrxrzgit.excrr r r git.objectsrrrrrgit.objects.utilrgit.utilrrrrrrrrfunrrrr r!r"r#r$typr%r&rutilr'r(r)r*typingr+r,r-r.r/r0r1r2r3r4r5r6r7r8 git.typesr9r:r;git.refs.referencer<git.repor=rrrcontextmanagerrODiffablerrMrMrMrNsB       ((  @