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.9.6.tar.gz (204.7 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.9.6-cp312-cp312-win_amd64.whl (1.8 MB view details)

Uploaded CPython 3.12Windows x86-64

everysk_lib-1.9.6-cp312-cp312-musllinux_1_2_x86_64.whl (2.8 MB view details)

Uploaded CPython 3.12musllinux: musl 1.2+ x86-64

everysk_lib-1.9.6-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl (2.7 MB view details)

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

everysk_lib-1.9.6-cp312-cp312-macosx_11_0_arm64.whl (1.9 MB view details)

Uploaded CPython 3.12macOS 11.0+ ARM64

everysk_lib-1.9.6-cp311-cp311-win_amd64.whl (1.8 MB view details)

Uploaded CPython 3.11Windows x86-64

everysk_lib-1.9.6-cp311-cp311-musllinux_1_2_x86_64.whl (2.3 MB view details)

Uploaded CPython 3.11musllinux: musl 1.2+ x86-64

everysk_lib-1.9.6-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl (2.3 MB view details)

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

everysk_lib-1.9.6-cp311-cp311-macosx_11_0_arm64.whl (1.8 MB view details)

Uploaded CPython 3.11macOS 11.0+ ARM64

File details

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

File metadata

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

File hashes

Hashes for everysk_lib-1.9.6.tar.gz
Algorithm Hash digest
SHA256 04b84bed4dcc7febe00157fb4e68d120890e5017bd63e6c56921e83ddaa7413e
MD5 c299779e5b19301f8d81aca646ddf770
BLAKE2b-256 eea617940c9ef681a8da9ff5817d5a828e1eb03298075ce03a8c3f6c6949c610

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.9.6-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 2f64b465b288dbef2eb88a4a0f2c24a98610dd183cd235d0a12ebbbb7963db6b
MD5 76cb6cba6033f41dc951f25b190a204e
BLAKE2b-256 be075d8e8623de3ee972d28b3029216d76b10a72479ac08147f3f8f99ac8c965

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.9.6-cp312-cp312-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 1278eb889056159e85e9b657abcf95418f2e97f897490c53dc0aadc135fcd4a2
MD5 19d183ec0687bc08f542d4e197556639
BLAKE2b-256 1b8db3906b3327f1e950a348159f9069b3c3a138c0907baf1aa0371b649fcbf2

See more details on using hashes here.

File details

Details for the file everysk_lib-1.9.6-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.9.6-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 b588432051e4af8b2f386ca3870b8c9ac16a63456709d94c8dae751a5903e82c
MD5 3dd91d72576e086246c0f3984e1451f0
BLAKE2b-256 93e6ba38f865d0c93812e92d63f932572ea5d9384b23f9ba92582fe4facb2e96

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.9.6-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 bcb3a0119d559ba4901a3297ecf167f83db6e74baa11b1383d719d46491c6433
MD5 75f0c4e56c0093ab1cf516441edb4d9b
BLAKE2b-256 6a2d6c82b865be9cf0f479c3eaad726f4d91a1421dabb46a481b4fbab456a6fc

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.9.6-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 ddcf37f8f8a79c46a49e4ef44369d3f64e8dd1a177b0ec4f2f5edbff0585eb38
MD5 a17db303feb7e21c6e3500180adfff7f
BLAKE2b-256 f0e655eaa912651b48d1f4a5aa03ca4291d95f865f2b7e13f80e736c44c4ed09

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.9.6-cp311-cp311-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 3cc2a4e9a969bf43595be262360543a952e88a176f086182a5742da6cee7e832
MD5 cb5f8a2dbc0acac2fcde43738094eb12
BLAKE2b-256 2d21e035b88d0b17ad159177cdfdf21ba43358bfa6d32faa59b2b5c0df10f995

See more details on using hashes here.

File details

Details for the file everysk_lib-1.9.6-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.9.6-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 0271532a78813cba671f6cebdf0c7f1c2146ba7cde9a48bf2f3e0d679d75dee4
MD5 0d58e219168520feeea8daf04205d806
BLAKE2b-256 3b84b34592cbc640c7427d46fb393027d114530f033d8fd97c0086da0006e9a1

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.9.6-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 9262f256b4caf1b690a8e1b23c2f942af054a00bebdc838fbe2fe2393f7049bb
MD5 9e4a95c61da5601973554b906d92fa79
BLAKE2b-256 01a01ad50e7f43e9c2eac286ae085e41c311731fd436a5a110b64d60b77cd659

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