automatic import of python-selic-apiopeneuler20.03

1 files changed, 163 insertions, 0 deletions

diff --git a/python-selic-api.spec b/python-selic-api.spec
new file mode 100644
index 0000000..ca7480b
--- /dev/null
+++ b/python-selic-api.spec
@@ -0,0 +1,163 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-selic-api
+Version:	0.0.6
+Release:	1
+Summary:	API para obtenção dos dados da SELIC.
+License:	MIT
+URL:		https://github.com/marceloid/selic_api
+Source0:	https://mirrors.aliyun.com/pypi/web/packages/c4/5c/c4bf6162bd8a6ec00029861e4ad49b30cd0ba5badc8fc32af6fdb8110dda/selic_api-0.0.6.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-requests
+Requires:	python3-dateutil
+Requires:	python3-beautifulsoup4
+Requires:	python3-certifi
+
+%description
+# selic_api
+ API para obter a taxa SELIC acumulada para fins de cálculo da atualização monetária para os tributos da Prefeitura de Belo Horizonte.
+
+## Publishing a new version on PyPI
+
+To publish a new version of a Poetry package to PyPI, follow these steps:
+
+1. Update the version number of your package in your project's pyproject.toml file. This should be done according to the Semantic Versioning guidelines.
+2. Build the distribution files for the new version of your package by running the following command in your project's root directory:
+
+`poetry build`
+
+This will create a dist directory with the distribution files for your package.
+
+3. Check that the generated distribution files are correct by running the following command:
+
+`poetry check`
+
+This will perform several checks on the generated distribution files and report any issues.
+
+4. Publish the new version of your package to PyPI by running the following command:
+
+`poetry publish`
+
+This will upload the distribution files to PyPI and make the new version of your package available for installation.
+
+Note that you will need to have a PyPI account and be logged in to it for this step to work.
+
+Also, if this is the first time you are publishing your package to PyPI, you will need to create a new release on GitHub (or other version control system you use) and tag it with the new version number before running the poetry publish command. This is because PyPI requires that the source code for each release be available online.
+
+
+%package -n python3-selic-api
+Summary:	API para obtenção dos dados da SELIC.
+Provides:	python-selic-api
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-selic-api
+# selic_api
+ API para obter a taxa SELIC acumulada para fins de cálculo da atualização monetária para os tributos da Prefeitura de Belo Horizonte.
+
+## Publishing a new version on PyPI
+
+To publish a new version of a Poetry package to PyPI, follow these steps:
+
+1. Update the version number of your package in your project's pyproject.toml file. This should be done according to the Semantic Versioning guidelines.
+2. Build the distribution files for the new version of your package by running the following command in your project's root directory:
+
+`poetry build`
+
+This will create a dist directory with the distribution files for your package.
+
+3. Check that the generated distribution files are correct by running the following command:
+
+`poetry check`
+
+This will perform several checks on the generated distribution files and report any issues.
+
+4. Publish the new version of your package to PyPI by running the following command:
+
+`poetry publish`
+
+This will upload the distribution files to PyPI and make the new version of your package available for installation.
+
+Note that you will need to have a PyPI account and be logged in to it for this step to work.
+
+Also, if this is the first time you are publishing your package to PyPI, you will need to create a new release on GitHub (or other version control system you use) and tag it with the new version number before running the poetry publish command. This is because PyPI requires that the source code for each release be available online.
+
+
+%package help
+Summary:	Development documents and examples for selic-api
+Provides:	python3-selic-api-doc
+%description help
+# selic_api
+ API para obter a taxa SELIC acumulada para fins de cálculo da atualização monetária para os tributos da Prefeitura de Belo Horizonte.
+
+## Publishing a new version on PyPI
+
+To publish a new version of a Poetry package to PyPI, follow these steps:
+
+1. Update the version number of your package in your project's pyproject.toml file. This should be done according to the Semantic Versioning guidelines.
+2. Build the distribution files for the new version of your package by running the following command in your project's root directory:
+
+`poetry build`
+
+This will create a dist directory with the distribution files for your package.
+
+3. Check that the generated distribution files are correct by running the following command:
+
+`poetry check`
+
+This will perform several checks on the generated distribution files and report any issues.
+
+4. Publish the new version of your package to PyPI by running the following command:
+
+`poetry publish`
+
+This will upload the distribution files to PyPI and make the new version of your package available for installation.
+
+Note that you will need to have a PyPI account and be logged in to it for this step to work.
+
+Also, if this is the first time you are publishing your package to PyPI, you will need to create a new release on GitHub (or other version control system you use) and tag it with the new version number before running the poetry publish command. This is because PyPI requires that the source code for each release be available online.
+
+
+%prep
+%autosetup -n selic_api-0.0.6
+
+%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-selic-api -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Jun 20 2023 Python_Bot <Python_Bot@openeuler.org> - 0.0.6-1
+- Package Spec generated