git-project 0.1.1__tar.gz → 0.1.3__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (52) hide show
  1. {git_project-0.1.1 → git_project-0.1.3}/PKG-INFO +33 -8
  2. {git_project-0.1.1 → git_project-0.1.3}/_version.py +2 -2
  3. {git_project-0.1.1 → git_project-0.1.3}/docs/changelog.rst +57 -1
  4. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/configobj.py +4 -4
  5. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/git.py +463 -68
  6. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/main.py +16 -0
  7. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/project.py +8 -3
  8. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/shell.py +54 -5
  9. {git_project-0.1.1 → git_project-0.1.3}/tests/test_confobj.py +45 -2
  10. {git_project-0.1.1 → git_project-0.1.3}/tests/test_git.py +742 -5
  11. {git_project-0.1.1 → git_project-0.1.3}/tests/test_main.py +38 -0
  12. {git_project-0.1.1 → git_project-0.1.3}/tests/test_project.py +46 -0
  13. {git_project-0.1.1 → git_project-0.1.3}/tests/test_scopedobj.py +1 -1
  14. git_project-0.1.3/tests/test_shell.py +220 -0
  15. git_project-0.1.1/tests/test_shell.py +0 -55
  16. {git_project-0.1.1 → git_project-0.1.3}/.gitignore +0 -0
  17. {git_project-0.1.1 → git_project-0.1.3}/CONTRIBUTORS +0 -0
  18. {git_project-0.1.1 → git_project-0.1.3}/COPYING +0 -0
  19. {git_project-0.1.1 → git_project-0.1.3}/MANIFEST.in +0 -0
  20. {git_project-0.1.1 → git_project-0.1.3}/changelog.d/README.rst +0 -0
  21. {git_project-0.1.1 → git_project-0.1.3}/changelog.py +0 -0
  22. {git_project-0.1.1 → git_project-0.1.3}/docs/Makefile +0 -0
  23. {git_project-0.1.1 → git_project-0.1.3}/docs/api.rst +0 -0
  24. {git_project-0.1.1 → git_project-0.1.3}/docs/authors.rst +0 -0
  25. {git_project-0.1.1 → git_project-0.1.3}/docs/conf.py +0 -0
  26. {git_project-0.1.1 → git_project-0.1.3}/docs/contributing.rst +0 -0
  27. {git_project-0.1.1 → git_project-0.1.3}/docs/index.rst +0 -0
  28. {git_project-0.1.1 → git_project-0.1.3}/docs/intro.rst +0 -0
  29. {git_project-0.1.1 → git_project-0.1.3}/docs/license.rst +0 -0
  30. {git_project-0.1.1 → git_project-0.1.3}/docs/make.bat +0 -0
  31. {git_project-0.1.1 → git_project-0.1.3}/docs/plugins.rst +0 -0
  32. {git_project-0.1.1 → git_project-0.1.3}/pyproject.toml +0 -0
  33. {git_project-0.1.1 → git_project-0.1.3}/requirements.txt +0 -0
  34. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/__init__.py +0 -0
  35. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/commandline.py +0 -0
  36. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/exception.py +0 -0
  37. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/gitproject.py +0 -0
  38. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/parsermanager.py +0 -0
  39. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/plugin.py +0 -0
  40. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/pluginmanager.py +0 -0
  41. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/py.typed +0 -0
  42. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/runnable.py +0 -0
  43. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/scopedobj.py +0 -0
  44. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/substitutable.py +0 -0
  45. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/test_support/__init__.py +0 -0
  46. {git_project-0.1.1 → git_project-0.1.3}/src/git_project/test_support/common.py +0 -0
  47. {git_project-0.1.1 → git_project-0.1.3}/tests/conftest.py +0 -0
  48. {git_project-0.1.1 → git_project-0.1.3}/tests/test_changelog.py +0 -0
  49. {git_project-0.1.1 → git_project-0.1.3}/tests/test_gitproject.py +0 -0
  50. {git_project-0.1.1 → git_project-0.1.3}/tests/test_parsermanager.py +0 -0
  51. {git_project-0.1.1 → git_project-0.1.3}/tests/test_runnable.py +0 -0
  52. {git_project-0.1.1 → git_project-0.1.3}/tests/test_substitutable.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: git-project
3
- Version: 0.1.1
3
+ Version: 0.1.3
4
4
  Summary: The extensible stupid project manager
5
5
  Author-email: "David A. Greene" <dag@obbligato.org>
6
6
  License-Expression: AGPL-3.0-or-later
@@ -228,15 +228,40 @@ Authors
228
228
  .. _David Greene: https://github.com/greened
229
229
 
230
230
 
231
- `0.1.1`_ - 2026-10-19
231
+ `0.1.3`_ - 2026-11-17
232
232
  ---------------------
233
- Added
234
- .....
235
- - ``ConfigObject.iter_idents`` lists the idents of the objects recorded under a subsection, so a plugin can offer them as ``candidates``.
236
- - ``--menu=json`` gives each argument ``complete``, ``candidates`` and ``repeatable`` keys, set from new ``complete=`` and ``candidates=`` keywords to ``add_argument`` and from the argparse action.
237
- - ``--menu=json-tree`` prints the whole command tree in one call, with each subcommand's menu nested under its ``menu`` key.
233
+ Changed
234
+ .......
235
+ - Reading a key with several values as an attribute now gives a
236
+ ``tuple`` instead of a ``frozenset``. Code that compares the value
237
+ with a set, or uses set operations on it, needs ``set(...)``.
238
238
 
239
- .. _Unreleased: https://github.com/greened/git-project/compare/v0.1.1...HEAD
239
+ Fixed
240
+ .....
241
+ - ``Git.checkout``, ``Git.add_worktree``, ``Git.update_symbolic_ref`` and
242
+ ``Git.committish_is_pushed`` now take a short name that is both a branch and
243
+ a tag as the branch, and so do ``Project.branch_is_merged``,
244
+ ``Project.branch_is_merged_remotely`` and ``Project.branch_is_pushed``. The
245
+ tag was taken in its place. A checkout or a symbolic ref could then land on
246
+ the tag, a worktree add failed, and a branch could be reported merged,
247
+ unmerged, pushed or unpushed by the tag's commit. The new
248
+ ``Git.branch_or_committish_ref`` does the lookup. An unmerged SHA given to
249
+ ``Project.branch_is_merged`` or ``Project.branch_is_pushed`` now gives False
250
+ instead of an ``AttributeError``.
251
+ - A key with several values now gives them in the same order on every
252
+ run, the order git reads them from the config files. Before, the order
253
+ changed from one run to the next, so choices and ``--menu=json`` built
254
+ from such a key were reordered.
255
+ - ``run_command_with_shell`` no longer dies on a Ctrl-C or a SIGTERM while
256
+ its command runs. It waits for the command and returns its status. A
257
+ SIGTERM is sent on to the command, and so is a SIGINT when git-project is
258
+ not in the terminal's foreground group. Before, git-project exited and left
259
+ the command running. When the command dies of a signal, git-project now
260
+ exits by the same signal, so a shell loop running it stops on a Ctrl-C.
261
+
262
+ .. _Unreleased: https://github.com/greened/git-project/compare/v0.1.3...HEAD
263
+ .. _0.1.3: https://github.com/greened/git-project/compare/v0.1.2...v0.1.3
264
+ .. _0.1.2: https://github.com/greened/git-project/compare/v0.1.1...v0.1.2
240
265
  .. _0.1.1: https://github.com/greened/git-project/compare/v0.1.0...v0.1.1
241
266
  .. _0.1.0: https://github.com/greened/git-project/compare/v0.0.44...v0.1.0
242
267
  .. _0.0.44: https://github.com/greened/git-project/compare/v0.0.43...v0.0.44
@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
18
18
  commit_id: str | None
19
19
  __commit_id__: str | None
20
20
 
21
- __version__ = version = '0.1.1'
22
- __version_tuple__ = version_tuple = (0, 1, 1)
21
+ __version__ = version = '0.1.3'
22
+ __version_tuple__ = version_tuple = (0, 1, 3)
23
23
 
24
24
  __commit_id__ = commit_id = None
@@ -31,6 +31,60 @@ ChangeLog
31
31
  `Unreleased`_
32
32
  -------------
33
33
 
34
+ `0.1.3`_ - 2026-11-17
35
+ ---------------------
36
+ Changed
37
+ .......
38
+ - Reading a key with several values as an attribute now gives a
39
+ ``tuple`` instead of a ``frozenset``. Code that compares the value
40
+ with a set, or uses set operations on it, needs ``set(...)``.
41
+
42
+ Fixed
43
+ .....
44
+ - ``Git.checkout``, ``Git.add_worktree``, ``Git.update_symbolic_ref`` and
45
+ ``Git.committish_is_pushed`` now take a short name that is both a branch and
46
+ a tag as the branch, and so do ``Project.branch_is_merged``,
47
+ ``Project.branch_is_merged_remotely`` and ``Project.branch_is_pushed``. The
48
+ tag was taken in its place. A checkout or a symbolic ref could then land on
49
+ the tag, a worktree add failed, and a branch could be reported merged,
50
+ unmerged, pushed or unpushed by the tag's commit. The new
51
+ ``Git.branch_or_committish_ref`` does the lookup. An unmerged SHA given to
52
+ ``Project.branch_is_merged`` or ``Project.branch_is_pushed`` now gives False
53
+ instead of an ``AttributeError``.
54
+ - A key with several values now gives them in the same order on every
55
+ run, the order git reads them from the config files. Before, the order
56
+ changed from one run to the next, so choices and ``--menu=json`` built
57
+ from such a key were reordered.
58
+ - ``run_command_with_shell`` no longer dies on a Ctrl-C or a SIGTERM while
59
+ its command runs. It waits for the command and returns its status. A
60
+ SIGTERM is sent on to the command, and so is a SIGINT when git-project is
61
+ not in the terminal's foreground group. Before, git-project exited and left
62
+ the command running. When the command dies of a signal, git-project now
63
+ exits by the same signal, so a shell loop running it stops on a Ctrl-C.
64
+
65
+ `0.1.2`_ - 2026-10-22
66
+ ---------------------
67
+ Fixed
68
+ .....
69
+ - ``Git.refname_is_merged`` now resolves a target given as a short branch
70
+ name to that branch, and ``Project.branch_is_merged`` and
71
+ ``Project.branch_is_pushed`` look up each project branch as a branch. A tag
72
+ with the same name, such as a tag ``master``, was taken in its place. A
73
+ branch could then be reported merged when only the tag contained it, or
74
+ unmerged or unpushed when the project branch contained it.
75
+ - ``Git.clone`` and ``Git.fetch_remote`` run the git CLI for an ssh url
76
+ without a password, so they use the ssh agent, ``~/.ssh/config`` and
77
+ ``known_hosts`` as plain git does, and a Host alias now resolves. An ssh
78
+ clone has the same branches, upstream config and remote ``HEAD`` as a
79
+ libgit2 clone. A failure is a one-line ``GitProjectError`` that carries
80
+ git's error. ssh sends keepalives, so a link that stops answering fails in
81
+ about a minute. ``GIT_SSH_COMMAND`` turns that off, and so do
82
+ ``GIT_SSH`` and ``core.sshCommand`` when ``ssh.id`` is unset. An ssh clone
83
+ or fetch through git gives up after six hours. A libgit2 clone or fetch
84
+ that reached an ssh server with no key to offer died with ``TypeError:
85
+ credential does not implement interface``, and now fails with a one-line
86
+ error.
87
+
34
88
  `0.1.1`_ - 2026-10-19
35
89
  ---------------------
36
90
  Added
@@ -268,7 +322,9 @@ Fixed
268
322
  ``git_project``. No declared environment supplied Sphinx either, so a
269
323
  ``docs`` environment with Sphinx is now declared.
270
324
 
271
- .. _Unreleased: https://github.com/greened/git-project/compare/v0.1.1...HEAD
325
+ .. _Unreleased: https://github.com/greened/git-project/compare/v0.1.3...HEAD
326
+ .. _0.1.3: https://github.com/greened/git-project/compare/v0.1.2...v0.1.3
327
+ .. _0.1.2: https://github.com/greened/git-project/compare/v0.1.1...v0.1.2
272
328
  .. _0.1.1: https://github.com/greened/git-project/compare/v0.1.0...v0.1.1
273
329
  .. _0.1.0: https://github.com/greened/git-project/compare/v0.0.44...v0.1.0
274
330
  .. _0.0.44: https://github.com/greened/git-project/compare/v0.0.43...v0.0.44
@@ -36,7 +36,7 @@ arguments on top.
36
36
  Setting an attribute writes it to the config at once, and reading it reads
37
37
  the config. Values must be strings. ``add_item`` adds a value to a key
38
38
  instead of replacing it, which makes a key with several values. Read back, a
39
- key with several values gives a ``frozenset``.
39
+ key with several values gives a ``tuple``, in the order git reads the values.
40
40
 
41
41
  The attributes are properties on the class, not on the instance. The first
42
42
  time a class sets a key, the class gains a property for it, and every
@@ -243,12 +243,12 @@ class ConfigObject:
243
243
  git config when written."""
244
244
 
245
245
  def fun_get(self):
246
- result = set(self.iter_multival(name))
246
+ result = tuple(dict.fromkeys(self.iter_multival(name)))
247
247
  if not result:
248
248
  return None
249
249
  if len(result) == 1:
250
- return result.pop()
251
- return frozenset(result)
250
+ return result[0]
251
+ return result
252
252
 
253
253
  def fun_set(self, value):
254
254
  self._set_item(name, value)