So it's possible to generate a package with empty summary which then fails to build SRPM, because Summary is missing.
Make it impossible, summary can be generated automatically in case none if found in the upstream data.
+ pyp2spec google-cloud-appengine-logging --fedora-compliant --top-level
Generating configuration file
Assuming 'google-cloud-appengine-logging' is a package name
Querying PyPI for package 'google-cloud-appengine-logging'
Assuming changelog --message=Package generated with pyp2spec
Assuming --description=This is package 'google-cloud-appengine-logging' generated automatically by pyp2spec.
Assuming --summary=
Assuming --version=1.1.0
Attempting to get license from Classifiers
License in Classifiers not found, looking for the 'License' keyword
Assuming --license=Apache 2.0
Assuming --release=1
Only top-level modules will be checked
Saving configuration file to './python-google-cloud-appengine-logging.conf'
Configuration file was saved successfully
Generating spec file
Saving spec file to 'python-google-cloud-appengine-logging.spec'
Spec file was saved successfully
Done
So it's possible to generate a package with empty summary which then fails to build SRPM, because Summary is missing. Make it impossible, summary can be generated automatically in case none if found in the upstream data.