different utils and tools for projects
collecting python modules into library.
needs VTK
brew install vtk
install from pypi
pip install laapyCore
install from source
to work on project install source locally, activate venv and run (if mac run zsh version):
pip install -e .[dev]
pip install -e '.[dev]'
use
from working_tools import tet
test setup state
python setup.py sdist
create manifest
check-manifest --create
git add MANIFEST.in
build to upload
python setup.py bdist_wheel sdist
twine upload dist/*
Metadata
Release files for laapyCore 0.0.3
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 | |
|---|---|---|---|---|
| laapyCore-0.0.3.tar.gz | 6.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| laapyCore-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.6 kB
Release files / laapyCore-0.0.3.tar.gz
| Download URL | laapyCore-0.0.3.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05f53bf00f6b5fcc44cb15ed2d4ba6a727476cdad5f5f1fcf1050a19b309c38e
|
|
BLAKE2b-256 checksum How to use checksums |
c5f79f5b98a5bd9e1a893eddffcbeac05bce61113a3d64455a5ff8636424918d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.5
|
Release files / laapyCore-0.0.3-py3-none-any.whl
| Download URL | laapyCore-0.0.3-py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ff2d305cb7f011efcf148dd3e8414737c296724520afea15e58ac7369af6dfa1
|
|
BLAKE2b-256 checksum How to use checksums |
f7579e3f6f4abe0378ae0cf841ac57e7e6d47d338b960c2c3a100e74a43c654c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.5
|
Security for laapyCore 0.0.3
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.