Eggs wrapped `install`, `uninstall` and `update` of `pip`.
The eggs file is `eggs.txt` which just keep **user-care** packages without
other dependency packages. It like this:
```
[prod]
sanic = 0.5.0
[dev]
pylint = 1.8.2
rope = 0.10.7
```
## Section
The default section_of is `prod` for production environment. You can freely set your section_of
## Usage
```
python eggs.py -h
```
### Init
```
python3 eggs.py init
python3 eggs.py init [new-egg]
```
### Install
```
python eggs.py install
python eggs.py install bcrypt
python eggs.py install -S dev rope
```
### Uninstall
```
python eggs.py uninstall bcrypt rope
```
### Update
```
python eggs.py update
```
### List
```
python eggs.py list
```
### Search
```
python eggs.py search jwt
```
## RoadMap
- 0.1.0 simple wrap *venv* and *pip* command
- 0.2.0 remove commands
- 0.3.0 add eggs cache
Metadata
Release files for eggs 0.0.3
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 |
|---|---|---|---|---|
| eggs-0.0.3.tar.gz | 4.6 kB | Without provenance | Details for eggs-0.0.3.tar.gz |
Release files / eggs-0.0.3.tar.gz
| Download URL | eggs-0.0.3.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b0614de90f279e2e7db95eb3221d163c7d528d216bdbaa647e5470206988c373
|
|
BLAKE2b-256 checksum How to use checksums |
71b22943822862dd292f3e93f845f56b9eada85d1e045597fb7296e720fafbf3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for eggs 0.0.3
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.