Munir Siddiqui

Update tox.ini and re-generate requirements
tox.ini needs to have env for specific Python versions as this
is needed by the CI Zuul jobs, e.g., py310, py312 etc. Since we
are using the same CI cleanup procedure as with other charms,
this may also modify requirements files, so we re-generate
them to be sure they are in sync.
Change-Id: I07109efaec7182d16164eabf5875edc44074ea7d
Signed-off-by: Munir Siddiqui munir.siddiqui@canonical.com

2个月前182次提交

srcUpdate tox.ini and re-generate requirements2个月前
unit_testsFix mocking for wrapped OpenStack releases2年前
.bzrignoreInitial charm10年前
.gitignoreUpdates to enable jammy and finalise charmcraft builds4年前
.gitreviewOpenDev Migration Patch7年前
.stestr.confReplace ostestr with stestr in testing framework.7年前
.zuul.yamlAdd charmcraft 3 support1年前
LICENSEAdd functional tests10年前
README.mdMoving to OFTC5年前
bindep.txtAdd Kinetic and Zed support4年前
charmcraft.yamlCleanup Master CI2个月前
merged-requirements-py312.txtUpdate tox.ini and re-generate requirements2个月前
osci.yamlAdd charmcraft 3 support1年前
rebuildRebuild for Flamingo updates9个月前
rename.shAdd charmcraft 3 support1年前
requirements.inCleanup Master CI2个月前
test-requirements-py312.txtFix requirements files2个月前
test-requirements.inCleanup Master CI2个月前
tox.iniUpdate tox.ini and re-generate requirements2个月前
metadata.yamlMigrate charm to charmhub latest/edge track4年前

README.md

Overview

This is a “source” charm, which is intended to be strictly the top layer of a built charm. This structure declares that any included layer assets are not intended to be consumed as a layer from a functional or design standpoint.

Test and Build

Building, pushing and publishing to the charm store is automated by CI to ensure consistent flow. Manually building is useful for development and testing, however.

tox -e pep8
tox -e py34  # or py27 or py35
tox -e build

Contact Information

OFTC IRC: #openstack-charms

关于

python shell

README.md

552.0 KB

邀请码

加入我们
官网邮箱：gitlink@ccf.org.cn

QQ群

公众号