Skip to main content

Generic lib to share python code on Everysk.

Project description

Everysk Library

Testing CI - Test Security Checks
Package PyPI Latest Release

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/




Back to the top

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

everysk_lib-1.12.12.tar.gz (231.2 kB view details)

Uploaded Source

Built Distributions

If you're not sure about the file name format, learn more about wheel file names.

everysk_lib-1.12.12-cp312-cp312-win_amd64.whl (1.9 MB view details)

Uploaded CPython 3.12Windows x86-64

everysk_lib-1.12.12-cp312-cp312-musllinux_1_2_x86_64.whl (2.9 MB view details)

Uploaded CPython 3.12musllinux: musl 1.2+ x86-64

everysk_lib-1.12.12-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl (2.9 MB view details)

Uploaded CPython 3.12manylinux: glibc 2.17+ x86-64manylinux: glibc 2.28+ x86-64

everysk_lib-1.12.12-cp312-cp312-macosx_11_0_arm64.whl (2.1 MB view details)

Uploaded CPython 3.12macOS 11.0+ ARM64

everysk_lib-1.12.12-cp311-cp311-win_amd64.whl (1.9 MB view details)

Uploaded CPython 3.11Windows x86-64

everysk_lib-1.12.12-cp311-cp311-musllinux_1_2_x86_64.whl (2.5 MB view details)

Uploaded CPython 3.11musllinux: musl 1.2+ x86-64

everysk_lib-1.12.12-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl (2.4 MB view details)

Uploaded CPython 3.11manylinux: glibc 2.17+ x86-64manylinux: glibc 2.28+ x86-64

everysk_lib-1.12.12-cp311-cp311-macosx_11_0_arm64.whl (1.9 MB view details)

Uploaded CPython 3.11macOS 11.0+ ARM64

File details

Details for the file everysk_lib-1.12.12.tar.gz.

File metadata

  • Download URL: everysk_lib-1.12.12.tar.gz
  • Upload date:
  • Size: 231.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for everysk_lib-1.12.12.tar.gz
Algorithm Hash digest
SHA256 0db39384a08f50ae3add6ce9747d0fce72bf1f132837ffd1fe23899c43aef52b
MD5 14767de6f869a1e4d28194b34bbe5dab
BLAKE2b-256 95731bd0b41a636ff223a6c358e0e044a1091667febd468de8334eab57cefaa2

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.12-cp312-cp312-win_amd64.whl.

File metadata

File hashes

Hashes for everysk_lib-1.12.12-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 d0d195c15bbc9f4d9aad36bae5350f6334438625699289d9e1fb7545d623382c
MD5 e3ce0ccb1b3b6ae823f39c67c9c40353
BLAKE2b-256 5e0b0a8b28ad8528e1d3ad6fbcefb67f7beb1ae18d297222a3494b7a02fafdc8

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.12-cp312-cp312-musllinux_1_2_x86_64.whl.

File metadata

File hashes

Hashes for everysk_lib-1.12.12-cp312-cp312-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 3981f03a2f1a6e0ac970bb70ce52671dbe622c2abd38a2f345be056c8856be30
MD5 f591d9510bea45aeac04d2e84e53b695
BLAKE2b-256 165c094fe6f2946fa5192473345d34704a3f17e675ef3c6f077fe392a449b985

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.12-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for everysk_lib-1.12.12-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 6bb5283a4314b936b799b56c8518a3a69e3b37be9641a8312e25cc4ed0e8c467
MD5 86f750d2a45aba1c090031ceb5374200
BLAKE2b-256 7361ed399cc86cdeba42dce260f763e52e466422d8da6eb34cbb62f21c235f08

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.12-cp312-cp312-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for everysk_lib-1.12.12-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 bda87002d3a28aaee54fbfcd79e45bffa837b2fba854d291f3f64339ba0c059f
MD5 1114a272b4bfd4fe0271cdc1b56b4355
BLAKE2b-256 26b6836e66a18863b72e46deed195ad9a067fab598364e0f66957ad62bce0b14

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.12-cp311-cp311-win_amd64.whl.

File metadata

File hashes

Hashes for everysk_lib-1.12.12-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 afee37cc85d71752e36b907ef18980325831e1335be13d88bc8ef9a6c4cb63e7
MD5 aee9e7b0f4db90cbf38d21eefe0c080e
BLAKE2b-256 7cb9b9e69c2b95c6f8000460c15bfae72f1db729f90df41fca918349513dfd51

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.12-cp311-cp311-musllinux_1_2_x86_64.whl.

File metadata

File hashes

Hashes for everysk_lib-1.12.12-cp311-cp311-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 eebcc8f7cf0da9f6621eaedd2eb29ae6455ccf524ef00d044a99f65b9dc630a5
MD5 c6544b9ac86d6d97e4d6e49b388ab19b
BLAKE2b-256 16ce022e30474b0c660abc604c43f6655bae57697a54fb27d32f7297d3f94bd7

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.12-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for everysk_lib-1.12.12-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 8506c4e9d25332182e72b4058ec81687f4579598f8b730d7c4a0ef9fe891c439
MD5 7ae8bb785b5aa3b40962a146d3200987
BLAKE2b-256 fc1a834d18e8e213dba8f9cef8610df457b52cff1d54eaa0e231dee71d046155

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.12-cp311-cp311-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for everysk_lib-1.12.12-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 8aa2f04c5f2b3186b58fb2fd2dc9f2a404ee38eedfe5fd91524c4e3704423bf4
MD5 02c21973c9c7932aa80092e4041eadef
BLAKE2b-256 838ede44b147881d674a2f6fae6716f1d758cb1e110cef366dd59594b17c6888

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page