AϮ d dl mZ d dlZd dlZd dlmZ d dlZd dlmZ d dl Z d dl
Z
d dl m Z m
Z
d dlmZmZmZmZ d dlmZmZmZmZmZ d dlmZ d d lm Z m Z m Z m Z m Z m!Z!m"Z" d d
l#m$Z$ d d l%m&Z& d dl'm(Z) d dl*m+Z, d d
l-m.Z.m/Z/m0Z0m1Z1m2Z2m3Z3m4Z4m5Z5 d dl6m7Z7m8Z8m9Z9 d dl:m;Z;mZ> d dl?m@Z@mAZAmBZBmCZCmDZDmEZEmFZFmGZGmHZHmIZImJZJmKZKmLZLmMZM d dlNmOZOmPZP eJrd dl mQZQ d dlRmSZS d dlTmUZU d dlmVZV eMeeeWeXf ZYdZZ G d de e)j[ e Z\dS ) ) ExitStackN)BytesIO)S_ISLNK) force_bytesdefenc)GitCommandError
CheckoutErrorGitErrorInvalidGitRepositoryError)Blob SubmoduleTreeObjectCommit) Serializable) LazyMixinLockedFDjoin_path_nativefile_contents_roto_native_path_linux unbare_repo
to_bin_sha)IStream)MemoryDB ) entry_key write_cache
read_cacheaggressive_tree_mergewrite_tree_from_cachestat_mode_to_index_mode S_IFGITLINKrun_commit_hook)BaseIndexEntry
IndexEntry StageType)TemporaryFileSwappost_clear_cache
default_indexgit_working_dir)AnyBinaryIOCallableDictIOIterableIteratorListNoReturnSequence
TYPE_CHECKINGTupleTypeUnion)
Commit_ishPathLike)Popen)Repo) Reference)Actor) IndexFiler r& c x e Zd ZdZdZdZeZdhdddeedf ddfd Z d
e
ddf fd Z defd Z e
defd
ZdidZdedd fdZdee fdZdjdededd fdZ dkdedef deddfdZeedhdededef dd fd Ze dddee
e f dd fd Z e ddded e dd fd Z e!d d d e"e de#e fd Z$ dld"d#d$ed%ed&e%d'e&f d(e%eeegdf d)edede
f fd*Z'd+ fd,e%e(e)e*f gef de#e(e)e*f fd-Z+de,eee(e)e*f f fd.Z-e d/ee.ee)f de(ee)f fd0 Z/d1e#e* dd fd2Z0dmd3Z1de fd4Z2d5eee
d6e3d7 f deee
d6e3d7 f fd8Z4d9edefd:Z5d;e"eee*e.dZ7e!e8d ee
d?e%d(e%d@ee. dee. f
dA Z9d!dB dd!dfd;e"eee*e.d dndLe
dMee?df dNedOedP dQedP dRee@j@ e
df dSee@j@ e
df dTedeAfdUZBdLe
ddfdVZCdidWZDde
fdXZEde
fdYZFdjd"dZd[edeGfd\ZHeddd] fd edeIe f dCed(e%d e dede#e e"e f f
d^ ZJe dod`eeAdae
f dHed edeIe f dNed e dd f db ZKeLjM jN ddfdcee3d7 dddee
df d eeee e(ed'f df dfed e deLjO f
fdg
ZP xZQS )pr? ad
Implements an Index that can be manipulated using a native implementation in
order to save git command function calls wherever possible.
It provides custom merging facilities allowing to merge without actually changing
your index or your working tree. This way you can perform 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 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 index.write() once you are done manipulating the index directly
before operating on it using the git command)repoversionentries_extension_data
_file_path NrA r< file_pathreturnc p || _ | j | _ d| _ |p| | _ dS )a Initialize 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)rA _VERSIONrB rD _index_pathrE )selfrA rG s `/builddir/build/BUILD/cloudlinux-venv-1.0.10/venv/lib/python3.11/site-packages/git/index/base.py__init__zIndexFile.__init__| s8 } " $-$C1A1A1C1CrJ attrc |dk r t j | j t j }n# t $ r i | _ Y d S w xY w t
|dd }t j | n# t j | w xY w| | d S t t | | d S )NrC T)stream
allow_mmap) osopenrE O_RDONLYOSErrorrC r close _deserializesuperr? _set_cache_)rM rP fdrR __class__s rN r[ zIndexFile._set_cache_ s 9
WT_bk::
MO tt
)"TdKKK f % % % % % )T " " . .t 4 4 4 4 4s $. AAA. .Bc l | j j rt | j j d S t d )Nindexz)No git directory given to join index path)rA git_dirr r rM s rN rL zIndexFile._index_path s4 9 O#DI$5w?? ?!"MNN NrJ c | j S )z3:return: Path to the index file we are representing)rE ra s rN pathzIndexFile.path s rJ c . | ` dS # t $ r Y dS w xY w)z5Safely clear the entries cache so it can be recreatedN)rC AttributeErrorra s rN _delete_entries_cachez IndexFile._delete_entries_cache s2 DD s
rR c L t | \ | _ | _ | _ }| S )zEInitialize this instance with index values read from the given stream)r rB rC rD )rM rR _conten_shas rN rY zIndexFile._deserialize s% HRSYHZHZE dlD$8+ rJ c T t | j d S )zK:return: list of entries, in a sorted fashion, first by path, then by stagec | j | j fS Nrc stagees rN z+IndexFile._entries_sorted.. s AFAG;L rJ )key)sortedrC valuesra s rN _entries_sortedzIndexFile._entries_sorted s' dl))++1L1LMMMMrJ Fignore_extension_datac f | }| j }|rd }t ||| | S rk )rt rD r )rM rR ru rC extension_datas rN
_serializezIndexFile._serialize s? &&(( - " !NGV^444 rJ c H | j t |p| j }| dd }d} | || d}|s| n # |s| w w xY w| | || _ dS dS )a Write 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 git-write-tree afterwards to create a tree
representing your written changes.
If this data is present in the written index, git-write-tree
will instead write the stored/cached tree.
Alternatively, use IndexFile.write_tree() to handle this case
automatically
:return: self # does it? or returns None?T)writerR FN)rC r rE rU rx rollbackcommit)rM rG ru lfdrR oks rN rz zIndexFile.write s 8
y3DO44T22
OOF$9 : : :B
'DOOO ! s A' 'B rhsbasec g d}|| | | | | j j | | S )a Merge the given rhs treeish into the current index, possibly taking
a common base treeish into account.
As opposed to the :func:`IndexFile.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 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
index.from_tree call.) --aggressivez-iz-m)appendrA git read_tree)rM r r argss rN
merge_treezIndexFile.merge_tree sW : +G*F*F KK C
%%% rJ tree_shac d |D }t |j | } | | }t t d |D d |D }||_ |S )a Merge 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 IndexFile instance. Its path will be undefined.
If you intend to write such a merged Index, supply an alternate file_path
to its 'write' method.c F g | ] }t t | S )r str).0ts rN
z!IndexFile.new..$ s& &L&L&Laz#a&&'9'9&L&L&LrJ c 3 2 K | ]}|j |j fV d S rk rl r ro s rN z IndexFile.new..+ s+ 99q!&!'"999999rJ c 3 > K | ]}t j | V d S rk )r% from_baser s rN r z IndexFile.new.., s- ??Q%a((??????rJ )r odbdictziprC )clsrA r tree_sha_bytes base_entriesinstrC s rN newz
IndexFile.new s 'M&L8&L&L&L,TX~FF s4yy:> 99L999??,???
;
;
rJ treeishkwargsc t | dk st | dk r t dt | z g }t | dk r*| d | d t 5 }| t j |j }| d|j z | | | t t |j d |j j
|i | | ||j }|j |cd
d
d
S # 1 swxY w Y d
S ) aS Merge 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 Tree Objects, Commits or 40 byte hexshas. The result
changes according to the amount of trees.
If 1 Tree is given, it will just be read into a new index
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.
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 git-read-tree
:return:
New 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 '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 kwarg
to override that.
As the underlying git-read-tree command takes into account the current index,
it will be temporarily moved out of the way to assure there are no unsuspected
interferences.r z.Please specify between 1 and 3 treeish, got %ir z--resetr )dirz--index-output=%sr_ N)len
ValueErrorr r
enter_contexttempfileNamedTemporaryFiler` nameextendr' r r r rC )r rA r r arg_liststack tmp_indexr_ s rN from_treezIndexFile.from_tree3 s F w<<1 G q 0 0 MPST[P\P\ \]] ].0 w<.raise_exc~ s GrJ ?*[)onerrorN) Exceptionr3 r rA working_tree_dirrT sepospisabsjoinlstatr st_modereplacerW rc existsglob_iter_expand_pathswalk)rM r r rrsrc abs_pathstresolved_pathsfroot_dirsfiles rela_files rN r z IndexFile._iter_expand_pathsv sK x
* + +
Z ( / ( /D4yyH9X&&
- 8At,,
Xh''
2:&& "**2r22222
7>>(++
C8OOWZ^fWfWf!%8!4!4 >11 ! 4 4TYx5H5H I I 5 5 !!ffnnR 4 44444
/*,'(I*N*N*N H H&D%%* H H !ht||B';';Y G GGGGGHH
/
/
/ &&r2.......
/M( / ( /s% ;B==
C
C
"A
F11"GGTprocr; filepathitemfmakeexc. fprogressread_from_stdoutc ||d| d}|j m |j d|z t n # t $ r} | |d}~ww xY w|j |r2|j +|j } ||d| |S )ai Write 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 git-update-index 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, gits 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) stdinrz encoder IOErrorflushstdoutreadlinestrip) rM r r r r r r rvalro s rN _write_path_to_stdinz IndexFile._write_path_to_stdin s . (E4(((!% : !
(
&8"3!;!;F!C!CDDDD
(
(
( hjja'
(
J 2 7;''))//11D (D$''' s 5A
A( A##A(c dS )NTr r s rN rp zIndexFile. s d rJ predicatec # K | j D ]@}| | j }|j |_ |j |f} || r|V AdS )aR
:return: Iterator yielding tuples of 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 BlobFilter, allows you to yield blobs
only if they match a given list of paths.N)rC rs to_blobrA sizerm )rM r entrybloboutputs rN
iter_blobszIndexFile.iter_blobs ss \((** E==++D
DIk4(Fy
rJ c d }i }| | D ]5\ }}| |j g ||f 6| D ]}| |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. I.e. a file removed on the 'other' branch whose entries
are at stage 3 will not have a stage 3 entry.
c | d dk S )Nr r r s rN rp z*IndexFile.unmerged_blobs.. s QqTQY rJ )r
setdefaultrc r rs sort)rM is_unmerged_blobpath_maprm r lines rN unmerged_blobszIndexFile.unmerged_blobs s /.AC ??+;<< E EKE4 2 . . 5 5udm D D D D OO%% D IIKKKKrJ r c t | S rk )r )r r s rN r zIndexFile.entry_key s
% rJ r c |D ]y}|j df}|| j v r$t dt |j z dD ]"} | j |j |f= # t $ r Y w xY wt j | | j |< z| S )aF Resolve 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 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()
r z!Path %r already exists at stage 0)r rF r )rc rC r r KeyErrorr% from_blob)rM r r stage_null_keyrm s rN
resolve_blobszIndexFile.resolve_blobs s F FD "i^N -- !Ds49~~!UVVV #
di%788 D
,6+?+E+EDL ( ( s A
A A c . | | S )zReread the contents of our index file, discarding all cached information
we might have.
:note: This is a possibly dangerious operations as it will discard your changes
to index.entries
:return: self)rf ra s rN updatezIndexFile.update' s
""$$$ rJ c
H t }| }t ||t dt | \ }}| | | j j t | j |d }||_
|S )a Writes this index to a corresponding Tree object into the repository's
object database and return it.
:return: 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 UnmergedEntriesError:r r rc ) r rt r slicer stream_copysha_iterrA r r _cache)rM mdbrC binsha
tree_items root_trees rN
write_treezIndexFile.write_tree2 s jj&&(( 27Cq#g,,AWAW X X
666 F444 % rJ r zgit_diff.Diffablezgit_diff.Diffable.Indexc z | | | n# t $ r Y nw xY w|S rk )popr_
IndexError)rM r s rN _process_diff_argsz IndexFile._process_diff_argsK sO HHTZZ%% & & & & D s (+
88rc c h t j | s|S | j j rt d t | t | j j s t d|d| j j t j
|| j j S )z
:return: Version of path relative to our git directory or raise ValueError
if it is not within our git directoryzrequire non-bare repositoryzAbsolute path z is not in git repository at ) r r rA barer r
startswithr r rT rc relpath)rM rc s rN _to_relative_pathzIndexFile._to_relative_pathV s y K 9> K+,IJJ J4yy##C (B$C$CDD u *RVRVRVX\XaXrXr stt twtTY%?@@@rJ itemsr
c g }g }t |t t j f r|g}|D ]}t |t t j f r)| | | Lt |t t f r(| t j | t |t r| | t d|z ||fS )z?Split the items into two lists of path strings and BaseEntries.zInvalid Type: %r)
isinstancer rT r: r r
r r
r$ r TypeError)rM r r rC r s rN _preprocess_add_itemsz IndexFile._preprocess_add_itemsb s ec2; / 0 0 GE ; ;D$bk 233
; T 3 3D 9 9::::D4"344
;~ 7 = =>>>>D.11
;t$$$$ 2T 9:::g~ rJ c t j }t |j rfd}nfd} | 5 } |d | j j t t j |j
| } |d ddd n # 1 swxY w Y t t |j |j
dt f S )zStore file at filepath in the database and return the base index entry
Needs the git_working_dir decorator active ! This must be assured in the calling codec n t t t j t S )N)encoding)r r rT readlinkr r s rN rp z'IndexFile._store_path..~ s( '+bkZbNcNcntBuBuBu:v:v rJ c $ t d S Nrb)rU r s rN rp z'IndexFile._store_path.. s $x"6"6 rJ FTNr )rT r r r rA r storer r typest_sizer$ r! r r )rM r r r open_streamrR istreams ` rN _store_pathzIndexFile._store_pathx s* Xh
2: 72v2v2v2vKK6666K
[]] 0f Ihx 0 0 0im))'$)RZ*P*PQQG Ihh / / / 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 '
33$X..
s AB##B'*B'
path_rewriterrC c
g }|r|D ]}t j | r4|}|t t | j j dz d }n-|}| j j r t j | j j | }t | j t j t t j | j t | } | t j | |d d = t | dk sJ | | D ]+}
| | |
| ,|S )Nr r )r r r r rA r r r NULL_BIN_SHAr! rT statr r r r$ r r r ) rM r r r rC
entries_addedrc abspathgitrelative_pathr r s rN _entries_for_pathsz IndexFile._entries_for_paths sf /1
?
?9T?? Y "G'+CDI4N0O0O,P,PST,T,V,V'W$$'+$y1 Y"%(49+EGW"X"X I%+BGG,<,<,DEE()9:: ~ 7 = =>>>>aaa =!!Q&&&& //66 H HH !1!1(I!F!F G G G G rJ c d S rk r r s rN rp zIndexFile. D rJ forcerz write_extension_datac | | \ }g }|r+| | || rd D } | rt d d t D r t
d
fd }
|
| |rCt D ]3\ } } t
| j | j | j || f | < 4t D ]/\ } }
| v }|s$ |
j
d |
|
j
d
|
0| |D ]%}
t j |
| j
|
j
d f< &|r| | |S )a5 Add files from the working tree, specific blobs or BaseIndexEntries
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, i.e. 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 can be directories
like 'lib', the latter ones will add all the files within the directory and
subdirectories.
This equals a straight git-add.
They are added at stage 0
- Blob or 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 Blob objects.
They are added at stage 0
- BaseIndexEntry or type
Handling equals the one of 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 git-add 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 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) function returning a path
for each passed entry which is the path to be actually recorded for the
object created from 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 `git commit` command to write an
old tree, instead of a new one representing the now changed index.
This doesn't matter if you use `IndexFile.commit()`, which ignores the `TREE` extension altogether.
You should set it to True if you intend to use `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:
http://opensource.apple.com/source/Git/Git-26/src/git-htmldocs/technical/index-format.txt
:return:
List(BaseIndexEntries) representing the entries just actually added.
:raise OSError:
if a supplied Path did not exist. Please note that BaseIndexEntry
Objects that do not have a null sha will be added even if their paths
do not exist.
c ( g | ]}|j d k
|S )r )moder s rN r z!IndexFile.add../ s C C Cqqv{{{{{rJ zXAt least one Entry has a null-mode - please use index.remove to remove files for clarityc B g | ] \ }}|j t j k | S r )r r r )r iro s rN r z!IndexFile.add..8 s, #h#h#h$!QTZTgHgHgAHgHgHgrJ rM r? rH Nc D ]O}| }| |j }t |j |j |j |j f |< Pd S rk )r rc r$ r- r rm )rM ei
null_entry new_entryrC r null_entries_indicess rN handle_null_entriesz*IndexFile.add..handle_null_entries; sn 2 %,R[
$($4$4Z_i$P$P '5 * ) 0 * 0 * ' ' rJ FTr )ru )rM r? rH N)r r r% r enumerater* r$ r- r rm rc r% r rC rz )rM r r) r r rz r* r r" null_mode_entriesr5 r/ ro r
progress_sentrC r4 s ` @@rN addz
IndexFile.add s# \ 33E::w.0
d !8!8
yZa!b!b c c c 3 * C CG C C C
n $i#h)G2D2D#h#h#h #
*
!
" $#D)))
_ %g . . _ _DAq!/17MMZ[L\L\0]!^!^GAJJ
&g . .
7
75 !%9 9
$ 7 Iej%777 Iej$666
) ) )
# H HE,6,@,G,GDL%*a ) ) G JJ1E-EJ F F F rJ c g }t |t t j f r|g}|D ]}t |t t
t ff r.| | |j St |t r)| | | t d|z |S )z|Returns a list of repo-relative paths from the given items which
may be absolute or relative paths, entries or blobszInvalid item type: %r) r
r rT r: r$ r r
r r
rc r )rM r r r s rN _items_to_rela_pathsz IndexFile._items_to_rela_pathso s ec2; / 0 0 GE @ @D$ $ 1B CDD
@ T 3 3DI > >????D#&&
@ T 3 3D 9 9:::: 7$ >??? rJ working_treec g }|s| d | d | | } | j j j ||fi | }d |D S )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.
- Blob Object
Only the path portion is used in this case.
- BaseIndexEntry or compatible type
The only relevant information here Yis 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 git-rm, such
as 'r' to allow recursive removal of
: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--c " g | ] }|d d
S ) r )r ps rN r z$IndexFile.remove.. s ///A!B$///rJ )r r; rA r rm
splitlines)rM r r< r r r
removed_pathss rN removezIndexFile.remove s V $ KK
# # # D ))%00(
(u????JJLL
0/ ////rJ skip_errorsc g }|r| d | | }t | dk rt d | d| dd }d|d< g } | j j j ||fi | }t t t | dz t | D ]n} || d }
t |
dk sJ d || z | |
d
d d |
d f o|r|S | d | j j j ||fi | |S )
aM Rename/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.
:parma items:
Multiple types of items are supported, please see the '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 git-mv, 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 GitCommandError: If git could not handle your requestz-krF zLPlease provide at least one source and one destination of the move operationdry_runnNTz to zToo many tokens in %sr r ) r r; r r r rA r mvrC rangeintsplit) rM r rF r r r was_dry_runoutmvlineslntokenss rN movezIndexFile.move s > KK ))%00 u::>> kll l jjFJJsD,A,ABB y "$)-"499&99DDFF CLL1 ,--s7||<< 3 3B R[&&v..Fv;;!###% committer author_date commit_date
skip_hooksc z |spt d| | | t d| | | }| | } t
j | j | ||||||| }
|st d| |
S )a Commit the current default index file, creating a commit object.
For more information on the arguments, see Commit.create_from_tree().
:note: If you have manually altered the .entries member of this instance,
don't forget to write() your changes to disk beforehand.
Passing skip_hooks=True is the equivalent of using `-n`
or `--no-verify` on the command line.
:return: Commit object representing the new commitz
pre-commitz
commit-msg)rX rY rZ r[ z post-commit) r# _write_commit_editmsg_commit_editmsg_filepath_read_commit_editmsg_remove_commit_editmsgr r create_from_treerA ) rM rU rV rW rX rY rZ r[ r\ treer s rN r| zIndexFile.commit s & * L$ / / / & &w / / / L$0M0M0O0O P P P//11G ' ' ) ) ) & I ##
1 M4 0 0 0 rJ c t | d 5 }| | t d d d d S # 1 swxY w Y d S )Nwb)rU r_ rz r r )rM rU commit_editmsg_files rN r^ z IndexFile._write_commit_editmsg+ s
$//114
8
8 > > > > > > > > > > > > > > > > > >s .A A"%A"c R t j | d S rk )rT rE r_ ra s rN ra z IndexFile._remove_commit_editmsg/ s$
$//1122222rJ c t | d 5 }| t cd d d S # 1 swxY w Y d S r )rU r_ readdecoder )rM rf s rN r` z IndexFile._read_commit_editmsg2 s
$//114
8
8 =???rJ Popen[bytes]
ignore_stdoutc |j }|r(| | d}|s |j r|j }|j r-|j | |S )NrJ )r r rX r ri wait)r r ro stdin_IOr s rN _flush_stdin_and_waitz IndexFile._flush_stdin_and_wait9 s : NN NN ( ([%%''F ; K IIKKK
rJ c d S rk r r' s rN rp zIndexFile.M r( rJ c P dg|r d g g g dddt t ddffd }| d d
|d < |dd d | j j j i | |dd
d d | j D } || |S t |t r|g}| j d d
|d < t j |d< | j j j fi |fd}g }|D ] } t | | }
d } | j |
df n# t $ r t |
} | d s| dz
} | j D ]b}
t |
j | r9|
j }| ||||d | | d
} cY nw xY w| s0| |
| ||d | |
! | d
n # t* $ r t- dg w xY w || |S )a Checkout 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 ``write`` method
in case you have altered the enties 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 CheckoutError.
:param fprogress:
see :func:`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 git-checkout-index
:return:
iterable yielding paths to files which have been checked out and are
guaranteed to match the version stored in the index
:raise 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 who ignores them ).
Raise 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 git-checkout like behaviour,
use head.checkout instead of index.checkout.
z--indexz--forcer rn iter_checked_out_filesrH Nc | j }|sd S | }| t }d}| D ]}| d sG| d s1d}d}d} | | rA |d t |
| n| | rS |t | | d
| nk| | rA |d t |
| n | `|D ]Y}
| |
rB |dt |
|
nZrt d d
| r>t t | t z
} t d |
d S ) 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-index zMSome files could not be checked out from the index due to local modifications)stderrri rj r rC r endswithr r rfindr listsetr )r rv stderr_IO stderr_bytesr| endingsr is_a_dir unlink_issuealready_exists_issuero valid_files failed_filesfailed_reasons
unknown_liness rN
handle_stderrz)IndexFile.checkout..handle_stderr s I
0t (~~ / / !((00FG ))++
'=>> tWmGnGn 0H#;L+I(}}X..
3$++D1ACMM>1A,BCCC&--h7777 66 3$++D\1B1BTZZPS__1T,UVVV&--l;;;; ';<< 3$++D1MC8L4M4M3M1M,NOOO&--.BCCCC%,,T222 ! A}}Q'' $++Ds1vvg ,>???&--a000
L%&=sFKKK
"3'=#>#>\ARAR#R S S #c "
rJ z--allr
as_processFTc 3 $ K | ] }|j V d S rk r r s rN r z%IndexFile.checkout.. s$ ??A??????rJ z--stdinr c t t dt z dj S )Nrz r{ )r tupler| ri )r r s rN rp z$IndexFile.checkout.. s0 /Ft/TVY[_[f[k[k[m[m n n rJ r /)r )ro zWSome files could not be checked out from the index, probably because they didn't exist.)r r0 r: rA r checkout_indexrq rC rs r
r
subprocessPIPEr r
r r} rc r r rs r r )rM r r) r r r rval_itermake_excchecked_out_filesrc co_pathpath_is_directoryfolderr rA r r r r r s @@@@@rN checkoutzIndexFile.checkoutH su d { # KK " " "
3 3 QYHZ 3 _c 3 3 3 3 3 3 3 3 n = KK #$F< IdE4 ( ( (/49=/@@@D IIKKK IdD$ ' ' '?? )<)<)>)>???I M$ * * * %%%
LL KK " " "#'F< *F9 /49=/????DnnnnnH02
6
6.t/E/Ed/K/KLL$)! 5L'1 ... 5 5 5 \\F!??3// & #
!% !4!4!6!6 5 5 uz??55f== 5 %
A 5 5dAq(Ihm 5 n n n - 4 4Q 7 7 704 - 5 5 5 ) 6--dGT8Yin-ooo%,,W555
**4t*DDDD"
#m "
M$ 1 2 2 2$ $s (E88B/H*)H*"I: : JHEADr| r= c " t | | j | }|s
|j | _ nl|j }|D ]b}| | } t |d } || | j | < 9# t $ r | j | = n# t $ r Y nw xY wY _w xY w| |r| |d |r<| j j
| j | d|z | S )a Reset the index to reflect the tree at the given commit. This will not
adjust our HEAD reference as opposed to HEAD.reset by default.
:param commit:
Revision, Reference or Commit specifying the commit we should represent.
If you want to specify a tree only, use 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 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 git-reset
.. note:: IndexFile.reset, as opposed to HEAD.reset, will not delete anyfiles
in order to maintain a consistent working tree. Instead, it will just
checkout the files according to their state in the index.
If you want git-reset like behaviour, use *HEAD.reset* instead.
:return: selfr T)r r) z%s: Updating HEAD)logmsg) r r rA rC r
r r rz r rW
set_commitr| )
rM r| r< r rW r new_instnierc rq s
rN resetzIndexFile.reset sI V ::'' 6:: #+DLL"C
--d33 #D!,,C(+CDL%% L - -#
3 MMTM 2 2 2 e IN % %di&6&6v&>&>GZ]cGc % d d d s6 A::
B!B
B!
BB!BB! B!otherr r create_patchc | j | k r$t d| z || j u rt j S t |t r| j
| }t |t r1| dd }| |d< |j | j ||fi |S |t d|z t t | j |||fi |S )aC Diff this index against the working copy or a Tree or Commit object
For a documentation of the parameters and return values, see,
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 indexRFNzV >w ># >+ > > > [>D 4/ 4/Xh5G 4/HU]L^ 4/ 4/ 4/ [4/~ "&& && & &
3=) & XtX 6 <=
& &
tSy & & & &R ESN !5D #9":D"@A % 4( ) $XtE)T/4J/K%K L . !u^Xy%H I !eT\^gTgNh ! ! ! [!! !; ! ! ! !F D 2 5 148Q3RRST
eC,d3L.MMN O
Ah
A8
A
A
A
A eHdNK$O PQ tH~tN 33 4 ,
H
n
, % Cy% % %
n% %
n
% % % _ [% T 0 0>B%*v v hnk IJKv v v
Xc8m 4d :; v
v #v
n v v v v pXxhi.W(X YYZ
h * #40 40hnk IJK40 40 40
c 40 40 40 ] 40l "A Ahnk IJKA A A
eCHo A A A ] AL 37'+*.;?;? ( (( j$ ./( (
m$ ( '
( 8,c478( 8,c478( (
( ( ( (T>S >T > > > >3 3 3 3=c = = = =@# @ @ @ @
Y^
26 0 0 q% q%T8H--.q% q% q%
q%
tXh'();; <
q% q% q% ]q%h 39 "15 H Hfk3./H H T8H--. H
H
H
H H H ]HZ V^UfUlMQ " +Q +QT34fhTQR+Q XtH~uXs]/CTIJ+Q +Q
+Q
+Q +Q +Q +Q +Q +Q +Q +Q +Q +QrJ r? )]
contextlibr r r ior rT r! r r r
git.compatr r git.excr r r
r git.objectsr r
r r r git.objects.utilr git.utilr r r r r r r
gitdb.baser gitdb.dbr git.diffr r os.pathrc r funr r r r r r! r" r# typr$ r% r& utilr' r( r) r* typingr+ r, r- r. r/ r0 r1 r2 r3 r4 r5 r6 r7 r8 git.typesr9 r: r; git.repor< git.refs.referencer= r> r r r __all__r r? r rJ rN r s ! X W W W W W W W W W W W * ) ) ) ) )
V U U U U U U U U U U U " + * * * * * * * ,,,,,, fc5(
)
6SQ SQ SQ SQ SQ 8,l SQ SQ SQ SQ SQrJ