The repository or configuration that created this release differ from a previous release. View details.
pysource-minimize
If you build a linter, formatter or any other tool which has to analyse python source code you might end up searching bugs in pretty large input files.
pysource_minimize is able to remove everything from the python source which is not related to the problem.
CLI
You can use pysource-minimize from the command line like follow:
pysource-minimize --file bug.py --track "Assertion" -- python bug.py
This executes python bug.py and tries to find the string “Assertion” in the output.
The ---file bug.py will be minimized as long as “assertion” is part of the output of the command.
The --file option can be specified multiple times and there is also an --dir option which can be used to search directories recursively for Python files.
[!WARNING] Be careful when you execute code which gets minimized. It might be that some combination of the code you minimize erases your hard drive or does other unintended things.
API
Example for single files:
>>> from pysource_minimize import minimize
>>> source = """
... def f():
... print("bug"+"other string")
... return 1+1
... f()
... """
>>> print(minimize(source, lambda new_source: "bug" in new_source))
"""bug"""
This example minimizes multiple files and searches for sets which have 2 common elements:
>>> from pathlib import Path
>>> from typing import Dict
>>> from pprint import pprint
>>> from pysource_minimize._minimize import minimize_all
>>> sources = {
... Path(
... "a.py"
... ): """\
... l={1,81894,9874,89228,897985,897498,9879,9898}
... """,
... Path(
... "b.py"
... ): """\
... l={5,81894,9274,89218,897985,897298,9879,9898}
... """,
... Path(
... "c.py"
... ): """\
... l={0,81894,9874,89218,897985,897498,9879,9298}
... """,
... }
>>> def check(sources: Dict[Path, str | None], current_filename: Path) -> bool:
... # current_filename can be used for progress output
... # print(f"working on {current_filename} ...")
... sets = []
... for source in sources.values():
... if source is not None:
... globals = {}
... try:
... exec(source, globals)
... except:
... return False
... if "l" not in globals:
... return False
... sets.append(globals["l"])
... return (
... len(sets) >= 2
... and all(isinstance(s, set) for s in sets)
... and len(set.intersection(*sets)) >= 2
... )
...
>>> pprint(minimize_all(sources, checker=check))
{PosixPath('a.py'): None,
PosixPath('b.py'): 'l = {81894, 0}',
PosixPath('c.py'): 'l = {0, 81894}'}
You might think that there are no two zeros in the original sets.
This problem can occur if your check function is not specific enough.
pysource-minimize tries to minimize numbers and strings, does so for one of the sets and finds that it satisfies your check.
It generates new code during the minimization and can only use the check function to know if the solution is correct.
This kind of problem can be solved by using a more precise check function or a --track argument when using the CLI.
For example, you can add a check that all numbers in the set must be non-zero.
However, this problem will not occur if you are looking for real minimal examples that throw certain exceptions.
The worst that can happen here is that pysource-minimize finds another example that triggers the same problem.
fixed check function
>>> from pathlib import Path
>>> from typing import Dict
>>> from pprint import pprint
>>> from pysource_minimize._minimize import minimize_all
>>> sources = {
... Path(
... "a.py"
... ): """\
... l={1,81894,9874,89228,897985,897498,9879,9898}
... """,
... Path(
... "b.py"
... ): """\
... l={5,81894,9274,89218,897985,897298,9879,9898}
... """,
... Path(
... "c.py"
... ): """\
... l={0,81894,9874,89218,897985,897498,9879,9298}
... """,
... }
>>> def check(sources: Dict[Path, str | None], current_filename: Path) -> bool:
... # current_filename can be used for progress output
... # print(f"working on {current_filename} ...")
... sets = []
... for source in sources.values():
... if source is not None:
... globals = {}
... try:
... exec(source, globals)
... except:
... return False
... if "l" not in globals:
... return False
... sets.append(globals["l"])
... return (
... len(sets) >= 2
... and all(isinstance(s, set) for s in sets)
... and len(result := set.intersection(*sets)) >= 2
... and 0 not in result
... )
...
>>> pprint(minimize_all(sources, checker=check))
{PosixPath('a.py'): None,
PosixPath('b.py'): 'l = {81894, 89218}',
PosixPath('c.py'): 'l = {81894, 89218}'}
Sponsors
I would like to thank my sponsors. Without them, I would not be able to invest so much time in my projects. If you want, you can also support my work.
Bronze sponsor 🥉
Metadata
Release files for pysource-minimize 0.10.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
The repository or configuration that created these release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pysource_minimize-0.10.1.tar.gz | 9.3 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pysource_minimize-0.10.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.3 MB
Release files / pysource_minimize-0.10.1.tar.gz
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | pysource_minimize-0.10.1.tar.gz |
|---|---|
| Size | 9.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05000b5174207d10dbb6da1a67a6f3a6f61d295efa17e3c74283f0d9ece6401c
|
|
BLAKE2b-256 checksum How to use checksums |
03e614136d4868c3ea2e46d7f83faef26d07fd9231b7bd3fc811b6b6f8688cf2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 30, 2025.
Transparency logRelease files / pysource_minimize-0.10.1-py3-none-any.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | pysource_minimize-0.10.1-py3-none-any.whl |
|---|---|
| Size | 18.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
69b41fd2f0c1840ca281ec788c6ffb4e79680b06c7cc0e7c4d9a75321654b709
|
|
BLAKE2b-256 checksum How to use checksums |
f5de847456f142124b242933a1cea17aea7041d297f1ac99b411c5dee69ac250
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 30, 2025.
Transparency logSecurity for pysource-minimize 0.10.1
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.
Change of provenance
The configuration that created this release differs from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Configuration
- Removed 0.10.0 ci.yml
- Added 0.10.1 create-release.yml
Attestation for pysource_minimize-0.10.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 30, 2025.
Transparency logA 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.