As the number of projects grow, it becomes difficult to keep notebooks organized and searchable on your local machine.
See blog post for for how this project got started and the tools behind it..
Kapitsa is a simple, minimally configured command line program that provides a centralized way to search and keep track of your notebooks. Users simply configure paths where they keep their notebooks. Kapitsa provides convenience methods do do the following:
Providing the ability to search your notebooks and any notebooks on your machine makes finding code examples easier. Search all notebooks on your local machine -- that means notebooks you pulled from Github, too.
Have you ever solved some complex problem and thought bookmarking the solution for later would be beneficial? With Kapitsa, you just tag the cell with a relevant "keyword" and find it later with kapitsa tags "keyword".
Having trouble remembering how to use some API in [insert library here]? Just run kapitsa search "function" to search your notebooks for all cells containing function in their source.
Where was that notebook you worked on 2 weeks ago? Running kapitsa recent will jog your memory.
> kapitsa search "series|dataframe"Find cells matching "pandas" AND "numpy".
> kapitsa search "(?=.*pandas)(?=.*regex)"
Note: The above command does seem ridiculously complex for an and statement. Perhaps there is a better way. For now, I wanted the users to have complete control over the argument passed to jq to do the search.
Thu, 05 Mar 2020 17:05:29 -0500 /Users/Me/Github/States/train/Population.ipynb Wed, 04 Mar 2020 11:42:24 -0500 /Users/Me/Github/Class/examples/Intro-To-Pandas.ipynb Mon, 24 Feb 2020 22:58:51 -0500 /Users/Me/Projects/BigTime/train/Marketing-Plan.ipynbPrint out a list of all paths containing notebook files:
/Users/Me/Github/kapitsa/examples/ /Users/Me/Projects/Classifiers/train/awards-grants/ /Users/Me/Projects/Classifiers/train/noaa/ /Users/Me/Tutorials/DeepLearning/Fish
Users must have jq >= jq-1.6 installed because you need something to parse notebook documents (.ipynb) which are json.
> git clone https://github.com/gitjeff05/kapitsa > cd kapitsa && chmod u+rx kapitsa # Make `kapitsa` executable by the user.Create
.kapitsa configuration file.
> echo '{"path":"$HOME/Github/kapitsa"}' > ~/.kapitsa # separate paths by ":" Create an environment variable, KAPITSA that points to your config file.
> export KAPITSA=$HOME/.kapitsa # add to your .bash_profile
> . ./kapitsa # add to your .bash_profileTest that everything is working:
If you get a list of paths then you are good to go. Add more paths (separated by ':') to the path key in .kapitsa config file.
Open a ticket for bug reports or feature requests.
Testing and compatibility:Kapitsa has been tested on the following platforms.
If Kapitsa is not working for you, please open a pull request with as much information as possible so we can try to get it working.
Under the hood Kapitsa uses jq regular expressions (PCRE) through the test method. Anything you can pass to jq's test method should also be valid for Kapitsa. Please open a ticket if you find any functionality missing.
> tree -L 2
.
├── LICENSE
├── README.md
├── examples
│ ├── dataframe_nih_2019.ipynb
│ ├── nih_2019.gzip
│ └── zip_geo.gzip
├── kapitsa
└── lib
├── find_in_notebook_source.sh
├── find_in_notebook_tags.sh
├── find_notebook_directories.sh
└── find_recent_notebooks.sh
2 directories, 10 files
Note that any of the files in lib are meant to be run on their own or through kapitsa.
This program is meant to be minimal and portable. Most of the functionality is through find and jq. I have not included comprehensive install scripts that would do a lot of the setup for you (e.g., editing .bash_profile or adding files to your $HOME directory). Users should be at least somewhat familiar with the command line (i.e., knowledge of .bash_profile (or similar), alias and chmod). Anyone can read the contents of kapitsa and know that it simply reads some files and produces an output. Please open an issue to file a bug or request a feature.
I have done my best to ensure that this code can do no harm. The primary use of this script is to read files and output the results. It does not write to directories or publish anything it finds. It does not track your usage. It makes no network requests at all. I encourage you to check the source code and open an issue to alert the author of any security vulnerabilities.
Licensed under the Apache License, Version 2.0
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4