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

Uploaded CPython 3.12Windows x86-64

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

Uploaded CPython 3.12macOS 11.0+ ARM64

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

Uploaded CPython 3.11Windows x86-64

everysk_lib-1.11.10-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.10-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.10-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.10.tar.gz.

File metadata

  • Download URL: everysk_lib-1.11.10.tar.gz
  • Upload date:
  • Size: 231.5 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.11.10.tar.gz
Algorithm Hash digest
SHA256 7f46a5a7398f8e98662d91f4b6212caf9cfae378da7dc602993c2c60d51e9b44
MD5 eec47ee412e70eefc1e1f5a63d411ac6
BLAKE2b-256 70e6c3a5483869565ea1fc07b51e6ed56c3d52f222036ee49e7402e7491316aa

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.10-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 04884cd8265f36780c47ddc515aeab0a34f3a4f2dc4ac68370c3760ed6330955
MD5 6fd77aff34d45fd7454d7e115f6e4f8b
BLAKE2b-256 bc80771bc20cf2b7ccd584e62c87d6448899e9fae33c1887d1b5de185b78bf65

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.10-cp312-cp312-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 76ae207887915a01eb5b26b13447efbe3c22c239e0ff0c3b34d08083d6f272cd
MD5 b1770bf963302a5a39374e4a9913c16f
BLAKE2b-256 b4b7cdaed4b9561643281c7e1311451a0c82ac9ce968eee89d9424cbc8a3643c

See more details on using hashes here.

File details

Details for the file everysk_lib-1.11.10-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.10-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 40e372546066b75a30cd5c1fb579d06d17ed68c13598d10fdba9f80bd5eaa953
MD5 1d44d25a7016facb63016db10edfe2da
BLAKE2b-256 486874fa55b899caeb27239d45830ae8758f8db3c9440224bc33360740d97c74

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.10-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 89eb7194a642ed51c9e491e1642c4ebf368db0906e0f10e33fde4f46ab42f352
MD5 d813ce85ce809ea89b629e016213a329
BLAKE2b-256 f883acd9503d9ae0a206adf854f46d2d6e36a93e89ade83752e41416d8c14bc1

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.10-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 93614d50ba47892b5d2d8a3181ae1dfa02ce63b857a8768ea85232e72bd69954
MD5 a221f863ca4f104473119d84781580ff
BLAKE2b-256 d43b0cc104cea130e40b07dff430e5b615c7772e982bdeff1769f499399e09fb

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.10-cp311-cp311-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 99137aa817b10bbf0b1ec8168647b1d1aa3cea6823451bc2f23792579cf5fae8
MD5 d0f31e69ec9e4fbd66784549d1a3d6d2
BLAKE2b-256 dba7057aa79f85dff3f531be93594402331525aaf9e2106a4a6b60c14695d327

See more details on using hashes here.

File details

Details for the file everysk_lib-1.11.10-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.10-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 d560ce327faeaa394b1198b411bd30cb7d88929d51d04017c88476384c0437c0
MD5 e3db8ca540f4d02867512aa461344af0
BLAKE2b-256 274df055db638b9c24f702e5c6b68205336947617c9eeccefc665c0da9dcaa79

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.10-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 02b60ab89b747369580f851a8f928a5e35c021ee40fad661555e28753a684ba4
MD5 9b3f2176f19b61f36fe301e0eaf6c07b
BLAKE2b-256 34adc6da62a76903db91dd3c5d093bf1fd6cedb3c5dcfc1443d2a30349042aa3

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