Why CodeSnip
Its completely free, open source package which helps you while you code. It is used to save code snippets in one place and you can access them any time using your terminal/command prompt.
Usage
Suppose I have a function which is used to retrieve items from our database and I use that a lot.
function xyz(){ ... ... }
In such a scenario, I will copy the function and in my terminal
To save
I will write: codesnip -s "database retrieve items firebase" This code will save the function you copied. It creates a folder named as database which contains snippets you saved for working on database.
If you want to fetch your function
codesnip -f "database retrieve" or codesnip -f "database firebase" or any combination of keys you passed. (NOTE folder name should always be present, in this case its database). This command copies the function to your clipboard, and if multiple functions are found, displays their keys on the terminal to choose from.
Print existing folders
codesnip -p
Print all the items in a folder
codesnip -f "database" (KEEP IN MIND, database is folder we created. It can be named anything and you can have any number of folders. This is just used for the sake of example.)
Export our codesnippets for others
codesnip -e (Exports to current working directory)
Import from current working directory
codesnip -ic (NOTE DO NOT CHANGE NAME OF CODESNIP DATA FILE. IT SHOULD BE OF SAME NAME AS IT WAS WHEN EXPORTED.)
ALSO, when updating package you have to export the data file and then update. After update is complete you need to import the data file again.
To delete any code snippet in your folder
codesnip -d "database retrieve"
Metadata
Release files for codesnip 1.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| codesnip-1.0.6.tar.gz | 5.1 kB | Without provenance | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codesnip-1.0.6-py3.7.egg | Legacy Egg format | - | - | Details |
| codesnip-1.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.2 kB
Release files / codesnip-1.0.6.tar.gz
| Download URL | codesnip-1.0.6.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c7e909811245feee5799f26501daf85636bab9e86dffaccd6725f0481fc90a44
|
|
BLAKE2b-256 checksum How to use checksums |
365ae8943580cf844f624d70b1304e7971762ef391fba9f813c0a2da38aa349a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.7.4
|
Release files / codesnip-1.0.6-py3.7.egg
| Download URL | codesnip-1.0.6-py3.7.egg |
|---|---|
| Size | 9.8 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
3fe7f2dfe3c9790842fbcb08608f5c5130c4f3bf409db9a7536837c6c252e88b
|
|
BLAKE2b-256 checksum How to use checksums |
1e73c69121de8da6f9efc36ddb38ecbe1863ad9a1af2b3095b1e7ef79122d5f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.7.4
|
Release files / codesnip-1.0.6-py3-none-any.whl
| Download URL | codesnip-1.0.6-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
81101341370a52dbc10ce962da627d8e256fd702a292c90da35a259e5df0d566
|
|
BLAKE2b-256 checksum How to use checksums |
852feabe1c245695f1c93a356a4954cfc5be5cc89ea9f48a62e9a97b60d4c2c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.7.4
|
Security for codesnip 1.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.