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

Uploaded CPython 3.12Windows x86-64

everysk_lib-1.11.12-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.12-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.12-cp312-cp312-macosx_11_0_arm64.whl (2.0 MB view details)

Uploaded CPython 3.12macOS 11.0+ ARM64

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

Uploaded CPython 3.11Windows x86-64

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

File metadata

  • Download URL: everysk_lib-1.11.12.tar.gz
  • Upload date:
  • Size: 233.2 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.11.12.tar.gz
Algorithm Hash digest
SHA256 c790f985b0fb25022ee1b5cdb55be2095f2c7eb28acfe8a10daf4dbcf1ba5917
MD5 9515309eae053a7abbdf8bd3b132b7ba
BLAKE2b-256 ddecac7b2c63561510e476069383d38f1c628049aa8d49a1a4f82fbd424ea98c

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.12-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 e786ca6d8152dd3d17801ffd0a9407e816e6a3beb6612c72ea3077f835c1cf4c
MD5 ca611a7111985b9d850115cc9c5f7913
BLAKE2b-256 f9701c83f2bf3d97e3a2c53ae84f5c8181cf6883d68426d5a065199f99a92f91

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.12-cp312-cp312-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 68113270113fbc474425a3e4f290e5a44c12754a5a0c1b814bf85a1acfb84643
MD5 eda833b99fe74f0725f19045ebb877b0
BLAKE2b-256 d275c7a6e7148e7bbebe0275444a729da819d3f81d12c41245b0325f1b8e5f00

See more details on using hashes here.

File details

Details for the file everysk_lib-1.11.12-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.12-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 ccd58d9d611194b46ab19ecfcaf7f438cf17bb511579661143c83a56abe89c3d
MD5 add22219d99ca73b41ee6d3a42f72644
BLAKE2b-256 a678f446ac32ce2ddb10971d22a7a87bdf9b6b1a5064e29c4a0fde3ee98bf1c9

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.12-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 d65e60d316f783792bcd00a1d76f411e5a690a5c4ad0aeb3291e76899088b651
MD5 bc312c4a248887acde2dd91fa28c23d6
BLAKE2b-256 bd07bc9f31049f16d6c3d250b2db2efa3738b0266eacd060985d847aded1a5eb

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.12-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 4678539ec84f398dea6ca1c6ad122d8597784761f4ecffd234429d2bbf72c5d6
MD5 0e4a9edf04fce9b1b0a2511b19fc97ab
BLAKE2b-256 69179afdaf91126e1f831de55af95940ce12e3ffaf09c39fe07d8cbb3492ee2c

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.12-cp311-cp311-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 fad219e8855ab86a9d9271074b39eb2f6a1329dd81d0909f874c30b73d3d8055
MD5 06a51e6fcf7ffdf8ecaf5d216d458006
BLAKE2b-256 42db28a5c96e08605a8c87268d24f67a11a4284a440187ce1c95bbd7fda04a11

See more details on using hashes here.

File details

Details for the file everysk_lib-1.11.12-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.12-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 e15c2f59798603d2f01086fb06da1fca908642d3a1be127ded8b5ead37cf516c
MD5 1001e5a5dd41c8cf80a213e220ef0ba3
BLAKE2b-256 0c2f02c653f9993c0ef53c4f5f29ed6228eea1c607ffe679ffd080fa6564b581

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for everysk_lib-1.11.12-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 0bf37b9fd88180d59e4ca70572780d908b54624618143278cbecda5afdd7ed6a
MD5 c139bbef8f29bf1c6c65be1b1ffe3328
BLAKE2b-256 ef74e705fb968f729bfd514468d4ccbf39941ec2b077656450d2b39b3f2f4f18

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