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.11.tar.gz (230.8 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.11-cp312-cp312-win_amd64.whl (1.9 MB view details)

Uploaded CPython 3.12Windows x86-64

everysk_lib-1.12.11-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.11-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.11-cp312-cp312-macosx_11_0_arm64.whl (2.1 MB view details)

Uploaded CPython 3.12macOS 11.0+ ARM64

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

Uploaded CPython 3.11Windows x86-64

everysk_lib-1.12.11-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.11-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.11-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.11.tar.gz.

File metadata

  • Download URL: everysk_lib-1.12.11.tar.gz
  • Upload date:
  • Size: 230.8 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.11.tar.gz
Algorithm Hash digest
SHA256 89fedef770f5b8313e17f690ceb1bce073f1685e561c87c1663e59daa00fe1e2
MD5 63d37a12588f02f7f831f893cfb028bf
BLAKE2b-256 9c888261d0f5107ba68db67618e4967705bca8239f2f74073761778ab6cab49b

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.11-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 0f4b8baf1e3f8c283902ca50aab41e2aaa418c6837ef5dad6c3cac11b1bc4ac0
MD5 b5d066c89b6614e6f536090ce39fc55f
BLAKE2b-256 a4d1aed6f7a9b9659a000bac756c92995f8a8e5d5394a96c94530d285bfd2e9b

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.11-cp312-cp312-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 fed92a581aeaccc35b1da14a9f85d73c4a313d418a1676184d837278a2b7213f
MD5 003a611d8839c24c1af4df12a2e4d621
BLAKE2b-256 54f75a1cc02730b6e39a102cc2f1902ce7e8be203edea49466ccbe1d15636b47

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.11-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.11-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 ce6bf78b82036db9eed0b4ed5fbf076ea602ce4290a822d41d43b58a78384f5d
MD5 580568e21ae43c67eae030aea3e548da
BLAKE2b-256 ef5ecaae70779e7c86a7b26bf2ceba3d68f01ae8aec891a03602fc323717c246

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.11-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 7c105f31160cf1a9536e4a95657b2e7eaf0b5329332423e420b295bb4bcbff9f
MD5 9dce64133274ae8b0d47bfa9dc2d6285
BLAKE2b-256 3a1ee7946b1fddfc455f0b5c0e61e36a88a7ebc25986f8f35d10d82bbb2e274e

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.11-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 61cfd3c1bf2e03a7b470ab954f7600b9f08ac629aac7d37fa26e84c69e4fccd1
MD5 4f8492b398b8531007d190258a6b3227
BLAKE2b-256 b52b29a085eeabeb691d8df6173b45a6a3d57c2239d3359a078e32c4660be62b

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.11-cp311-cp311-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 1a68ef2e64c44db87bd369b0cd4fc55b1a0e112a20e151f388dde7586d8d8e52
MD5 aa6995693e3c0919c95f0bb234b8ab28
BLAKE2b-256 a881db29253e3b3a58fc754e49f6d4316b8d1458da79b89b97c09c35b24cfd68

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.11-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.11-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 b6f7a789d7f465d237ce63dd69e3f112d4a45a73620f1b35babcc67f1b170030
MD5 18e2d7a097d39204e6021445805ee148
BLAKE2b-256 9de2c6251562ee05892dcf94e082e02b1305633e5fcef6796570172400e26699

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.11-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 a1243521fc71491f7c502ccc4d6d09275798b72427a28530d2a7eab43dce9ea0
MD5 9c9a804a9485d9b12406d61ef66d3f40
BLAKE2b-256 9833df8e084cf063e1140c07f07816a2a1cd1ff5d5662b28becc72d78a6df737

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