pdd-cli 0.0.26__py3-none-any.whl → 0.0.27__py3-none-any.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Potentially problematic release.
This version of pdd-cli might be problematic. Click here for more details.
- pdd/__init__.py +1 -1
- pdd/cli.py +12 -3
- pdd/cli_1_0_2_0_20250510_000314.py +1054 -0
- pdd/cli_2_0_1_0_20250510_000314.py +1054 -0
- pdd/cli_3_0_1_0_20250510_000314.py +1054 -0
- pdd/cli_4_0_1_0_20250510_000314.py +1054 -0
- pdd/fix_verification_errors.py +2 -2
- pdd/fix_verification_errors_loop.py +5 -1
- pdd/fix_verification_main.py +21 -1
- pdd/generate_output_paths.py +43 -2
- pdd/llm_invoke.py +208 -176
- pdd/prompts/find_verification_errors_LLM.prompt +18 -7
- pdd/prompts/fix_verification_errors_LLM.prompt +18 -6
- {pdd_cli-0.0.26.dist-info → pdd_cli-0.0.27.dist-info}/METADATA +3 -3
- {pdd_cli-0.0.26.dist-info → pdd_cli-0.0.27.dist-info}/RECORD +19 -15
- {pdd_cli-0.0.26.dist-info → pdd_cli-0.0.27.dist-info}/WHEEL +0 -0
- {pdd_cli-0.0.26.dist-info → pdd_cli-0.0.27.dist-info}/entry_points.txt +0 -0
- {pdd_cli-0.0.26.dist-info → pdd_cli-0.0.27.dist-info}/licenses/LICENSE +0 -0
- {pdd_cli-0.0.26.dist-info → pdd_cli-0.0.27.dist-info}/top_level.txt +0 -0
|
@@ -6,14 +6,25 @@
|
|
|
6
6
|
|
|
7
7
|
% Here is the code_module that is being used by the program: <code_module>{code}</code_module>
|
|
8
8
|
|
|
9
|
-
% Here are the output logs from the program run: <
|
|
9
|
+
% Here are the output logs from the program run: <o>{output}</o>
|
|
10
|
+
|
|
11
|
+
% IMPORTANT CONSIDERATIONS:
|
|
12
|
+
% 1. The prompt may only describe part of the functionality needed by the program.
|
|
13
|
+
% 2. Always consider compatibility between the program and code_module as the highest priority.
|
|
14
|
+
% 3. Functions used by the program must exist in the code_module, even if not mentioned in the prompt.
|
|
15
|
+
% 4. The prompt might only request new functionality to be added to existing code.
|
|
10
16
|
|
|
11
17
|
% Follow these steps to identify any issues:
|
|
12
|
-
Step 1.
|
|
13
|
-
Step 2.
|
|
14
|
-
Step 3.
|
|
15
|
-
Step 4.
|
|
16
|
-
Step 5.
|
|
18
|
+
Step 1. First, identify all functions and features in the code_module that are used by the program, as these must be preserved.
|
|
19
|
+
Step 2. Compare the program and code_module against the prompt and explain any discrepancies.
|
|
20
|
+
Step 3. Analyze the input/output behavior of the program and verify if it meets the expected behavior described in the prompt.
|
|
21
|
+
Step 4. Identify any potential edge cases, error handling issues, or performance concerns that could cause problems in the future.
|
|
22
|
+
Step 5. Check the code for potential bugs that haven't manifested yet.
|
|
23
|
+
Step 6. If any issues are found, explain in detail the root cause of each issue and how it could impact the program's functioning.
|
|
24
|
+
Step 7. Carefully distinguish between:
|
|
25
|
+
a. Incompatibilities (functions called by program but missing from code_module) - these are critical issues
|
|
26
|
+
b. Prompt adherence issues (code doesn't match prompt requirements) - these are important but secondary to compatibility
|
|
27
|
+
c. Implementation issues (bugs, edge cases) - these should be addressed without breaking compatibility
|
|
17
28
|
|
|
18
29
|
% After your analysis, determine the number of distinct issues found. If no issues are found, the count should be 0.
|
|
19
30
|
|
|
@@ -23,5 +34,5 @@
|
|
|
23
34
|
% "issues_count": <integer_count_of_issues_found>,
|
|
24
35
|
% "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."
|
|
25
36
|
% }}
|
|
26
|
-
% Ensure the "details" field contains your complete textual analysis from Steps 1-
|
|
37
|
+
% Ensure the "details" field contains your complete textual analysis from Steps 1-7.
|
|
27
38
|
% Ensure the "issues_count" is an integer representing the total number of distinct problems you've identified in your details.
|
|
@@ -6,21 +6,33 @@
|
|
|
6
6
|
|
|
7
7
|
% Here is the code_module that is being used by the program: <code_module>{code}</code_module>
|
|
8
8
|
|
|
9
|
-
% Here are the
|
|
9
|
+
% Here are the output_logs from the program run: <output_logs>{output}</output_logs>
|
|
10
10
|
|
|
11
11
|
% Here are the potential issues that need to be fixed: <issues>{issues}</issues>
|
|
12
12
|
|
|
13
|
+
% CRITICAL INSTRUCTIONS:
|
|
14
|
+
% 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.
|
|
15
|
+
% 2. When the original prompt and program have conflicting requirements, prioritize in this order:
|
|
16
|
+
% a. Keep the program working with the same output (preserve existing functions)
|
|
17
|
+
% b. Add any new functionality requested by the prompt
|
|
18
|
+
% c. Improve/fix the implementation details of existing functions
|
|
19
|
+
% 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.
|
|
20
|
+
% 4. First analyze how the program interacts with the code module to identify all required functions, then ensure your fix preserves these interaction points.
|
|
21
|
+
% 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.
|
|
22
|
+
% 6. If your previous fixes resulted in verification failures related to missing functions, ensure those functions are included in your solution.
|
|
23
|
+
|
|
13
24
|
% Follow these steps to fix the program or code_module:
|
|
14
25
|
Step 1. Analyze and understand each identified issue in the context of the code_module and program.
|
|
15
|
-
Step 2.
|
|
16
|
-
Step 3.
|
|
17
|
-
Step 4.
|
|
18
|
-
Step 5.
|
|
26
|
+
Step 2. Analyze how the program uses the code_module to determine all functions that must be preserved.
|
|
27
|
+
Step 3. For each issue, develop a solution that addresses the root cause while still satisfying the prompt requirements AND maintaining backward compatibility.
|
|
28
|
+
Step 4. Implement the fixes, ensuring the changes resolve the issues without introducing new problems.
|
|
29
|
+
Step 5. Provide the complete fixed code_module and program with explanations for each significant change made.
|
|
30
|
+
Step 6. Verify that the fixed code meets all requirements from the original prompt and addresses all identified issues while preserving program functionality.
|
|
19
31
|
|
|
20
32
|
% Return your response as a single, valid JSON object.
|
|
21
33
|
% The JSON object must conform to the following structure:
|
|
22
34
|
% {{
|
|
23
|
-
% "explanation": "Detailed explanation of all steps taken, including analysis of issues, solutions developed, and verification that the fixes are correct and meet prompt requirements.",
|
|
35
|
+
% "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.",
|
|
24
36
|
% "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.",
|
|
25
37
|
% "fixed_program": "The complete, runnable, and fixed Python code for the program. This should ONLY be the code, with no additional text or commentary."
|
|
26
38
|
% }}
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: pdd-cli
|
|
3
|
-
Version: 0.0.
|
|
3
|
+
Version: 0.0.27
|
|
4
4
|
Summary: PDD (Prompt-Driven Development) Command Line Interface
|
|
5
5
|
Author: Greg Tanaka
|
|
6
6
|
Author-email: glt@alumni.caltech.edu
|
|
@@ -45,7 +45,7 @@ Requires-Dist: pytest-asyncio; extra == "dev"
|
|
|
45
45
|
Requires-Dist: z3-solver; extra == "dev"
|
|
46
46
|
Dynamic: license-file
|
|
47
47
|
|
|
48
|
-
.. image:: https://img.shields.io/badge/pdd--cli-v0.0.
|
|
48
|
+
.. image:: https://img.shields.io/badge/pdd--cli-v0.0.27-blue
|
|
49
49
|
:alt: PDD-CLI Version
|
|
50
50
|
|
|
51
51
|
PDD (Prompt-Driven Development) Command Line Interface
|
|
@@ -106,7 +106,7 @@ After installation, verify:
|
|
|
106
106
|
|
|
107
107
|
pdd --version
|
|
108
108
|
|
|
109
|
-
You'll see the current PDD version (e.g., 0.0.
|
|
109
|
+
You'll see the current PDD version (e.g., 0.0.27).
|
|
110
110
|
|
|
111
111
|
Advanced Installation Tips
|
|
112
112
|
--------------------------
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
pdd/__init__.py,sha256=
|
|
1
|
+
pdd/__init__.py,sha256=aMNZOZGgl3FTqSDHXRunJ_oo1_quZIcAV6yzCNVeiWs,477
|
|
2
2
|
pdd/auto_deps_main.py,sha256=NVLqL5FHxe2eorViXTuh8z2zH9Sb-b6MNN9aZ1hqevY,3552
|
|
3
3
|
pdd/auto_include.py,sha256=aCa2QXDlOdKbh4vS3uDjWptkHB_Qv3QBNCbZe6mGWoo,6074
|
|
4
4
|
pdd/auto_update.py,sha256=Pfav1hrqQIDjZIPuIvryBeM7k-Rc72feVUTJZPtigaU,2889
|
|
@@ -6,7 +6,11 @@ pdd/bug_main.py,sha256=cSGBnHmFIA8WrkGiohJFVRuM2086v-wlPvTJqTv00WQ,4631
|
|
|
6
6
|
pdd/bug_to_unit_test.py,sha256=oejqoKomLseKknYDFlQKQ04TNT3soqOjMPghxty8Guo,6311
|
|
7
7
|
pdd/change.py,sha256=EKmv7WvXNX24rjLCnrcaoo4xOVkNhCa9HLRbpMAxQSw,5036
|
|
8
8
|
pdd/change_main.py,sha256=5IAFW1_eazYCr3F1DlfO6FDpNDZ4LgkXBWLb6rKW-PQ,25643
|
|
9
|
-
pdd/cli.py,sha256=
|
|
9
|
+
pdd/cli.py,sha256=5tOftlikdO9Kka5sMF2Pm9s-N5GEaSwZdt_GyQnR-J0,37425
|
|
10
|
+
pdd/cli_1_0_2_0_20250510_000314.py,sha256=oYQJiuc5txvR24YJyCt9jwBJlwr3ufAGhzxVhIjj0oI,37360
|
|
11
|
+
pdd/cli_2_0_1_0_20250510_000314.py,sha256=oYQJiuc5txvR24YJyCt9jwBJlwr3ufAGhzxVhIjj0oI,37360
|
|
12
|
+
pdd/cli_3_0_1_0_20250510_000314.py,sha256=5tOftlikdO9Kka5sMF2Pm9s-N5GEaSwZdt_GyQnR-J0,37425
|
|
13
|
+
pdd/cli_4_0_1_0_20250510_000314.py,sha256=5tOftlikdO9Kka5sMF2Pm9s-N5GEaSwZdt_GyQnR-J0,37425
|
|
10
14
|
pdd/cmd_test_main.py,sha256=aSCxRnSurg15AvPcJDAPp9xy8p_qqnjU1oV14Hi2R54,5301
|
|
11
15
|
pdd/code_generator.py,sha256=DqQNN6jCNjSJvHi0IFyqkSfak6LeDG-yQHPYnvd4AJQ,4424
|
|
12
16
|
pdd/code_generator_main.py,sha256=G2eRBPXc1cGszkk0PbIPmJZHPaf_dw5d2yZbsvQZA3c,4793
|
|
@@ -27,10 +31,10 @@ pdd/fix_code_module_errors.py,sha256=O7W-jqQ7REdAY7x03tjzAC2xzxUJwl89vHCdlfPGqd0
|
|
|
27
31
|
pdd/fix_error_loop.py,sha256=BdoI08HD30BHCjjfvpH7zamdjv6sMqi70li_oRu_-P0,24004
|
|
28
32
|
pdd/fix_errors_from_unit_tests.py,sha256=SdL4wgo6ARgIClTTYlHuNu12t1cE4YohpGqo4Mcj1P8,9192
|
|
29
33
|
pdd/fix_main.py,sha256=q2FDggCGXSbrMlb6OaxCmpJ5v02W8tmRU8IKmHdYYbQ,13799
|
|
30
|
-
pdd/fix_verification_errors.py,sha256=
|
|
31
|
-
pdd/fix_verification_errors_loop.py,sha256=
|
|
32
|
-
pdd/fix_verification_main.py,sha256=
|
|
33
|
-
pdd/generate_output_paths.py,sha256=
|
|
34
|
+
pdd/fix_verification_errors.py,sha256=_ToACv9z10YIoUUbwQSS41dXKsQ_lJi2FHy1qBYHMpY,16566
|
|
35
|
+
pdd/fix_verification_errors_loop.py,sha256=tSCkzdvLGl4kXBUfwdxZDK8dHWsn7hYsGH9-tdrIDVc,52992
|
|
36
|
+
pdd/fix_verification_main.py,sha256=b6258kXSTJ8PptkebWNDVxmd6CKclY3p0ZjhcILJ3mc,20163
|
|
37
|
+
pdd/generate_output_paths.py,sha256=o8Sjx0zLeBXXxEirGewcla40RinjTfnkrxBldRQ6HvI,20237
|
|
34
38
|
pdd/generate_test.py,sha256=6wNICtDP-_sWaura0PrrTrCRqjUbgzpTRMk0mTxupL4,4845
|
|
35
39
|
pdd/get_comment.py,sha256=yuRtk68-SDkMaGzOSyIFdldRoymJBRSKjOYkr0narVc,2627
|
|
36
40
|
pdd/get_extension.py,sha256=ZSsbi7n-tFw-7RQX7c3pV1qWsRt72qS_3AlAYjV53jA,2393
|
|
@@ -40,7 +44,7 @@ pdd/git_update.py,sha256=Ya7eI7YFtGIpT7FdziFJfnFkiZlj8I9Lh98lqtXfClc,2855
|
|
|
40
44
|
pdd/increase_tests.py,sha256=dlYd9PosV3g8kpDlQh6gd8WUauClvs_-Z8ERRD-kZk4,3456
|
|
41
45
|
pdd/insert_includes.py,sha256=UASoq_46UNL6l7VGB7DW2jb4kcWlP6Hbj2EWuh7210Q,5310
|
|
42
46
|
pdd/install_completion.py,sha256=H_FIid0eHCn7I6HHIsBqdComAxjLIu7CbD6yfMU48aw,5085
|
|
43
|
-
pdd/llm_invoke.py,sha256=
|
|
47
|
+
pdd/llm_invoke.py,sha256=457rD3f7KQHJ3BtI4boxTurArCww2zWAl4X77TxVROs,65788
|
|
44
48
|
pdd/load_prompt_template.py,sha256=4NH8_t5eon_vcyTznqtemJ_yAPkTJm_hSdTRgzj3qEQ,1907
|
|
45
49
|
pdd/mcp_config.json,sha256=D3ctWHlShvltbtH37zbYb6smVE0V80_lGjDKDIqsSBE,124
|
|
46
50
|
pdd/pdd_completion.fish,sha256=rs-43fa3kcDBN1uy4oxiofLAWmaqW0U2j5Mu4wCHh5M,6121
|
|
@@ -83,10 +87,10 @@ pdd/prompts/extract_prompt_update_LLM.prompt,sha256=XH2muMzTb_wqcQS9rR4THXe6TP7B
|
|
|
83
87
|
pdd/prompts/extract_promptline_LLM.prompt,sha256=owIBRaF2bWwg3S64uyMKzOFMdvvmI_EEGoF97Pa9118,813
|
|
84
88
|
pdd/prompts/extract_unit_code_fix_LLM.prompt,sha256=c4l6twMLC2YqDDvOj_DcaKmJQF8kIupeqvkueK_OQng,14301
|
|
85
89
|
pdd/prompts/extract_xml_LLM.prompt,sha256=eRcHaL-khShpb7C1_b7wmBJHfo2Kh1Wvjo_aOcWZovU,561
|
|
86
|
-
pdd/prompts/find_verification_errors_LLM.prompt,sha256=
|
|
90
|
+
pdd/prompts/find_verification_errors_LLM.prompt,sha256=sBax_pfe-mFW4kY-vhvE_AFQwNSsofNLmnxYz_SYzUo,2797
|
|
87
91
|
pdd/prompts/fix_code_module_errors_LLM.prompt,sha256=sjqB-apFtiMZerXm_qZEuA6pfRtk2hOiXxPXwuxIZxM,2462
|
|
88
92
|
pdd/prompts/fix_errors_from_unit_tests_LLM.prompt,sha256=Yy6WIg9WfizrFpFZogoCtlQy-H123ycc_SaF6m8_Ljo,5079
|
|
89
|
-
pdd/prompts/fix_verification_errors_LLM.prompt,sha256=
|
|
93
|
+
pdd/prompts/fix_verification_errors_LLM.prompt,sha256=8GLdGBFMPWRnOw-D1CEObSPqw6FdzEgmGhui6oA_EzY,3474
|
|
90
94
|
pdd/prompts/generate_test_LLM.prompt,sha256=eCI7CTMpoA76DTruTgWygClxJX0gj_uNxTqHbmqcJ50,2254
|
|
91
95
|
pdd/prompts/increase_tests_LLM.prompt,sha256=rekFzLRuZy99KifEKNlmPYoQdl8wa04112mtCdIY6S8,955
|
|
92
96
|
pdd/prompts/insert_includes_LLM.prompt,sha256=g-p2gXKENsqvfK5Q9FYbqFsIJ5CP7rbxmd4rROA-W80,1453
|
|
@@ -98,9 +102,9 @@ pdd/prompts/trim_results_start_LLM.prompt,sha256=OKz8fAf1cYWKWgslFOHEkUpfaUDARh3
|
|
|
98
102
|
pdd/prompts/unfinished_prompt_LLM.prompt,sha256=-JgBpiPTQZdWOAwOG1XpfpD9waynFTAT3Jo84eQ4bTw,1543
|
|
99
103
|
pdd/prompts/update_prompt_LLM.prompt,sha256=prIc8uLp2jqnLTHt6JvWDZGanPZipivhhYeXe0lVaYw,1328
|
|
100
104
|
pdd/prompts/xml_convertor_LLM.prompt,sha256=YGRGXJeg6EhM9690f-SKqQrKqSJjLFD51UrPOlO0Frg,2786
|
|
101
|
-
pdd_cli-0.0.
|
|
102
|
-
pdd_cli-0.0.
|
|
103
|
-
pdd_cli-0.0.
|
|
104
|
-
pdd_cli-0.0.
|
|
105
|
-
pdd_cli-0.0.
|
|
106
|
-
pdd_cli-0.0.
|
|
105
|
+
pdd_cli-0.0.27.dist-info/licenses/LICENSE,sha256=-1bjYH-CEjGEQ8VixtnRYuu37kN6F9NxmZSDkBuUQ9o,1062
|
|
106
|
+
pdd_cli-0.0.27.dist-info/METADATA,sha256=wMbiINMThQNBEc0_NyQ5jjQxkP31CjT1nA1jfrB0DpY,6911
|
|
107
|
+
pdd_cli-0.0.27.dist-info/WHEEL,sha256=DnLRTWE75wApRYVsjgc6wsVswC54sMSJhAEd4xhDpBk,91
|
|
108
|
+
pdd_cli-0.0.27.dist-info/entry_points.txt,sha256=Kr8HtNVb8uHZtQJNH4DnF8j7WNgWQbb7_Pw5hECSR-I,36
|
|
109
|
+
pdd_cli-0.0.27.dist-info/top_level.txt,sha256=xjnhIACeMcMeDfVNREgQZl4EbTni2T11QkL5r7E-sbE,4
|
|
110
|
+
pdd_cli-0.0.27.dist-info/RECORD,,
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|