1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
|
%global _empty_manifest_terminate_build 0
Name: python-modelon-impact-client
Version: 2.4.0
Release: 1
Summary: Client library for easy scripting against Modelon Impact
License: BSD
URL: https://www.modelon.com/modelon-impact
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/9c/d4/432bb3742738b6f57362b58fd2ce2a619c7bcf9daa4d9deed4fe6e933056/modelon_impact_client-2.4.0.tar.gz
BuildArch: noarch
Requires: python3-requests
Requires: python3-semantic_version
Requires: python3-types-requests
%description
# Modelon-impact-client
Client library for easy scripting against Modelon Impact
## Installation
For installation instructions and requirements, please refer to the [documentation](https://modelon-impact-client.readthedocs.io).
## Develop
### Devcontainer
If you are developing with VS Code you can use the devcontainer which gives gives you a ready to use environment for development. Just click the "Reopen in Container" button after opening the project in VS Code.
#### Tips and tricks
It is possible to run the 'make' commands listed bellow using the devcontainer. It will detect being in a container and bypass Docker parts of the commands.
You can open a project with the dev-container directly without having to open and then re-load. Standing in the project directory you can run:
```
devcontainer open .
```
Note that this requires the [devcontainer-cli](https://code.visualstudio.com/docs/remote/devcontainer-cli).
You can add your own extensions to devcontainers. These extensions will be added for all devcontainers. First open your 'settings' as JSON. Then, to add for example the "GitLens" extension, put the following at the bottom of the settings:
```
...
"remote.containers.defaultExtensions": ["eamodio.gitlens"]
}
```
VS Code also have a `'Install Local Extensions in 'Remote'` command, but it must be repeated for each devcontainer and everytime a devcontainer is re-built.
### Creating a shell
Modelon-impact-client is developed using a Docker container for all build tools.
You can get a shell into said container by running:
```
make shell
```
### Manage dependencies
Dependencies are managed by poetry. Add dependencies by running
`poetry add <package>` or `poetry add <package> --dev` inside the shell
### Running tests
Tests are executed by running `make test`. You can also run `make test-watch` to get a watcher
that continuously re-runs the tests.
### Running lint
```
make lint
```
## Build
Building modelon-impact-client is done by running
```
make wheel
```
## Release
The modelon-impact-client build process is a fully automated using `Semantic-release`.
Automation is enabled for:
- Bumping version
- Generate changelog
This is done based on git commit semantics as described here: https://semantic-release.gitbook.io/semantic-release/
To make a new release simply run:
```
make publish
```
This command will detect what branch you are on and your git history and make a appropriate release.
Current configuration can be found in `.releaserc` and specifies that commits to branch `master` should be released and
commits to branch `beta` should be released as a `pre-release`.
This workflow make sure that no administrative time needs to be put into managing the release workflow.
%package -n python3-modelon-impact-client
Summary: Client library for easy scripting against Modelon Impact
Provides: python-modelon-impact-client
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-modelon-impact-client
# Modelon-impact-client
Client library for easy scripting against Modelon Impact
## Installation
For installation instructions and requirements, please refer to the [documentation](https://modelon-impact-client.readthedocs.io).
## Develop
### Devcontainer
If you are developing with VS Code you can use the devcontainer which gives gives you a ready to use environment for development. Just click the "Reopen in Container" button after opening the project in VS Code.
#### Tips and tricks
It is possible to run the 'make' commands listed bellow using the devcontainer. It will detect being in a container and bypass Docker parts of the commands.
You can open a project with the dev-container directly without having to open and then re-load. Standing in the project directory you can run:
```
devcontainer open .
```
Note that this requires the [devcontainer-cli](https://code.visualstudio.com/docs/remote/devcontainer-cli).
You can add your own extensions to devcontainers. These extensions will be added for all devcontainers. First open your 'settings' as JSON. Then, to add for example the "GitLens" extension, put the following at the bottom of the settings:
```
...
"remote.containers.defaultExtensions": ["eamodio.gitlens"]
}
```
VS Code also have a `'Install Local Extensions in 'Remote'` command, but it must be repeated for each devcontainer and everytime a devcontainer is re-built.
### Creating a shell
Modelon-impact-client is developed using a Docker container for all build tools.
You can get a shell into said container by running:
```
make shell
```
### Manage dependencies
Dependencies are managed by poetry. Add dependencies by running
`poetry add <package>` or `poetry add <package> --dev` inside the shell
### Running tests
Tests are executed by running `make test`. You can also run `make test-watch` to get a watcher
that continuously re-runs the tests.
### Running lint
```
make lint
```
## Build
Building modelon-impact-client is done by running
```
make wheel
```
## Release
The modelon-impact-client build process is a fully automated using `Semantic-release`.
Automation is enabled for:
- Bumping version
- Generate changelog
This is done based on git commit semantics as described here: https://semantic-release.gitbook.io/semantic-release/
To make a new release simply run:
```
make publish
```
This command will detect what branch you are on and your git history and make a appropriate release.
Current configuration can be found in `.releaserc` and specifies that commits to branch `master` should be released and
commits to branch `beta` should be released as a `pre-release`.
This workflow make sure that no administrative time needs to be put into managing the release workflow.
%package help
Summary: Development documents and examples for modelon-impact-client
Provides: python3-modelon-impact-client-doc
%description help
# Modelon-impact-client
Client library for easy scripting against Modelon Impact
## Installation
For installation instructions and requirements, please refer to the [documentation](https://modelon-impact-client.readthedocs.io).
## Develop
### Devcontainer
If you are developing with VS Code you can use the devcontainer which gives gives you a ready to use environment for development. Just click the "Reopen in Container" button after opening the project in VS Code.
#### Tips and tricks
It is possible to run the 'make' commands listed bellow using the devcontainer. It will detect being in a container and bypass Docker parts of the commands.
You can open a project with the dev-container directly without having to open and then re-load. Standing in the project directory you can run:
```
devcontainer open .
```
Note that this requires the [devcontainer-cli](https://code.visualstudio.com/docs/remote/devcontainer-cli).
You can add your own extensions to devcontainers. These extensions will be added for all devcontainers. First open your 'settings' as JSON. Then, to add for example the "GitLens" extension, put the following at the bottom of the settings:
```
...
"remote.containers.defaultExtensions": ["eamodio.gitlens"]
}
```
VS Code also have a `'Install Local Extensions in 'Remote'` command, but it must be repeated for each devcontainer and everytime a devcontainer is re-built.
### Creating a shell
Modelon-impact-client is developed using a Docker container for all build tools.
You can get a shell into said container by running:
```
make shell
```
### Manage dependencies
Dependencies are managed by poetry. Add dependencies by running
`poetry add <package>` or `poetry add <package> --dev` inside the shell
### Running tests
Tests are executed by running `make test`. You can also run `make test-watch` to get a watcher
that continuously re-runs the tests.
### Running lint
```
make lint
```
## Build
Building modelon-impact-client is done by running
```
make wheel
```
## Release
The modelon-impact-client build process is a fully automated using `Semantic-release`.
Automation is enabled for:
- Bumping version
- Generate changelog
This is done based on git commit semantics as described here: https://semantic-release.gitbook.io/semantic-release/
To make a new release simply run:
```
make publish
```
This command will detect what branch you are on and your git history and make a appropriate release.
Current configuration can be found in `.releaserc` and specifies that commits to branch `master` should be released and
commits to branch `beta` should be released as a `pre-release`.
This workflow make sure that no administrative time needs to be put into managing the release workflow.
%prep
%autosetup -n modelon-impact-client-2.4.0
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-modelon-impact-client -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Wed May 10 2023 Python_Bot <Python_Bot@openeuler.org> - 2.4.0-1
- Package Spec generated
|
