%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 ` or `poetry add --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 ` or `poetry add --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 ` or `poetry add --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 - 2.4.0-1 - Package Spec generated