muts_core
Mutations from mutmut:
- Number + 1
- str -> XXstrXX
- lambda x: ... -> lambda x: None, lambda x: 0
- dict(a=b, c=d) -> dict(aXX=b, c=d), dict(a=b, cXX=d)
- foo(a, b) -> foo(b), foo(a)
- a.lower() -> a.upper()
- Remove any unary operators
- is -> is not, is not -> is, in -> not in, not in -> in, break -> return, continue -> break
- True -> False, False -> True, deepcopy -> copy
- This mapping:
{ cst.Plus: cst.Minus, cst.Add: cst.Subtract, cst.Minus: cst.Plus, cst.Subtract: cst.Add, cst.Multiply: cst.Divide, cst.Divide: cst.Multiply, cst.FloorDivide: cst.Divide, cst.Modulo: cst.Divide, cst.LeftShift: cst.RightShift, cst.RightShift: cst.LeftShift, cst.BitAnd: cst.BitOr, cst.BitOr: cst.BitAnd, cst.BitXor: cst.BitAnd, cst.Power: cst.Multiply, cst.AddAssign: cst.SubtractAssign, cst.SubtractAssign: cst.AddAssign, cst.MultiplyAssign: cst.DivideAssign, cst.DivideAssign: cst.MultiplyAssign, cst.FloorDivideAssign: cst.DivideAssign, cst.ModuloAssign: cst.DivideAssign, cst.LeftShiftAssign: cst.RightShiftAssign, cst.RightShiftAssign: cst.LeftShiftAssign, cst.BitAndAssign: cst.BitOrAssign, cst.BitOrAssign: cst.BitAndAssign, cst.BitXorAssign: cst.BitAndAssign, cst.PowerAssign: cst.MultiplyAssign, cst.LessThan: cst.LessThanEqual, cst.LessThanEqual: cst.LessThan, cst.GreaterThan: cst.GreaterThanEqual, cst.GreaterThanEqual: cst.GreaterThan, cst.Equal: cst.NotEqual, cst.NotEqual: cst.Equal, cst.And: cst.Or, cst.Or: cst.And, }
- mutate all augmented assignments (+=, *=, |=, etc.) to normal = assignments
- mutate
a = btoa = Noneanda = Noneto `a = "" - Drop the case statements in a match.
Example prompt (in Russian):
Я запустил мутационное тестирование и узнал, что если мы в файле @awaits/utils/end_of_wrappers.py в 15 строке мы заменим 0 на 2 - этого мутанта наши тесты не убивают. Напиши ОДИН тест, который его убьет. Для этого тебе нужно 1. понять общую логику этого участка кода; 2. понять, как она ломается, если мы сделаем это изменение; 3. временно изменить этот участок кода и попробовать запустить тесты, убедиться, что не падают; 4. написать тест, который проверяет ту логику, которую ты выявил, он должен падать; 5. "починить" код, который ты сломал, и убедиться, что тест больше не падает; 6. если не сработало - попробуй вернуть все как было и снова начать с 1 пункта, но придумать другую гипотезу, и так по кругу, пока не получится (сами гипотезы где-то записывай, чтобы не повторяться). В итоге должен получиться ОДИН новый тест (убедись, что он всего один!), все остальное состояние репозитория должно остаться нетронутым.
Metadata
Release files for mutating-core 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mutating_core-0.0.1.tar.gz | 9.4 kB | With provenance | Details for mutating_core-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mutating_core-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for mutating_core-0.0.1-py3-none-any.whl |
Total release size: 18.7 kB
Release files / mutating_core-0.0.1.tar.gz
| Download URL | mutating_core-0.0.1.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4379fe9f39298aff1bcd3d1e319b420a2371cd74cb9a82ec6b6cebeac3b02074
|
|
BLAKE2b-256 checksum How to use checksums |
5da9c74a59643cdac3581997f9d273cfd2d1684c8185c4f3857000737b2131d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 25, 2026.
Transparency logRelease files / mutating_core-0.0.1-py3-none-any.whl
| Download URL | mutating_core-0.0.1-py3-none-any.whl |
|---|---|
| Size | 9.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2464e784f1f62bf09dd332230a04ebc413d50257fdc080f9e7896f436dce2b3
|
|
BLAKE2b-256 checksum How to use checksums |
d730f2ab8a4c4afc373a7c9b4c617288c715b14f1927e9cb3de7652b1885ebd9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 25, 2026.
Transparency logSecurity for mutating-core 0.0.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for mutating_core-0.0.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 Mar 25, 2026.
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.