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

Uploaded CPython 3.12Windows x86-64

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

Uploaded CPython 3.12macOS 11.0+ ARM64

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

Uploaded CPython 3.11Windows x86-64

everysk_lib-1.12.14-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.14-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.14-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.14.tar.gz.

File metadata

  • Download URL: everysk_lib-1.12.14.tar.gz
  • Upload date:
  • Size: 232.1 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.14.tar.gz
Algorithm Hash digest
SHA256 44bca912caa20e60fe520ae5b9ef4dad8a53474845ddb7bcd058b585cf7da78d
MD5 087465cc133452ca99c9863fabbd1678
BLAKE2b-256 57ec5fcd3ad37a26e80206204b0d5ed784e3a888363245bb257d307dcdef0ebb

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.14-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 89fffe68e564636f327527015ea4c30ac11cddea7650948c080a8642298bd1c1
MD5 c7595e93efda83c689c199918dbc6b85
BLAKE2b-256 d04f0e79f606f7df9fb085c7920b9c039295d7e6874a0d7899c959dff92f8fff

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.14-cp312-cp312-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 d7244cbcadc209217b05337e920b025a0acd9f19a898dd9eac77a3d80d2b8e18
MD5 edc002ed0a91d3a11f9a3609b0ddc331
BLAKE2b-256 56c15f6d5f147206de57ad3a0975bc2b63f43cb1ba4e9d328bbbdf4c28b85c44

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.14-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.14-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 ac8d04b17126315324c36c3cee1c6a7ce0a9322b9f6885f6d5db78d0adab7b13
MD5 b68468881694e29e7b6717cf3a3951f0
BLAKE2b-256 5f70db94fa880fa2a8cfe5f75b4a21128859e592afbee33fee494c814067d376

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.14-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 b5eff01a1578deed580b74985e36065d09e4625122c4bd8e69028cc03c6e5e14
MD5 a3e9b43cefd405ac4a34e000b0725335
BLAKE2b-256 f839c684dad9aefd5e41b971ea656bd088bde68a5879ffdd9127c7fda7389bad

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.14-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 c12ccb0720e6c5b23e68eb494d827afc7aa7b66551b11800dec698c38d0f063a
MD5 fa04d05015f32d79863797b29a20af75
BLAKE2b-256 c11e8ecd46ddfdda2ea9956b342c916160dac8ba06d0695370f86b4ed68a7556

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.14-cp311-cp311-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 512172923b39c42f4a490b2bb7378ce078251c720d284e168796d4375ad91396
MD5 adc83df2c11c494da6ed0c0e3c1ce7e1
BLAKE2b-256 08fe3775586ad52df6c1d4915f29d71345953dfde533d9032c2df47d0976694a

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.14-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.14-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 a2c5a79dea04cce4ad96e4bfe5fc8e9bbd659754e5fa9f8f10b06cb50d3e03a7
MD5 e9aea430441fa19b201b2e01608e75dc
BLAKE2b-256 d7b406b74d65f58d5c774f261d08070b2c230fc908dbdf6541897aa9c79980e4

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.14-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 a141caaec4148099221be1fe258af77ff3867caabe66af6d2e5b3f49e66d2f03
MD5 a9bb7e804556d8c065e963d24ca546a5
BLAKE2b-256 8f3a4d87ddd7c90957c9c92d1ac22ef76b3911ecfddf521a6ab08a9254b8ec02

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