%global _empty_manifest_terminate_build 0 Name: python-et-micc Version: 1.1.8 Release: 1 Summary: A practical Python project skeleton generator. License: MIT URL: https://github.com/etijskens/et-micc Source0: https://mirrors.nju.edu.cn/pypi/web/packages/8c/d3/743f6ce072f133c6184d337e451084a4693c902bc1324a8f11d3d6bb24cd/et-micc-1.1.8.tar.gz BuildArch: noarch Requires: python3-click Requires: python3-cookiecutter Requires: python3-sphinx-click Requires: python3-sphinx-rtd-theme Requires: python3-walkdir Requires: python3-tomlkit Requires: python3-semantic_version Requires: python3-pypi-simple %description Micc_ does not do all of this by itself. For many things it relies on other strong open source tools and it is therefor open source as well (MIT Licence). Here is a list of tools micc_ is using or cooperating with happily: * `Pyenv `_: management of different Python versions. * `Pipx `_ for installation of CLIs in a system-wide way. * `Poetry `_ for dependency management, virtual environment management, packaging and publishing. * `Git `_ for version control. * `CMake `_ is usde for building binary extension modules written in C++. The above tools are not dependencies of Micc_ and must be installed separately. Then there are a number of python packages on which micc_ depends and which are automatically installed when poetry_ creates a virtual environment for a project. * `Cookiecutter `_ for creating boilerplate code from templates for all the parts that can be added to your project. * `Python-semanticversion `_ for managing version strings and dependency version constraints according to the `Semver 2.0 `_ specification. * `Pytest `_ for testing your code. * `Click `_ for a pythonic and intuitive definition of command-line interfaces (CLIs). * `Sphinx `_ to extract documentation from your project's doc-strings. * `Sphinx-click `_ for extracting documentation from the click_ command descriptions. * `F2py `_ for transforming modern Fortran code into performant binary extension modules interfacing nicely with `Numpy `_. * `Pybind11 `_ as the glue between C++ source code and performant binary extension modules, also interfacing nicely with Numpy_. %package -n python3-et-micc Summary: A practical Python project skeleton generator. Provides: python-et-micc BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-et-micc Micc_ does not do all of this by itself. For many things it relies on other strong open source tools and it is therefor open source as well (MIT Licence). Here is a list of tools micc_ is using or cooperating with happily: * `Pyenv `_: management of different Python versions. * `Pipx `_ for installation of CLIs in a system-wide way. * `Poetry `_ for dependency management, virtual environment management, packaging and publishing. * `Git `_ for version control. * `CMake `_ is usde for building binary extension modules written in C++. The above tools are not dependencies of Micc_ and must be installed separately. Then there are a number of python packages on which micc_ depends and which are automatically installed when poetry_ creates a virtual environment for a project. * `Cookiecutter `_ for creating boilerplate code from templates for all the parts that can be added to your project. * `Python-semanticversion `_ for managing version strings and dependency version constraints according to the `Semver 2.0 `_ specification. * `Pytest `_ for testing your code. * `Click `_ for a pythonic and intuitive definition of command-line interfaces (CLIs). * `Sphinx `_ to extract documentation from your project's doc-strings. * `Sphinx-click `_ for extracting documentation from the click_ command descriptions. * `F2py `_ for transforming modern Fortran code into performant binary extension modules interfacing nicely with `Numpy `_. * `Pybind11 `_ as the glue between C++ source code and performant binary extension modules, also interfacing nicely with Numpy_. %package help Summary: Development documents and examples for et-micc Provides: python3-et-micc-doc %description help Micc_ does not do all of this by itself. For many things it relies on other strong open source tools and it is therefor open source as well (MIT Licence). Here is a list of tools micc_ is using or cooperating with happily: * `Pyenv `_: management of different Python versions. * `Pipx `_ for installation of CLIs in a system-wide way. * `Poetry `_ for dependency management, virtual environment management, packaging and publishing. * `Git `_ for version control. * `CMake `_ is usde for building binary extension modules written in C++. The above tools are not dependencies of Micc_ and must be installed separately. Then there are a number of python packages on which micc_ depends and which are automatically installed when poetry_ creates a virtual environment for a project. * `Cookiecutter `_ for creating boilerplate code from templates for all the parts that can be added to your project. * `Python-semanticversion `_ for managing version strings and dependency version constraints according to the `Semver 2.0 `_ specification. * `Pytest `_ for testing your code. * `Click `_ for a pythonic and intuitive definition of command-line interfaces (CLIs). * `Sphinx `_ to extract documentation from your project's doc-strings. * `Sphinx-click `_ for extracting documentation from the click_ command descriptions. * `F2py `_ for transforming modern Fortran code into performant binary extension modules interfacing nicely with `Numpy `_. * `Pybind11 `_ as the glue between C++ source code and performant binary extension modules, also interfacing nicely with Numpy_. %prep %autosetup -n et-micc-1.1.8 %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-et-micc -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Wed May 10 2023 Python_Bot - 1.1.8-1 - Package Spec generated