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

This version

1.9.9

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

Uploaded CPython 3.12Windows x86-64

everysk_lib-1.9.9-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.9-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.9-cp312-cp312-macosx_11_0_arm64.whl (1.9 MB view details)

Uploaded CPython 3.12macOS 11.0+ ARM64

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

Uploaded CPython 3.11Windows x86-64

everysk_lib-1.9.9-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.9-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.9-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.9.tar.gz.

File metadata

  • Download URL: everysk_lib-1.9.9.tar.gz
  • Upload date:
  • Size: 207.2 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.9.tar.gz
Algorithm Hash digest
SHA256 4046b245b80fb8c9c978bf6d07337a17795f409eb90eda4138e44d5c2b45d3c5
MD5 0ecbebe344f49fb7c615f203cad6a056
BLAKE2b-256 cd260e683d4bf543350a452fe503a5dd6d4ff069c02959a12a0b6b4d4c66a3df

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.9.9-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 a27afc2ef7183be321ab03a7b37920a758400418ca3ca2be7fb2e294d96d2ebf
MD5 ddb9297ace9a140b29ae7000fbdf92d6
BLAKE2b-256 bda3ddb3b18638959f96800cac2c1baaaf1324b130f77e6ee5434215e5c30684

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.9.9-cp312-cp312-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 0e10eea931dffb9132a09b61e2bb3e99fe385a2c77d6a193bd4287f21bc3aa55
MD5 d82e35da04f585567e61a136e0841cb3
BLAKE2b-256 c3ad2496077c8ab29b98f082e3f08df3c4ed236d5ef5fe50a20d0d748b677919

See more details on using hashes here.

File details

Details for the file everysk_lib-1.9.9-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.9-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 f2d7f5242f93bb6ffb6c35cd6bfb545ed317c1e7604d9dd370dbb907b28d1474
MD5 4b6bcd690bfa1c860456078ced6c3be7
BLAKE2b-256 b9738179b5c62bd34def69c22077f39c1c624fe909260932b2532d1ee81f6e43

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.9.9-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 e7e59b57f8a51f32881bfc647b1e078d1a29ce6f3414cb03a34f989650c7e2a1
MD5 68e851fb633bc0b1b1661dbb59652ba5
BLAKE2b-256 e9166b924c3ef70b94a6abb995d9d58e619094acce6af05383cbc2b2dc87889b

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.9.9-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 490ef4a0c59fd88fb879686c2be40b90d2bf9b03a069111e91b523ab2cb4a0c3
MD5 46bf49aef1555f09bb96ba58a3d8cb62
BLAKE2b-256 bfd44166bcb3e7ab91280336f24e54577425a5a97083475c844a7a26770f0d01

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.9.9-cp311-cp311-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 7ebbde479534a8bc25c50ab6800b11d2221eddb111f289a318b1c41ef21334d5
MD5 6221a34664e17eb04d7f9cf1e470d7ab
BLAKE2b-256 1372028639a82be178ac0b64f88c94a24082fc8f2ee2da63c2f72646ff53f1d8

See more details on using hashes here.

File details

Details for the file everysk_lib-1.9.9-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.9-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 374db413e4d388897c16cad0b3a25320e7b478a957919f3edb19fe7d70a26df7
MD5 69fb053b6fc5379afd9d846668286968
BLAKE2b-256 4bce2322cb887e63fb06000017217f13d1f2322df37f36404e61845a26ec1caa

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.9.9-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 8b55d26c3a02c201953a501c47be891b242c5de6e4dcb5398f94a981ec9e97e9
MD5 e863194ff66bff4d3266d85d94e0e296
BLAKE2b-256 d63c5d9349fd2da65a47d357666e3ada14a8b0b1f6b3e633464fa8526aca7b7a

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