Yet Anther LeetCode Cli
Api is similar to git
- lee ls lee ls 1
- lee pull lee pull 1
- lee push lee push 1
install
sudo pip install lee==2.3.0
help
usage: main.py [-h] [-p] [-r] [-d] [-j] {ls,pull,push,log} ...
positional arguments:
{ls,pull,push,log}
ls list questions, solution
pull pull question related files to local disk by
push push file to server
log status of server
optional arguments:
-h, --help show this help message and exit
-p, --proxy auto proxy at 127.0.0.1:18888 for debug, and ignore SSL
certificate verification (default: False)
-r, --refresh get request will refresh cache (default: False)
-d, --debug debug mode. debug logger will output (default: False)
-j, --json pure json output (default: False)
development
# tox for distribute
make dev
todo
- work with fzf
- supoort leetcode.com, and it should be easr
- automatically cache your language setting. every time you specify you language with -l, it will change automatically
thx
leetcode-cli. :)
Metadata
Release files for lee 2.4.0
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 | Actions |
|---|---|---|---|---|
| lee-2.4.0.macosx-10.7-x86_64.tar.gz | 24.2 kB | Without provenance | Details for lee-2.4.0.macosx-10.7-x86_64.tar.gz |
Release files / lee-2.4.0.macosx-10.7-x86_64.tar.gz
| Download URL | lee-2.4.0.macosx-10.7-x86_64.tar.gz |
|---|---|
| Size | 24.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
59713fdc24d8b4c0843015bd0813431571f933b2d25a0185115cb19341adc30c
|
|
BLAKE2b-256 checksum How to use checksums |
2efea448fb12683eb2f2392bcc2301c89ed30a48a6a04c5dc1510ff4c6cb0ef1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.4.2 requests/2.22.0 setuptools/40.6.3 requests-toolbelt/0.9.1 tqdm/4.28.1 CPython/3.7.1
|
Security for lee 2.4.0
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.