%global _empty_manifest_terminate_build 0 Name: python-grpc-stubs Version: 1.53.0.1 Release: 1 Summary: Mypy stubs for gRPC License: MIT URL: https://github.com/shabbyrobe/grpc-stubs Source0: https://mirrors.nju.edu.cn/pypi/web/packages/5f/37/90c8512fa00d9df747751868616f2db266d3a2e01b83081c8f425b3601db/grpc-stubs-1.53.0.1.tar.gz BuildArch: noarch Requires: python3-grpcio %description This is a PEP-561-compliant stub-only package which provides type information of [gRPC](https://grpc.io>). Install using pip: pip install grpc-stubs Tests (courtesy of [pytest-mypy-plugins](https://github.com/typeddjango/pytest-mypy-plugins>): pip install -r requirements-dev.txt ./tools.sh test ## Python Support grpc-stubs is tested with 3.7 or later, but ideally it should support Python 3.6 as grpc still supports this. Python 3.6 had to be disabled in the tests due to various cascading fiascos and a lack of time to contend with them. Feel free to submit a PR if you'd like to see it returned, or open issues. Ensure that you supply an MRE as per the contributing guidelines below. ## Contributing ### Minimum Reproducible Examples (MRE) Unfortunately, due to the fussy nature of `grpc` and its dependencies, and the huge amount of time required to construct a context in which to verify and debug issues, starting from 2022-04-16, fairly strict issue and pull request templates have been added. Minimum Reproducible Examples are now a hard requirement for pull requests that touch the typing surface, and a soft requirement for issues. PRs without a functioning MRE transfer the burden entirely from the contributor to the maintainer, and I simply don't have time to do the deep-dives required to build out MREs from scratch when issues inevitably crop up. PRs without a trivially executable MRE will be closed without further consideration; of course you are always welcome to reopen once you have added a verified MRE! ### Tests This project uses a slightly old version of https://github.com/TypedDjango/pytest-mypy-plugins for testing. All new contributions will be required to include at least one, but probably multiple tests. See `typesafety/test_*.yml`. ### Code-generated stubs PRs containing auto-generated stubs have had to be reverted several times due to issues. Starting from 2022-04-16, autogenerated stubs from `mypy-protobuf` will not be accepted without extensive tests, and will not be accepted with edit warnings left in. It's ok to use this tool to seed stubs, but not to refresh stubs - once contributed to this repo, the stubs should be presumed to have been written by hand. ## Calls for assistance There are several areas where `grpc-stubs` could use some TLC. If you'd like to help with any of this, please reach out! ### Maintainers It's unlikely I'll be returning to grpc full-time for the foreseeable future, and my knowledge of the minutiae fades with each passing year. If anyone wishes to assume maintainership of this project ongoing, please reach out. ## Other Very Useful Typed Python Stuff - https://github.com/TypedDjango - https://github.com/typeddjango/pytest-mypy-plugins - https://github.com/typeddjango/awesome-python-stubs %package -n python3-grpc-stubs Summary: Mypy stubs for gRPC Provides: python-grpc-stubs BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-grpc-stubs This is a PEP-561-compliant stub-only package which provides type information of [gRPC](https://grpc.io>). Install using pip: pip install grpc-stubs Tests (courtesy of [pytest-mypy-plugins](https://github.com/typeddjango/pytest-mypy-plugins>): pip install -r requirements-dev.txt ./tools.sh test ## Python Support grpc-stubs is tested with 3.7 or later, but ideally it should support Python 3.6 as grpc still supports this. Python 3.6 had to be disabled in the tests due to various cascading fiascos and a lack of time to contend with them. Feel free to submit a PR if you'd like to see it returned, or open issues. Ensure that you supply an MRE as per the contributing guidelines below. ## Contributing ### Minimum Reproducible Examples (MRE) Unfortunately, due to the fussy nature of `grpc` and its dependencies, and the huge amount of time required to construct a context in which to verify and debug issues, starting from 2022-04-16, fairly strict issue and pull request templates have been added. Minimum Reproducible Examples are now a hard requirement for pull requests that touch the typing surface, and a soft requirement for issues. PRs without a functioning MRE transfer the burden entirely from the contributor to the maintainer, and I simply don't have time to do the deep-dives required to build out MREs from scratch when issues inevitably crop up. PRs without a trivially executable MRE will be closed without further consideration; of course you are always welcome to reopen once you have added a verified MRE! ### Tests This project uses a slightly old version of https://github.com/TypedDjango/pytest-mypy-plugins for testing. All new contributions will be required to include at least one, but probably multiple tests. See `typesafety/test_*.yml`. ### Code-generated stubs PRs containing auto-generated stubs have had to be reverted several times due to issues. Starting from 2022-04-16, autogenerated stubs from `mypy-protobuf` will not be accepted without extensive tests, and will not be accepted with edit warnings left in. It's ok to use this tool to seed stubs, but not to refresh stubs - once contributed to this repo, the stubs should be presumed to have been written by hand. ## Calls for assistance There are several areas where `grpc-stubs` could use some TLC. If you'd like to help with any of this, please reach out! ### Maintainers It's unlikely I'll be returning to grpc full-time for the foreseeable future, and my knowledge of the minutiae fades with each passing year. If anyone wishes to assume maintainership of this project ongoing, please reach out. ## Other Very Useful Typed Python Stuff - https://github.com/TypedDjango - https://github.com/typeddjango/pytest-mypy-plugins - https://github.com/typeddjango/awesome-python-stubs %package help Summary: Development documents and examples for grpc-stubs Provides: python3-grpc-stubs-doc %description help This is a PEP-561-compliant stub-only package which provides type information of [gRPC](https://grpc.io>). Install using pip: pip install grpc-stubs Tests (courtesy of [pytest-mypy-plugins](https://github.com/typeddjango/pytest-mypy-plugins>): pip install -r requirements-dev.txt ./tools.sh test ## Python Support grpc-stubs is tested with 3.7 or later, but ideally it should support Python 3.6 as grpc still supports this. Python 3.6 had to be disabled in the tests due to various cascading fiascos and a lack of time to contend with them. Feel free to submit a PR if you'd like to see it returned, or open issues. Ensure that you supply an MRE as per the contributing guidelines below. ## Contributing ### Minimum Reproducible Examples (MRE) Unfortunately, due to the fussy nature of `grpc` and its dependencies, and the huge amount of time required to construct a context in which to verify and debug issues, starting from 2022-04-16, fairly strict issue and pull request templates have been added. Minimum Reproducible Examples are now a hard requirement for pull requests that touch the typing surface, and a soft requirement for issues. PRs without a functioning MRE transfer the burden entirely from the contributor to the maintainer, and I simply don't have time to do the deep-dives required to build out MREs from scratch when issues inevitably crop up. PRs without a trivially executable MRE will be closed without further consideration; of course you are always welcome to reopen once you have added a verified MRE! ### Tests This project uses a slightly old version of https://github.com/TypedDjango/pytest-mypy-plugins for testing. All new contributions will be required to include at least one, but probably multiple tests. See `typesafety/test_*.yml`. ### Code-generated stubs PRs containing auto-generated stubs have had to be reverted several times due to issues. Starting from 2022-04-16, autogenerated stubs from `mypy-protobuf` will not be accepted without extensive tests, and will not be accepted with edit warnings left in. It's ok to use this tool to seed stubs, but not to refresh stubs - once contributed to this repo, the stubs should be presumed to have been written by hand. ## Calls for assistance There are several areas where `grpc-stubs` could use some TLC. If you'd like to help with any of this, please reach out! ### Maintainers It's unlikely I'll be returning to grpc full-time for the foreseeable future, and my knowledge of the minutiae fades with each passing year. If anyone wishes to assume maintainership of this project ongoing, please reach out. ## Other Very Useful Typed Python Stuff - https://github.com/TypedDjango - https://github.com/typeddjango/pytest-mypy-plugins - https://github.com/typeddjango/awesome-python-stubs %prep %autosetup -n grpc-stubs-1.53.0.1 %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-grpc-stubs -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Fri Apr 21 2023 Python_Bot - 1.53.0.1-1 - Package Spec generated