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

Uploaded CPython 3.12Windows x86-64

everysk_lib-1.11.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.11.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.11.11-cp312-cp312-macosx_11_0_arm64.whl (2.0 MB view details)

Uploaded CPython 3.12macOS 11.0+ ARM64

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

Uploaded CPython 3.11Windows x86-64

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

File metadata

  • Download URL: everysk_lib-1.11.11.tar.gz
  • Upload date:
  • Size: 231.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.11.11.tar.gz
Algorithm Hash digest
SHA256 4d8bbb062b1e9424f965888c41c193f03454de546de0cf778f6cf0f007ad4c33
MD5 e1047fd3e70fb8eac5cec2eba160d309
BLAKE2b-256 fbd0db6de9d83f91e03733d1dab12725b4d7e8cbd70a9729d521657d24101c48

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.11-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 2aa672f7a62b668568680b1c59973cd07d4509761dee3ae3bb9a2ed7d86b36cb
MD5 e111f79b240d8fd3597d77b95f560572
BLAKE2b-256 f72c80fc0705afdee3ce1481462a3750d07f18b431ea8661306ea17cfe93ce65

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.11-cp312-cp312-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 64c9b8c991bda231d89aca046a3692d6f102960aaf37989a7ffb56c8eca51aae
MD5 099cb16329e897afae92af6718510ff4
BLAKE2b-256 0420d8b58d2b3fa6ac6b38a263e5255e521ac641f6ccb8677d8eb10ed8ebd9fc

See more details on using hashes here.

File details

Details for the file everysk_lib-1.11.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.11.11-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 21301dde65cf95cf5978c6cc3b0ddc0a65d9e770eecc03c8ea8e2f820afcb9d8
MD5 7e9b8004187d3de2c8b8a537c2d745ce
BLAKE2b-256 2241b9018a07bb4000c4ef4ec865b4a77e295a68aad04a5050c2bc0a926b08e6

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.11-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 6cbe907043186e4a0ff416d9acfc6a3493dc96c832f57fd9ab4daddd09c2a3ca
MD5 3c2d34f0075187a26bdf44cd0250ee9a
BLAKE2b-256 9ee0efe87408ef43f27391b61c2692cc93e51873809abdb346f77ed09c2754c3

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.11-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 e665dc73246d57b0946d0d2988a491286d35f9a47645b47313614fc6f419d459
MD5 f48cfcf446acd047009dfb3218730ee9
BLAKE2b-256 44e6201fb6d7d058118893278ccd493ba0bdfa4289e8a9c73aca7d3e85ef19c8

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.11-cp311-cp311-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 104e72467ad005d1575755dbd3468196d2df5691908f48b0ea2fae7af9b97303
MD5 eff6ddbd853342a5be7c75d364a77608
BLAKE2b-256 6ee1169d87af02a0c94ee674d2ce7b1efe9c964389baa0a9b9bac8900ae96a86

See more details on using hashes here.

File details

Details for the file everysk_lib-1.11.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.11.11-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 b9744ff3321ff6ab2af0db6d8a3ae9d26739690e3f996e61bef14664b388a888
MD5 cc13bc67346c21e63218eb238cfd402f
BLAKE2b-256 0a1f7fd02faccf06c44b10ac8a233a5bbfc25a5b6342f276d9500c1302dc1b0e

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.11-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 e56b66d63bc5d100ab22bf953295daa3cc73d3de3a32a5da90b887bd4cd5e980
MD5 5f6c03c074e6260da48cee6cb14e8922
BLAKE2b-256 f68463b1332f291a2d78921141592cd7ebcd8ac269c1bcd091bd669e1980b78b

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