ssi_pingme
Dev mode
#Create the dev environment in ./.venv then activate it so you're working in it
conda env create -p ./.venv --file conda.dev.env.yaml
conda activate ./.venv
#Need to add kernel to jupyterhub for processing on server, ipykernel is part of conda.dev.env.yaml
python -m ipykernel install --user --name=Pingme
#After this change your kernel to Pingme via JupyterHub (top right of a notebook)
#Now we need to create the repo locally
nbdev_export
#with it created we can install the dev env
pip install -e '.[dev]'
#optional test to ensure it worked
core_hello_world test #to test everything works
#now we can do nbdev_prepare
nbdev_prepare
Install
pip install ssi_pingme
How to use
Fill me in please! Don’t forget code examples:
1 + 1
2
Metadata
Release files for ssi-pingme-note-name-override-due-to-collision 0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ssi_pingme_note_name_override_due_to_collision-0.0.4-py3-none-any.whl | Python 3 | none | any | Details for ssi_pingme_note_name_override_due_to_collision-0.0.4-py3-none-any.whl |
Release files / ssi_pingme_note_name_override_due_to_collision-0.0.4-py3-none-any.whl
| Download URL | ssi_pingme_note_name_override_due_to_collision-0.0.4-py3-none-any.whl |
|---|---|
| Size | 14.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23b1f4c7de0c1501a4d0a247f8694d316db4e381adc08b51ca50c98145841527
|
|
BLAKE2b-256 checksum How to use checksums |
a4c8f0074e79a652db3f04de20601fcb945d4b8f0dd6d20b06ae9497b1fff5ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.11.11
|
Security for ssi-pingme-note-name-override-due-to-collision 0.0.4
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.