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

Uploaded CPython 3.12Windows x86-64

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

Uploaded CPython 3.12macOS 11.0+ ARM64

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

Uploaded CPython 3.11Windows x86-64

everysk_lib-1.12.10-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.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.12.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.12.10.tar.gz.

File metadata

  • Download URL: everysk_lib-1.12.10.tar.gz
  • Upload date:
  • Size: 230.7 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.10.tar.gz
Algorithm Hash digest
SHA256 49001cd3eb92844e420db99bb2f84a1adfdb8936125a504b380641c7b2485525
MD5 811d73bfdfa602b030fa3b2ec7c1aea1
BLAKE2b-256 3baf14aaa8577e38806007cf4f11b30a66814f661984220c7f0d2d7c680c0945

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.10-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 0db0b1cbfa87867728daada4d8954f7d6123753334e71a898ae8fc65047a7ef0
MD5 928186cd5c4ca4b4d242f544d69e0341
BLAKE2b-256 7f070a02e71d6c0573232c6c3c3715a10f8749eff37efc7811598d8e33f4fc37

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.10-cp312-cp312-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 2d1d241fa3d9931b2e5ef0945c08da57fa4d984204421d445a2a458c4a81debd
MD5 9741776046b506674c226b1313b97503
BLAKE2b-256 3974a8070f6cfdbaa7f3ed1b22e724c81d5b5546fcabbdb6e7780335008407f1

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.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.12.10-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 250e996779523d9a7ac7082b648c9e8570e47c52d45c75dc65eb016bc6fe2053
MD5 4c1d15883d433edc545ee19733dbb3f7
BLAKE2b-256 587d079e42ec23963b25cc11c98927a4176d06bb7aabb85ff6af0cc3761dcf73

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.10-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 83b15e6c92fca3ab053c431b98c8d03194f2ce6acff0cd88c62b034dc2683e99
MD5 701aaaa969338ec9d48b0599149c64d8
BLAKE2b-256 2c177fa68c45bf7e6f41e4acfdfe558bcdeed6258b41eeba06d95d06456a679f

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.10-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 c4451df919dfd22757da62aaeef5a1c541a0af20f50a00114d4090d3c6fea3c1
MD5 2ce51cb15af0752bcba2bbb93a84ec11
BLAKE2b-256 a87353fff88fa8f05002e845d828eb6fa481eb61cf05112542426661dadf4dd3

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.10-cp311-cp311-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 9305fcc2b6dda5c1087fd6dbc1ab6d40211715e5044675ada17efab89f8b44a6
MD5 658031cf1bd64ab49e19d10f344722a4
BLAKE2b-256 61d7881ff0936624fe0c6e2a0279385cc49f3a43a790d0c41ce6b6583b0c7d31

See more details on using hashes here.

File details

Details for the file everysk_lib-1.12.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.12.10-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 1cf33d2e8dda4232050ba3d09815602725ea348401db3a436a02eb174a02a614
MD5 0afc6365eba4728048c72011ce67cfa5
BLAKE2b-256 5971d3911f11ef38e3f0852aea727639b46a21e21c517c7043598d3b5d90ef95

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.12.10-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 628af133c4e6cc30ce7d89cfd062c07916ef0ba2a081fa18e8b65a3a037acfdf
MD5 68bbc39a553a9273f738a0637aa1134a
BLAKE2b-256 1a7c09fde08d9a35b2e219195d00a067e2d1fc7162cce6ab3c3642556cb32dc2

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