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

Uploaded CPython 3.12Windows x86-64

everysk_lib-1.12.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.12.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.12.13-cp312-cp312-macosx_11_0_arm64.whl (2.1 MB view details)

Uploaded CPython 3.12macOS 11.0+ ARM64

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

Uploaded CPython 3.11Windows x86-64

everysk_lib-1.12.13-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.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.12.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.12.13.tar.gz.

File metadata

  • Download URL: everysk_lib-1.12.13.tar.gz
  • Upload date:
  • Size: 231.8 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.13.tar.gz
Algorithm Hash digest
SHA256 8449a39682f9ae110d3eaac7c7ec511af43666380d07b241eb74021850bbb6e4
MD5 432b05333321413b395b81345b8c3086
BLAKE2b-256 1e5184e357d5a3a44c6ada8b28c34bc0d5db4691eb7d9397db711180bce63f12

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.13-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 b47ad1cb91d760d379f8bd7ce346c0c6ea1a7e1e2859633ed8cbe7a9fbdb0b6a
MD5 50d5ee34fa7f95a5f793462b8b363586
BLAKE2b-256 6c3e9bdc348f7548fd1018986f4722a4e810eb7a6de464d41dc60e445ee14fcc

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.13-cp312-cp312-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 75eb3f47a813460477ce207225daa93fe9d6155d6158582e7d089f487d8ef984
MD5 c881537f7232479fa228691f18b434b8
BLAKE2b-256 fc0790768be076cf0e7d9369503e216d021b48c5aa4803971eab6b04dfbe4b52

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.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.12.13-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 837eda048308bb6230c33d5f6564dba1e607e16100386f0a845a654852485eeb
MD5 946ae7c730ec9275730c32e78ae97e82
BLAKE2b-256 61ef3b4665b0f8466ca47a6c75eac3f7a441817c21648e296b0d36bea8fc0a2f

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.13-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 56da38803a42183321a2ac434e21f165ed8e7cb59ad70ca20b77183b8e0dc67c
MD5 0d53c23a38d491bc06eb1f8b92dd08d2
BLAKE2b-256 220876662572db9d33538680e8e6822706a0fc6ccacc5e3291e6f4eb04d7d6b7

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.13-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 aee7f22d8a164de90a30294fe1ce184a9d2ebafe7221b52af3e0a760de8a9d9b
MD5 1e7acb4978b2b212bd3254967c47a0dd
BLAKE2b-256 dc15787c0fe6ff421318c4fd847981e61919bbfe37012f933d055d62f9a83f6e

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.13-cp311-cp311-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 05606012f4dc4d5264c70da89ca1a14ac182bfe5a8eaa708441f9692f4515fb2
MD5 285c911fc18cce4095df2bdb4997be96
BLAKE2b-256 6bac6f48f2c39b5ef68848479e7e4ed111e9ebcf9dc977b6ac2b239e4769d731

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.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.12.13-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 ed443ea1f0ae926e28f615bd98b274a68f29ff7082029b8c7c83cd3da52539ba
MD5 2f79bed215dd4672fc5c3d689b1f3797
BLAKE2b-256 414f326d350678cf619d828b2e50e68b991bbc20f5520741b8b65869d6abd35b

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.13-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 cdfe6220741568eff3ce8413cbd96a15c22851483dba0848f681b5483e763a26
MD5 1d256c1f68fc7cad32347fb8575e6804
BLAKE2b-256 3634e9ef0137b7100702294d951d073e1498e85ff53bf86b9f28fa75f8e564b4

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