pvieito/PythonKit

PythonKit is a Swift package that enables native interoperability with Python, allowing Swift code to dynamically load and interact with the Python runtime. It provides an ergonomic API for calling Python functions and classes, along with specific support for converting data between Swift arrays and NumPy ndarrays. The system is maintained as a command-line tool-free library, relying on Swift Package Manager for distribution and testing.

This change introduces the initial public release of the PythonKit Swift package, providing a framework to interact with Python from Swift code. The repository is now structured as a public project with an Apache 2.0 license, including documentation (README, AGENTS.md) and configuration files (.gitignore) to support usage via Swift Package Manager and runtime Python library loading.

(repo-wide) · high confidence

The PythonTool command-line interface has been removed from the project. This change deletes the tool's source files (including main.swift, which previously handled argument parsing and Python module listing via CommandLineKit) and its associated configuration files (Info.plist, OperatingSystemVersion.swift), effectively eliminating the standalone CLI capability.

PythonTool · high confidence

The Xcode project file (project.pbxproj) and the associated workspace configuration (contents.xcworkspacedata) have been deleted from the repository. This removes the native Xcode build system support for the PythonKit library, indicating a shift away from Xcode-based development or build workflows for this component.

PythonKit.xcodeproj · high confidence

The .agents/skills and .claude/skills directories are now symlinks pointing to ../Agents/Skills, centralizing skill definitions. Additionally, placeholder .gitkeep files were added to the Agents/Instructions and Agents/Skills directories to ensure they are tracked by version control.

.agents, .claude, Agents · high confidence

The PythonKit library has been completely rewritten to provide a native Swift interoperability layer for Python, replacing the previous \PythonGlue\ implementation. The new \Python.swift\ core introduces \PythonObject\ with \@dynamicMemberLookup\ and \@dynamicCallable\ for ergonomic Python interaction, and \PythonLibrary.swift\ implements robust runtime dynamic loading of the Python library across macOS, Linux, and Windows. Additionally, the new \NumpyConversion.swift\ file adds support for bridging \numpy.ndarray\ data to and from Swift arrays, enabling seamless integration with the NumPy ecosystem.

PythonKit · high confidence

Added new test suites in the Tests directory to verify core PythonKit functionality. NumpyConversionTests validates the conversion between Swift arrays and NumPy arrays, including handling of different data types, empty arrays, and strided views. PythonFunctionTests exercises the creation of Python functions and classes from Swift closures, covering keyword arguments, dynamic class construction, inheritance, and exception handling. PythonRuntimeTests ensures correct behavior of the Python runtime integration, including list and dictionary operations, range and slice handling, binary/unary operators, and error throwing.

Tests · high confidence

The Package.swift manifest has been updated to specify Swift tools version 6.0 while explicitly setting the language mode to Swift 5 via the \swiftLanguageModes\ configuration. This ensures compatibility with the newer Swift Package Manager tooling while maintaining source compatibility with Swift 5 code.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 61 → 61 (+0.0)
• Rubric changed (rubric-2026.09.11 → rubric-2026.09.18) — scores are not directly comparable.

• Code Health 98 → 98 (+0.0)
• Architecture 100 → 100 (+0.0)
• Maturity 44 → 44 (+0.0)
• Readiness 51 → 55 (+3.6)
• Security 97 → 97 (+0.0)

• Documentation: no architecture or design documentation (README.md)

• Coverage not measured — Swift suite
• Redundant operations for importing modules. attemptImport and import appear to perform the same core action (importing a module by name), differing only potentially in error handling semantics (throwing vs returning an object that might represent an error or nil), which is not clearly distinguished by the name alone.

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

pvieito/PythonKit was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.