Skip to main content

Qaviton Package Manager

logo
version open issues downloads code size

Tired of redundant packaging systems for your software?
qaviton is here to help!
we can package everything into simple

git branches:

  |
 dev
  |
tests
  |  
release/2019.9.1.21.12.2.127916      
  |
release/2019.9.2.0.39.13.173494     
  |
release/latest

you can now install this package:
pip install git+https://github.com/owner/package.git@release/latest#egg=package

Installation

pip install --upgrade qaviton_package_manager

Requirements

  • git 2.16+
  • Python 3.6+

Features

  • CI CD workflow ✓
  • managing private+public packages ✓
  • managing nested private packages ✓
  • cli + scripting ✓
  • pip capabilities ✓
  • git capabilities ✓
  • pypi capabilities ✓
  • automatic builds ✓
  • secure credentials ✓
  • crossplatform ✓
  • nested/multiple packages ✗
  • pip -e installs ✗ (coming soon)
  • docker build ✗ (but can be used with the run function)
  • docker push ✗ (but can be used with the run function)

Usage

creating a manager:

(venv) windows> qpm ^
--create ^
--url "https://github.com/owner/project.git" ^
--username "user1" ^
--password "pass@#$" ^
--email "awsome@qaviton.com" ^
--pypi_user "supasayajin" ^
--pypi_pass "final space" 
(venv) bash$ qpm  \
--create  \
--url "https://github.com/owner/project.git"  \
--username "user1"  \
--password "pass@#$"  \
--email "awsome@qaviton.com"  \
--pypi_user "supasayajin"  \
--pypi_pass "final space"  \
/

this should leave you with the following project structure:

project/
  ├ package/
  │   └ __init__.py  # with __author__, __version__, __author_email__, __description__, __url__, __license__
  ├ tests/
  │   └ __init__.py
  ├ .gitignore
  ├ LICENSE 
  ├ README.md
  ├ requirements.txt
  ├ requirements-test.txt
  ├ setup.py
  └ package.py  # ignored by .gitignore

now let's build a package:

# package.py
from qaviton_package_manager import Manager
from qaviton_package_manager import decypt

# if this is not secure enough, you can add cache_timeout=3600 
# and store credentials in memory
# manager = Manager(cache_timeout=3600)  
# and we need to insert the credentials in run time: > python package.py --username "x"  --password "z"
manager = Manager(**decypt(
    key=b'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx==',
    token=b'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx==',
))


if __name__ == "__main__":
    # running with lambdas will protect you from processes getting stuck
    manager.run(
        lambda: manager.update(), # pip install -r requirements.txt --upgrade
        lambda: manager.update_test(), # pip install -r requirements-test.txt --upgrade
        lambda: manager.test(), # python -m pytest --junitxml=test_report.xml tests
        lambda: manager.build(), # git commit, tag & push (internal logic is more complicated)
        lambda: manager.upload(), # upload to pypi
    )

make sure you have at list 1 passing test for your package

# tests/my_package_test.py
def test_with_100p_coverage():
    print("testing my package!\nPASS")
# we can now create a package
python package.py

CLI:

we can call any method and send any parameter to the manager through cli:

# release a version if all tests pass
qpm --username "" --password "" --update --update_test --test --build --upload

# build a stable version if all tests pass
qpm --username "" --password "" --update --update_test --test --build "stable/latest"

# install cachetools using pip and save the requirement in requirements.txt
qpm --install cachetools

# cache credentials in memory
qpm --username "" --password "" --cache_timeout "-1"

# using the system & python to execute tests
qpm --test "system" "echo success" --test "python" "-c" "print(\"py success\");"

Script:

# ci_cd.py
from qaviton_processes import run, escape, python
from package import manager
from datetime import datetime


d = datetime.utcnow()
docker_url = manager.vars['docker_url']
docker_user = manager.vars['docker_user']
docker_pass = manager.vars['docker_pass']
docker_email = manager.vars['docker_email']
SSH_PRIVATE_KEY = manager.kwargs['SSH_PRIVATE_KEY']
docker_tag = manager.kwargs['docker_tag']
branch_build = "ci_cd/latest"
dev_branch = "dev"

manager.run(
    lambda: manager.should_build(from_branch=dev_branch, to_branch=branch_build),
    lambda: manager.install(),
    lambda: manager.install_test(),
    lambda: manager.test.pytest("tests/ci_cd"),
    lambda: manager.build(to_branch=branch_build, version=f'{d.year}.{d.month}.{d.day}'),
    # docker distribute
    lambda: run(f"docker login --username=\"{escape(docker_user)}\" --password=\"{escape(docker_pass)}\" --email=\"{escape(docker_email)}\" \"{escape(docker_url)}\""),
    lambda: run(f"docker build --force-rm -t test-multi-stage-builds --build-arg SSH_PRIVATE_KEY=\"{escape(SSH_PRIVATE_KEY)}\" ."),
    lambda: run(f"docker tag {docker_tag} yourhubusername/verse_gapminder:firsttry"),
    lambda: run("docker push yourhubusername/verse_gapminder"),
    # deploy script
    lambda: python("deploy.py")    
)
# schedualer.py
from time import time, sleep
from datetime import datetime, timedelta
from qaviton_processes import python_code_async

d = datetime.utcnow()
date = datetime(year=d.year, month=d.month, day=d.day, hour=22)
delta = timedelta(days=1)

# build a package once a day at 22pm
while True:
    python_code_async('import ci_cd')
    date += delta
    sleep(date.timestamp()-time())

warnings

  • this manager is meant for automated ci cd purposes
    and should not be used instead of regular git commit/push/merge.
    make sure to avoid using it on unstable branches
    to avoid failed packaging requests or potential data loss.
    we recommend using it from a CI CD dedicated branch.

  • the manager defaults to encrypted credentials,
    if encrypted credentials on the disk are not secure enough,
    please make sure to enable caching, to store credentials in memory

Metadata

Release files for qaviton-package-manager 2019.9.24.22.41.24.927252

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for qaviton-package-manager 2019.9.24.22.41.24.927252
File Size Uploaded Provenance Actions
qaviton_package_manager-2019.9.24.22.41.24.927252.tar.gz 21.7 kB Without provenance Details for qaviton_package_manager-2019.9.24.22.41.24.927252.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for qaviton-package-manager 2019.9.24.22.41.24.927252
File Interpreter ABI Platform Actions
qaviton_package_manager-2019.9.24.22.41.24.927252-py2.py3-none-any.whl Python 2, Python 3 none any Details for qaviton_package_manager-2019.9.24.22.41.24.927252-py2.py3-none-any.whl

Total release size: 55.6 kB

Release files / qaviton_package_manager-2019.9.24.22.41.24.927252.tar.gz

Download URL qaviton_package_manager-2019.9.24.22.41.24.927252.tar.gz
Size 21.7 kB
Tags Source
SHA-256 checksum
How to use checksums
c2fc73e022d4e8654e89f0bca6eda8ca4f1c727aa39c2645ed75585e8e5a39d1
BLAKE2b-256 checksum
How to use checksums
1760c49f3f6a9f8fa14bc9a671d1703a97821f41e7eae5999e18485f1522dc9a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.35.0 CPython/3.6.7

Release files / qaviton_package_manager-2019.9.24.22.41.24.927252-py2.py3-none-any.whl

Download URL qaviton_package_manager-2019.9.24.22.41.24.927252-py2.py3-none-any.whl
Size 33.9 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
f762a7c7f0e3ff95c00f9064c411200faaa0bde21777cb2dfff92453976a2955
BLAKE2b-256 checksum
How to use checksums
9480591cf50e78de260f41d0b27f787cbd48941608dcba3a287233491869405b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.35.0 CPython/3.6.7

Security for qaviton-package-manager 2019.9.24.22.41.24.927252

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.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page