automatic import of python-apify-clientopeneuler20.03

3 files changed, 318 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..d4134e9 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/apify_client-1.0.0.tar.gz
diff --git a/python-apify-client.spec b/python-apify-client.spec
new file mode 100644
index 0000000..2512402
--- /dev/null
+++ b/python-apify-client.spec
@@ -0,0 +1,316 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-apify-client
+Version:	1.0.0
+Release:	1
+Summary:	Apify API client for Python
+License:	Apache Software License
+URL:		https://github.com/apify/apify-client-python
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/cc/40/dd2477e25e0d0a04f2eb55d7febaaa8543d953a57a5230dbef49263f0a7a/apify_client-1.0.0.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-httpx
+Requires:	python3-autopep8
+Requires:	python3-flake8
+Requires:	python3-flake8-bugbear
+Requires:	python3-flake8-commas
+Requires:	python3-flake8-comprehensions
+Requires:	python3-flake8-datetimez
+Requires:	python3-flake8-docstrings
+Requires:	python3-flake8-isort
+Requires:	python3-flake8-noqa
+Requires:	python3-flake8-pytest-style
+Requires:	python3-flake8-quotes
+Requires:	python3-flake8-unused-arguments
+Requires:	python3-isort
+Requires:	python3-mypy
+Requires:	python3-pep8-naming
+Requires:	python3-pre-commit
+Requires:	python3-pytest
+Requires:	python3-pytest-asyncio
+Requires:	python3-pytest-only
+Requires:	python3-pytest-randomly
+Requires:	python3-pytest-timeout
+Requires:	python3-pytest-xdist
+Requires:	python3-redbaron
+Requires:	python3-sphinx
+Requires:	python3-sphinx-autodoc-typehints
+Requires:	python3-sphinx-markdown-builder
+Requires:	python3-types-setuptools
+
+%description
+# Apify API client for Python
+
+The Apify API Client for Python is the official library to access the [Apify API](https://docs.apify.com/api/v2) from your Python applications.
+It provides useful features like automatic retries and convenience functions to improve your experience with the Apify API.
+
+If you want to develop Apify Actors in Python,
+check out the [Apify SDK for Python](https://docs.apify.com/sdk/python) instead.
+
+## Installation
+
+Requires Python 3.8+
+
+You can install the package from its [PyPI listing](https://pypi.org/project/apify-client).
+To do that, simply run `pip install apify-client` in your terminal.
+
+## Usage
+
+For usage instructions, check the documentation on [Apify Docs](https://docs.apify.com/api/client/python/) or in [`docs/docs.md`](docs/docs.md).
+
+## Development
+
+### Environment
+
+For local development, it is required to have Python 3.8 installed.
+
+It is recommended to set up a virtual environment while developing this package to isolate your development environment,
+however, due to the many varied ways Python can be installed and virtual environments can be set up,
+this is left up to the developers to do themselves.
+
+One recommended way is with the built-in `venv` module:
+
+```bash
+python3 -m venv .venv
+source .venv/bin/activate
+```
+
+To improve on the experience, you can use [pyenv](https://github.com/pyenv/pyenv) to have an environment with a pinned Python version,
+and [direnv](https://github.com/direnv/direnv) to automatically activate/deactivate the environment when you enter/exit the project folder.
+
+### Dependencies
+
+To install this package and its development dependencies, run `make install-dev`
+
+### Formatting
+
+We use `autopep8` and `isort` to automatically format the code to a common format. To run the formatting, just run `make format`.
+
+### Linting, type-checking and unit testing
+
+We use `flake8` for linting, `mypy` for type checking and `pytest` for unit testing. To run these tools, just run `make check-code`.
+
+### Documentation
+
+We use the [Google docstring format](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html) for documenting the code.
+We document every user-facing class or method, and enforce that using the flake8-docstrings library.
+
+The documentation is then rendered from the docstrings in the code using Sphinx and some heavy post-processing and saved as `docs/docs.md`.
+To generate the documentation, just run `make docs`.
+
+### Release process
+
+Publishing new versions to [PyPI](https://pypi.org/project/apify-client) happens automatically through GitHub Actions.
+
+On each commit to the `master` branch, a new beta release is published, taking the version number from `src/apify_client/_version.py`
+and automatically incrementing the beta version suffix by 1 from the last beta release published to PyPI.
+
+A stable version is published when a new release is created using GitHub Releases, again taking the version number from `src/apify_client/_version.py`. The built package assets are automatically uploaded to the GitHub release.
+
+If there is already a stable version with the same version number as in `src/apify_client/_version.py` published to PyPI, the publish process fails,
+so don't forget to update the version number before releasing a new version.
+The release process also fails when the released version is not described in `CHANGELOG.md`,
+so don't forget to describe the changes in the new version there.
+
+
+%package -n python3-apify-client
+Summary:	Apify API client for Python
+Provides:	python-apify-client
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-apify-client
+# Apify API client for Python
+
+The Apify API Client for Python is the official library to access the [Apify API](https://docs.apify.com/api/v2) from your Python applications.
+It provides useful features like automatic retries and convenience functions to improve your experience with the Apify API.
+
+If you want to develop Apify Actors in Python,
+check out the [Apify SDK for Python](https://docs.apify.com/sdk/python) instead.
+
+## Installation
+
+Requires Python 3.8+
+
+You can install the package from its [PyPI listing](https://pypi.org/project/apify-client).
+To do that, simply run `pip install apify-client` in your terminal.
+
+## Usage
+
+For usage instructions, check the documentation on [Apify Docs](https://docs.apify.com/api/client/python/) or in [`docs/docs.md`](docs/docs.md).
+
+## Development
+
+### Environment
+
+For local development, it is required to have Python 3.8 installed.
+
+It is recommended to set up a virtual environment while developing this package to isolate your development environment,
+however, due to the many varied ways Python can be installed and virtual environments can be set up,
+this is left up to the developers to do themselves.
+
+One recommended way is with the built-in `venv` module:
+
+```bash
+python3 -m venv .venv
+source .venv/bin/activate
+```
+
+To improve on the experience, you can use [pyenv](https://github.com/pyenv/pyenv) to have an environment with a pinned Python version,
+and [direnv](https://github.com/direnv/direnv) to automatically activate/deactivate the environment when you enter/exit the project folder.
+
+### Dependencies
+
+To install this package and its development dependencies, run `make install-dev`
+
+### Formatting
+
+We use `autopep8` and `isort` to automatically format the code to a common format. To run the formatting, just run `make format`.
+
+### Linting, type-checking and unit testing
+
+We use `flake8` for linting, `mypy` for type checking and `pytest` for unit testing. To run these tools, just run `make check-code`.
+
+### Documentation
+
+We use the [Google docstring format](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html) for documenting the code.
+We document every user-facing class or method, and enforce that using the flake8-docstrings library.
+
+The documentation is then rendered from the docstrings in the code using Sphinx and some heavy post-processing and saved as `docs/docs.md`.
+To generate the documentation, just run `make docs`.
+
+### Release process
+
+Publishing new versions to [PyPI](https://pypi.org/project/apify-client) happens automatically through GitHub Actions.
+
+On each commit to the `master` branch, a new beta release is published, taking the version number from `src/apify_client/_version.py`
+and automatically incrementing the beta version suffix by 1 from the last beta release published to PyPI.
+
+A stable version is published when a new release is created using GitHub Releases, again taking the version number from `src/apify_client/_version.py`. The built package assets are automatically uploaded to the GitHub release.
+
+If there is already a stable version with the same version number as in `src/apify_client/_version.py` published to PyPI, the publish process fails,
+so don't forget to update the version number before releasing a new version.
+The release process also fails when the released version is not described in `CHANGELOG.md`,
+so don't forget to describe the changes in the new version there.
+
+
+%package help
+Summary:	Development documents and examples for apify-client
+Provides:	python3-apify-client-doc
+%description help
+# Apify API client for Python
+
+The Apify API Client for Python is the official library to access the [Apify API](https://docs.apify.com/api/v2) from your Python applications.
+It provides useful features like automatic retries and convenience functions to improve your experience with the Apify API.
+
+If you want to develop Apify Actors in Python,
+check out the [Apify SDK for Python](https://docs.apify.com/sdk/python) instead.
+
+## Installation
+
+Requires Python 3.8+
+
+You can install the package from its [PyPI listing](https://pypi.org/project/apify-client).
+To do that, simply run `pip install apify-client` in your terminal.
+
+## Usage
+
+For usage instructions, check the documentation on [Apify Docs](https://docs.apify.com/api/client/python/) or in [`docs/docs.md`](docs/docs.md).
+
+## Development
+
+### Environment
+
+For local development, it is required to have Python 3.8 installed.
+
+It is recommended to set up a virtual environment while developing this package to isolate your development environment,
+however, due to the many varied ways Python can be installed and virtual environments can be set up,
+this is left up to the developers to do themselves.
+
+One recommended way is with the built-in `venv` module:
+
+```bash
+python3 -m venv .venv
+source .venv/bin/activate
+```
+
+To improve on the experience, you can use [pyenv](https://github.com/pyenv/pyenv) to have an environment with a pinned Python version,
+and [direnv](https://github.com/direnv/direnv) to automatically activate/deactivate the environment when you enter/exit the project folder.
+
+### Dependencies
+
+To install this package and its development dependencies, run `make install-dev`
+
+### Formatting
+
+We use `autopep8` and `isort` to automatically format the code to a common format. To run the formatting, just run `make format`.
+
+### Linting, type-checking and unit testing
+
+We use `flake8` for linting, `mypy` for type checking and `pytest` for unit testing. To run these tools, just run `make check-code`.
+
+### Documentation
+
+We use the [Google docstring format](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html) for documenting the code.
+We document every user-facing class or method, and enforce that using the flake8-docstrings library.
+
+The documentation is then rendered from the docstrings in the code using Sphinx and some heavy post-processing and saved as `docs/docs.md`.
+To generate the documentation, just run `make docs`.
+
+### Release process
+
+Publishing new versions to [PyPI](https://pypi.org/project/apify-client) happens automatically through GitHub Actions.
+
+On each commit to the `master` branch, a new beta release is published, taking the version number from `src/apify_client/_version.py`
+and automatically incrementing the beta version suffix by 1 from the last beta release published to PyPI.
+
+A stable version is published when a new release is created using GitHub Releases, again taking the version number from `src/apify_client/_version.py`. The built package assets are automatically uploaded to the GitHub release.
+
+If there is already a stable version with the same version number as in `src/apify_client/_version.py` published to PyPI, the publish process fails,
+so don't forget to update the version number before releasing a new version.
+The release process also fails when the released version is not described in `CHANGELOG.md`,
+so don't forget to describe the changes in the new version there.
+
+
+%prep
+%autosetup -n apify-client-1.0.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-apify-client -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 1.0.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..46d2779
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+ac3b9a038435e2588ebb41c844b61b04  apify_client-1.0.0.tar.gz