Skip to main content

# pyrefact Automatic python refactoring, with the goal of simplifying complicated code, deleting dead code, and to some extent improve performance.

It is strongly recommended that you version control or otherwise backup any code you run pyrefact on.

## Features

  • Delete unused imports

  • Move safe imports to toplevel

  • Add missing imports by guessing what you probably wanted. * For example, if Sequence is used but never defined, it will insert from typing import Sequence at the top of the file.

  • Rename variables, functions and classes with conventions.

  • Delete unused functions, classes and variables.

  • Remove most pointless simple statements.

  • Remove branches of code that obviously do nothing useful.

  • Remove unreachable code.

  • Replace hardcoded inlined collections and comprehensions with set or generator equivalents in places where that would improve performance.

  • Remove redundant chained calls involving sorted(), set(), tuple(), reversed() and list().

  • Replace sorted()[:n] with heapq.nsmallest, replace sorted()[0] with min

  • Rename unused variables to _

  • Delete variables named _, unless where that would cause a syntax error.

  • Move code into primitive functions.

  • Remove duplicate function definitions.

  • Remove redundant elif and else.

  • Use is for comparisons to None, True and False instead of ==.

  • Remove unused self and cls function arguments, and add @staticmethod or @classmethod.

  • Move functions decorated with @staticmethod outside of their class namespaces.

  • Run black and isort with –line-length=100. (Will be removed in a future release)

  • More to come!

## Usage

`bash pip install pyrefact python -m pyrefact /path/to/filename.py --preserve /path/to/module/where/filename/is/used `

When running, pyrefact will do a number of different fixes in sequence after eachother. The intention of how these fixes are ordered is not to create a pretty result in the end, but for the earlier steps to expose patterns that later steps of pyrefact can re-refactor. While this typically works well, it is also the case that some steps of pyrefact (especially when creating abstracted functions) have a way of creating new problems that the earlier steps would have solved. Therefore, my advice is that you manually re-run pyrefact until convergence.

## Prerequisites

Many features require python>=3.9 to work, and pyrefact is not tested with earlier python versions. Some effort is made for it not to crash on 3.8, but most of the cool stuff is disabled.

Metadata

Release files for pyrefact 28

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

Source distribution (sdist)

Source distribution for pyrefact 28
File Size Uploaded Provenance Actions
pyrefact-28.tar.gz 29.5 kB Without provenance Details for pyrefact-28.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for pyrefact 28
File Interpreter ABI Platform Actions
pyrefact-28-py3-none-any.whl Python 3 none any Details for pyrefact-28-py3-none-any.whl

Total release size: 61.6 kB

Release files / pyrefact-28.tar.gz

Download URL pyrefact-28.tar.gz
Size 29.5 kB
Tags Source
SHA-256 checksum
How to use checksums
3b3aee654a56a185ce994b42c930ff36073cccb11ca0b766dcf9800abd72ff82
BLAKE2b-256 checksum
How to use checksums
9f74dbb32c5b65253d1f10bc38b7b857d6ef69afe6942fdf12323df99c85ac72
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.9.15

Release files / pyrefact-28-py3-none-any.whl

Download URL pyrefact-28-py3-none-any.whl
Size 32.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0923c5770840ca05227e07f8ab5a199ba633fc7100774f66be7295479aa892c2
BLAKE2b-256 checksum
How to use checksums
674db843c2d6c8b76217f2da1cefa2cf9cb4be951e75ed7fc6ab926ba51e4ee3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.9.15

Security for pyrefact 28

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.

Release history Release notifications | RSS feed

This release

28 This release

2 release files No provenance

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