easy-deps
Package manager for python based on pip3
Solve the main problem of pip - fucking horrible deps.
Just try it, and you will understand it.
All your project config and deps will store in .ezdeps.json like this:
{
"name": "ezdeps",
"version": "1.0.4",
"description": "Package manager for python",
"documentation_path": "./README.md",
"author": {
"name": "Vitaly Kisel <jellyb0y>",
"email": "kisel@internet.ru"
},
"scripts": [
"./scripts/ezdeps"
],
"dependencies": {
"pip": "^20.0.0",
"wheel": "0.36.2",
"twine": "3.4.1"
},
"dev_dependencies": {},
"python_requires": ">=3.8",
"classifiers": [
"Programming Language :: Python :: 3.8",
"License :: OSI Approved :: MIT License",
"Operating System :: OS Independent"
],
"include_package_data": true
}
You don't more need use setuptools, it is already in it.
install
Install package: pip install ezdeps
Usage
Common usage:
ezdeps <command> [options] [packages]
Commands:
-
install- Install packages- options:
<-S | --default>? [packages, ...]Install packages to default dependencies<-D | --development> [packages, ...]Install packages to dev_dependencies<-A | --all>Install packages from dependency list.ezdeps.json
- options:
-
uninstall- Uninstall packages- options:
[packages, ...]Uninstall packages from deps
- options:
-
update- Update packages- options:
[packages, ...]Update packages in deps
- options:
-
build- Build package -
publish- Publish packages- options:
<-C | --clear>Clear temp files after publishing<-R | --repository>Set up repository name in your.ezdepsrc<--repository-url> [url]Set up repository url<--username> [username]Set up registry username<--password> [password]Set up registry password
- options:
Common options:
- <-J | --without-json> Do not write json file
Using .ezdepsrc
To store your keys and tokens you have to create ~/.ezdepsrc file:
[gitlab.com]
USER=myuser # Test user for gitlab regitsry
PASSWORD=topsecret # Test passwd for gitlab regitsry
[github.com]
USER=myuser # Test user for github regitsry
PASSWORD=topsecret # Test passwd for github regitsry
REPOSITORY_URL=https://example.com/ # regitsry url for github (optional)
REPOSITORY_NAME=github # regitsry name (optional) to rewrite `github.com` to `github`
e (optional) to rewrite `github.com` to `github`
Metadata
Release files for ezdeps 1.2.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 | |
|---|---|---|---|---|
| ezdeps-1.2.0.tar.gz | 9.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ezdeps-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.6 kB
Release files / ezdeps-1.2.0.tar.gz
| Download URL | ezdeps-1.2.0.tar.gz |
|---|---|
| Size | 9.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7360471b594a88ba7bfe21c6a7eac763bda7247e16de52980ea827c9d72ecc0
|
|
BLAKE2b-256 checksum How to use checksums |
bf4eef9e488ec72abf193f495681fd934d79f7f246ac0871eeda88bf19328c50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.5
|
Release files / ezdeps-1.2.0-py3-none-any.whl
| Download URL | ezdeps-1.2.0-py3-none-any.whl |
|---|---|
| Size | 12.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7cfd719a9ab8e1a947ce69965fcea781a3d977de2b7b7126f0acfc3c7e12a044
|
|
BLAKE2b-256 checksum How to use checksums |
d5094e36470e42aadd98a3345cbda7cc63240577fe13132a966b0789637b29e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.5
|
Security for ezdeps 1.2.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.