pdd-cli 0.0.30__py3-none-any.whl → 0.0.32__py3-none-any.whl

pdd/prompts/diff_analyzer_LLM.prompt

@@ -0,0 +1,69 @@
+% You are an expert code analyzer, tasked with determining if changes between two prompts are significant enough to warrant complete code regeneration.
+
+% Given:
+    - The original prompt used to generate code
+    - A new, updated prompt
+    - The existing code generated from the original prompt
+% Your task is to:
+    1. Analyze the differences between the original and new prompts
+    2. Evaluate how significantly these differences would impact the code implementation
+    3. Decide if the changes require completely regenerating the code or if incremental patching would be sufficient
+    4. Provide a clear description of the changes needed, which will be used for patching if applicable
+
+% Output a JSON object with:
+    - is_big_change: boolean - true if changes are significant enough to require complete regeneration, false if incremental patching is sufficient
+    - change_description: string - detailed description of changes needed, especially helpful for incremental patching
+
+% Guidelines for determining significant changes:
+    - Major architectural changes (significantly different data structures, algorithms, or patterns)
+    - Addition of entirely new functionalities that alter the core purpose
+    - Changes to return types or critical input parameters
+    - Major changes to the programming paradigm or approach
+    - Substantial adjustments to business logic
+
+% Examples of changes that can be handled incrementally:
+    - Bug fixes or minor logic corrections
+    - Adding or modifying non-critical validation
+    - Adding simple helper functions
+    - Renaming variables or functions
+    - Adding documentation or comments
+    - Minor enhancements to existing functionality
+    - Small adjustments to error handling
+
+% Be conservative in determining if a change is "big" - if there's significant uncertainty, prefer complete regeneration.
+
+ORIGINAL_PROMPT:
+<original_prompt>
+{ORIGINAL_PROMPT}
+</original_prompt>
+
+NEW_PROMPT:
+<new_prompt>
+{NEW_PROMPT}
+</new_prompt>
+
+EXISTING_CODE:
+<existing_code>
+{EXISTING_CODE}
+</existing_code>
+
+Analyze the differences between the original and new prompts. Consider how these differences would impact the implementation of the code.
+
+First, identify and list the specific changes between the prompts:
+
+1. [List each significant change]
+
+Next, evaluate if these changes fundamentally alter the approach needed in the code implementation:
+
+2. [Your detailed analysis]
+
+Based on your analysis, determine whether these changes require completely regenerating the code or if they can be addressed with targeted modifications to the existing code.
+
+Output your conclusion as a JSON object with the following format:
+<output_json_example>
+{{
+  "analysis": "A detailed analysis of the changes needed 1 and 2 above",
+  "change_description": "A detailed description of the changes needed..."
+  "is_big_change": true/false,
+}}
+</output_json_example>

pdd/prompts/find_verification_errors_LLM.prompt

@@ -6,13 +6,13 @@
 
 % Here is the code_module that is being used by the program: <code_module>{code}</code_module>
 
-% Here are the output logs from the program run: <o>{output}</o>
+% Here are the output logs from the program run: <output_logs>{output}</output_logs>
 
 % IMPORTANT CONSIDERATIONS:
-% 1. The prompt may only describe part of the functionality needed by the program.
-% 2. Always consider compatibility between the program and code_module as the highest priority.
-% 3. Functions used by the program must exist in the code_module, even if not mentioned in the prompt.
-% 4. The prompt might only request new functionality to be added to existing code.
+    1. The prompt may only describe part of the functionality needed by the program.
+    2. Always consider compatibility between the program and code_module as the highest priority.
+    3. Functions used by the program must exist in the code_module, even if not mentioned in the prompt.
+    4. The prompt might only request new functionality to be added to existing code.
 
 % Follow these steps to identify any issues:
     Step 1. First, identify all functions and features in the code_module that are used by the program, as these must be preserved.
@@ -28,11 +28,11 @@
 
 % After your analysis, determine the number of distinct issues found. If no issues are found, the count should be 0.
 
-% Return your response as a single, valid JSON object.
-% The JSON object must conform to the following structure:
-% {{
-%   "issues_count": <integer_count_of_issues_found>,
-%   "details": "A detailed explanation of all steps taken during your analysis, including any discrepancies, bugs, or potential issues identified. If no issues are found, this can be a brief confirmation."
-% }}
-% Ensure the "details" field contains your complete textual analysis from Steps 1-7.
-% Ensure the "issues_count" is an integer representing the total number of distinct problems you've identified in your details.
+% Return your response as a single, valid JSON object. The JSON object must conform to the following structure:
+<example_output>
+    {{
+    "details": "A detailed explanation of all steps taken during your analysis, including any discrepancies, bugs, or potential issues identified. If no issues are found, this can be a brief confirmation.",
+    "issues_count": <integer_count_of_issues_found>
+    }}
+</example_output>
+% Ensure the "details" field contains your complete textual analysis from Steps 1-7 and ensure the "issues_count" is an integer representing the total number of distinct problems you've identified in your details.

pdd/prompts/fix_verification_errors_LLM.prompt

@@ -11,15 +11,15 @@
 % Here are the potential issues that need to be fixed: <issues>{issues}</issues>
 
 % CRITICAL INSTRUCTIONS:
-% 1. IMPORTANT: Ensure your fixes maintain backward compatibility with the original program's function calls. If the program calls a function not mentioned in the prompt, preserve that function in your fixed code.
-% 2. When the original prompt and program have conflicting requirements, prioritize in this order:
-%    a. Keep the program working with the same output (preserve existing functions)
-%    b. Add any new functionality requested by the prompt
-%    c. Improve/fix the implementation details of existing functions
-% 3. Do not remove any functions that are called by the original program, even if they are not explicitly requested in the prompt. The prompt may only specify new functionality to add.
-% 4. First analyze how the program interacts with the code module to identify all required functions, then ensure your fix preserves these interaction points.
-% 5. Prefer making additive changes (adding new functions, improving existing ones) rather than removing functionality, even if that means going beyond the minimal requirements of the prompt.
-% 6. If your previous fixes resulted in verification failures related to missing functions, ensure those functions are included in your solution.
+    1. IMPORTANT: Ensure your fixes maintain backward compatibility with the original program's function calls. If the program calls a function not mentioned in the prompt, preserve that function in your fixed code.
+    2. When the original prompt and program have conflicting requirements, prioritize in this order:
+        a. Keep the program working with the same output (preserve existing functions)
+        b. Add any new functionality requested by the prompt
+        c. Improve/fix the implementation details of existing functions
+    3. Do not remove any functions that are called by the original program, even if they are not explicitly requested in the prompt. The prompt may only specify new functionality to add.
+    4. First analyze how the program interacts with the code module to identify all required functions, then ensure your fix preserves these interaction points.
+    5. Prefer making additive changes (adding new functions, improving existing ones) rather than removing functionality, even if that means going beyond the minimal requirements of the prompt.
+    6. If your previous fixes resulted in verification failures related to missing functions, ensure those functions are included in your solution.
 
 % Follow these steps to fix the program or code_module:
     Step 1. Analyze and understand each identified issue in the context of the code_module and program.
@@ -29,11 +29,12 @@
     Step 5. Provide the complete fixed code_module and program with explanations for each significant change made.
     Step 6. Verify that the fixed code meets all requirements from the original prompt and addresses all identified issues while preserving program functionality.
 
-% Return your response as a single, valid JSON object.
-% The JSON object must conform to the following structure:
-% {{
-%   "explanation": "Detailed explanation of all steps taken, including analysis of issues, solutions developed, and verification that the fixes are correct and meet critical instructions and prompt requirements.",
-%   "fixed_code": "The complete, runnable, and fixed Python code for the code_module. This should ONLY be the code, with no additional text or commentary.",
-%   "fixed_program": "The complete, runnable, and fixed Python code for the program. This should ONLY be the code, with no additional text or commentary."
-% }}
+% Return your response as a single, valid JSON object. The JSON object must conform to the following structure:
+<example_output>
+    {{
+    "explanation": "Detailed explanation of all steps taken, including analysis of issues, solutions developed, and verification that the fixes are correct and meet critical instructions and prompt requirements.",
+    "fixed_code": "The complete, runnable, and fixed Python code for the code_module. This should ONLY be the code, with no additional text or commentary.",
+    "fixed_program": "The complete, runnable, and fixed Python code for the program. This should ONLY be the code, with no additional text or commentary."
+    }}
+</example_output>
 % Ensure that the "fixed_code" and "fixed_program" fields contain only the raw source code. Do not include any markdown formatting, comments (unless part of the code itself), or any other explanatory text within these fields.

{pdd_cli-0.0.30.dist-info → pdd_cli-0.0.32.dist-info}/METADATA

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: pdd-cli
-Version: 0.0.30
+Version: 0.0.32
 Summary: PDD (Prompt-Driven Development) Command Line Interface
 Author: Greg Tanaka
 Author-email: glt@alumni.caltech.edu
 License: MIT
-Project-URL: Homepage, https://github.com/gltanaka/pdd
-Project-URL: Repository, https://github.com/gltanaka/pdd.git
-Project-URL: Issue-Tracker, https://github.com/gltanaka/pdd/issues
+Project-URL: Homepage, https://github.com/promptdriven/pdd.git
+Project-URL: Repository, https://github.com/promptdriven/pdd.git
+Project-URL: Issue-Tracker, https://github.com/promptdriven/pdd/issues
 Keywords: prompt-driven development,code generation,AI,LLM,unit testing,software development
 Classifier: Development Status :: 3 - Alpha
 Classifier: Intended Audience :: Developers
@@ -16,7 +16,7 @@ Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Topic :: Software Development :: Code Generators
 Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
-Requires-Python: >=3.11
+Requires-Python: >=3.12
 Description-Content-Type: text/x-rst
 License-File: LICENSE
 Requires-Dist: GitPython==3.1.44
@@ -46,7 +46,7 @@ Requires-Dist: pytest-asyncio; extra == "dev"
 Requires-Dist: z3-solver; extra == "dev"
 Dynamic: license-file
 
-.. image:: https://img.shields.io/badge/pdd--cli-v0.0.30-blue
+.. image:: https://img.shields.io/badge/pdd--cli-v0.0.32-blue
    :alt: PDD-CLI Version
 
 PDD (Prompt-Driven Development) Command Line Interface
@@ -130,7 +130,7 @@ After installation, verify:
 
    pdd --version
 
-You'll see the current PDD version (e.g., 0.0.30).
+You'll see the current PDD version (e.g., 0.0.32).
 
 Advanced Installation Tips
 --------------------------

{pdd_cli-0.0.30.dist-info → pdd_cli-0.0.32.dist-info}/RECORD

@@ -1,15 +1,15 @@
-pdd/__init__.py,sha256=UlmLFvxuZysa-xxH1RaK3HNVs1VCgVD7DZxe8y-jEv8,477
+pdd/__init__.py,sha256=oBlK2EdKLxWULcsuHgrlD34jImz8M12FUeCXxTkbxIk,632
 pdd/auto_deps_main.py,sha256=NVLqL5FHxe2eorViXTuh8z2zH9Sb-b6MNN9aZ1hqevY,3552
 pdd/auto_include.py,sha256=aCa2QXDlOdKbh4vS3uDjWptkHB_Qv3QBNCbZe6mGWoo,6074
 pdd/auto_update.py,sha256=Pfav1hrqQIDjZIPuIvryBeM7k-Rc72feVUTJZPtigaU,2889
 pdd/bug_main.py,sha256=cSGBnHmFIA8WrkGiohJFVRuM2086v-wlPvTJqTv00WQ,4631
 pdd/bug_to_unit_test.py,sha256=oejqoKomLseKknYDFlQKQ04TNT3soqOjMPghxty8Guo,6311
 pdd/change.py,sha256=EKmv7WvXNX24rjLCnrcaoo4xOVkNhCa9HLRbpMAxQSw,5036
-pdd/change_main.py,sha256=5IAFW1_eazYCr3F1DlfO6FDpNDZ4LgkXBWLb6rKW-PQ,25643
-pdd/cli.py,sha256=Z5AE8uVUnzZiuEyZqe9lMu6hUG6pK2_qg9NBwEPNIks,37463
+pdd/change_main.py,sha256=Tk0aHY8Z2d-d0m7lLfc_HqgOqs4x_dJD1IrVZSxuxIM,25580
+pdd/cli.py,sha256=VFoyx3iJmFeHCc4HhOc_7tiz3FY9oJjCUtS9PR1wwl0,38341
 pdd/cmd_test_main.py,sha256=aSCxRnSurg15AvPcJDAPp9xy8p_qqnjU1oV14Hi2R54,5301
 pdd/code_generator.py,sha256=DqQNN6jCNjSJvHi0IFyqkSfak6LeDG-yQHPYnvd4AJQ,4424
-pdd/code_generator_main.py,sha256=G2eRBPXc1cGszkk0PbIPmJZHPaf_dw5d2yZbsvQZA3c,4793
+pdd/code_generator_main.py,sha256=wup3O2dVh9JzlGsWtXvypqAHgHyBZHOWAe3NJuV_-g4,18648
 pdd/comment_line.py,sha256=sX2hf4bG1fILi_rvI9MkkwCZ2IitgKkW7nOiw8aQKPY,1845
 pdd/conflicts_in_prompts.py,sha256=XaEm9jIMcbENTyhphD8NXs2EmRxuPu1EI8GHrsiRwq0,4687
 pdd/conflicts_main.py,sha256=O87s9baSa9DJMndxPIdsnYO_spoajcv9jii3XYt_-fM,3473
@@ -28,8 +28,8 @@ pdd/fix_error_loop.py,sha256=BdoI08HD30BHCjjfvpH7zamdjv6sMqi70li_oRu_-P0,24004
 pdd/fix_errors_from_unit_tests.py,sha256=SdL4wgo6ARgIClTTYlHuNu12t1cE4YohpGqo4Mcj1P8,9192
 pdd/fix_main.py,sha256=q2FDggCGXSbrMlb6OaxCmpJ5v02W8tmRU8IKmHdYYbQ,13799
 pdd/fix_verification_errors.py,sha256=_ToACv9z10YIoUUbwQSS41dXKsQ_lJi2FHy1qBYHMpY,16566
-pdd/fix_verification_errors_loop.py,sha256=tSCkzdvLGl4kXBUfwdxZDK8dHWsn7hYsGH9-tdrIDVc,52992
-pdd/fix_verification_main.py,sha256=b6258kXSTJ8PptkebWNDVxmd6CKclY3p0ZjhcILJ3mc,20163
+pdd/fix_verification_errors_loop.py,sha256=CVkskhxXu7su95HXQkOCmU2yJgY6zf0vMbGDxxNmuh4,54754
+pdd/fix_verification_main.py,sha256=ydMfUn0USemh_lmxhKV2vZv75impgLsPbnoZio-G7K0,21792
 pdd/generate_output_paths.py,sha256=o8Sjx0zLeBXXxEirGewcla40RinjTfnkrxBldRQ6HvI,20237
 pdd/generate_test.py,sha256=6wNICtDP-_sWaura0PrrTrCRqjUbgzpTRMk0mTxupL4,4845
 pdd/get_comment.py,sha256=yuRtk68-SDkMaGzOSyIFdldRoymJBRSKjOYkr0narVc,2627
@@ -38,6 +38,7 @@ pdd/get_jwt_token.py,sha256=BGxqMh7qf2mG-TFw7JlV941O9XtrW22L_dRoS_UZNjM,11560
 pdd/get_language.py,sha256=yxyQqVEb5H3ep3Hc6XgAl3vMLTHD5OIs8ZSekB493GA,1438
 pdd/git_update.py,sha256=Ya7eI7YFtGIpT7FdziFJfnFkiZlj8I9Lh98lqtXfClc,2855
 pdd/increase_tests.py,sha256=dlYd9PosV3g8kpDlQh6gd8WUauClvs_-Z8ERRD-kZk4,3456
+pdd/incremental_code_generator.py,sha256=cWo3DJ0PybnrepFEAMibGjTVY3T8mLVvPt5W8cNhuxU,9402
 pdd/insert_includes.py,sha256=UASoq_46UNL6l7VGB7DW2jb4kcWlP6Hbj2EWuh7210Q,5310
 pdd/install_completion.py,sha256=H_FIid0eHCn7I6HHIsBqdComAxjLIu7CbD6yfMU48aw,5085
 pdd/llm_invoke.py,sha256=457rD3f7KQHJ3BtI4boxTurArCww2zWAl4X77TxVROs,65788
@@ -64,13 +65,15 @@ pdd/update_model_costs.py,sha256=zfGqWoVIjBppKUt1Naq2ZsIdiucwfH6at2DflcwkJf8,229
 pdd/update_prompt.py,sha256=OdPRIAMu7OBx7E4SOU95hWgdtBY4oO8XOe1dvPChMlU,4351
 pdd/xml_tagger.py,sha256=5AWzOboNuXMJmmIpi1hhPPAB6nxbBOkRqgoPLpoGYT8,4292
 pdd/data/language_format.csv,sha256=xUTmFHXSBVBRfPV-NKG3oWo5_ped5ukP-ekFcIlVzJk,877
-pdd/data/llm_model.csv,sha256=enzLqM-cZl1GUjN4gkCcNw24VtMS39FdDa7aujg2-Gs,1489
+pdd/data/llm_model.csv,sha256=BZioMyxUlDuJdcxFCDV2BTw1ssiHKZBf4OxELIy4JGY,1487
 pdd/prompts/auto_include_LLM.prompt,sha256=0t-Jmm5o6vVTmqsISTUiewqPT8bB389UZnJoHZvgtu4,13967
 pdd/prompts/bug_to_unit_test_LLM.prompt,sha256=KdMkvRVnjVSf0NTYIaDXIMT93xPttXEwkMpjWx5leLs,1588
-pdd/prompts/change_LLM.prompt,sha256=W3sE6XZ2fb35XdqOykK1hDPtqkHSv9MZGD3sT8B8WjY,2083
+pdd/prompts/change_LLM.prompt,sha256=5rgWIL16p3VRURd2_lNtcbu_MVRqPhI8gFIBt1gkzDQ,2164
+pdd/prompts/code_patcher_LLM.prompt,sha256=yeV4lsRuPQzNdKRV_LQUOmmWh2yhu8YgKXUWo4bge4I,2392
 pdd/prompts/conflict_LLM.prompt,sha256=46DB_qOCtsfVsj6y8E8grI0izxAk_-ixoENUUHQAkHc,1593
 pdd/prompts/continue_generation_LLM.prompt,sha256=Jsd3eeu23heqw2frfOLzZ5c9dn0QZrfWGratfyWV-ac,111
 pdd/prompts/detect_change_LLM.prompt,sha256=-q8VqXAv6ufEE193DNbTcgpbxiKISR5-5j3M0TTqa8s,4522
+pdd/prompts/diff_analyzer_LLM.prompt,sha256=2lZI4g4DO9NwMPnxVJW717dGG5LQuBXqgeIjYfplEdU,2901
 pdd/prompts/example_generator_LLM.prompt,sha256=48mUvjEYxQYf_HhDLP6RGOz6_d_go6JNExZ9g8aicCg,610
 pdd/prompts/extract_auto_include_LLM.prompt,sha256=BamIIt8qrML2ZtNe3D4K30iMobJ4URtkyomHCDaf0iw,313
 pdd/prompts/extract_code_LLM.prompt,sha256=rRql9Dv2Rn01F2hFeaGzfh9apxCkjY7WzAG0SAvIe8M,2470
@@ -83,10 +86,10 @@ pdd/prompts/extract_prompt_update_LLM.prompt,sha256=XH2muMzTb_wqcQS9rR4THXe6TP7B
 pdd/prompts/extract_promptline_LLM.prompt,sha256=owIBRaF2bWwg3S64uyMKzOFMdvvmI_EEGoF97Pa9118,813
 pdd/prompts/extract_unit_code_fix_LLM.prompt,sha256=c4l6twMLC2YqDDvOj_DcaKmJQF8kIupeqvkueK_OQng,14301
 pdd/prompts/extract_xml_LLM.prompt,sha256=eRcHaL-khShpb7C1_b7wmBJHfo2Kh1Wvjo_aOcWZovU,561
-pdd/prompts/find_verification_errors_LLM.prompt,sha256=sBax_pfe-mFW4kY-vhvE_AFQwNSsofNLmnxYz_SYzUo,2797
+pdd/prompts/find_verification_errors_LLM.prompt,sha256=NwmJbAFkNwSWaJOsewznb7hbOljc9AJ-Sf6fB7xIACI,2863
 pdd/prompts/fix_code_module_errors_LLM.prompt,sha256=sjqB-apFtiMZerXm_qZEuA6pfRtk2hOiXxPXwuxIZxM,2462
 pdd/prompts/fix_errors_from_unit_tests_LLM.prompt,sha256=Yy6WIg9WfizrFpFZogoCtlQy-H123ycc_SaF6m8_Ljo,5079
-pdd/prompts/fix_verification_errors_LLM.prompt,sha256=8GLdGBFMPWRnOw-D1CEObSPqw6FdzEgmGhui6oA_EzY,3474
+pdd/prompts/fix_verification_errors_LLM.prompt,sha256=zZrQQnBRBL42fINmCC2WjQlLGPNriIuHsnzrkN5seN8,3532
 pdd/prompts/generate_test_LLM.prompt,sha256=eCI7CTMpoA76DTruTgWygClxJX0gj_uNxTqHbmqcJ50,2254
 pdd/prompts/increase_tests_LLM.prompt,sha256=rekFzLRuZy99KifEKNlmPYoQdl8wa04112mtCdIY6S8,955
 pdd/prompts/insert_includes_LLM.prompt,sha256=g-p2gXKENsqvfK5Q9FYbqFsIJ5CP7rbxmd4rROA-W80,1453
@@ -98,9 +101,9 @@ pdd/prompts/trim_results_start_LLM.prompt,sha256=OKz8fAf1cYWKWgslFOHEkUpfaUDARh3
 pdd/prompts/unfinished_prompt_LLM.prompt,sha256=-JgBpiPTQZdWOAwOG1XpfpD9waynFTAT3Jo84eQ4bTw,1543
 pdd/prompts/update_prompt_LLM.prompt,sha256=prIc8uLp2jqnLTHt6JvWDZGanPZipivhhYeXe0lVaYw,1328
 pdd/prompts/xml_convertor_LLM.prompt,sha256=YGRGXJeg6EhM9690f-SKqQrKqSJjLFD51UrPOlO0Frg,2786
-pdd_cli-0.0.30.dist-info/licenses/LICENSE,sha256=-1bjYH-CEjGEQ8VixtnRYuu37kN6F9NxmZSDkBuUQ9o,1062
-pdd_cli-0.0.30.dist-info/METADATA,sha256=P77AbVeiMa4ylyAk6skGkZ73Lx5LY9gZSXlRBUmcJJ8,7762
-pdd_cli-0.0.30.dist-info/WHEEL,sha256=DnLRTWE75wApRYVsjgc6wsVswC54sMSJhAEd4xhDpBk,91
-pdd_cli-0.0.30.dist-info/entry_points.txt,sha256=Kr8HtNVb8uHZtQJNH4DnF8j7WNgWQbb7_Pw5hECSR-I,36
-pdd_cli-0.0.30.dist-info/top_level.txt,sha256=xjnhIACeMcMeDfVNREgQZl4EbTni2T11QkL5r7E-sbE,4
-pdd_cli-0.0.30.dist-info/RECORD,,
+pdd_cli-0.0.32.dist-info/licenses/LICENSE,sha256=-1bjYH-CEjGEQ8VixtnRYuu37kN6F9NxmZSDkBuUQ9o,1062
+pdd_cli-0.0.32.dist-info/METADATA,sha256=gnrubUf69rPVr3t01FvagrPuxrJ3B6JRbHXjYQYB3OQ,7778
+pdd_cli-0.0.32.dist-info/WHEEL,sha256=zaaOINJESkSfm_4HQVc5ssNzHCPXhJm0kEUakpsEHaU,91
+pdd_cli-0.0.32.dist-info/entry_points.txt,sha256=Kr8HtNVb8uHZtQJNH4DnF8j7WNgWQbb7_Pw5hECSR-I,36
+pdd_cli-0.0.32.dist-info/top_level.txt,sha256=xjnhIACeMcMeDfVNREgQZl4EbTni2T11QkL5r7E-sbE,4
+pdd_cli-0.0.32.dist-info/RECORD,,

{pdd_cli-0.0.30.dist-info → pdd_cli-0.0.32.dist-info}/WHEEL

@@ -1,5 +1,5 @@
 Wheel-Version: 1.0
-Generator: setuptools (80.4.0)
+Generator: setuptools (80.8.0)
 Root-Is-Purelib: true
 Tag: py3-none-any