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

Uploaded CPython 3.12Windows x86-64

everysk_lib-1.11.13-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.11.13-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.11.13-cp312-cp312-macosx_11_0_arm64.whl (2.0 MB view details)

Uploaded CPython 3.12macOS 11.0+ ARM64

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

Uploaded CPython 3.11Windows x86-64

everysk_lib-1.11.13-cp311-cp311-musllinux_1_2_x86_64.whl (2.4 MB view details)

Uploaded CPython 3.11musllinux: musl 1.2+ x86-64

everysk_lib-1.11.13-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.11.13-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.11.13.tar.gz.

File metadata

  • Download URL: everysk_lib-1.11.13.tar.gz
  • Upload date:
  • Size: 233.4 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.11.13.tar.gz
Algorithm Hash digest
SHA256 d1745c6a3804fbb05a104dd4a0bec9662fe93dc9fced468ed977792a87282cb7
MD5 3134c0fd8917bcaa9e689b94607a305e
BLAKE2b-256 4952f6e7aa0f371c03ea2e548ec02a5e13b9724a0d3583b57b48f2199459fb07

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.13-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 48e6d7fee99691605deff2679e3838327fb3d3cdc924689d46eaba7eb41dbf96
MD5 f4dcaa0c324697c555499e2571ec858d
BLAKE2b-256 5bb3be7eae8dc2df30393f4108c6d82ef0fc3244dd603bab04243584ae143ee3

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.13-cp312-cp312-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 f0985d35972d8fb9423195e2a944157ca3722758b6cab2126dc2704aa9d71633
MD5 93318c088bf5670441ea013eb57cf399
BLAKE2b-256 07425d8fda2360ed471a1b00c2d81404279559d0e00990f192fa93b459db78ea

See more details on using hashes here.

File details

Details for the file everysk_lib-1.11.13-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.11.13-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 387ddc7e96c030d63f511cafc4516265c77f56d6655a7daa3c09bd6a01197dbe
MD5 08538b46ee2b895ae7be76842257779d
BLAKE2b-256 de93dfcd10129eed4425ec214d64d1f741db0593f12382d777d93488c9caf498

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.13-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 39edc3ddce510e76292ab553acf38c2ee52dd7008eba7a3b63fbed91770c1052
MD5 6c8abd00a9a91aa770119308ba10e00f
BLAKE2b-256 7038c28fcb18e922d2354e49ff4cab08fca3c4ab253f3c068001cb28cfcda230

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.13-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 17abb5519bcb249e06fb4a448bcaa593413aa3710e29f7e72ec4d2e09ca2a7ac
MD5 a06701d992891232c0e9f622553f11f3
BLAKE2b-256 0a87436e9eadd8e53ad7d6cd45577025cf661b0a898493c27ac40a3776ee1bec

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.13-cp311-cp311-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 81bd498027ae20bca9db0106f8b633c2e124a7b4d8d3fcc29802fd46a5d41967
MD5 f5acbdf780d105cf3422349bb39658ea
BLAKE2b-256 e24622adcea556a4cb571ccd41d2b676f6857b8da93c31e644a032360cea072f

See more details on using hashes here.

File details

Details for the file everysk_lib-1.11.13-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.11.13-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 081cf47f0f1aa5eef007d3e06d32acb1aac1bb50d08764ab0d8aef9017b1f6fc
MD5 bdd435dca1affbcbf0813fbc68097c08
BLAKE2b-256 6d6aa064f2d7a14eaec6f86ab8b1efb94be33c5f85a7968270767dbec90894a5

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.13-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 f8d6eef04782616bd7800d145021410cbfbb5f37647561a1f38979ab83059d88
MD5 dbecfa20917eba04786aabfc83dd4ac5
BLAKE2b-256 e2ecab3153b91b07b6622e1f9812d02467dd252d464a8197d43a5038d4cf19b7

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