Skip to main content

# lumigo-python-wrapper :stars:

![CircleCI](https://circleci.com/gh/lumigo-io/lumigo-python-wrapper/tree/master.svg?style=svg&circle-token=d98d1b95f34b49be2caa58c49d8a70d6a7587b88) ![Version](https://badge.fury.io/py/lumigo-python-wrapper.svg) ![codecov](https://codecov.io/gh/lumigo-io/lumigo-python-wrapper/branch/master/graph/badge.svg?token=d8CvqyKTnq)

This is [lumigo-python-wrapper](https://), Lumigo’s Python tracer for distributed tracing and performance monitoring.

Supported Python Runtimes: 3.6, 3.7, 3.8

# Usage

# Manually

## Configuration @lumigo/lumigo_python_wrapper offers several different configuration options. Pass modify the environment variables:

  • LUMIGO_DEBUG=TRUE - Enables debug logging

  • LUMIGO_SECRET_MASKING_REGEX=[“regex1”, “regex2”] - Prevents Lumigo from sending keys that match the supplied regular expressions. All regular expressions are case-insensitive. By default, Lumigo applies the following regular expressions: [“.*pass.*”, “.*key.*”, “.*secret.*”, “.*credential.*”, “.*passphrase.*”].

# Contributing

Contributions to this project are welcome from all! Below are a couple pointers on how to prepare your machine, as well as some information on testing.

## Preparing your machine Getting your machine ready to develop against the package is a straightforward process:

1. Clone this repository, and open a CLI in the cloned directory 1. Create a virtual environment for the project virtualenv venv -p python3 1. Activate the virtualenv: . venv/bin/activate 1. Install dependencies: pip install -r requirements.txt 1. Navigate to the source directory: cd src and 1. Run the setup script: python setup.py develop. 1. Run pre-commit install in your repository to install pre-commit hooks

Note: If you are using pycharm, ensure that you set it to use the virtualenv virtual environment manager. This is available in the menu under PyCharm -> Preferences -> Project -> Interpreter

## Running the test suite We’ve provided an easy way to run the unit test suite: * Run ./scripts/checks.sh in the root folder.

Metadata

Release files for lumigo-python-wrapper 0.3.14

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for lumigo-python-wrapper 0.3.14
File Interpreter ABI Platform Actions
lumigo_python_wrapper-0.3.14-py3-none-any.whl Python 3 none any Details for lumigo_python_wrapper-0.3.14-py3-none-any.whl

Release files / lumigo_python_wrapper-0.3.14-py3-none-any.whl

Download URL lumigo_python_wrapper-0.3.14-py3-none-any.whl
Size 16.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8735e7fdb494f3531e662e64c0e2ca9813410c82ea9245421fbc100de41702cc
BLAKE2b-256 checksum
How to use checksums
b37632f4b00217f3f3a4554e0a689fd6dd38126b8cf059fd7f5a520727075150
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.0 CPython/3.7.4

Security for lumigo-python-wrapper 0.3.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page