dimo-python-sdk 1.3.0__tar.gz → 1.3.2__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.
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/PKG-INFO +7 -7
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/README.md +5 -5
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo_python_sdk.egg-info/PKG-INFO +7 -7
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo_python_sdk.egg-info/requires.txt +1 -1
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/pyproject.toml +2 -2
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/LICENSE +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/__init__.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/api/__init__.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/api/attestation.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/api/auth.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/api/device_definitions.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/api/token_exchange.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/api/trips.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/api/valuations.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/constants.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/dimo.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/environments.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/errors.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/eth_signer.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/graphql/__init__.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/graphql/identity.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/graphql/telemetry.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/permission_decoder.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo/request.py +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo_python_sdk.egg-info/SOURCES.txt +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo_python_sdk.egg-info/dependency_links.txt +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo_python_sdk.egg-info/top_level.txt +0 -0
- {dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/setup.cfg +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.1
|
|
2
2
|
Name: dimo-python-sdk
|
|
3
|
-
Version: 1.3.
|
|
3
|
+
Version: 1.3.2
|
|
4
4
|
Summary: DIMO SDK in Python
|
|
5
5
|
Author-email: Barrett Kowalsky <barrettkowalsky@gmail.com>
|
|
6
6
|
Project-URL: Homepage, https://github.com/DIMO-Network/dimo-python-sdk
|
|
@@ -14,7 +14,7 @@ Description-Content-Type: text/markdown
|
|
|
14
14
|
License-File: LICENSE
|
|
15
15
|
Requires-Dist: requests>=2.30.0
|
|
16
16
|
Requires-Dist: eth-account==0.13.4
|
|
17
|
-
Requires-Dist: eth-utils
|
|
17
|
+
Requires-Dist: eth-utils>=5.0.0
|
|
18
18
|
|
|
19
19
|
# DIMO Python Developer SDK
|
|
20
20
|
|
|
@@ -85,7 +85,7 @@ The SDK offers 3 basic functions that maps to the steps listed in [Authenticatio
|
|
|
85
85
|
|
|
86
86
|
signature = dimo.auth.sign_challenge(
|
|
87
87
|
message = challenge['challenge'],
|
|
88
|
-
private_key = '<
|
|
88
|
+
private_key = '<api_key>'
|
|
89
89
|
)
|
|
90
90
|
|
|
91
91
|
tokens = dimo.auth.submit_challenge(
|
|
@@ -101,13 +101,13 @@ The SDK offers 3 basic functions that maps to the steps listed in [Authenticatio
|
|
|
101
101
|
As mentioned earlier, this is the streamlined function call to directly get the `developer_jwt`. The `address` field in challenge generation is omitted since it is essentially the `client_id` of your application per Developer License:
|
|
102
102
|
|
|
103
103
|
```python
|
|
104
|
-
auth_header = dimo.auth.
|
|
104
|
+
auth_header = dimo.auth.get_dev_jwt(
|
|
105
105
|
client_id = '<client_id>',
|
|
106
106
|
domain = '<domain>',
|
|
107
|
-
private_key = '<
|
|
107
|
+
private_key = '<api_key>'
|
|
108
108
|
)
|
|
109
109
|
|
|
110
|
-
# Store the Developer JWT from the auth_header
|
|
110
|
+
# Store the Developer JWT from the auth_header
|
|
111
111
|
dev_jwt = auth_header["access_token"]
|
|
112
112
|
```
|
|
113
113
|
|
|
@@ -151,7 +151,7 @@ This method uses your client_id to check the privileges for a specified token_id
|
|
|
151
151
|
|
|
152
152
|
```python
|
|
153
153
|
# Start by obtaining a Developer JWT
|
|
154
|
-
auth_header = dimo.auth.
|
|
154
|
+
auth_header = dimo.auth.get_dev_jwt(
|
|
155
155
|
client_id = '<client_id>',
|
|
156
156
|
domain = '<domain>',
|
|
157
157
|
private_key = '<private_key>'
|
|
@@ -67,7 +67,7 @@ The SDK offers 3 basic functions that maps to the steps listed in [Authenticatio
|
|
|
67
67
|
|
|
68
68
|
signature = dimo.auth.sign_challenge(
|
|
69
69
|
message = challenge['challenge'],
|
|
70
|
-
private_key = '<
|
|
70
|
+
private_key = '<api_key>'
|
|
71
71
|
)
|
|
72
72
|
|
|
73
73
|
tokens = dimo.auth.submit_challenge(
|
|
@@ -83,13 +83,13 @@ The SDK offers 3 basic functions that maps to the steps listed in [Authenticatio
|
|
|
83
83
|
As mentioned earlier, this is the streamlined function call to directly get the `developer_jwt`. The `address` field in challenge generation is omitted since it is essentially the `client_id` of your application per Developer License:
|
|
84
84
|
|
|
85
85
|
```python
|
|
86
|
-
auth_header = dimo.auth.
|
|
86
|
+
auth_header = dimo.auth.get_dev_jwt(
|
|
87
87
|
client_id = '<client_id>',
|
|
88
88
|
domain = '<domain>',
|
|
89
|
-
private_key = '<
|
|
89
|
+
private_key = '<api_key>'
|
|
90
90
|
)
|
|
91
91
|
|
|
92
|
-
# Store the Developer JWT from the auth_header
|
|
92
|
+
# Store the Developer JWT from the auth_header
|
|
93
93
|
dev_jwt = auth_header["access_token"]
|
|
94
94
|
```
|
|
95
95
|
|
|
@@ -133,7 +133,7 @@ This method uses your client_id to check the privileges for a specified token_id
|
|
|
133
133
|
|
|
134
134
|
```python
|
|
135
135
|
# Start by obtaining a Developer JWT
|
|
136
|
-
auth_header = dimo.auth.
|
|
136
|
+
auth_header = dimo.auth.get_dev_jwt(
|
|
137
137
|
client_id = '<client_id>',
|
|
138
138
|
domain = '<domain>',
|
|
139
139
|
private_key = '<private_key>'
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.1
|
|
2
2
|
Name: dimo-python-sdk
|
|
3
|
-
Version: 1.3.
|
|
3
|
+
Version: 1.3.2
|
|
4
4
|
Summary: DIMO SDK in Python
|
|
5
5
|
Author-email: Barrett Kowalsky <barrettkowalsky@gmail.com>
|
|
6
6
|
Project-URL: Homepage, https://github.com/DIMO-Network/dimo-python-sdk
|
|
@@ -14,7 +14,7 @@ Description-Content-Type: text/markdown
|
|
|
14
14
|
License-File: LICENSE
|
|
15
15
|
Requires-Dist: requests>=2.30.0
|
|
16
16
|
Requires-Dist: eth-account==0.13.4
|
|
17
|
-
Requires-Dist: eth-utils
|
|
17
|
+
Requires-Dist: eth-utils>=5.0.0
|
|
18
18
|
|
|
19
19
|
# DIMO Python Developer SDK
|
|
20
20
|
|
|
@@ -85,7 +85,7 @@ The SDK offers 3 basic functions that maps to the steps listed in [Authenticatio
|
|
|
85
85
|
|
|
86
86
|
signature = dimo.auth.sign_challenge(
|
|
87
87
|
message = challenge['challenge'],
|
|
88
|
-
private_key = '<
|
|
88
|
+
private_key = '<api_key>'
|
|
89
89
|
)
|
|
90
90
|
|
|
91
91
|
tokens = dimo.auth.submit_challenge(
|
|
@@ -101,13 +101,13 @@ The SDK offers 3 basic functions that maps to the steps listed in [Authenticatio
|
|
|
101
101
|
As mentioned earlier, this is the streamlined function call to directly get the `developer_jwt`. The `address` field in challenge generation is omitted since it is essentially the `client_id` of your application per Developer License:
|
|
102
102
|
|
|
103
103
|
```python
|
|
104
|
-
auth_header = dimo.auth.
|
|
104
|
+
auth_header = dimo.auth.get_dev_jwt(
|
|
105
105
|
client_id = '<client_id>',
|
|
106
106
|
domain = '<domain>',
|
|
107
|
-
private_key = '<
|
|
107
|
+
private_key = '<api_key>'
|
|
108
108
|
)
|
|
109
109
|
|
|
110
|
-
# Store the Developer JWT from the auth_header
|
|
110
|
+
# Store the Developer JWT from the auth_header
|
|
111
111
|
dev_jwt = auth_header["access_token"]
|
|
112
112
|
```
|
|
113
113
|
|
|
@@ -151,7 +151,7 @@ This method uses your client_id to check the privileges for a specified token_id
|
|
|
151
151
|
|
|
152
152
|
```python
|
|
153
153
|
# Start by obtaining a Developer JWT
|
|
154
|
-
auth_header = dimo.auth.
|
|
154
|
+
auth_header = dimo.auth.get_dev_jwt(
|
|
155
155
|
client_id = '<client_id>',
|
|
156
156
|
domain = '<domain>',
|
|
157
157
|
private_key = '<private_key>'
|
|
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
|
|
|
4
4
|
|
|
5
5
|
[project]
|
|
6
6
|
name = "dimo-python-sdk"
|
|
7
|
-
version = "1.3.
|
|
7
|
+
version = "1.3.2"
|
|
8
8
|
authors = [
|
|
9
9
|
{ name="Barrett Kowalsky", email="barrettkowalsky@gmail.com" },
|
|
10
10
|
]
|
|
@@ -21,7 +21,7 @@ classifiers = [
|
|
|
21
21
|
dependencies = [
|
|
22
22
|
"requests>=2.30.0",
|
|
23
23
|
"eth-account==0.13.4",
|
|
24
|
-
"eth-utils
|
|
24
|
+
"eth-utils>=5.0.0",
|
|
25
25
|
]
|
|
26
26
|
|
|
27
27
|
[project.urls]
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
{dimo_python_sdk-1.3.0 → dimo_python_sdk-1.3.2}/dimo_python_sdk.egg-info/dependency_links.txt
RENAMED
|
File without changes
|
|
File without changes
|
|
File without changes
|