| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
cmd: taskkill now pipes stderror to nul as well
|
|
|
|
| |
persistent commands are killed before trying to remove the directory. Unfortunately, it still claims someone has opened the file. handle.exe does not show anyone, so what is happening here ? Is it just a windows odity ? If nothing helps I could just keep the temp data, but lets do some more testing first
|
| |
|
| |
|
|
|
|
|
|
| |
object
repo.tree: improved to be less restricting
|
|
|
|
| |
unify error handling amongst clients using the process directly. It might be needed to add a flag allowing to easily override that
|
|
|
|
| |
wrong thing by _not_ stripping the final newline at the end of all git commands we use. This is the default now which cannot be changed - perhaps its wrong to remove it, but in way you'd always want the final newline stripped unless you get data directly, but there are better ways to do that ( blob.data, blob.data_stream, blob.stream_data )
|
|
|
|
|
|
|
|
|
|
|
| |
low memory footprint.
Still, the git-cat-file command keeps all data in an interal buffer instead of streaming it directly.
This is a git design issue though, and will be hard to address without some proper git-hacking.
Conflicts:
lib/git/cmd.py
|
|
|
|
|
| |
repo.archive: made it work with new way of custom output streams
added test for repo.archive which was missing for some reason
|
|
|
|
| |
directly.Considering the implementation of the git commnd which temporarily keeps it in a cache, it doesnt make a huge diffence as the data is kept in memory while streaming. Only good thing is that it is in a different process so python will never see it if done properly
|
|
|
|
| |
operations more convenient, like repo.remotes.origin.fetch
|
|
|
|
|
|
| |
the respective modules that use them
fixed repo.daemon_export which did not work anymore due to incorrect touch implementation and wrong property names
|
|
|
|
|
|
| |
stream - previously it would cache everything to memory and try to provide zipping functionality itself
gitcmd: allows the output stream to be set explicitly which is mainly useful for archiving operations
|
|
|
|
| |
obsolete once the interface overhaul is finished. This commit is just intermediate
|
|
|
|
| |
possible input ref - the objects pointed to by refs are now baked on demand - perhaps it should change to always be re-retrieved using a property as it is relatively fast - this way refs can always be cached
|
|
|
|
| |
information retrieval
|
|
|
|
|
|
|
| |
output directly from the output stream
commit: now reads commit information directly from the output stream of the process by implementing its iterator method
repo: removed log method as it was redundant ( equal to the commits method )
|
|
|
|
| |
editor to work with the files properly. Can convert it back for releaes
|
| |
|
|\ |
|
| | |
|
| | |
|
|/
|
|
| |
handles this correctly
|
| |
|
|
|
|
| |
One bug remaining: git on windows is returning status 0 for `git this-does-not-exist`, so no GitCommandError is raised.
|
| |
|
| |
|
|
|
|
| |
http://groups.google.com/group/git-python/browse_thread/thread/b8f3580abf31f9db?hl=en# and passed Git a working_tree again (sort of).
|
| |
|
|
|
|
|
|
|
|
| |
removed the combined output of stderr and stdout.
Also renamed with_status to extended_output.
The method_missing function needs to be modified, as it does a kwargs.pop(xxx, None); which resulted in with_excpetions=None -> False all the time...
Test should follow tomorrow.
|
|
|
|
|
|
|
|
| |
Having execute() use a different directory is an important piece
of API information so I added more documentation about it and
renamed the flag to just "keep_cwd" since that's shorter and simpler.
Signed-off-by: David Aguilar <davvid@gmail.com>
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* commit 'sverre/master':
Added a with_keep_cwd option
Improved the GIT_PYTHON_TRACE=full output format
Added /dist to .gitignore
Conflicts:
lib/git/cmd.py
Signed-off-by: David Aguilar <davvid@gmail.com>
|
| |
| |
| |
| |
| |
| |
| | |
When executing commands, if the with_keep_cwd option is
specified, the current working directory will be set to
os.getcwd() instead of the directory containing the
.git directory.
|
| |
| |
| |
| |
| |
| | |
It now also shows stderr if there was any on it, and only
shows stdout if there was any output. Also added a '->'
between the command and the return value as a visual clue.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In order to avoid the expense of parsing .git/config
just to know whether or not a repository is bare
at __init__ time, we just pass an optional flag to
Git.__init__():
bare_repo with a default value of False.
Repo.init_bare() was updated to pass this flag.
We could have an optional Git.read_bare_status() function
that does the expensive lookup. Then, users can optionally
call it at runtime if they really need to know whether or not
a repository is bare. That seems like a decent tradeoff between
speed, correctness, and common use cases.
Signed-off-by: David Aguilar <davvid@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a fix on top of Govind's latest performance improvement.
self._cwd was always set to self._git_dir which means
a lot of commands that require work trees were not available
to GitPython. Execute now uses self._cwd which is equal to
self._git_dir by default, and self.get_work_tree() if a work tree
exists.
Signed-off-by: David Aguilar <davvid@gmail.com>
|
|/
|
|
|
|
|
|
| |
Calling git to find the git_dir and work_tree is very costly.
This patch uses the same mechanisim to find the git_dir as native
git does without shelling out.
Signed-off-by: Govind Salinas <blix@sophiasuchtig.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
git does not accept commands of the form:
git cmd --xx=False
or
git cmd -xFalse
This patch prevents transform_kwargs from producing
command lines with those values.
This adds some flexibility/syntactic sugar for callers
since they can then assume that kwargs with a False value
are not passed to git commands.
Signed-off-by: David Aguilar <davvid@gmail.com>
|
|
|
|
|
|
|
| |
Keyword args shouldn't use spaces around the equals sign
per PEP 8.
Signed-off-by: David Aguilar <davvid@gmail.com>
|
|
|
|
| |
http://gitorious.org/projects/git-python/repos/apollo13/comments#comment_105 my mistake ;) I'll investigate this further, but I think we are on the safe side now...
|
| |
|
|
|