sornobase
My base libraries. sorno is just a brand name that I use for my stuff. It’s convenient to use that as a package name instead of the usual “org.xxx”.
The source code of the whole project is in github: https://github.com/hermantai/sornobase
PyPI page: https://pypi.python.org/pypi/sornobase
Installation
If you don’t have Python installed, you first need to install it from https://www.python.org/downloads/. You need a version at least 3.
For the following commands, add sudo in front of the commands if you are getting permission error.
A Python package management system will make your life easier, so install pip: https://pip.pypa.io/en/stable/installation/
Install libmagic
The library depends on python-magic: https://pypi.org/project/python-magic/
That requires the installation of libmagic:
$ brew install libmagic
Install with pip
$ pip install sornobase
Install from source
You can install sornobase from the source code by cloning the git repo:
$ git clone https://github.com/hermantai/sornobase
Then cd to the sornobase directory:
$ cd sornobase
Install it:
$ python setup.py install
Running the tests
In the directory containing the ./test.sh file, then run it:
$ ./test.sh
You can run tests only for the sorno library:
$ ./test_sornobase.sh
Or tests only for the scripts:
$ ./test_scripts.sh
Unit testing
You can run the unit tests in the sornobase/tests directory. First, set up the testing environment by running:
$ source setup_test_env.sh
If you have installed sornobase in your machine, the sornobase library from the installation is used instead of your local changes because of easy-install messing with the search path. In that case you need to either remove the egg manually or bump up the version and install it with your local changes to override the existing version.
Then you can run individual unit tests with:
$ python sornobase/tests/test_xxx.py
Deployment
The only deployment destinations for now is github and PyPI. In github, this project resides in the sornobase project: https://github.com/hermantai/sornobase
To deploy to PyPI, first install twine:
$ pip install twine
Then you can use the script to deploy to PyPI:
$ ./pypi_deploy_with_twine.sh
Use sudo if you encounter permission issues when running the commands.
Use the following if you get an error saying “twine cannot be found” even twine is on your PATH:
sudo env "PATH=$PATH" ./pypi_deploy_with_twine.sh
If twine does not work, use the old school:
$ ./pypi_deploy.sh
Metadata
Release files for sornobase 0.2
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 |
|---|---|---|---|---|
| sornobase-0.2.tar.gz | 14.3 kB | Without provenance | Details for sornobase-0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sornobase-0.2-py3.9.egg | Legacy Egg format | - | - | Details for sornobase-0.2-py3.9.egg |
Total release size: 49.0 kB
Release files / sornobase-0.2.tar.gz
| Download URL | sornobase-0.2.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9324566dedf94c4573452f98b8683333932b3c784bb796524bda88a94b0d65eb
|
|
BLAKE2b-256 checksum How to use checksums |
6d39a2e72ff271d75ae70a8b734c144a5ab787eddc51ff0707d3dac7282a6285
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.2
|
Release files / sornobase-0.2-py3.9.egg
| Download URL | sornobase-0.2-py3.9.egg |
|---|---|
| Size | 34.7 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
1efe269d91bf77c03fe4bb52a8955617222655fc03f971499cbed899016a8c4c
|
|
BLAKE2b-256 checksum How to use checksums |
c52c571c46de131f1776710d5fa5928f8d2c7a51dabf1b1a34bd0eacf0653235
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.2
|
Security for sornobase 0.2
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.