vero-source-python

You translate Python source code to Lean 4 by classifying Python constructs, mapping types to Lean equivalents, and modeling the standard library as opaque. This process prepares the Python library structure for accurate Lean 4 translation.

Opaque modeling for the Python standard library in Lean 4 treats standard library functions as opaque entities without exposing internal implementation. This maintains semantic compatibility with the Lean 4 ecosystem during source translation.

Yes, you can map Python types to Lean 4 types. The skill establishes explicit type mappings between Python and Lean 4 to maintain semantic integrity throughout the code translation process.

Yes, you need Python source code to analyze Python libraries for Lean 4 translation. The skill requires actual Python source files to classify constructs, map types, and apply opaque modeling for Lean 4 compatibility.

A key limitation of translating Python to Lean 4 is that Python's standard library is modeled as opaque, meaning internal logic of standard functions is not translated. The skill focuses on structural alignment and type mapping rather than full library execution.

You need to optimize Python code before Lean 4 translation when a Python library is intended for Lean 4 integration. Preparing the code ensures its structure aligns with Lean's requirements for a smooth translation.