daytona-upgrade 0.1.0__tar.gz

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.
Files changed (162) hide show
  1. daytona_upgrade-0.1.0/.gitignore +5 -0
  2. daytona_upgrade-0.1.0/LICENSE +202 -0
  3. daytona_upgrade-0.1.0/PKG-INFO +291 -0
  4. daytona_upgrade-0.1.0/README.md +277 -0
  5. daytona_upgrade-0.1.0/pyproject.toml +48 -0
  6. daytona_upgrade-0.1.0/src/daytona_upgrade/__init__.py +11 -0
  7. daytona_upgrade-0.1.0/src/daytona_upgrade/__main__.py +5 -0
  8. daytona_upgrade-0.1.0/src/daytona_upgrade/_assignment_proofs.py +257 -0
  9. daytona_upgrade-0.1.0/src/daytona_upgrade/_dependencies.py +261 -0
  10. daytona_upgrade-0.1.0/src/daytona_upgrade/_manifest_cfg.py +124 -0
  11. daytona_upgrade-0.1.0/src/daytona_upgrade/_manifest_resolvers.py +120 -0
  12. daytona_upgrade-0.1.0/src/daytona_upgrade/_manifest_setup.py +253 -0
  13. daytona_upgrade-0.1.0/src/daytona_upgrade/_member_write_flow.py +64 -0
  14. daytona_upgrade-0.1.0/src/daytona_upgrade/_project_index_model.py +65 -0
  15. daytona_upgrade-0.1.0/src/daytona_upgrade/_requirements.py +123 -0
  16. daytona_upgrade-0.1.0/src/daytona_upgrade/_scopes.py +261 -0
  17. daytona_upgrade-0.1.0/src/daytona_upgrade/_setup_values.py +57 -0
  18. daytona_upgrade-0.1.0/src/daytona_upgrade/_setup_writes.py +46 -0
  19. daytona_upgrade-0.1.0/src/daytona_upgrade/_workflow_index.py +207 -0
  20. daytona_upgrade-0.1.0/src/daytona_upgrade/_workflow_scopes.py +133 -0
  21. daytona_upgrade-0.1.0/src/daytona_upgrade/analysis_filter.py +141 -0
  22. daytona_upgrade-0.1.0/src/daytona_upgrade/annotation_exports.py +143 -0
  23. daytona_upgrade-0.1.0/src/daytona_upgrade/annotation_flow.py +141 -0
  24. daytona_upgrade-0.1.0/src/daytona_upgrade/annotation_proofs.py +257 -0
  25. daytona_upgrade-0.1.0/src/daytona_upgrade/annotations.py +109 -0
  26. daytona_upgrade-0.1.0/src/daytona_upgrade/attribute_proofs.py +241 -0
  27. daytona_upgrade-0.1.0/src/daytona_upgrade/attributes.py +150 -0
  28. daytona_upgrade-0.1.0/src/daytona_upgrade/augmented_proofs.py +49 -0
  29. daytona_upgrade-0.1.0/src/daytona_upgrade/bindings.py +150 -0
  30. daytona_upgrade-0.1.0/src/daytona_upgrade/call_proofs.py +100 -0
  31. daytona_upgrade-0.1.0/src/daytona_upgrade/call_sites.py +93 -0
  32. daytona_upgrade-0.1.0/src/daytona_upgrade/calls.py +231 -0
  33. daytona_upgrade-0.1.0/src/daytona_upgrade/class_field_mutations.py +60 -0
  34. daytona_upgrade-0.1.0/src/daytona_upgrade/class_imports.py +46 -0
  35. daytona_upgrade-0.1.0/src/daytona_upgrade/class_method_stores.py +53 -0
  36. daytona_upgrade-0.1.0/src/daytona_upgrade/class_stores.py +225 -0
  37. daytona_upgrade-0.1.0/src/daytona_upgrade/classflow.py +249 -0
  38. daytona_upgrade-0.1.0/src/daytona_upgrade/cli.py +262 -0
  39. daytona_upgrade-0.1.0/src/daytona_upgrade/client_double_targets.py +220 -0
  40. daytona_upgrade-0.1.0/src/daytona_upgrade/client_parameters.py +164 -0
  41. daytona_upgrade-0.1.0/src/daytona_upgrade/cloud_api_url.py +15 -0
  42. daytona_upgrade-0.1.0/src/daytona_upgrade/collection_proofs.py +223 -0
  43. daytona_upgrade-0.1.0/src/daytona_upgrade/comments.py +45 -0
  44. daytona_upgrade-0.1.0/src/daytona_upgrade/compose_detection.py +65 -0
  45. daytona_upgrade-0.1.0/src/daytona_upgrade/compose_discovery.py +64 -0
  46. daytona_upgrade-0.1.0/src/daytona_upgrade/compose_environment.py +140 -0
  47. daytona_upgrade-0.1.0/src/daytona_upgrade/compose_includes.py +235 -0
  48. daytona_upgrade-0.1.0/src/daytona_upgrade/compose_projects.py +107 -0
  49. daytona_upgrade-0.1.0/src/daytona_upgrade/compose_yaml.py +271 -0
  50. daytona_upgrade-0.1.0/src/daytona_upgrade/compoundflow.py +117 -0
  51. daytona_upgrade-0.1.0/src/daytona_upgrade/config.py +141 -0
  52. daytona_upgrade-0.1.0/src/daytona_upgrade/config_arguments.py +54 -0
  53. daytona_upgrade-0.1.0/src/daytona_upgrade/config_constructor.py +55 -0
  54. daytona_upgrade-0.1.0/src/daytona_upgrade/config_factory_calls.py +157 -0
  55. daytona_upgrade-0.1.0/src/daytona_upgrade/config_literal_mappings.py +61 -0
  56. daytona_upgrade-0.1.0/src/daytona_upgrade/config_members.py +156 -0
  57. daytona_upgrade-0.1.0/src/daytona_upgrade/config_messages.py +38 -0
  58. daytona_upgrade-0.1.0/src/daytona_upgrade/config_origins.py +233 -0
  59. daytona_upgrade-0.1.0/src/daytona_upgrade/config_readers.py +182 -0
  60. daytona_upgrade-0.1.0/src/daytona_upgrade/config_uses.py +204 -0
  61. daytona_upgrade-0.1.0/src/daytona_upgrade/constructor_access.py +137 -0
  62. daytona_upgrade-0.1.0/src/daytona_upgrade/constructor_errors.py +192 -0
  63. daytona_upgrade-0.1.0/src/daytona_upgrade/constructor_parameters.py +93 -0
  64. daytona_upgrade-0.1.0/src/daytona_upgrade/constructor_safety.py +180 -0
  65. daytona_upgrade-0.1.0/src/daytona_upgrade/context_managers.py +84 -0
  66. daytona_upgrade-0.1.0/src/daytona_upgrade/controlflow.py +274 -0
  67. daytona_upgrade-0.1.0/src/daytona_upgrade/dependency_scope.py +117 -0
  68. daytona_upgrade-0.1.0/src/daytona_upgrade/dependency_versions.py +30 -0
  69. daytona_upgrade-0.1.0/src/daytona_upgrade/descriptors.py +178 -0
  70. daytona_upgrade-0.1.0/src/daytona_upgrade/docker_environment.py +110 -0
  71. daytona_upgrade-0.1.0/src/daytona_upgrade/dotenv_environment.py +162 -0
  72. daytona_upgrade-0.1.0/src/daytona_upgrade/double_ownership.py +143 -0
  73. daytona_upgrade-0.1.0/src/daytona_upgrade/double_rewrites.py +62 -0
  74. daytona_upgrade-0.1.0/src/daytona_upgrade/environment.py +215 -0
  75. daytona_upgrade-0.1.0/src/daytona_upgrade/environment_paths.py +130 -0
  76. daytona_upgrade-0.1.0/src/daytona_upgrade/environment_python.py +258 -0
  77. daytona_upgrade-0.1.0/src/daytona_upgrade/environment_values.py +17 -0
  78. daytona_upgrade-0.1.0/src/daytona_upgrade/export_checks.py +69 -0
  79. daytona_upgrade-0.1.0/src/daytona_upgrade/expression_names.py +23 -0
  80. daytona_upgrade-0.1.0/src/daytona_upgrade/external_calls.py +67 -0
  81. daytona_upgrade-0.1.0/src/daytona_upgrade/factory_consumers.py +75 -0
  82. daytona_upgrade-0.1.0/src/daytona_upgrade/factory_patch_reviews.py +64 -0
  83. daytona_upgrade-0.1.0/src/daytona_upgrade/factory_patch_scopes.py +130 -0
  84. daytona_upgrade-0.1.0/src/daytona_upgrade/fallback_proofs.py +75 -0
  85. daytona_upgrade-0.1.0/src/daytona_upgrade/field_arguments.py +192 -0
  86. daytona_upgrade-0.1.0/src/daytona_upgrade/field_effects.py +208 -0
  87. daytona_upgrade-0.1.0/src/daytona_upgrade/field_factories.py +119 -0
  88. daytona_upgrade-0.1.0/src/daytona_upgrade/field_initialization.py +107 -0
  89. daytona_upgrade-0.1.0/src/daytona_upgrade/field_safety.py +90 -0
  90. daytona_upgrade-0.1.0/src/daytona_upgrade/flow.py +265 -0
  91. daytona_upgrade-0.1.0/src/daytona_upgrade/function_proofs.py +108 -0
  92. daytona_upgrade-0.1.0/src/daytona_upgrade/functionflow.py +260 -0
  93. daytona_upgrade-0.1.0/src/daytona_upgrade/generated_parameters.py +103 -0
  94. daytona_upgrade-0.1.0/src/daytona_upgrade/generator_proofs.py +259 -0
  95. daytona_upgrade-0.1.0/src/daytona_upgrade/import_only_clients.py +114 -0
  96. daytona_upgrade-0.1.0/src/daytona_upgrade/importflow.py +173 -0
  97. daytona_upgrade-0.1.0/src/daytona_upgrade/imports.py +173 -0
  98. daytona_upgrade-0.1.0/src/daytona_upgrade/instance_fields.py +159 -0
  99. daytona_upgrade-0.1.0/src/daytona_upgrade/lexical.py +75 -0
  100. daytona_upgrade-0.1.0/src/daytona_upgrade/local_class_doubles.py +134 -0
  101. daytona_upgrade-0.1.0/src/daytona_upgrade/local_double_targets.py +189 -0
  102. daytona_upgrade-0.1.0/src/daytona_upgrade/local_doubles.py +251 -0
  103. daytona_upgrade-0.1.0/src/daytona_upgrade/loopflow.py +145 -0
  104. daytona_upgrade-0.1.0/src/daytona_upgrade/manifest_errors.py +53 -0
  105. daytona_upgrade-0.1.0/src/daytona_upgrade/manifests.py +225 -0
  106. daytona_upgrade-0.1.0/src/daytona_upgrade/mapping.json +5743 -0
  107. daytona_upgrade-0.1.0/src/daytona_upgrade/member_mutations.py +159 -0
  108. daytona_upgrade-0.1.0/src/daytona_upgrade/mock_configuration.py +23 -0
  109. daytona_upgrade-0.1.0/src/daytona_upgrade/mock_filter.py +89 -0
  110. daytona_upgrade-0.1.0/src/daytona_upgrade/mock_inference.py +228 -0
  111. daytona_upgrade-0.1.0/src/daytona_upgrade/mock_links.py +30 -0
  112. daytona_upgrade-0.1.0/src/daytona_upgrade/mock_module_factories.py +61 -0
  113. daytona_upgrade-0.1.0/src/daytona_upgrade/mock_proofs.py +219 -0
  114. daytona_upgrade-0.1.0/src/daytona_upgrade/mock_spec_origins.py +241 -0
  115. daytona_upgrade-0.1.0/src/daytona_upgrade/models.py +165 -0
  116. daytona_upgrade-0.1.0/src/daytona_upgrade/module_proofs.py +24 -0
  117. daytona_upgrade-0.1.0/src/daytona_upgrade/notebook_environment.py +40 -0
  118. daytona_upgrade-0.1.0/src/daytona_upgrade/notebook_json.py +123 -0
  119. daytona_upgrade-0.1.0/src/daytona_upgrade/notebooks.py +244 -0
  120. daytona_upgrade-0.1.0/src/daytona_upgrade/parameter_proofs.py +101 -0
  121. daytona_upgrade-0.1.0/src/daytona_upgrade/parameter_relay_flow.py +94 -0
  122. daytona_upgrade-0.1.0/src/daytona_upgrade/parameter_relay_uses.py +231 -0
  123. daytona_upgrade-0.1.0/src/daytona_upgrade/parameter_usage.py +202 -0
  124. daytona_upgrade-0.1.0/src/daytona_upgrade/partial_analysis.py +114 -0
  125. daytona_upgrade-0.1.0/src/daytona_upgrade/persistent_workflow.py +48 -0
  126. daytona_upgrade-0.1.0/src/daytona_upgrade/prefix_proofs.py +54 -0
  127. daytona_upgrade-0.1.0/src/daytona_upgrade/project.py +257 -0
  128. daytona_upgrade-0.1.0/src/daytona_upgrade/project_configs.py +186 -0
  129. daytona_upgrade-0.1.0/src/daytona_upgrade/project_dependencies.py +31 -0
  130. daytona_upgrade-0.1.0/src/daytona_upgrade/project_discovery.py +169 -0
  131. daytona_upgrade-0.1.0/src/daytona_upgrade/project_environment.py +53 -0
  132. daytona_upgrade-0.1.0/src/daytona_upgrade/project_index.py +125 -0
  133. daytona_upgrade-0.1.0/src/daytona_upgrade/project_paths.py +211 -0
  134. daytona_upgrade-0.1.0/src/daytona_upgrade/project_progress.py +53 -0
  135. daytona_upgrade-0.1.0/src/daytona_upgrade/project_result.py +43 -0
  136. daytona_upgrade-0.1.0/src/daytona_upgrade/proof_mutations.py +88 -0
  137. daytona_upgrade-0.1.0/src/daytona_upgrade/pytest_collection.py +100 -0
  138. daytona_upgrade-0.1.0/src/daytona_upgrade/python_floor.py +48 -0
  139. daytona_upgrade-0.1.0/src/daytona_upgrade/reachability.py +18 -0
  140. daytona_upgrade-0.1.0/src/daytona_upgrade/reflective_names.py +116 -0
  141. daytona_upgrade-0.1.0/src/daytona_upgrade/regular_files.py +32 -0
  142. daytona_upgrade-0.1.0/src/daytona_upgrade/report_items.py +18 -0
  143. daytona_upgrade-0.1.0/src/daytona_upgrade/requirement_rendering.py +40 -0
  144. daytona_upgrade-0.1.0/src/daytona_upgrade/resolution.py +212 -0
  145. daytona_upgrade-0.1.0/src/daytona_upgrade/return_proofs.py +175 -0
  146. daytona_upgrade-0.1.0/src/daytona_upgrade/review_forwarding.py +60 -0
  147. daytona_upgrade-0.1.0/src/daytona_upgrade/safety.py +77 -0
  148. daytona_upgrade-0.1.0/src/daytona_upgrade/shared_error_guidance.py +100 -0
  149. daytona_upgrade-0.1.0/src/daytona_upgrade/source_encoding.py +76 -0
  150. daytona_upgrade-0.1.0/src/daytona_upgrade/source_text.py +38 -0
  151. daytona_upgrade-0.1.0/src/daytona_upgrade/source_transform.py +46 -0
  152. daytona_upgrade-0.1.0/src/daytona_upgrade/store_names.py +46 -0
  153. daytona_upgrade-0.1.0/src/daytona_upgrade/subclasses.py +228 -0
  154. daytona_upgrade-0.1.0/src/daytona_upgrade/suggestion_owners.py +170 -0
  155. daytona_upgrade-0.1.0/src/daytona_upgrade/suggestions.py +243 -0
  156. daytona_upgrade-0.1.0/src/daytona_upgrade/toml_values.py +35 -0
  157. daytona_upgrade-0.1.0/src/daytona_upgrade/transform.py +276 -0
  158. daytona_upgrade-0.1.0/src/daytona_upgrade/url_writes.py +165 -0
  159. daytona_upgrade-0.1.0/src/daytona_upgrade/wildcard_exports.py +82 -0
  160. daytona_upgrade-0.1.0/src/daytona_upgrade/wildcard_imports.py +42 -0
  161. daytona_upgrade-0.1.0/src/daytona_upgrade/writes.py +89 -0
  162. daytona_upgrade-0.1.0/src/daytona_upgrade/yaml_flow.py +205 -0
@@ -0,0 +1,5 @@
1
+ .venv/
2
+ dist/
3
+ __pycache__/
4
+ .pytest_cache/
5
+ .ruff_cache/
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright [yyyy] [name of copyright owner]
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
@@ -0,0 +1,291 @@
1
+ Metadata-Version: 2.5
2
+ Name: daytona-upgrade
3
+ Version: 0.1.0
4
+ Summary: Upgrade Daytona 0.x Python projects to SDK 2.x on the v0 namespace
5
+ Project-URL: Homepage, https://github.com/daytona/rlp
6
+ Project-URL: Repository, https://github.com/daytona/rlp
7
+ License-Expression: Apache-2.0
8
+ License-File: LICENSE
9
+ Requires-Python: >=3.9
10
+ Requires-Dist: libcst<2,>=1.8
11
+ Requires-Dist: packaging<27,>=24
12
+ Requires-Dist: tomlkit<0.14,>=0.13
13
+ Description-Content-Type: text/markdown
14
+
15
+ # daytona-upgrade for Python
16
+
17
+ Upgrade Daytona SDK 0.x projects to SDK 2.x **without moving workloads to v2**. The tool keeps the root `Daytona` / `AsyncDaytona` client, adds `.v0` to proven client calls, moves resource imports and all shared errors unconditionally to `daytona.v0` to preserve 0.x constructors, attributes and `except` behavior, and updates dependencies to `daytona[v0-sdk]>=2,<3`. Unproven calls get a `FIXME(daytona-upgrade)` only when their receiver is linked to Daytona; calls with no such evidence (including generic names, dict-held or `Any`-typed clients) get no FIXME and must be reviewed by hand. The tool is precision-first and best-effort, not a completeness verifier. Dynamic `__all__` keeps known unrelated exports non-client while making client or unknown exports uncertain, including nested wildcard imports. Possible replacements never preserve stale local Daytona proofs.
18
+
19
+ Requires Python 3.9 or later.
20
+ SDK 2.x requires Python 3.10 or later; update your application's supported versions before installing it. Dependency markers stay unchanged.
21
+ Run this tool with an interpreter that supports your source syntax.
22
+
23
+ ```bash
24
+ uvx daytona-upgrade --dry # preview the patch
25
+ uvx daytona-upgrade . --yes # upgrade a clean Git tree
26
+ pipx run daytona-upgrade path/to/project # alternative runner
27
+ ```
28
+
29
+ **No installers or lockfile updates run.** Review the changes, run the printed lock/install command, and test your application. Keep custom/self-hosted API URLs on SDK 0.x: the tool refuses those projects before writing any files.
30
+ SDK 2.x builds the v0 client lazily. A root constructor inside a `try` that catches Daytona errors receives a manual item and FIXME only when that client's `.v0` is not accessed there, including accesses added by the upgrade. Access the assigned client's `.v0` inside that `try` to keep credential errors within its handlers.
31
+ For constructor keywords, `--drop-api-url` only permits dropping non-literal URLs that you assert target Daytona Cloud; it does not permit a literal custom URL.
32
+ Unresolved `DaytonaConfig(**options)` mappings also require that assertion;
33
+ the call is left unchanged with a manual-review item. Literal dictionaries
34
+ are inspected like explicit keyword arguments.
35
+ An unknown `**options` remains unresolved even alongside an explicit Cloud
36
+ `api_url` or `server_url`, in either order. Python rejects duplicate keywords at
37
+ runtime, but the tool does not infer URL safety from that runtime constraint.
38
+ Attribute assignments and `setattr` writes of `api_url` / `server_url` are
39
+ checked only on names constructed or annotated as `DaytonaConfig`, including
40
+ lexically enclosing module configs used in functions or methods. Unrelated URL
41
+ fields are untouched. Every proven `Daytona(config)` / `AsyncDaytona(config)`
42
+ construction requires a config whose origin and URL safety can be verified across
43
+ its uses, including later nested writes. Printing, standard logging, `repr`, `str`,
44
+ `json.dumps`, f-strings and config field reads do not escape; unknown calls and aliases do.
45
+ SDK 2.x `DaytonaConfig` is a dataclass, not a Pydantic model: known Pydantic APIs get
46
+ `config-field` items and FIXMEs. Replace `model_dump` / `dict` with `dataclasses.asdict(cfg)`,
47
+ `model_copy` / `copy` with `dataclasses.replace(cfg, ...)`, and `model_validate` / `parse_obj` with `DaytonaConfig(**values)`.
48
+ Literal copy updates and validation dictionaries receive the same URL checks as constructors.
49
+ Undecorated synchronous factories consisting of a direct `return DaytonaConfig(...)` carry literal-origin proof, including through project imports. Their returned constructors receive the same URL checks as inline configs; a return annotation alone does not establish URL safety.
50
+ Other unresolved configs (including parameters and opaque factories or imports) require `--drop-api-url`, named in messages and JSON next steps; they stay manual. Shadowed readers are untrusted.
51
+ Literal Cloud URLs and `None` (the 0.x default) are removed; other writes refuse
52
+ the upgrade. With `--drop-api-url`, those unresolved writes are instead left
53
+ unchanged with a `config-field` item for manual removal.
54
+
55
+ ## Optional v2 guidance
56
+
57
+ ```bash
58
+ uvx daytona-upgrade --suggest-v2
59
+ uvx daytona-upgrade --suggest-v2 --json # report only; writes nothing
60
+ uvx daytona-upgrade --remove-suggestions
61
+ ```
62
+
63
+ Suggestions are tagged `daytona-v2:` comments, with the v2 equivalent, behavior differences, workflow dependencies, and migration documentation links.
64
+ Shared-error guidance covers named imports and namespace imports such as
65
+ `import daytona.v0 as sdk` when their shared error classes are used.
66
+ Service aliases use the owning sandbox when known; otherwise suggestions use the service handle directly when the v2 call stays on that service.
67
+ Calls that move to another service ask you to move the call to the owning sandbox, with `sandbox` as the example receiver. Workflow headers include calls through sandbox and service aliases.
68
+ Calls inside nested functions that use the sandbox count too.
69
+ If a closure declares the binding `global` or `nonlocal`, rebinds it, and calls a lifecycle method, the earlier producer's workflow is also marked persistence-dependent; keep it on `.v0`.
70
+ Workflows with root sandbox `start`, `stop`, `pause`, `archive`, `set_autostop_interval`, `set_auto_pause_interval`, or `set_auto_archive_interval` calls, or client `start`/`stop` calls taking the sandbox, are marked to stay on `.v0`: SDK 2.x `create()` cannot make the persistent sandbox they need yet.
71
+ The header names those calls in source order within that workflow, ending direct-call membership when its sandbox binding is reassigned. Deferred calls in nested functions and lambdas count whether declared before or after the producer, including simple local sandbox aliases inside those functions; unrelated shadowed parameters and locals do not. The first iterable of a comprehension or generator expression is evaluated eagerly in its enclosing scope and follows that binding's direct-call window. Client calls retain their single-line callee text (for example, `d.v0.stop`), while sandbox calls use the bare method name. `set_auto_delete_interval` does not trigger this header.
72
+ They never change calls or dependencies. Re-running replaces the tagged comments;
73
+ removal deletes only those comments. `FIXME(daytona-upgrade)` comments are kept
74
+ for you to resolve manually. v0 IDs, snapshots, volumes and preview URLs
75
+ do not automatically carry over to v2. Documentation links point at the Daytona
76
+ docs until the dedicated migration guide is published.
77
+
78
+ ## Options
79
+
80
+ | Option | Behavior |
81
+ |---|---|
82
+ | `[path]` | Project root (default: current directory), or a single file |
83
+ | `--dry` | Print a unified diff; write nothing and skip Git safety |
84
+ | `--print` | Print changed files; write nothing and skip Git safety |
85
+ | `--json` | Print the shared report schema; with `--suggest-v2`, write nothing and skip Git safety |
86
+ | `--force` | Skip the Git check entirely, allowing uncommitted changes |
87
+ | `-y`, `--yes` | Skip confirmation (also automatic for non-interactive stdin) |
88
+ | `--drop-api-url` | Accept API URLs the tool cannot verify or that come from the environment, asserting they point at Daytona Cloud |
89
+ | `--strict` | Exit 1 if manual review items remain |
90
+ | `-v`, `--version` | Print version |
91
+ | `-h`, `--help` | Print usage |
92
+
93
+ Exit codes: **0** completed (manual items may remain), **1** internal/input
94
+ processing error or strict-mode manual items, **2** refused (dirty tree, custom
95
+ API URL, a project-owned SDK module, invalid arguments, or no Daytona dependency/code).
96
+
97
+ ## Scope and safety
98
+
99
+ Synchronous `Daytona` spec/autospec mocks route proven members through `.v0`, including proven pytest fixture returns and yields.
100
+ Bare local doubles adapt only when their consumers' accesses through the parameter
101
+ move to `.v0` too, without forwarding to unrewritten code or other unresolved uses. Otherwise they stay
102
+ unchanged; a consumer with moved accesses requires `mock-target` review.
103
+ Default factory-patch review follows indexed calls within the decorated function or
104
+ `with` block, or the test function for started patches and patch fixtures. An unused
105
+ default patch, or one reaching only unchanged consumers, produces no item. Unknown
106
+ patch lifetimes and unpacked options retain conservative review. Explicit replacement
107
+ expressions still undergo the existing double-shape review.
108
+ Local fake modules replacing proven SDK-module helpers route known 0.x submodule paths;
109
+ uncertain replacements retain `mock-target` review.
110
+ Check FastAPI `dependency_overrides` fakes, `functools.wraps`-decorated consumers,
111
+ and detached bound-method aliases by hand; their test-double setup and assertions are not followed.
112
+ Indexed, undecorated functions retain client-argument links in unannotated parameters, across project imports and forwarding chains.
113
+ These links produce FIXMEs, never inferred annotations or automatic `.v0` rewrites.
114
+ The spec must be positively resolved to the synchronous class, including aliases or a synchronous factory annotated `type[Daytona]`. Nullable class-return annotations and overwritten factories require review, not `.v0` routing. A client-class annotation alone is not proof of synchronous origin. Class/static/instance factories and postponed annotations use the same rule; other client-typed specs require `mock-target` review.
115
+ `AsyncDaytona` spec mocks, including walrus aliases and conditional async/unresolved specs, require review:
116
+ SDK 2.x's `.v0` property does not auto-create async mock methods. Configure it with a separate async-spec'd mock before migrating awaited calls.
117
+ For synchronous instance mocks, `configure_mock` literal moved-member keys become `v0.<key>`, including dotted paths and keywords.
118
+ Dynamic or colliding keys stay unchanged with `mock-target` review and invalidate later rewrite proofs for the mock and possible aliases.
119
+ `v0`, `v2`, and `close` configuration stays on the root. Manual items fail `--strict`.
120
+
121
+ Constructor mocks such as `patch("app.Daytona")` receive a `mock-target` item: configure moved methods under `return_value.v0`. Unrelated mock targets and user-defined `patch` helpers are left alone. Mock review retains earlier Daytona construction evidence after rebinding, never as proof for rewriting ordinary calls. Generated dataclass constructors prove unchanged defaults and direct factories; annotated attrs and Pydantic fields also prove direct client factories without converters, validators or custom initialization hooks. Uncertain initialization retains FIXME review. An explicit dataclass field argument takes precedence, but proves a field only with generated initialization or a direct, same-name parameter store. Unknown spreads, inherited signatures and uncertain `kw_only` options preserve linked calls as FIXMEs. `ClassVar` and `KW_ONLY` declarations occupy no constructor position; fields after `KW_ONLY` are keyword-only unless explicitly overridden. `InitVar` inputs occupy constructor positions but never prove instance attributes. Explicitly typed `self` fields retain their existing policy unless custom or replaced attribute read, write or delete hooks make field lookups opaque.
122
+
123
+ Python `.py`, `.pyi`, and notebook code cells are discovered recursively. Pytest fixture evidence applies to collected test functions and methods, decorated fixtures, and functions in `conftest.py`, never ordinary production functions merely sharing fixture parameter names. Collection defaults to `test_*.py` / `*_test.py` modules, `test`-prefixed functions and `Test`-prefixed classes. The tool searches from the scan directory (the parent for a single file) upward to the filesystem root for collection settings. At each directory it checks `pytest.ini`, `pyproject.toml` with `[tool.pytest.ini_options]`, `tox.ini` with `[pytest]`, then `setup.cfg` with `[tool:pytest]`; the first applicable file wins without merging. Nearest fixture declarations still take precedence over ancestor `conftest.py` declarations.
124
+ Virtual environments, generated trees, Git metadata and symlinks are skipped. Scans exceeding 200 files print progress to stderr; smaller scans also print a status line after three seconds. JSON reports remain on stdout. Analysis is whole-project and grows with the code scanned: a ~40k-line tree takes about five minutes, and a large monorepo can take much longer, so point the tool at the directories that use Daytona (plus their tests and the dependency manifest) rather than the repository root.
125
+ Files are syntax-checked before flow filtering; relevant imports, environment writes, mocks, dynamic imports, unresolved wildcard exports and implicit pytest fixture links retain analysis. Fixture definitions, conftests and pytest plugin declarations are retained even without an explicit SDK import. Unrelated files retain import ownership.
126
+ In both tools, an unreadable file or directory inside the scanned tree produces
127
+ an `unsupported-file` item: `<path> could not be read: <strerror>; fix its permissions, then rerun.`
128
+ (`fix the problem, then rerun.` for a non-permission error)
129
+ Paths are project-relative; the run exits 1 without writing any files (a readable
130
+ custom API URL still takes precedence and refuses with exit 2).
131
+ Upgrades refuse for a `daytona` or `daytona_sdk` module (`.py` or `.pyi`) or
132
+ regular package (containing `__init__.py`) or namespace directory containing
133
+ Python sources (`.py` or `.pyi`) directly in an import root: the scan base,
134
+ `src/`, directories containing a supported dependency manifest, or source roots
135
+ declared in `pyproject.toml` by setuptools, Poetry or Hatch. Single-file scans
136
+ also check sibling modules, regular packages and namespace sources.
137
+ Rename a colliding local module before rerunning: it can shadow the SDK, or the
138
+ installed SDK can override a namespace portion and break local imports.
139
+ Nested regular packages elsewhere produce a non-blocking `private-import` item:
140
+ they shadow the SDK only if their parent directory is on `sys.path`.
141
+ Directories without Python sources do not refuse; ignored trees such as
142
+ `.venv`, `.tox`, `site-packages` and `node_modules` remain excluded.
143
+ Suggestion/removal modes remain available.
144
+ Notebook cells share flow analysis in document order; IPython magic lines are
145
+ preserved, and `%pip install` / `!pip install` Daytona requirements are updated.
146
+ Notebook edits preserve the original JSON bytes outside changed code-cell
147
+ sources, including metadata, outputs, key order, indentation, and the presence
148
+ or absence of a final newline.
149
+ Notebook diagnostics use `file.ipynb#cell=N:line:column`, with a one-based cell
150
+ index (including non-code cells) and a line number local to that cell.
151
+ Before masking magic lines, `%env` / `%set_env` assignments (`NAME=value` or
152
+ `NAME value`) and single `!export NAME=value` assignments receive the same
153
+ environment URL checks as Python writes. `%env` reads are ignored;
154
+ `$variable` / `{expression}` interpolation requires manual review rather than
155
+ being treated as a literal URL.
156
+
157
+ Supported manifests: `requirements*.txt`, `*-requirements.txt` (including
158
+ `dev-requirements.txt`), `requirements*.in`, `constraints*.in`, `constraints*.txt`,
159
+ `pyproject.toml`, `setup.cfg`, `setup.py`, and `Pipfile`.
160
+ Standalone `constraints*.txt` files retain constraint semantics: their versions
161
+ can migrate, but a manual item reminds you to enable `v0-sdk` on the consuming
162
+ requirement. Invalid TOML produces a file-specific `unsupported-file` item and
163
+ blocks writes without printing a traceback; other supported manifest parse
164
+ failures also name the project-relative file.
165
+ Recognized environment/deployment files (`.env*`, `Dockerfile*`, compose YAML, YAML under `k8s/`, `helm/`, `charts/`, or `deploy/`, and `.github/workflows/`) are scanned for Daytona API URL variables and reported for review, never modified. Compose service `env_file` and `include[].env_file` inputs are scanned at every plausible project base, including literal include `project_directory` values; literal `include[].path` manifests are scanned recursively with a cycle guard, regardless of filename. Dynamic, aliased, or unparseable includes retain environment review. Deployment directories are matched relative to the Git checkout (the whole absolute path when Git cannot answer), so scanning `deploy/` directly applies the same checks as scanning its parent.
166
+ Binding-proven `load_dotenv` / `dotenv_values` calls also scan explicitly loaded files regardless of filename, including `dotenv_path=`, literal aliases, `find_dotenv("name.env")`, `Path(__file__).parent / "name.env"`, and `os.path.join(os.path.dirname(__file__), "name.env")`. Explicit relative paths are checked against both the selected project root and the source file's directory. Default loaders and `find_dotenv` scan every existing candidate from the source directory upward through the selected root, including intermediate directories. Pydantic-settings `SettingsConfigDict(env_file=...)`, nested `class Config: env_file = ...`, and constructor `_env_file=` overrides on proven `BaseSettings` subclasses receive the same checks, including literal lists/tuples. These inputs are scanned conservatively even without a proven downstream client use.
167
+ Dynamic, missing or unreadable loader inputs produce an `env-api-url` review item, as do unresolved keyword expansions, CWD-dependent searches (`usecwd=True`), or searches with no match before leaving the selected root. No project loader is executed. Other locations such as `config/prod.env` remain uninspected unless explicitly loaded.
168
+ `.env.example`, `.env.sample`, and `.env.template` are ignored unless explicitly loaded; `.env.test` is scanned. Comments and empty values are ignored. Literal non-Cloud URLs in active files or Python `os.environ` / `os.putenv` writes refuse the upgrade, including `os.environ.update({...})` and `os.environ |= {...}`.
169
+ Environment declarations using `${NAME:-default}`, `${NAME-default}`, `${NAME:+word}` or `${NAME+word}` receive the same Cloud/custom checks on the selectable value. Bare references and required-variable expressions (`:?` / `?`) remain unresolved review; a reference inside another setting is not a declaration.
170
+ Compose detection uses Compose filenames, explicit `COMPOSE_FILE` or include selection, a top-level `services` mapping, or an include list containing only paths or Compose include fields (`path`, `env_file`, `project_directory`). Unselected `.gitlab-ci.yml` files are not Compose. Unrelated YAML is filtered before tokenization; Compose YAML over 5 MiB retains environment review instead of being tokenized. Explicitly loaded environment inputs also have a 5 MiB byte limit; pipes and device files are never read.
171
+ Tuple/list assignments pair literal RHS elements with their targets; unresolved unpacking is reported for review. `os.environ.__setitem__(key=..., value=...)` is recognized too.
172
+ `--drop-api-url` acknowledges these environment settings without removing them; they remain manual-review items. Only if this environment refusal fires and you have verified the URL really points at Daytona Cloud, rerun with `--drop-api-url`. Cloud or dynamic environment values are reported without refusing. Cloud URL schemes and hostnames are case-insensitive; the `/api` path is case-sensitive.
173
+ Docker `ENV` / `ARG` scanning includes `ONBUILD` instructions. Closed heredoc
174
+ bodies are ignored, including those in `ONBUILD RUN`; if a terminator is missing,
175
+ the remaining lines are scanned as instructions so malformed input cannot hide
176
+ later URL diagnostics.
177
+ A `package.json`
178
+ produces guidance to run `npx daytona-upgrade` separately.
179
+
180
+ Local requirements/constraints includes are followed within the project root.
181
+ Included filenames need no particular extension. For partial-root upgrades,
182
+ ancestor includes are inspected read-only within the nearest Git checkout;
183
+ cycles and symlinks are skipped, and constraints never certify a runtime dependency.
184
+ Hash-locked or backslash-continued Daytona requirements remain unchanged with a
185
+ `manual-dependency` item: change them to `daytona[v0-sdk]>=2,<3` and regenerate
186
+ hashes before running upgraded code. Poetry constraint alternatives retain their
187
+ Python, marker and platform conditions; unsupported alternatives need manual edits.
188
+ UTF-8 BOMs, CRLF endings and Python source encoding declarations are preserved.
189
+ Only files with planned edits require lossless decoding. Each edited file with
190
+ invalid UTF-8 (or an invalid Python coding declaration) produces an
191
+ `unsupported-file` item with a project-relative path; the run exits 1 without
192
+ writing any files. Convert those files to UTF-8 or correct their Python coding
193
+ declarations before rerunning. Scan-only files and unchanged sources, manifests
194
+ and notebooks are read with replacement characters when needed and never written.
195
+ If replacement-decoded Python cannot be parsed, the tool reports the encoding
196
+ remedy instead of a generic syntax error, even when no edit could be planned.
197
+ Editable, VCS/URL and unknown dependency
198
+ syntax that cannot be rewritten is reported as `manual-dependency`, never skipped
199
+ silently. A project Python range allowing versions below 3.10 (or an unparsed
200
+ range) also gets a `manual-dependency` compatibility item.
201
+ In `setup.cfg`, single-line dependency lists split on semicolons; put requirements
202
+ with environment markers on separate, indented lines. Ambiguous declarations
203
+ stay unchanged with a `manual-dependency` item; `file:` requirements stay unchanged
204
+ and require manual migration of the referenced files. Static `setup(**kwargs)` dictionaries
205
+ are checked for `python_requires`; unresolved expansions require manual floor review.
206
+ Legacy uv `dev-dependencies` arrays and PDM development groups are migrated too.
207
+ uv `override-dependencies` migrate to `daytona[v0-sdk]>=2,<3`; PDM
208
+ `[tool.pdm.resolution.overrides]` registry versions migrate to
209
+ `daytona = ">=2,<3"` because its table form cannot express extras. uv
210
+ `constraint-dependencies` remain extra-less because uv ignores constraint
211
+ extras; override and constraint requirements retain markers. Unrestricted constraints and constraints
212
+ already matching `>=2,<3` migrate automatically; other constraint policies
213
+ (including `<1` and old version pins), source/URL overrides, and ambiguous PDM
214
+ overrides stay unchanged with a `manual-dependency` item. Review their intent
215
+ before changing them; `--strict` exits 1 while those items remain.
216
+ If source changes without an updated Daytona requirement or a declaration already
217
+ requiring SDK 2.x with the `v0-sdk` extra, a `manual-dependency` item asks you to
218
+ update its declaration.
219
+ Manifests within the project and its parents up to the Git root are checked;
220
+ parent manifests are never edited.
221
+ Partial-root scans emit one informational `types-unresolved` item at `.` when
222
+ a manifest lives above the scan root, or Python sources elsewhere in the Git
223
+ checkout import Daytona. It does not fail `--strict`; scan the full project to
224
+ include shared clients. Files outside the selected root remain read-only.
225
+ uv and PDM resolver declarations in ancestor manifests that need changes are
226
+ reported for manual review, even when a nearer runtime dependency is already upgraded.
227
+ Daytona `[tool.uv.sources]` overrides in local or ancestor manifests produce a `manual-dependency` item; review them manually before installing SDK 2.x.
228
+ A `setup.py` requirement list modified between its definition and the
229
+ `setup()` call, including through an alias, cannot certify that the runtime
230
+ dependency already supports SDK 2.x.
231
+ When the mapping supplies the pinned v0 export list, historical names missing
232
+ from that bundle get a `private-import` item: use the v2 API or remove the name; it is unavailable from `daytona.v0`. Known bundled 0.x submodules are not missing exports. All dunder names (including `__file__` and `__version__`) stay on the renamed root in both attributes and `from` imports, without an item.
233
+
234
+ All transformations are calculated before the first write, so a custom URL or
235
+ parse failure in a later file cannot leave earlier files upgraded. Every output
236
+ is first written to a temporary file in its target directory, flushed and
237
+ `fsync`ed, with the original's permission bits copied. Only after all outputs
238
+ are prepared does the tool atomically replace each target in order. If a write
239
+ or replacement fails, the tool restores already-replaced targets from their
240
+ original bytes using the same temporary-file and atomic-replacement procedure,
241
+ and removes newly created targets before exiting 1. Temporary files are cleaned
242
+ up on success; error-path cleanup is best-effort. Rollback failures are reported
243
+ explicitly, with any leftover temporary paths appended to the original write error.
244
+ Write failures name the project-relative target, not its temporary staging file.
245
+ Each replacement is atomic, not the multi-file operation: a crash or forced
246
+ termination can leave some complete replacements applied and temporary files
247
+ behind, but cannot truncate an original file during writing.
248
+ Flow analysis is conservative: optional expression writes, match captures and
249
+ base-object rebinding invalidate receiver proofs. Escaping holders lose unannotated field proofs: call arguments (including containers, keys, keywords and spreads), method receivers, called captures, or storage elsewhere. Calls on `self` are not escapes: class-wide writes already cover methods. Explicit client annotations survive escapes; any call receiving `self` fences unannotated fields later in that function. Recognized literal reflective writes below affect only their destination. Later linked uses get FIXMEs, never `.v0`; direct clients keep identity proofs. Known class construction alone is not an escape. Class attributes require every
250
+ write to agree; an annotation cannot overrule an unknown or non-client write. Joins retain client uncertainty across reaching paths in `if`, `try`, loops, and `match`; returns do not contribute, breaks bypass loop `else`, and continues feed exhaustion. Loop-backedge joins affect only names assigned in the body, preserving invariant parameter evidence; cached loop/function write sets avoid rescanning during replay. Bounded fixed-point replay carries evidence through successive aliases across iterations. Comprehension walrus assignments retain both the zero-execution entry evidence and uncertain enclosing-scope writes, including possibly unbound names. Sequential `except*` handlers include preceding handlers' writes, even when those handlers raise. `finally` joins remain conservative across unwinding paths.
251
+ An empty first iterable literal (`[]` or `()`) prevents comprehension-body writes, so prior client proofs survive. Expression-wide invalidation clears parent names before dotted members, including when a later operand rebinds an alias. Nested-definition decorators, defaults, annotations and class bases retain possible outer-generator client yields for review; nested function and lambda bodies are excluded. A proven `AsyncExitStack.enter_async_context(cm=value)` accepts the explicit keyword like its positional form; extra keywords and `**kwargs` do not establish proof. After `with` / `async with` using unknown context managers, receiver proofs must
252
+ agree at entry and every body prefix because an exception may be suppressed; differing client evidence produces a FIXME rather than disappearing.
253
+ Binding-proven non-suppressing contexts preserve body proofs: `open`, `io.open`,
254
+ `Path(...).open()`, threading locks and semaphores (including proven lock bindings),
255
+ `Condition()` with its default lock, tempfile contexts, and `Daytona(...)` /
256
+ `AsyncDaytona(...)`. Binding-proven `nullcontext(value)` returns `value` under either context protocol. A proven `AsyncExitStack` instance's `enter_async_context(cm)` returns the asynchronous entry value of `cm`; shadowed stack bindings do not establish proof. Project subclass entry overrides leave the target unproven rather than assuming it is the manager. Shadowed or unknown context managers remain conservative.
257
+ Reflective writes (`setattr`, `object.__setattr__`, `__dict__` and `vars(...)` subscripts/updates) participate in sequential, deferred and loop analysis. Recognized literal-key writes through proven-unshadowed builtins invalidate only the named field; replacement values and nested opaque calls still follow the holder-escape rule above. Unknown keys fence every field. Proven Daytona values establish literal-field evidence unless the builtin operation is shadowed. Short-circuit paths, mixed factory annotations and augmented client collections retain uncertain evidence for review; augmented client/subclass results stay unproven. Proven `ExitStack`/`AsyncExitStack.enter_context(cm)` (also `cm=...`) preserves entry evidence, unless overridden. Container mutations invalidate proofs through aliases. Return annotations on
258
+ functions with unknown decorators do not prove that the decorated call returns a
259
+ client; calls relying on that lost proof get a FIXME rather than a silent miss. Collection results retain uncertain client-element evidence through loops and `yield from` wrappers. Pytest fixtures resolve from the test module to the nearest ancestor `conftest.py`; nearer non-client or unknown declarations shadow ancestor fixtures. Except for proven synchronous spec mocks, injected client evidence requires review even with a conflicting non-client annotation and never establishes rewrite proof. Concrete property and cached-property results take precedence over annotations; conflicting client evidence requires a FIXME. Generator parameters use annotation aliases and type-checking-only imports, including variadic positional element annotations. Nested client iterables retain manual-review evidence in dictionaries.
260
+ Dataclass `field(default_factory=Daytona)` / `AsyncDaytona` and zero-argument lambdas directly constructing either client can prove instance fields, including alongside options such as `repr=False`.
261
+ An unproven Daytona-linked factory requires a FIXME. Stable concrete defaults also prove class lookup; factory results do not.
262
+ Methods and lambdas do not inherit class-local names. External class-attribute mutations conservatively invalidate class defaults.
263
+ Imported project instances carry linked client-field provenance for FIXMEs and `mock-target` items, not proof to rewrite mutable fields. Unrelated same-named classes do not establish that link. Constructing an imported project class uses its defining module's field proofs, constructor metadata and safety hooks, just like a locally defined class. Writes to that class through imports or aliases anywhere in the indexed project demote the named field and its default to linked review evidence; computed names and opaque dictionary updates demote every field. Unrelated members retain their proofs. Exporting that instance through another module still carries only review evidence for its mutable client fields.
264
+ Classes or project bases with `__getattribute__` / `__getattr__`, or a replaced `__init__` (assignment or `setattr`), cannot prove instance or `self` fields; linked reads require a FIXME. Lookup hooks anywhere in a client subclass's project hierarchy also leave inherited member dispatch unproven. Direct assignments, `setattr` and `object.__setattr__` replacing moved client methods or service accessors with an unproven value get a `mock-target` item and FIXME; subsequent accesses of that member remain manual, while independent members retain their proofs. `default_language` is a data setting: its direct writes still migrate automatically to `.v0` without an item. Proven same-service direct assignments also migrate automatically.
265
+ Relative imports are never treated as SDK imports. Legacy SDK root wildcards split into `from daytona import *` followed by `from daytona.v0 import *`: the bundled v0 wildcard excludes client/config constructors, preserving the root client while retaining v0 resource and error classes. Known SDK exports carry import proofs; later unknown wildcard imports demote them to review-only evidence. Project wildcard imports honor literal `__all__` lists/tuples (including concatenation and `+=`); unresolved declarations do not import receiver proofs. Unproven values may require
266
+ manual fixes. Review reports and run tests. `patch.object(client, "create", ...)` and `patch.multiple(client, create=..., ...)` route proven receivers to `client.v0` when every patched member moved, including imported aliases, decorators, context managers and `.start()` calls; already migrated targets stay unchanged. Mixed `patch.multiple` targets require splitting by hand and get a `mock-target` item plus a FIXME. Class targets, unproven receivers and dynamic or non-moved members remain `mock-target` review items. String targets such as `patch("app.client.create")` route through `.v0` when the project index proves the client; unproven Daytona-related prefixes require review, while unrelated targets stay unchanged. Project-owned modules remain exempt even when named `daytona`; actual SDK client bindings and re-exports still follow their proofs. Resource paths still move under `daytona.v0`, and root-client class member paths still require review.
267
+ Generic client-like names (`client`, `http_client`) are not evidence: an
268
+ unresolved factory result gets a FIXME only with linked Daytona provenance or
269
+ a name, callee or resolved path containing `daytona` (case-insensitive).
270
+ External module attributes such as `settings.DAYTONA_CLIENT` and `deps.daytona` get a FIXME when untyped.
271
+ Local SDK `Daytona` / `AsyncDaytona` assignment annotations (quoted/optional too), including declarations before a separate assignment in the same scope, prove client receivers; unresolved SDK-like annotations require review. Module-level assignment aliases, `TypeAlias` declarations and PEP 695 aliases carry this evidence, including FastAPI `Annotated[Daytona, Depends(...)]` dependencies and quoted alias chains (bounded to 32 resolution steps). Imports carry resolved proof kinds from the alias's defining module, never alias text interpreted against the consumer's names. Aliases under `if TYPE_CHECKING:` also export annotation evidence, not runtime constructors. Forward alias references use module type evidence; conflicting branch assignments, imports and type aliases retain uncertainty. Unresolved client-bearing aliases produce a FIXME, so `--strict` fails. `type[Daytona]` and `Callable` values are not client instances; constructing a proven client class does establish an instance.
272
+ Annotations never override concrete non-client evidence or prove unknown `self.client` writes. Typed sequences (`list[Daytona]`, `Sequence[Daytona]`, `Iterable[Daytona]`, `tuple[Daytona, ...]`), generator return annotations (`Iterator[Daytona]`, `Generator[Daytona, ...]`, `AsyncGenerator[Daytona, None]`, `AsyncIterator[Daytona]`, `AsyncIterable[Daytona]`) and `*clients: Daytona` prove loop/comprehension elements; ambiguous client-bearing element types require review. Unannotated local generators support straight-line client yields and strict joins across conditional branches, including asynchronous generators; mixed or unknown yielded values never prove a client. Definition-time constructor evidence is discarded when later writes can replace it. Homogeneous typed tuples support unpacking, including starred remainder lists; heterogeneous tuples retain review evidence per position, without flagging unrelated positions. Single-generator comprehensions forwarding their iteration variable retain element evidence. `Optional`, `Union`, and `Annotated` wrappers require binding-proven imports from `typing` or `typing_extensions`, including aliases. Collection mutations and target rebinding invalidate this evidence. Dictionary lookups, `.values()`, `.items()` positions and client-typed key iteration require review; value annotations never establish client evidence for key iteration. Dictionary spreads, builtin `dict(...)` copies (including `dict(**clients)`), and dictionary unions carry existing client evidence, never invent it for unrelated or unknown mappings. Literal pair variables retain element evidence without flagging typed non-client values. Dictionary evidence remains unproven even when its value annotation is a proven client type.
273
+ String annotations using binding-proven SDK module paths move to `.v0`, including composite types such as `"list[daytona.Sandbox]"`; bare imported names follow their imports. Local types and unrelated imports are left alone. Unsupported moved-type strings get a FIXME.
274
+ Type strings passed to `typing.cast`, `ForwardRef`, `TypeVar` (bounds, constraints and defaults), `ParamSpec` (bounds and defaults), and `NewType` are rewritten like string annotations, including aliased imports and `typing_extensions` helpers. Starred type operands and `Unpack` references are traversed too.
275
+ Explicit `TypeAlias` values and PEP 695 `type` alias values, type-parameter bounds and constraints are treated as annotations too, including quoted types. Python 3.13 type-parameter defaults are also traversed. Run the tool on a Python version that supports your source syntax.
276
+ Runtime strings, including arguments of arbitrary calls nested inside type positions, `Literal` values and `Annotated` metadata stay unchanged.
277
+ Split imports copy the original trailing comment to both lines, including a plain trailing comment, so line-scoped suppressions remain effective. An unused suppression may need manual removal if your linter enables `RUF100` or mypy enables `warn_unused_ignores` for a copied `# type: ignore`.
278
+ Partial-scan notices require omitted Daytona dependencies or imports. Ancestor checks stop at the Git root, or after five parent levels outside Git.
279
+
280
+ Instances of project subclasses of `Daytona` / `AsyncDaytona` also route inherited
281
+ SDK members through `.v0`, including aliases and cross-module bases known to the
282
+ project index. A class call stays unproven with any opaque base, class keyword expansion, project `__new__`, metaclass other than binding-proven `abc.ABCMeta`, or decorator (including `dataclass`). A project-defined member stays untouched only when its class
283
+ precedes the SDK class in Python's C3 method resolution order. An unknown or
284
+ external base before the SDK leaves member ownership unproven and gets a FIXME.
285
+ Passing a config to a subclass counts as an escape unless every project class
286
+ before the SDK has no construction hooks, or only an undecorated `__init__`
287
+ that forwards the same parameters to `super().__init__` without touching them.
288
+ Other `__init__`, `__new__`, or `__init_subclass__` hooks require
289
+ `--drop-api-url` and manual config review.
290
+ Inherited SDK member access through `self` inside a subclass gets a FIXME instead:
291
+ rewriting the class itself requires a manual decision about its design.