Changelog¶
All notable changes to BetterPy are documented here. Stable CalVer releases use YYYY.MM.PATCH+BASELINE; prereleases use YYYY.MM.PATCH-channel.build. Historical stable sections may remain unsuffixed.
For the full changelog, see CHANGELOG.md on GitHub.
2026.11.3+263 - 2026-11-13¶
🚀 Features¶
- Interpreter Cleaner shows separate logical and allocated environment sizes. Both size columns sort numerically; partial logical scans are marked visibly, and tooltips explain that shared hardlinks and copy-on-write data make allocated size different from reclaimable space.
🐛 Bug Fixes¶
- Interpreter Cleaner sorts logical and allocated environment sizes by byte count instead of formatted text, correctly ordering mixed units and updating the order as size measurements finish.
- Interpreter Cleaner measures the target environment's allocated size when its root directory is a symlink, instead of reporting only the link's allocation.
request.getfixturevalue("name")now follows local aliases (req = request) and helper parameters that receiverequestat same-file call sites, and accepts parameters annotatedFixtureRequest/SubRequest. A locally shadowedrequestis no longer treated as the pytest request.
2026.11.2+263 - 2026-11-12¶
Interpreter Cleaner brings interpreter health and disk usage into one tool window, with safeguards for environments you still use.
🚀 Features¶
- Interpreter Cleaner lists registered Python interpreters with health status, environment type, and disk usage. Filter broken entries, highlight interpreters used by the current project, and open their directories in the file manager or terminal. Directory sizes are cached until Refresh.
- Remove broken or unsupported interpreter registrations in the background, with optional removal of leftover plain virtual-environment directories. Healthy interpreters and interpreters used by the current project or its modules are protected; managed Poetry, Pipenv, uv, Hatch, and Conda environment directories are never deleted.
🐛 Bug Fixes¶
- Mock type inference checks for a mock or class-patch origin before resolving unrelated references, avoiding recursive Python type evaluation and stack overflows during highlighting.
monkeypatch.setattrresolves attribute-name strings when a loop-variable target is inferred as a union of modules, avoiding false unresolved-reference warnings. Names absent from every candidate module remain unresolved.- Pytest fixture query caches compute resolved values outside the map lock, preventing highlighting threads from blocking each other and freezing the UI.
- Make mandatory updates the underlying type inside
Annotatedwithout losing its metadata. - Make optional preserves
Annotatedmetadata and string forward references, and recognizes types that are already nullable. Quoted forward references useT | Noneon Python 3.10+ andOptional[T]on older versions. - Expected MCP refactoring rejections, such as conflicting import-alias names, no longer create IDE error reports.
- Test/Production editor tabs dispose their global Code Vision mouse listener with the plugin service, preventing stale listeners after plugin reload.
- BetterPy's action usage listener no longer waits for a read lock on the UI thread while a write action is running, avoiding an IDE freeze.
2026.10.11+263 - 2026-10-31¶
🚀 Features¶
- Pytest configuration intelligence adds pytest 9.2 completion, validation, and native TOML value support.
- A version-gated inspection reports positional
parametrizeoptions. - A version-gated inspection reports higher-scope instance fixtures.
- A version-gated inspection reports misplaced fixture decorators.
- A version-gated inspection reports deprecated
yield_fixtureusage. -
A version-gated inspection reports unknown strict-marker
-mnames, respecting pytest's quoting and strictness rules. -
The unknown pytest fixture warning now offers Turn '
' into pytest fixture when the same file defines an undecorated, otherwise unused function with that name. The fix adds@pytest.fixtureand imports pytest when needed, without changing already-decorated functions. - BetterPy inspections now use PyCharm-style dash suppression codes. Suppress for … writes, for example,
# noinspection pytest-fixture-override-contract. Existing comments using the previous CamelCase IDs must be updated; inspection profiles and severities are unchanged.
🐛 Bug Fixes¶
- Pytest configuration diagnostics handle decoded TOML values, inline/dotted tables, INI-mode scalar conversions, and Python-style integer strings more accurately. Option catalogs are isolated by working directory, and unrelated completion requests no longer start pytest probes.
- Pytest configuration debug logging now includes option-catalog loading and pytest version resolution.
- Previously offered positional-to-keyword quick fixes now leave source and usage tracking unchanged after the inspection is disabled.
- Use actual test outcome imports class, constructor, and enum values from the correct module, reuses valid aliases and re-exports, and avoids names shadowed by local parameters or assignments. Ambiguous unqualified symbols remain unchanged rather than importing the wrong value.
- Pytest version detection follows each file's interpreter and refreshes after interpreter, package, and configuration changes. Fixture bindings are invalidated after
minversionedits, and authoritative interpreter probe results are preserved. - Parametrized run gutters use conservative pytest 9.2 predictions for long-string IDs, preserving explicit IDs and the
legacystrategy rather than guessing uncertain node IDs. - Quick fixes for unused pytest parametrization arguments now show the consistent
BetterPy:prefix in the intention menu. - Private-module import quick fixes now show the consistent
BetterPy:prefix in the intention menu. - Redundant-suppression detection recognizes the new dash-style suppression codes, and its quick fixes use the consistent
BetterPy:prefix. - Failed-test highlighting no longer offers inspection-suppression actions; suppressing the diagnostic cannot change the recorded test result.
2026.10.8+263 - 2026-10-26¶
🐛 Bug Fixes¶
- Internal test stability and CI reliability improvements; no user-facing changes.
2026.10.7+263 - 2026-10-26¶
🚀 Features¶
- The unused pytest parameter inspection now offers Capture unused parameters, adding an explicit assignment while preserving parametrization, test cases, and docstrings. When
_is already in use, the quick fix and capture intention choose a non-conflicting target. - Renaming a collected pytest function, method, or class initially selects only its descriptive name, preserving prefixes such as
test_andTest. Custompython_functionsandpython_classespatterns are respected, and the full identifier remains editable in both inline rename and the rename dialog.
🐛 Bug Fixes¶
- Inline bare tuple return now shows a conflict dialog for usages it cannot rewrite, so you can cancel or proceed instead of silently leaving those usages unchanged.
- The BetterPy status-bar menu remains accessible when the Python SDK is missing or unsupported, keeping Settings, diagnostics, and feature recovery controls available.
- The BetterPy status icon rechecks Python support in the background when hovered, recovering from a grey disabled indicator left behind while the interpreter was still initializing.
- Previewing Create pytest fixture no longer triggers an event-dispatch-thread error from undo listeners.
- Mock patch recognition no longer resolves unrelated calls with complex qualifiers, such as
get_client().patch(...)or Cython casts, preventing Python type errors while preservingpatch,mock.patch,unittest.mock.patch, andpatch.objectsupport. - Property usage counts avoid type inference on complex qualifiers such as subscript results and Cython casts, preventing Python type errors during Code Vision updates. Simple constructor calls and parenthesized calls such as
(Foo()).dataremain counted; qualifier chains containing calls are excluded from the typed fallback. - Name-string navigation and rename for
NewType,TypeVar, andParamSpecnow recognize aliases imported in function and class scopes and custom re-exports, without triggering type inference for unrelated calls. - Alias usage searches avoid resolving unrelated assignments and preserve class-attribute aliases with parenthesized reference qualifiers such as
(Source).data. - Alias usage searches skip Cython files (
.pyx,.pxd), preventing Python type errors during module-assignment usage Code Vision updates. - Direct test parametrization now replaces same-named fixture dependencies, including dependencies requested through another fixture. Fixture navigation, typing, usages, diagnostics, and alias intentions account for each test's overrides while preserving indirect parametrization.
- Fixture binding analysis now recognizes positional
indirectarguments, inherited class marks, and the final effectivepytestmarkassignment. - Fixture resolution and usage searches avoid repeated scans and limit local autouse-fixture analysis to its applicable files, improving responsiveness in large pytest projects.
- Parametrize argnames used through fixture dependencies,
usefixtures, or autouse fixtures no longer receive missing-parameter or unused-argument warnings. - Capturing unused parameters no longer overwrites an existing
_parameter or shadows_references; the quick fix and capture intention choose a non-conflicting target. -
Changes to pytest configuration can no longer leave stale collection patterns cached when a background lookup races with a configuration edit.
-
Pytest plugin discovery no longer keeps closed projects in memory through global caches.
2026.10.6+263 - 2026-10-25¶
🚀 Features¶
- The unused pytest parameter inspection now offers Capture unused parameters, adding an explicit assignment while preserving parametrization, test cases, and docstrings. When
_is already in use, the quick fix and capture intention choose a non-conflicting target. - Renaming a collected pytest function, method, or class initially selects only its descriptive name, preserving prefixes such as
test_andTest. Custompython_functionsandpython_classespatterns are respected, and the full identifier remains editable in both inline rename and the rename dialog.
🐛 Bug Fixes¶
- Inline bare tuple return now shows a conflict dialog for usages it cannot rewrite, so you can cancel or proceed instead of silently leaving those usages unchanged.
- The BetterPy status-bar menu remains accessible when the Python SDK is missing or unsupported, keeping Settings, diagnostics, and feature recovery controls available.
- The BetterPy status icon rechecks Python support in the background when hovered, recovering from a grey disabled indicator left behind while the interpreter was still initializing.
- Previewing Create pytest fixture no longer triggers an event-dispatch-thread error from undo listeners.
- Mock patch recognition no longer resolves unrelated calls with complex qualifiers, such as
get_client().patch(...)or Cython casts, preventing Python type errors while preservingpatch,mock.patch,unittest.mock.patch, andpatch.objectsupport. - Property usage counts avoid type inference on complex qualifiers such as subscript results and Cython casts, preventing Python type errors during Code Vision updates. Simple constructor calls and parenthesized calls such as
(Foo()).dataremain counted; qualifier chains containing calls are excluded from the typed fallback. - Name-string navigation and rename for
NewType,TypeVar, andParamSpecnow recognize aliases imported in function and class scopes and custom re-exports, without triggering type inference for unrelated calls. - Alias usage searches avoid resolving unrelated assignments and preserve class-attribute aliases with parenthesized reference qualifiers such as
(Source).data. - Alias usage searches skip Cython files (
.pyx,.pxd), preventing Python type errors during module-assignment usage Code Vision updates. - Direct test parametrization now replaces same-named fixture dependencies, including dependencies requested through another fixture. Fixture navigation, typing, usages, diagnostics, and alias intentions account for each test's overrides while preserving indirect parametrization.
- Fixture binding analysis now recognizes positional
indirectarguments, inherited class marks, and the final effectivepytestmarkassignment. - Fixture resolution and usage searches avoid repeated scans and limit local autouse-fixture analysis to its applicable files, improving responsiveness in large pytest projects.
- Parametrize argnames used through fixture dependencies,
usefixtures, or autouse fixtures no longer receive missing-parameter or unused-argument warnings. - Capturing unused parameters no longer overwrites an existing
_parameter or shadows_references; the quick fix and capture intention choose a non-conflicting target. - Changes to pytest configuration can no longer leave stale collection patterns cached when a background lookup races with a configuration edit.
2026.10.5+263 - 2026-10-16¶
🐛 Bug Fixes¶
- Fixed
FileEditorOpenRequestclass-loading failures on newer PyCharm 2026.3 EAP builds by using the public asynchronous editor API. Tab moves and layout restoration now await editor opening and caret navigation; the 263 plugin requires build263.6800.43or newer. - Test/Production editor tabs now classify Python stub files (
.pyi) and route same-kind stub navigation to the opposite split like.pyfiles. - Navigation across test/production editor splits now preserves the target caret and centers the destination; Search Everywhere navigation continues to use the intended split.
- Status-bar environment refreshes now coalesce per widget and cancel when their presentation scope ends, preventing stale icon updates and queued root-change probes from leaking past disposal.
- Top-level Extract Function now remains available through the platform Extract Method action on PyCharm 2026.2 and later, where the Python provider no longer exposes its legacy extraction handler.
- Console links now use supported platform navigation APIs on newer PyCharm builds and wait for the destination editor to open before updating its location.
[2026.10.1+263] - 2026-10-09¶
BetterPy adds Extract Function to Scope as an incubating refactoring to extract Python expressions or statements into functions, classes, or modules, adds a status-bar toggle for contextual feature tips, and improves mock assertions and type inference.
🚀 Features¶
- Extract Function to Scope extracts selected expressions or statements into a named helper in the current function, an enclosing function, or the module.
- Contextual feature tips can now be enabled or disabled directly from the BetterPy status-bar menu.
- Mock assertion methods now resolve
assert_called_onceand async await assertions on methods spied withmocker.spy(instance, "method"). - Report unexpected arguments for autospecced
patch.objectmethods. - Class-based mock specs now validate method-call and recorded-call assertion arguments by default, without requiring
autospec=True. Turn off Validate arguments when spec is a class in Mock type provider settings or use the contextual class-spec tip to disable the additional checks; autospec validation remains active.
🐛 Bug Fixes¶
- Fixed false missing-argument warnings on method assertions for instances created from autospecced class patches.
- Python navigation bar breadcrumbs render overload declarations by name instead of raw
PyFunction(...)text, while member lists still hide duplicate overloads. - Autospecced decorator assertions now preserve class and bound-instance receiver arguments without shifting type diagnostics onto the mock assertion qualifier.
monkeypatch.setattr(module, "name", value)now resolves module-level imports, including aliases, instead of reporting false unresolved references. Missing symbols remain errors.mocker.spy(receiver, "method")now resolves subscription receivers whose types require cross-file inference, avoiding false unresolved method-name strings. Missing methods remain errors.- Mock side-effect compatibility now checks keyword values forwarded through
**kwargs, recognizes the final definition of redefined callbacks, and ignores constant-falsespec/spec_setvalues - Fixture parameter typing now prioritizes BetterPy's resolved fixture value, so local overrides retain their type when a plugin provides the same fixture name.
- Autouse fixture consumer analysis now restores functions from the current PSI file provider during nested reference searches, preventing invalid-PSI errors while processing
conftest.py. - Plugin fixture styling now follows the effective provider; local overrides no longer inherit the plugin color.
- Fixture rename no longer invokes text-occurrence methods that are unresolved on affected PyCharm 2026.3 builds.
- Fixture Quick Documentation now includes return-class docstrings when the fixture has no docstring and preserves docstrings for methods accessed through fixture arguments.
- Quick Documentation on a fixture receiver in a member access keeps the fixture's documentation instead of switching to the enclosing method.
- “Copied from” notices in fixture Quick Documentation now link to the source class.
- Test/Production editor tabs now uses the full editor area for diffs and restores duplicate tabs, pins, and editor state on return.
- Navigation across test/production editor splits now preserves the target caret and centers the destination; Search Everywhere navigation continues to use the intended split.
- New pytest fixture previews no longer open a nested write command while generating the fixture.
- Pytest missing assert inspection now recognises standard
unittest.mockassertion calls on pytest fixture values. - Change visibility is no longer offered on assignments in a method's own scope; declarations and nested class-scope assignments remain available.
- Autospecced
patch.objectcall assertions now validate arguments against the patched method signature instead of exposingNonCallableMock's unboundSelfparameter. - Autospecced
patch.objectdecorator parameters and context-manager aliases now check assertion arguments, retaining explicit receivers for class targets and bound signatures for instance targets. Stacked patch decorators map mocks before trailing pytest fixture parameters. @patch("package.Class", autospec=True)now exposes mock helpers on instances constructed through the patched module binding; previously imported class aliases remain bound to the original class.- Class-based
spec_setsignatures now take precedence overspec, recorded-call checks recognizeMocksubclasses, and method return-value children no longer inherit the original class's method signatures. - Mock inference and assertion helpers for
patch.objectnow apply only while the patch is active and, for instance patches, only to the patched receiver. - Mock string references make
mocker.spy(instance, "method")names navigable and rename-aware, and retain standalonemock.patchreferences on newer IDEs without duplicating native ones.
2026.09.4 - 2026-09-18¶
BetterPy adds pytest fixture pull-up and push-down refactorings to widen or narrow fixture availability, and improves test-file renaming, fixture deletion, and Protocol implementation discovery.
🚀 Features¶
- Pull Up pytest fixture moves a class fixture to module level, a test-module fixture to its local
conftest.py, or a conftest fixture to the parent directory. Required imports and referenced helpers accompany the fixture, with preview and conflict checks before changes are applied. - Push Down pytest fixture moves or copies fixtures into test classes, sibling test modules, or child conftests. Consumer-aware destination selection supports multiple child directories and retains the source fixture when consumers still need it outside the selected destinations.
- Pytest file renaming now preselects only the editable test-file stem rather than the pytest prefix or extension. For example, renaming
test_login.pyselectslogin; custompython_filespatterns such ascheck_*.pyare respected too.
🐛 Bug Fixes¶
- Safe delete unused fixture now removes imports left unused by the deleted fixture while preserving imports needed by remaining code, quoted annotations, exports, and fixture injection. Undo restores the fixture and removed imports together.
- Class implementations Code Vision finds more valid Protocol implementations, including nested classes, instance attributes, inherited members, and generic or callable matches, while excluding unrelated Protocol descendants and respecting the search scope.
2026.09.3 - 2026-09-12¶
BetterPy adds redundant inspection-suppression detection and improves mock and pytest typing across supported PyCharm versions.
Features¶
- Unnecessary inspection suppressions (PY-45308) highlights redundant IDs in Python
# noinspectioncomments and removes only the selected ID, preserving the comment prefix and trailing explanation. Detection supports PyCharm's comment formats and kebab-case inspection IDs. On PyCharm build 263.3889.77 and later, the IDE provides equivalent behavior and BetterPy steps aside.
Bug Fixes¶
-
Jump to pytest node in test tree no longer resolves test locations on the event-dispatch thread while refreshing test results.
-
Mock typing preserves spec method return types, including async and chained calls, across PyCharm 2026.1, 2026.2, and 2026.3 EAP. Parameters injected by patch decorators are correctly typed as mocks rather than patchers.
- Mock assertion methods no longer produce incorrect implicit-self argument warnings on PyCharm 2026.3 EAP.
- Pytest fixture typing restores inference fallbacks when the IDE returns an explicit unknown type and recognizes additional
NoneTyperepresentations when handling optional fixture values. - Constant Final inspection generates valid
Anyannotations when a constant's inferred type is unknown. - UV script runner no longer fails while checking a run context whose source element has no containing file.
- MCP integration keeps tools available if feature-state lookup fails during a plugin reload.
2026.09.2 - 2026-09-08¶
This patch release adds direct bare tuple-return inlining while preserving Python expression grouping, fixes dynamic pytest action registration, and offers preliminary compatibility with PyCharm 263 EAP builds.
🚀 Features¶
- Unnecessary inspection suppressions (PY-45308) highlights redundant inspection IDs in Python
# noinspectioncomments and removes only the selected ID. - Inline bare tuple return directly inlines a function with one bare tuple return while preserving tuple grouping and avoiding a synthetic result variable.
🐛 Bug Fixes¶
- Pytest collection-pattern IDE integration no longer reports an action-registration error when the plugin is loaded dynamically; run-context filtering now overrides the stable parent group while preserving platform additions.
[2026.09.1] - 2026-09-06¶
This patch release improves pytest fixture navigation and parametrized test execution while extending compatibility to PyCharm 2026.3 EAP.
🐛 Bug Fixes¶
- Fixture Go to Type Declaration now offers every inferred class target when a fixture can return or yield multiple types, including navigation from fixture parameters and references in test bodies. This integration is active on PyCharm 2026.1; PyCharm 2026.2 and later bundle equivalent navigation natively.
- Pytest parametrized case runs now use the exact pytest node ID when launched from a case gutter or the Test Runner, including decimal and source-derived IDs, while the function gutter continues to run the whole test.
- Unknown dynamic pytest fixture inspection no longer reports dependencies of fixtures that have no discovered consumer scope and therefore do not execute.
- BetterPy settings now place feature prerequisites before dependent features and groups.
- IDE compatibility now covers PyCharm 2026.3 EAP in addition to PyCharm 2026.1 and 2026.2.
2026.09.0 - 2026-09-01¶
BetterPy aligns pytest run actions with configured collection patterns and expands headless MCP automation across feature-owned navigation, analysis, intentions, and refactorings.
🚀 Features¶
- Pytest collection-pattern IDE integration keeps editor run gutters and Run/Debug context actions aligned with configured
python_files,python_classes,python_functions, andtestpaths, including custom-named and inherited tests. - BetterPy MCP now exposes 59 additional feature-owned operations for navigation, analysis, intentions, and refactorings. Each tool follows its existing feature flag and uses headless PSI/index logic instead of IDE dialogs.
- UV script runner adds Generate → uv: script entry point for creating the first
[project.scripts]mapping and a live template for its target.
🐛 Bug Fixes¶
- Pytest fixture engine now discovers built-in fixtures declared on pytest's default-plugin classes, infers concrete
requestsubtypes, and returns complete fixture usages without an artificial result cap. - Pytest fixture editor integration now resolves builtin fixtures from the active interpreter's pytest source, so Cmd+B navigation and fixture availability follow the installed pytest version.
- Pytest fixture editor integration still types
monkeypatchfrom_pytest.monkeypatch.monkeypatchwhen the fixture file index lists no files for that name. - Pytest fixture editor integration recognizes version-gated entries in pytest's
default_pluginsmanifest, so standard fixtures such astmp_pathare not reported as unknown. - Pytest fixture documentation now shows
requestdocumentation fromFixtureRequest, including the class docstring when no enriched return type is available. - Pytest fixture to usefixtures inspection now offers conversion only for unused setup-only fixtures, not for fixtures that return or yield a value.
- Test/production editor tabs now preserve automatic pin state when files move across newly created splits and avoid reopening editor composites while restoring focus.
- Create pytest fixtures from parameters now keeps intention previews side-effect-free, including feature-tip scheduling.
- Contextual feature tips no longer schedule stale editor updates when focus leaves the editor or when source belongs to library code.
2026.08.5 - 2026-08-17¶
BetterPy adds first-class uv script run configurations and a quick fix for missing pytest test directories, while tightening pytest generation, collection, navigation, and result handling across existing workflows.
🚀 Features¶
- UV script runner creates and maintains workspace-local run configurations for detected
[project.scripts]and[project.gui-scripts]entry points, reusing existing configs and leaving user-specific settings untouched. Plugin-owned configs are removed when a script is commented out or deleted. - Missing pytest test directory highlights configured
testpathsthat do not exist and offers to create them. - New pytest members now insert
assert False, "Not implemented"in generated tests so they fail until a real assertion is written. - Generate class actions now uses the same unimplemented assertion in generated test-class methods.
- New pytest members recognize custom
python_classesandpython_functionscollection patterns when generating tests and fixtures. - Test/production editor tabs now honor configured pytest
python_filespatterns when identifying test files.
🐛 Bug Fixes¶
- Generate class actions avoids duplicate pytest class names and keeps the class action after the test action in the Generate menu.
- Jump to pytest node in test tree no longer shows a second gutter icon next to the run icon. The jump is now offered as an item inside the existing run gutter menu.
- Jump to pytest node in test tree now finds test nodes that the test tree has not expanded or is currently hiding, so the gutter menu item and the action are available right after a test run.
- Jump to pytest node in test tree remains available when the caret is inside a pytest function or class body.
- Parametrized case run gutter keeps the default
Run Testtooltip when the test-tree jump is not on the menu. - Parametrized case run gutter now derives accurate node IDs for custom IDs, complex values, Unicode data, and configured pytest collection patterns.
- Pytest fixture editor integration renames aliased fixtures from the
nameargument and updates their dynamic consumers. - Pytest failed-line inspection resolves failures to the correct file and class in projects with multiple pytest configuration roots.
- Use actual test outcome resolves stack traces correctly across multiple pytest configuration roots and custom collection patterns.
- Constant should be Final inspection restores collection and tuple type compatibility across PyCharm 2026.1, 2026.2, and 2026.3.
2026.08.4 - 2026-08-11¶
BetterPy makes generated Python and pytest declarations immediately editable and brings frequently used feature switches directly into the welcome experience.
🚀 Features¶
- Generate class actions now start live templates for generated class names, method names, and bodies, including dataclasses, frozen dataclasses, protocols, and Pydantic models.
- New pytest members now use live templates so generated tests and fixtures can be named and completed in place.
- Generate pytest hook now opens generated hook implementations as live templates for immediate editing.
- Quick Settings on the Welcome and What's New dialogs lets users enable or disable certain features without browsing through the settings panel.
🐛 Bug Fixes¶
- Pytest mark completion now combines multiple marker declarations on the same editor line into one gutter icon with a target chooser, while keeping known markers navigable alongside unknown markers.
2026.08.3 - 2026-08-10¶
BetterPy adds a focused set of pytest inspections, marker and plugin-reference tooling, and configurable Python Structure View enhancements.
🚀 Features¶
- In tester mode, What's new now opens the unreleased notes and provides a release selector for browsing every published changelog section.
- Enhanced Python Structure View adds BetterPy's filters and pytest-specific presentation to PyCharm's Python Structure View while preserving the platform's native navigation, expansion, and filtering behavior.
- Hide overloads adds a Structure View filter that hides
@overloadsignatures while keeping their implementation visible. - Filter private members adds a Structure View toggle for hiding single- and double-underscore members while keeping Python protocol methods such as
__init__visible. - Icons for pytest tests and fixtures distinguishes tests, fixtures, and regular functions in Structure View and adds filters for showing or hiding tests and fixtures in pytest files.
- Pytest fixture redundant parameter inspection reports unreferenced fixture parameters that are already provided by
autouse, class-levelusefixtures, or module-levelpytestmark. - Pytest fixture to usefixtures inspection converts unused fixture parameters to explicit
@pytest.mark.usefixtures(...)dependencies. - Pytest mark completion completes built-in, configured, and plugin-provided markers and adds navigation, rename, quick documentation, and strict-marker diagnostics for marker declarations.
- Pytest missing assert inspection reports tests that have no effective assertion or explicitly return a value, while recognizing pytest checks, unittest assertions, fluent assertion libraries, mocks, and project helpers.
- Pytest parametrize count mismatch inspection reports parameter rows whose value count does not match the declared argument names.
- Pytest parametrize ids count inspection reports when the number of explicit IDs does not match the number of parameter sets.
- Pytest parametrize unexpected keyword inspection reports unsupported keyword arguments passed to
pytest.mark.parametrize. - Pytest parametrize unused argname inspection reports parameter names that are never used and offers coordinated fixes for the decorator values and test signature.
- Pytest plugin references adds navigation, rename, usage search, and unresolved-reference diagnostics for module names in
pytest_plugins.
🐛 Bug Fixes¶
- What's new links feature entries to their documentation and uses more readable line spacing.
- Pytest context-manager APIs such as
pytest.raises(...)andpytest.warns(...)now count as checks only when they are actually entered, andassert_thathelpers are recognized only when imported from AssertPy or PyHamcrest. - Parametrize inspections no longer mistake unrelated local aliases ending in
mark.parametrizefor pytest decorators.
2026.08.2 - 2026-08-08¶
BetterPy now brings fixture creation, navigation, completion, and diagnostics closer to pytest's actual scope and availability rules.
🚀 Features¶
- Create pytest fixtures from parameters is now available and creates unknown fixtures in the nearest applicable scope, so local test and fixture parameters no longer default to unnecessarily broad fixture placement.
- Parametrize pytest test completes fixture-backed parameter names inside
@pytest.mark.parametrize, restricted to fixtures that are useful and available at the test's location.
🐛 Bug Fixes¶
- Pytest fixture engine now shows fixture return types in completion, navigates to the closest available fixture, distinguishes unavailable and recursively defined fixtures, recognizes more built-in fixtures, and avoids duplicate unresolved-fixture diagnostics and indirect-navigation targets.
- Pytest fixture engine now preserves the IDE's bundled fixture resolution and navigation when BetterPy is disabled, while clearing BetterPy-provided fixture types, documentation, and dynamic-fixture diagnostics when their corresponding features are muted.
- Fixture Editor Integration groups overridden fixtures by module, opens the implementation chooser on typed parameters in ordinary functions and on injected fixtures with declared return types and identifies the inferred type in the chooser title.
- Pytest hook generation preserves required imports in generated hooks and adds quick search to the hook chooser.
- Pytest fixture documentation no longer appears after the feature is disabled.
- Pytest fixture scope inspection validates dynamically requested fixtures against the requesting fixture's scope.
2026.08.1 - 2026-08-04¶
🐛 Bug Fixes¶
- Pytest fixture engine follows local decorator aliases so fixtures registered through conditional
pytest.fixture/pytest.yield_fixtureassignments, such asrequests-mock'spytest11entry point, are recognized correctly. - Private module import inspection no longer suggests exporting symbols from third-party dependencies, only flagging private-module imports that belong to your own project's code.
- Pytest parametrized case run gutter icon anchors per-case run configurations to the test file's own content root and module, so attached projects keep their own working directory and interpreter instead of inheriting one from an unrelated module.
2026.08.0 - 2026-08-02¶
This release ships BetterPy's mock-patching and mock-typing tooling in stable builds, previously available only in dev builds: mock type inference for Mock/MagicMock/AsyncMock with spec/spec_set support, mock.patch target navigation and mock.patch.object attribute completion/navigation, and an inspection for unresolved attributes on specced mocks. The pytest fixture engine also got a significant navigation/inspection performance pass for large repositories.
🚀 Features¶
- Mock assertion methods are now available, resolving
unittest.mockassertion methods (assert_called_once_with,assert_any_call, and similar) without enabling the broader dev-only mock type provider, and correctly resolve pytest-mock'sMock,MagicMock, andAsyncMockaliases to theirunittest.mockclasses for consistentspec/spec_settyping. - Mock type inference infers the type of
Mock,MagicMock, andAsyncMockconstruction and ofpatch/patch.objectreturn values, propagatingspec/spec_setclasses (including lists of protocols) through mock attribute and method access,return_value, and helper functions that return a mock, so calls on properly specced mocks resolve like calls on the real target. - Mock patch reference resolves and navigates the dotted target string passed to
mock.patch(...), including static segments of f-string targets, and lets Go to Declaration jump from amock.patch.object(target, "attribute")attribute string to the real attribute on the target class. - Mock patch object attribute completion completes the attribute name in
mock.patch.object(target, "attribute")calls based on the target's inferred type. - Mock unresolved reference inspection flags attribute reads and writes on specced
Mock/MagicMock/AsyncMockinstances that don't resolve against thespec/spec_setclass, catching typos that would otherwise be silently accepted byMock's auto-attribute behavior. - Pytest hook generation reads annotations and availability notes from the installed
hookspec.py, exposes hooks in registered plugin and test modules where pytest supports them, renders hook documentation and Code Vision hook implementations through F1, and extends hook navigation and override discovery to every registry-valid pytest location, including test and plugin modules.
🐛 Bug Fixes¶
- Pytest fixture engine speeds up fixture navigation and inspections in large repositories by caching inspection-facing resolve methods, routing reference resolution through the platform resolve cache, resolving re-exported fixtures from
conftest.pycorrectly, and capping oversized fixture-not-found diagnostics behind an on-demand chooser instead of one long error description. - Pytest test-tree navigation keeps editor actions and gutter markers synchronized with runner tree updates while avoiding background access to live test proxies and repeated full-tree scans.
- Toggle pytest skip from test tree resolves function, class, and module targets through a shared, deduplicated dispatch path so repeated selections toggle each target exactly once instead of drifting out of sync.
- Copy method annotations from parent safely transfers imports for quoted (string) type annotations into
TYPE_CHECKINGblocks, excluding value and metadata strings, aliasing conflicting bindings, and avoiding duplicate imports.
2026.07.1 - 2026-07-17¶
🐛 Bug Fixes¶
- Pytest fixture documentation falls back to rendering the fixture's own docstring when its return type can't be enriched with field/value info, instead of showing no documentation at all.
- Pytest fixture engine resolves fixture overrides shadowed by installed pytest plugins, discovers pytest plugins declared in nested source roots so
pytest_pluginsreferences resolve correctly across overlapping source roots, and avoids scanning uncommitted fixture PSI to prevent stale stub mismatches during editor searches. - Pytest fixture editor integration resolves fixture override imports for types imported under
TYPE_CHECKINGor other conditional blocks and for classes declared locally in a pytest plugin module, generates fixture overrides as pass-throughs that preserve the parent fixture's behavior and avoid recursion, and avoids nested blocking reads when resolving fixture override hierarchies during indexing. - Class implementations code vision avoids duplicate and stale results when resolving import aliases.
- Docstring Example Rendering renders the underlying class docstring for class aliases assigned from a class reference or class instantiation.
2026.07.0 - 2026-07-15¶
🚀 Features¶
- Pytest fixture intelligence now extends PyCharm's built-in pytest support with BetterPy's own fixture index and resolver. This improves fixture understanding across
conftest.py, plugin modules, autouse fixtures, fixture overrides, string-based fixture references, and dynamic fixture providers such asregister_fixture. - Pytest fixture inspections and navigation are now powered by that resolver. BetterPy can highlight unused fixtures, direct fixture imports, fixture-scope narrowing, uninjected fixture references, no-op
@pytest.mark.usefixturesdecorators, redundant fixture imports, andpytest_pluginsdeclarations in non-rootconftest.pyfiles, while also making pytest identifiers available in Search Everywhere and fixture Find Usages. - Pytest fixture hierarchy support makes fixtures behave more like ordinary overridden Python members. You can jump from an overriding fixture to the broader-scope fixture it shadows, and gutter markers show which narrower-scope fixtures override the current fixture.
- Pytest fixture editor integration makes fixture names act more like normal Python symbols: fixture parameters can resolve to the fixture definition pytest would choose, fixture-name completion uses the visible fixture set for the current file, and Go to Implementation can list narrower-scope fixture overrides.
- Pytest fixture Quick Documentation and type inference build on the same fixture model to cover cases tracked by the linked PyCharm issues, including richer fixture value types, unresolved or uninjected fixture references, and basic checks that a test or fixture parameter annotation matches the resolved fixture return type.
- Pytest parametrization helpers add intentions for creating and maintaining
@pytest.mark.parametrizedecorators, converting values to and frompytest.param(...), and running individual parametrized cases from the editor gutter. - Pytest test-tree actions add copyable node IDs, editor-to-test-tree navigation, skip toggling from the test tree, and a debug-logging run variant for the selected pytest node.
- Pytest test-writing helpers add Generate-menu actions for new tests, fixtures, and pytest hooks, plus editor intentions for toggling
@pytest.mark.skipand wrapping statements withpytest.raises(...). - Inherited attribute documentation shows an ancestor attribute's docstring when an overriding class attribute has no local documentation, preserving useful Quick Documentation across class hierarchies.
🐛 Bug Fixes¶
- Pytest fixture documentation, already available in stable, shows consumer-scoped fixture variants and follows static fixture pass-throughs in Quick Documentation, renders correctly for class-based fixture containers, and stays compatible with newer PyCharm platform versions.
- Pytest fixture editor integration suppresses feature nudges while focus is outside the editor.
- Class implementations code vision includes specced mocks in class inlays, ignores inferred protocol method return types, mirrors native protocol library implementation behavior, and keeps code-vision navigation constrained to the intended editor split.
- Go to target presentation mirrors native protocol library implementation behavior for library protocols.
- Test/Production editor tabs preserves the active split and placement when moving files right, avoids duplicate splits, keeps navigation history intact, guards editor tab pin checks, creates a split when needed for navigation routing, guards action event file lookups with read access, honors pytest's configured collection naming, and applies workspace-aware source roots consistently.
- Property usages code vision stabilizes usage-count recording and keeps code-vision navigation constrained to the intended editor split.
- Module assignment usages code vision keeps code-vision navigation constrained to the intended editor split.
- Constant should be Final inspection avoids unsafe
Finalannotations for literal regular-expression values, reuses existing and re-exported imports instead of adding duplicates, preserves literal builtin types and quote qualifiers, collapses homogeneous tuple types, normalizes generated import order, and supports newer PyCharm collection type APIs. - Shadowing stdlib module inspection no longer rewrites existing references when renaming through the dialog, and avoids subclassing a final platform file-action class.
- Missing None annotation inspection avoids emitting a duplicate quick-fix action.
- Docstring Example Rendering renders reStructuredText docstring examples and preserves field lists when rendering fenced code.
- Copy method annotations from parent avoids duplicate actions, prefers existing qualified imports, normalizes import insertion order, guards against stale PSI when reading the copy plan, and recognizes stub and implementation modules as the same module identity.
- Copy with imports avoids resolving shadowed names when copying imports.
- Generate class actions keeps generated names selected and normalizes generated import order.
- Export symbol to target avoids PSI reads outside read access, applies workspace-aware source roots, and uses pytest's configured naming when checking feature guards.
- Introduce Parameter Object (refactoring and MCP tool) respects disabled feature gates and reuses existing Python imports when generating parameter objects.
- Make parameter mandatory preserves override propagation.
- Make parameter optional preserves type-only optional declarations.
- Change visibility avoids running usage previews on the EDT and uses pytest's configured naming when checking feature guards.
- Attribute docstring renders module-assignment docstring examples correctly.
- Dict access avoids stale PSI after intention edits.
- Top-level extract function prevents refactoring-action crashes and tolerates a missing Python extract handler.
- Message console filter links constructor-style class representations in the console.
- Python navigation bar renders dunder methods correctly in navbar breadcrumbs.
- Use actual test outcome uses pytest's configured naming when checking feature guards.
- Analytics follows the IDE usage-statistics setting by default and no longer sends an opt-out event.
⚡ Performance¶
- Class implementations code vision reduces the work done by import-alias search.
2026.06.1 - 2026-06-05¶
🚀 Features¶
- Return path highlighting highlights every explicit
returnstatement in a Python function when the caret is on that function's return annotation.
🐛 Bug Fixes¶
- Pytest parametrized case run gutter icon only registers pytest-specific run targets and fully opts out when the feature is disabled, preserving PyCharm's built-in pytest gutter actions when other Python test configurations exist.
2026.06.0 - 2026-06-05¶
🚀 Features¶
- Top-level extract function (PY-40840, PY-44636, PY-73852) extracts selected module-level Python statements into a new function with explicit parameters and return values instead of relying on globals.
- Copy with imports (PY-62801) copies selected Python code together with the import statements referenced inside that selection.
- Docstring Example Rendering (PY-47744) renders doctests and fenced Python examples in Quick Documentation, including copy links for runnable doctest input.
- Use actual test outcome replaces expected assertion values with the actual value from the last failed pytest run.
- Pytest failed line inspection (PY-32337, PY-61067) highlights the line reported by the most recent pytest failure directly in the editor.
- Pytest parametrized case run gutter icon (PY-88558) adds gutter run targets for individual
pytest.mark.parametrizecases when BetterPy can infer the exact pytest node id. - Property usages code vision shows inline usage counts above Python properties and opens the matching project usages.
- Suppress missing docstrings on overloads (PY-56267) suppresses PyCharm's missing-docstring inspection for
@overloadsignatures while keeping the implementation subject to the normal rule. - BetterPy settings adds an all-features view and recent-feature controls so users can find, mute, and restore feature settings more directly.
🐛 Bug Fixes¶
- Toggle enum member value can toggle enum members back to literal values.
- Test/Production editor tabs adds tab sorting support and keeps the toolbar/menu state consistent with the active split mode.
- Class implementations code vision uses structural protocol search and keeps protocol implementation labels more precise.
- Constant should be Final inspection preserves declared constant types and keeps generated imports separated cleanly.
- BetterPy settings hides empty groups while searching, expands correctly from the status bar, and restores feature state after muting.
2026.05.2 - 2026-05-31¶
🚀 Features¶
- Pytest fixture documentation (PY-66245) with Quick Documentation and fixture-parameter type inference for primitive, generator-style, async, dataclass, Pydantic, TypedDict, and
conftest.pyfixture cases. - Introduce Parameter Object (PY-59270) now supports async functions, nested functions, and safe decorated targets, with warnings for local decorators that may depend on the original signature.
- Toggle enum member value
- Class implementations code vision (PY-56627) shows an inline code vision hint above each Python class displaying the number of implementations (subclasses) with uv-workspace-aware counting.
- Module assignment usages code vision shows an inline code vision hint above each module-level assignment with the number of project-scope usages, allowing navigation via a non-blocking read action for single usages or delegating to the platform's Show Usages flow for multiple usages.
- Test/Production editor tabs supports routing same-kind test/production navigation targets to the opposite editor split when enabled, complete with toolbar options and a toggle action.
- Add contextual feature nudges for intentions.
🐛 Bug Fixes¶
- Pytest fixture documentation (PY-66245) renders set literal values and unwraps async fixture return types as the injected fixture value type.
- Missing |None annotation inspection (PY-88504) is re-enabled and contributes a BetterPy quick-fix intention while leaving PyCharm's built-in diagnostic responsible on current IDE builds.
- NewType/TypeVar/ParamSpec references (PY-82966, PY-53658) adds a BetterPy quick-fix for
NewTypedeclarations whose string name no longer matches the assigned symbol. - Constant should be Final inspection keeps class-object constants as
Final[type[Cls]]instead of treating them as instances. - Shadowing stdlib module inspection (PY-23615, PY-43957) warns before creating stdlib-shadowing Python files and preserves existing imports when renaming files that already shadow standard-library modules.
- Generate class actions places generated classes above the caret and supports inserting them from inside function scopes.
2026.05.1 - 2026-05-21¶
🚀 Features¶
- Shadowing stdlib module inspection — report project files such as
random.py,logging.py, orjson.pythat shadow Python standard-library modules, offer a rename quick-fix, and warn before renaming a Python file to a stdlib-shadowing name (PY-23615, PY-43957). - Change visibility intention — when toggling method visibility in an inheritance hierarchy, ask whether to rename the whole hierarchy or only the selected method.
🐛 Bug Fixes¶
- Copy method annotations from parent — preserve module-alias qualifiers and relative module imports, and copy nested class annotations through the importable outer class so generated annotations remain valid.
- Shadowing stdlib module inspection — register the feature logging category and keep the inspection and rename confirmation processor under the stable feature package.
2026.05.0 - 2026-05-19¶
🚀 Features¶
- Attribute Docstring in Quick Documentation — show the string literal that follows a class attribute as its documentation in Quick Documentation popups (PY-63878).
- Constant should be Final inspection — report module-level constants that should be annotated with
Final, with safe quick-fixes that handle aliased module types,from __future__imports, function-local assignments, wildcard imports, and unknown types. - Test/Production editor tabs — keep test and production files in separate editor splits, with a toolbar toggle, configurable split alignment, pytest-config-aware test-file detection, file-color-based tab tinting, and respect for manual tab moves and pinning within a session.
- Show test usages — new Find Usages toggle to hide references from test sources, shipped alongside the existing Show type annotations toggle under a shared Usage filtering settings UI.
🐛 Bug Fixes¶
- Structural search: register the Python structural-search profile correctly, and recognize parenthesized expressions, assignments, calls, tuples, and other Python syntax equivalences during matching.
- Message console filter: restore navigation from console output to Python classes and pytest identifiers, and stop turning Pydantic error detail words into false console links.
- Missing
Noneannotation inspection: detect top-levelNonedefaults andAnnotated[...]annotations correctly, including typing wildcard imports and literalNonecases. - Python navigation bar: restore member filtering in the enhanced navigation bar, including overload-aware behavior.
- Go to Implementation presentation: preserve module and class context so same-named targets stay distinguishable in the chooser.
dict[key]access intention: avoid unsafe rewrites for assignment targets and unsafe receiver/key expressions, and preserve the behavior of default expressions when converting between bracket access,.get(), andtry/except KeyError.- Generate dataclass / frozen dataclass / Pydantic model actions: handle insertion edge cases so generated classes land in the expected location with consistent formatting.
- Make Parameter Mandatory / Optional intentions: harden availability and rewriting around inherited parameters and parameters that already carry defaults.
- Parameter Object refactoring: tighten introduce/inline validation, including safer handling of Pydantic models and unsupported inline targets.
- Copy method annotations from parent: preserve copied annotation imports when the parent method uses import aliases.
2026.04.14 - 2026-04-27¶
🚀 Features¶
- Add test/production editor tab mode
- Show BetterPy plugin version in the status bar widget tooltip
- Ship
message-console-filterin stable - Link settings features to versioned docs
📚 Documentation¶
- Add persistent Marketplace and GitHub links to the docs site
- Point changelog links to the public GitHub repo
- Remove redundant README text
2026.04.13 - 2026-04-27¶
🚀 Features¶
- (diagnostics) Copy Diagnostic Data now includes operating system, Python interpreter version, and the list of disabled features
- Ship
dict-accessin stable with dedicated docs - Ship
generate-class-actionsin stable - Ship
change-visibilityfeature in stable
🐛 Bug Fixes¶
- Use
implementationfor navigation and usage extensions in plugin.xml
🚜 Refactor¶
- (core) Move always-on actions out of feature packages
- Move feature schema to
META-INF
2026.04.12 - 2026-04-25¶
🚀 Features¶
- Structural search
- Move py-goto-target-presentation to stable
🧪 Testing¶
- Migrate from JUnit3 to JUnit 4
⚙️ Miscellaneous Tasks¶
- Bump intelliJPlatform to 2.15.0
- Bump zensical to 0.0.36
2026.04.11 - 2026-04-24¶
🚀 Features¶
- Extend navigation bar to show file members
🧪 Testing¶
- Migrate test suite from JUnit 3 to JUnit 4
2026.04.10 - 2026-04-21¶
🚀 Features¶
- Move copy-method-annotations-from-parent to TYPING_TYPE_HINTS
- Mark more features as incubating
- Auto-stamp since field in feature metadata at build time
- Add metadata row to docs rendering
- Require 'since' for features in non-wildcard feature-sets
- Set since=2026.04.05 for stable features; move maturity tooltip to badge only
🐛 Bug Fixes¶
- (intentions) Redirect MakeParameterMandatory to root base class in multi-level hierarchies
- (docs) Collapse consecutive horizontal rules left by stripped sections
- (docs) Load feature metadata from META-INF XML blocks
- (docs) Pre-expand feature blocks via docs_ext before handing off to zensical
- (docs) Drop empty group rows from Features Overview table
- (docs) Escape
|in feature displayName for reference tables - (docs) Remove "Default" column from reference tables
💼 Other¶
- Recover lost docs/plugin.xml/feature-metadata chain (43b9f7d8..4f39217a)
🚜 Refactor¶
- (docs) Unify on RELEASE_CHANNEL env and --channel CLI flag
- Build plugin.xml dynamically
- Include plugin registrations on build time
- Include *.actions.xml files
- Move feature file content to XML fragments
- Use test annotations to skip tests for features that are not configured
- (plugin-xml) Inline *.actions.xml fragments into canonical feature files
- Split _bootstrap.xml registrations into owning feature XMLs
- Retire TypeEvalContexts.java
🧪 Testing¶
- Validate metadata block
- Validate feature id matches filename
- Skip tests for excluded features in stable channel
⚙️ Miscellaneous Tasks¶
- Add purge release script
- (docs) Drop internal Pages deploy (plan does not support Pages on private repos)
- Upgrade to intellij-platform-plugin-template v2.5.0
- Disable jobs targeting dev branch
- Bump version to 2026.04.10