Reimplement in Python

[openjck]

I think I should rewrite this in Python, which has much better argument parsing support via the argparse library, which ships with Python.

I have made some progress already on the python branch.

To do

• [x] git-iadd
• [x] git-ireset
• [x] git-icommit
• [x] git-iswitch
• [x] git-idiff
• [x] git-idifftool
• [x] git-irestore
• [x] Distribute (pip, OS package, something else??)
• [x] Update install instructions (if not distributed in a straightforward way, the user will need to install the packages in requirements.txt)

[openjck]

Some advice which might help me to import utils that are shared amongst command scripts:

https://stackoverflow.com/questions/16981921/relative-imports-in-python-3/16985066#16985066

[openjck]

My next step on this is to finish converting git-idiff to Python, which is almost done on the python branch. The only known issue is that the pager is not used to ultimately show the diff when a pager is configured to be used with git diff.

edit: I think I have solved this, and pushed the solution up, but I want to test git-idiff and all other tests that have been edited more thoroughly before calling this done.

[openjck]

All of the commands have been reimplemented and pushed up. I would like to test them one more time. After that, I need to figure out how to distribute this and update the installation instructions accordingly.

[openjck]

Notes to self about distribution

Snap

• Links
  • Snap your Shell scripts
  • My current place in the Snap tutorial
  • Snap documentation for Python apps
  • Example Python Snap
  • Other useful Python Snaps
  • Accessing dotfiles
• Downsides
  • It's difficult or impossible to distribute multiple CLI executables from a single Snap. See this question.
  • I could distribute the snap as git-fzf and rename the commands to remove the preceding git-i, which would make the commands work when invoked as git fzf.add and git fzf.commit. I have tested this and it does work. That said, I do prefer names like iadd and icommit.
  • Even if it works, accessing the global Git configuration file(s) will be annoying because the user needs to run an additional command (sudo snap connect git-fzf:gitconfig)
  • I could ask that the Snap use classic confinement, which would fix that issue, but it would need approval
• Testing my snap
  • Run this command to test a snap: snapcraft clean && snapcraft && sudo snap install --dangerous ./git-fzf_0.0.1_amd64.snap && sudo snap connect git-fzf:gitconfig && git fzf.add
• Status
  • I have a Snap partly working on the python branch, but I get an error when running sudo snap connect git-fzf:gitconfig

pip

• It seems to be possible to distribute multiple CLI executables with pip. See this article.
• Other projects that are distributed via pip
  • vint
• Maybe Poetry would be a more modern choice?

Other methods

• Some projects, like git-plugins and forgit do recommend the distribution method I use now (git clone + $PATH) among others. However, this might be a bit tricky since the project uses Python libraries.

General

• I started looking into packaging it with Snap, but there are some downsides, so I want to look into packaging it with pip next. If I distribute it with pip, I'll need to remove the snap config, but I might want to keep other changes that were made in the commit that added the snap config.

[openjck]

I pushed up some code to the python branch which begins to use Poetry.

[openjck]

Hey that was easier than I thought.