# Clean files make clean
# Copy /hgmeans folder with .cpp and .h files make hgmeans
# Use Cython to create the interface with Python – here the hgmeans.cpp file should be created make build
# Create Python package – here a tarball file should be created in /dist folder make sdist
# To install the package locally, run: python3 -m pip install dist/* <!– sudo pip install dist/* –>
# To publish the package in PyPi repository, run: sudo twine upload dist/*
###
# Clean and compile >> cd hgmeans >> make clean >> make hgmeans >> cd ../
# Generate wheel file >> python3 setup.py sdist bdist_wheel
# Install the package locally >> sudo pip3 install dist/*
# Publish the package in PyPi repository >> sudo twine upload dist/*
1 maintainer
Metadata
1 maintainer
Release files for hgmeans 3.0
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 |
|---|---|---|---|---|
| hgmeans-3.0.tar.gz | 1.7 MB | Without provenance | Details for hgmeans-3.0.tar.gz |
Release files / hgmeans-3.0.tar.gz
| Download URL | hgmeans-3.0.tar.gz |
|---|---|
| Size | 1.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0816ca4b9b6ce9eac006704463d528a35697aa5f7114c750cca94fff3f6946a6
|
|
BLAKE2b-256 checksum How to use checksums |
527d9813f84d582d3e4ea209b0af1ba92bb2d2ca3905e65a4c875fb925a12791
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.8.10
|
Security for hgmeans 3.0
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.
