py_cui VS RecoverPy

py_cui - Another curses wrapper

It's great to see some more competitors on the TUI front of the Python ecosystem! I recently tried multiple existing frameworks and was not particularly happy with the state.

Here are the main contenders for libraries that provide higher-level API than urwid/ncurses:

* Picotui, https://github.com/pfalcon/picotui

* Npyscreen, https://github.com/npcole/npyscreen

* py_cui, https://github.com/jwlodek/py_cui

Both Picotui and Npyscreen are relatively unmaintained / considered feature-full. py_cui seems to be in the best shape.

Fingers crossed for this project making it through, building on top of Rich gives it quite a bit of headstart. You can also sponsor @willmcgugan on Github [0].

[0]: https://github.com/sponsors/willmcgugan

You're probably going to want to do this in a TUI. If I was going to attempt this project, I think I'd try py_cui which was written by a fellow Redditor u/QbaPolak17. Another possible (buy maybe less pretty) option is picotui. I've not implemented either of these, but py_cui looks fun.

So, when I found the different commands to get back my file and recover it, I wanted to create a clear UI to do it. Searching for a CUI library, I've stumbled upon py_cui, based on curses, it has a really easy learning curve. Easy to get it running.

I dit it with py_cui, it's based on curses library but really easier to work with.

Here is the GitHub: https://github.com/PabloLec/RecoverPy

I know about https://github.com/PabloLec/RecoverPy which you could use on an unmounted partition.

Hi! I recently release RecoverPy v1.5.0 and I think I might give you some news. -> Repo: https://github.com/PabloLec/RecoverPy -> What is it? RecoverPy is a 100% Python tool to not only recover deleted but also overwritten files. I got the idea when I was quite new to some programming best practices, especially version control... Long story short, I accidentally piped my output into my precious script... Just spent the day working on something and instead of typing myscript > log, I typed log > myscript, oh boy what a feeling. I knew some tools to recover deleted files, but my problem was quite different, I didn't deleted the file (in system words, marked the file blocks as deleted/available), I just replaced it's content. Talk about an impostor syndrome. After a long ride in the abysses of unix stackexchange, I found some dark combination of grep and dd command to search directly in your raw system partitions blocks and eventually recovered my file! But as the process was really slow and painful, I thought it might be a good idea to make a tool out of it. That's how RecoverPy was born.