Everysk Library
| Testing |   |
| Package |  |
The Everysk Library is a one-stop solution designed to help our teams and partners streamline workflows and maximize productivity.
Many projects at Everysk rely on multiple endpoints, engines, and utilities to automate workflows, handle entities such as portfolios, datastores, reports, and files, and perform complex calculations. Adopting and maintaining each of these components individually can be both time-consuming and expensive.
To address this challenge, Everysk developed the Everysk Library: a unified Python library that bundles these capabilities into a single, convenient package.
By consolidating essential functionalities — ranging from portfolio creation to workflow automation — Everysk Lib greatly simplifies implementation and ongoing maintenance. This all-in-one toolkit ensures you have everything you need to build powerful, scalable solutions across a variety of Everysk projects.
Table of Contents
Module Structure
Below we have the main directories that you will be working with.
flowchart TB
EveryskLibrary(["Everysk Library"])
SDKDir(["sdk"])
CoreDir(["core"])
ServerDir(["server"])
ApiDir(["api"])
EveryskLibrary --> SDKDir
EveryskLibrary --> CoreDir
EveryskLibrary --> ServerDir
EveryskLibrary --> ApiDir
Installation
To install the Everysk library, you will need to use pip's install command:
pip install everysk-lib
Verifying the Installation
After installing the library, it's a good practice to verify if the installation was successful. Here is how to achieve this:
1. Open a terminal
2. Start the Python interpreter by typing python and pressing Enter
3. In the Python interpreter, type the following command then press Enter:
import everysk
If the library has been installed correctly, this command should complete without any errors. If the library is not installed or there's a problem with the installation, Python will raise a ModuleNotFoundError
Documentation
The main documentation of the Everysk Library can be founded here: Everysk Library Documentation
Running Tests
This section provides instructions on how to run tests for the project. There are two scenarios, the first one is running tests in a development environment and the second one is running tests after the library has been installed from PyPI.
Running Tests in Development Environment
In a development environment you can use the provided shell script to run the tests. The script sets up the necessary environment and then run the tests. To execute the tests, open a bash terminal and run the following command.
./run.sh tests
Running Tests After the Library is Installed
After the library has been installed in your project from PyPI, you can start running tests using Python's built-in unittest module. To run tests use the following command:
python3 -m unittest everysk.core.tests
The command uses Python's unittest module as mentioned above as a script, which then runs the test in the everysk.core.tests package.
Running Tests with coverage
Code coverage us a way of measuring how many lines of code are executed while the automated tests are running.
To run tests along with a coverage report, you can use the provided shell script. The script will not only run the tests but also generate a coverage report that shows the percentage of code that was executed during the tests.
This is useful to identify sections of your code that are not being tested and may need additional tests.
1. Open a terminal in your Visual Studio Code environment.
2. Run the following command.
./run.sh coverage
This command executes the run.sh script with the coverage argument. The report will be displayed in the terminal after the script completed the tests.
Remember: a high coverage percentage is generally good, but 100% coverage does not ensures that your code is free from bugs or any other problem that might occur in your code. The full coverage just means that all the lines in your code were executed during the tests.
Contributing
Contributions are always welcome and greatly appreciated!
Go to the repository link and click on the Fork button to create your own copy of the everysk library.
Then clone the project in your own local machine by running the command below or using the GitHub Desktop.
git clone https://github.com/<your-username>/everysk-lib.git everysk-yourusername
This section creates a directory called everysk-yourusername to center all your code.
After that you can change the directory by:
cd everysk-yourusername
Create the upstream repository which will refer to the main repository that you just forked.
git remote add upstream https://github.com/Everysk/everysk-lib.git
Now run the following commands to make sure that your clone is up-to-date with main everysk repository
git checkout main
git pull upstream main
Shortly after, create a new branch to add your code
git checkout -b brand-new-feature
The command above will automatically switch to this newly created branch. At this moment your are able to make your modifications to the code and commit locally as you progress.
After all the code changes, you can submit your contribution by pushing the changes to your fork on GitHub:
git push origin brand-new-feature
The command above ensures that all the modifications that you've made are up-to-date with your current branch.
At the end of this process you will need to make a Pull Request to the main branch.
To achieve this, go to the GitHub page of the project and click on the Pull requests tab, then click on New pull request button.
This will open a new section used to compare branches, now choose your branch for merging into the main branch and hit the Create pull request button.
License
(C) Copyright 2025 EVERYSK TECHNOLOGIES
This is an unpublished work containing confidential and proprietary information of EVERYSK TECHNOLOGIES. Disclosure, use, or reproduction without authorization of EVERYSK TECHNOLOGIES is prohibited.
Date: Jan 2025
Contact: contact@everysk.com
URL: https://everysk.com/
1 maintainer
Metadata
1 maintainer
Release files for everysk-lib 1.13.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| everysk_lib-1.13.1.tar.gz | 264.9 kB | Details |
Built distributions (wheels)
Total release size: 19.2 MB
Release files / everysk_lib-1.13.1.tar.gz
| Download URL | everysk_lib-1.13.1.tar.gz |
|---|---|
| Size | 264.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
776adea97ff1ec429a97f83339993645c5697fb5e554818f42df94a250b35af3
|
|
BLAKE2b-256 checksum How to use checksums |
0d157d800d7df7dd9648484da6ce204000d38be99d74920ac4c2d70568a1564e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / everysk_lib-1.13.1-cp312-cp312-win_amd64.whl
| Download URL | everysk_lib-1.13.1-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
f256c0d47c4542a2117b4499941208380e8761d615464a32b819052ee80e7073
|
|
BLAKE2b-256 checksum How to use checksums |
c77910fa72f0baf829e469ad6614593ca4c5c2cbdb6549c46d9a58f8adb91b1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / everysk_lib-1.13.1-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | everysk_lib-1.13.1-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 3.0 MB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
c3dc83a24b8795f8187d36c1aac5c62b18574f74418cb6ff2b207f4f279d5ffc
|
|
BLAKE2b-256 checksum How to use checksums |
f0d13d3150476db529fe02979c7ae2c8e02fd716682f26416a1b314fb7738f9f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / everysk_lib-1.13.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | everysk_lib-1.13.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.9 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
66ca072eeb99106de2a006d01f36d0f29af5958c9f46d745c50493fe7bbfa145
|
|
BLAKE2b-256 checksum How to use checksums |
864b6c2c2a804089f6e211829b92ea85503b4b564ace879eab18a0ef3f986a52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / everysk_lib-1.13.1-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | everysk_lib-1.13.1-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
eb04c4667e52a00fdcb9ae83b5ed2f861e124a087b24004b7d6eeccf98265f0f
|
|
BLAKE2b-256 checksum How to use checksums |
7b9e02d93f38602ff02d1bdd970a860341b693ac9f7badfbc69991bd42f42237
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / everysk_lib-1.13.1-cp311-cp311-win_amd64.whl
| Download URL | everysk_lib-1.13.1-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
cf0556ec420fca349f9ffe7419ef50ad88465b8d90591778694d9429200d2d3e
|
|
BLAKE2b-256 checksum How to use checksums |
68968476c3c03b597d1e0d87f7c3144b26ca5862a83e0edfa59497acf7ddad8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / everysk_lib-1.13.1-cp311-cp311-musllinux_1_2_x86_64.whl
| Download URL | everysk_lib-1.13.1-cp311-cp311-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
ac9a51895eeeb8825946db0631a5c6859b26f447c573aae1515c904cb54a754d
|
|
BLAKE2b-256 checksum How to use checksums |
9da022a04de4cedfb3373d8feff2e02050631a845873fb78e845913b887441af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / everysk_lib-1.13.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | everysk_lib-1.13.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
9bffb3140099f4f5c7288ac361f6c3677a137689ffbb9eeb529c127900f81afa
|
|
BLAKE2b-256 checksum How to use checksums |
c29c15a1350be198e08f3befbdd5cb96d167b592ad5efd59b1ebdb4e1a4e0674
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / everysk_lib-1.13.1-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | everysk_lib-1.13.1-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
44647c1a1f878bb4369b676925f16d421b857884c1e80000ba084f1fa92df82f
|
|
BLAKE2b-256 checksum How to use checksums |
4bba30384202f1236cdb36ba6a9a1c76477c30f0619e7fa83d8ccd48f7244b6c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
