zipher-sdk 0.4.4__tar.gz → 0.4.6__tar.gz

{zipher-sdk-0.4.4 → zipher_sdk-0.4.6}/PKG-INFO

@@ -1,17 +1,25 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.4
 Name: zipher-sdk
-Version: 0.4.4
+Version: 0.4.6
 Summary: Python SDK for programmatic access to the Zipher API
-Home-page: UNKNOWN
 Author: Zipher Inc.
 Author-email: yoav@zipher.cloud
-License: UNKNOWN
-Platform: UNKNOWN
 Classifier: Programming Language :: Python :: 3
 Classifier: License :: OSI Approved :: MIT License
 Classifier: Operating System :: OS Independent
 Description-Content-Type: text/markdown
 License-File: LICENSE
+Requires-Dist: pydantic<3,>=2.4
+Requires-Dist: requests<3,>=2.28
+Requires-Dist: databricks-sdk<1,>=0.28
+Dynamic: author
+Dynamic: author-email
+Dynamic: classifier
+Dynamic: description
+Dynamic: description-content-type
+Dynamic: license-file
+Dynamic: requires-dist
+Dynamic: summary
 
 
 # Zipher SDK
@@ -136,6 +144,19 @@ optimized_cluster = client.update_existing_conf(job_id="my-job-id", existing_con
 
 ```
 
+#### Optional: passing per-run parameters
+
+You can specify run-level parameters that Zipher will take into consideration. This is useful for parametrized jobs, where Zipher can explicitly learn the different usage patterns of different parametes.
+
+
+```python
+optimized_cluster = client.update_existing_conf(
+    job_id="my-job-id",
+    existing_conf=config_payload,
+    run_params={"customer_ids": ["c1", "c2"], "lookback_days": "30"},
+)
+```
+
 ### Update Existing Multiple Tasks Configuration
 
 You can update multiple databricks tasks by initializing a zipher Client and sending a JSON representing a list of dbx SubmitTask objects to
@@ -202,4 +223,3 @@ optimized_tasks = client.get_optimized_tasks(job_id="my-job-id", tasks=tasks_to_
 
 # Continue with sending the optimized tasks to Databricks via the Databricks python SDK, Airflow operator, etc.
 ```
-

zipher-sdk-0.4.4/zipher_sdk.egg-info/PKG-INFO → zipher_sdk-0.4.6/README.md

@@ -1,18 +1,3 @@
-Metadata-Version: 2.1
-Name: zipher-sdk
-Version: 0.4.4
-Summary: Python SDK for programmatic access to the Zipher API
-Home-page: UNKNOWN
-Author: Zipher Inc.
-Author-email: yoav@zipher.cloud
-License: UNKNOWN
-Platform: UNKNOWN
-Classifier: Programming Language :: Python :: 3
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Operating System :: OS Independent
-Description-Content-Type: text/markdown
-License-File: LICENSE
-
 
 # Zipher SDK
 
@@ -136,6 +121,19 @@ optimized_cluster = client.update_existing_conf(job_id="my-job-id", existing_con
 
 ```
 
+#### Optional: passing per-run parameters
+
+You can specify run-level parameters that Zipher will take into consideration. This is useful for parametrized jobs, where Zipher can explicitly learn the different usage patterns of different parametes.
+
+
+```python
+optimized_cluster = client.update_existing_conf(
+    job_id="my-job-id",
+    existing_conf=config_payload,
+    run_params={"customer_ids": ["c1", "c2"], "lookback_days": "30"},
+)
+```
+
 ### Update Existing Multiple Tasks Configuration
 
 You can update multiple databricks tasks by initializing a zipher Client and sending a JSON representing a list of dbx SubmitTask objects to
@@ -201,5 +199,4 @@ tasks_to_optimize = [
 optimized_tasks = client.get_optimized_tasks(job_id="my-job-id", tasks=tasks_to_optimize)
 
 # Continue with sending the optimized tasks to Databricks via the Databricks python SDK, Airflow operator, etc.
-```
-
+```

{zipher-sdk-0.4.4 → zipher_sdk-0.4.6}/setup.py

@@ -8,7 +8,7 @@ with open('README.md', encoding='utf-8') as f:
 
 setup(
     name='zipher-sdk',
-    version='0.4.4',
+    version='0.4.6',
     description='Python SDK for programmatic access to the Zipher API',
     long_description=long_description,
     long_description_content_type='text/markdown',
@@ -16,9 +16,9 @@ setup(
     author_email='yoav@zipher.cloud',
     packages=find_packages(),
     install_requires=[
-        "pydantic==2.11.3",
-        "requests==2.32.3",
-        "databricks-sdk==0.52.0"
+        "pydantic>=2.4,<3",
+        "requests>=2.28,<3",
+        "databricks-sdk>=0.28,<1"
     ],
     entry_points={
         "console_scripts": [

zipher-sdk-0.4.4/README.md → zipher_sdk-0.4.6/zipher_sdk.egg-info/PKG-INFO

@@ -1,3 +1,26 @@
+Metadata-Version: 2.4
+Name: zipher-sdk
+Version: 0.4.6
+Summary: Python SDK for programmatic access to the Zipher API
+Author: Zipher Inc.
+Author-email: yoav@zipher.cloud
+Classifier: Programming Language :: Python :: 3
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pydantic<3,>=2.4
+Requires-Dist: requests<3,>=2.28
+Requires-Dist: databricks-sdk<1,>=0.28
+Dynamic: author
+Dynamic: author-email
+Dynamic: classifier
+Dynamic: description
+Dynamic: description-content-type
+Dynamic: license-file
+Dynamic: requires-dist
+Dynamic: summary
+
 
 # Zipher SDK
 
@@ -121,6 +144,19 @@ optimized_cluster = client.update_existing_conf(job_id="my-job-id", existing_con
 
 ```
 
+#### Optional: passing per-run parameters
+
+You can specify run-level parameters that Zipher will take into consideration. This is useful for parametrized jobs, where Zipher can explicitly learn the different usage patterns of different parametes.
+
+
+```python
+optimized_cluster = client.update_existing_conf(
+    job_id="my-job-id",
+    existing_conf=config_payload,
+    run_params={"customer_ids": ["c1", "c2"], "lookback_days": "30"},
+)
+```
+
 ### Update Existing Multiple Tasks Configuration
 
 You can update multiple databricks tasks by initializing a zipher Client and sending a JSON representing a list of dbx SubmitTask objects to
@@ -186,4 +222,4 @@ tasks_to_optimize = [
 optimized_tasks = client.get_optimized_tasks(job_id="my-job-id", tasks=tasks_to_optimize)
 
 # Continue with sending the optimized tasks to Databricks via the Databricks python SDK, Airflow operator, etc.
-```
+```

{zipher-sdk-0.4.4 → zipher_sdk-0.4.6}/zipher_sdk.egg-info/entry_points.txt

@@ -1,3 +1,2 @@
 [console_scripts]
 zipher = zipher.cli:main
-

zipher_sdk-0.4.6/zipher_sdk.egg-info/requires.txt

@@ -0,0 +1,3 @@
+pydantic<3,>=2.4
+requests<3,>=2.28
+databricks-sdk<1,>=0.28

zipher-sdk-0.4.4/zipher_sdk.egg-info/requires.txt

@@ -1,3 +0,0 @@
-pydantic==2.11.3
-requests==2.32.3
-databricks-sdk==0.52.0