This release is a pre-release and may not be stable for production use.
You welcome to use this tool in case you have a bug in as “hot” environment (prod, pre-prod,…) which can not reproduce it on your local IDE environment due to a chains of many HTTP or database requests
Basic steps:
- Record:
Intercept and save data from any API on data issued environment (prod, pre-prod,…)
- Fetch:
Transport intercepted data to your IDE environment.
- Replay:
Replay captured info form data environment into your IDE environment.
Repeat “Replay” step until you find a solution to the problem.
The idea is heavily inspired by vcrpy library. Here is listed some points where vcrpy does not perform well for out problem areas.
Metadata
Release files for interceporaptor 0.0.1.dev1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| interceporaptor-0.0.1.dev1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / interceporaptor-0.0.1.dev1-py3-none-any.whl
| Download URL | interceporaptor-0.0.1.dev1-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
60ab18cfa7283e31890ef4734af096d946a9c5b4cb8cc0f50f5603cb0f94fa83
|
|
BLAKE2b-256 checksum How to use checksums |
59873c19871fe03e499ae3fb456f357f10033c88a0733fd2e8e16146cb846801
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.13
|
Security for interceporaptor 0.0.1.dev1
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.