This release is a pre-release and may not be stable for production use.
config.pyfunc.com
START
setup local environment
python3 -m venv pytest-env
source pytest-env/bin/activate
Install required tools
pip install setuptools wheel setuptools-git-versioning build twine pip-tools toml path
pip install --upgrade setuptools_scm
pip install --upgrade twine
pip list
UPDATE
VERSION=1.2.15
#echo $VERSION > src/pyfunc_config/VERSION
echo "__version__ = '${VERSION}'" >> src/pyfunc_config/__init__.py
quick update
VERSION=1.2.21
git status
git tag $VERSION
git push origin --tags
git add pyproject.toml
git add .gitignore
git add *.py
git add *.md
git add src/*
git commit -m "new release"
git push
python -m setuptools_git_versioning
rm -rf build dist *.egg-info
python -m build
python -m twine upload dist/*
DETAILS
git tag 1.2.8
git push origin --tags
VERSION
python -m setuptools_git_versioning
update requirements
pip-compile pyproject.toml
pip-sync
build and publish your package:
Clean
rm -rf build dist *.egg-info
Build the Package with debug
python -m build --wheel -n
Build the Package
python -m build
Publish to PyPI
python -m twine upload dist/*
Another
Here's an updated GitHub Actions workflow to include the script execution:
py generate_init.py -p src/pyfunc_config
py -m build
twine check dist/*
test before publish
twine upload -r testpypi dist/*
publish
twine upload dist/*
Semantic versioning
The idea of semantic versioning (or SemVer) is to use 3-part version numbers, major.minor.patch, where the project author increments:
major when they make incompatible API changes,
minor when they add functionality in a backwards-compatible manner, and
patch, when they make backwards-compatible bug fixes.
1 maintainer
Metadata
1 maintainer
Release files for pyfunc-config 1.2.21.dev1
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 |
|---|---|---|---|---|
| pyfunc_config-1.2.21.dev1.tar.gz | 24.9 kB | Without provenance | Details for pyfunc_config-1.2.21.dev1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyfunc_config-1.2.21.dev1-py3-none-any.whl | Python 3 | none | any | Details for pyfunc_config-1.2.21.dev1-py3-none-any.whl |
Total release size: 38.5 kB
Release files / pyfunc_config-1.2.21.dev1.tar.gz
| Download URL | pyfunc_config-1.2.21.dev1.tar.gz |
|---|---|
| Size | 24.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f8229291a730f50de6bf1d9d4d415c7b74db77cda787464e5b5eefb839cce624
|
|
BLAKE2b-256 checksum How to use checksums |
934195d1d7cdb869c74413530ca948021fe143fadb8a488fce3cc0ca79e2a016
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Release files / pyfunc_config-1.2.21.dev1-py3-none-any.whl
| Download URL | pyfunc_config-1.2.21.dev1-py3-none-any.whl |
|---|---|
| Size | 13.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
404b07b31c0aaa718a500a581df9a35072591843e614a48b13787c1b425efeb2
|
|
BLAKE2b-256 checksum How to use checksums |
b8eef6cd4be96e12caf7270580a4f7f2ff37be6e0cbd6c32272ef7535a3a3b9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Security for pyfunc-config 1.2.21.dev1
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.
