Re: RPM build: unpackaged file .pyi

2022-03-24 Thread Miro Hrončok
On 24. 03. 22 13:19, Ben Beasley wrote: This is a “stub file” for type checking. It looks like upstream is trying to follow https://peps.python.org/pep-0484 rather than the later https://peps.python.org/pep-0561/. However, the way they are installing the stub file with data_files in setup.py

Re: RPM build: unpackaged file .pyi

2022-03-24 Thread Ben Beasley
This is a “stub file” for type checking. It looks like upstream is trying to follow https://peps.python.org/pep-0484 rather than the later https://peps.python.org/pep-0561/. However, the way they are installing the stub file with data_files in setup.py is resulting in it getting dumped in

RPM build: unpackaged file .pyi

2022-03-24 Thread Denis Fateyev
Hello there, After bumping upstream version in "python-apsw", I have noticed that a new Python .pyi file was created in the new version, so the package build process started to fail: error: Installed (but unpackaged) file(s) found: /usr/apsw.pyi