qiq is the thin layer over pip with some principles.
- requirements.txt becomes qiq.txt
- virtual environment created in project in
venv - every package in
qiq.txthas exact version or links to local directory - can make symlinks for local development
No requirements except Python 3.
Usage
For example My-Company-Core is the Company's core library used almost in all projects. It's development files located relative to current project is ../my_company_core.
Our qiq.txt will be:
+dev:../my_company_core
My-Company-Core==1.2.7
Flask==1.0.2
flask-cors==3.0.7
+dev is the flag, which can be given in qiq command.
This will symlink my_company_core to ../my_company_core:
qiq +dev
And this will install production use code to venv:
qiq
By default used library name is last directory in path. It can be overriden with name and ==:
+dev:Company-Core==../my_company_core
VCS also supported:
+dev:git+ssh://gitlab.com/myteam/mycompanycore.git@2313ceee
1 maintainer
Metadata
1 maintainer
Release files for qiq 0.5
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 |
|---|---|---|---|---|
| qiq-0.5.tar.gz | 4.4 kB | Without provenance | Details for qiq-0.5.tar.gz |
Release files / qiq-0.5.tar.gz
| Download URL | qiq-0.5.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6114bdaf333f79a7e94bf458e87253a8fa22d3fa7a93285ce60f9a0a9a1e3dc1
|
|
BLAKE2b-256 checksum How to use checksums |
a70b8676cc96dce90bbb6e9503c2eed359ac431e8372c1505c6cbf65d7701f8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/2.7.15
|
Security for qiq 0.5
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.
