The `SPECPARTS` directory is leaking into setuptools package discovery. When
upstream Python projects choose to use automatic Python package discovery by
setuptools, `SPECPARTS` is considered a Python package (because empty
directories actually *are* Python packages) and when not explicitly excluded,
it makes setuptools die with:
```
...
discovered packages -- ['pgactivity', 'SPECPARTS', 'pgactivity.queries']
Traceback (most recent call last):
...
File "/usr/lib/python3.11/site-packages/setuptools/discovery.py", line 441,
in _analyse_flat_layout
return self._analyse_flat_packages() or self._analyse_flat_modules()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/setuptools/discovery.py", line 447,
in _analyse_flat_packages
self._ensure_no_accidental_inclusion(top_level, "packages")
File "/usr/lib/python3.11/site-packages/setuptools/discovery.py", line 477,
in _ensure_no_accidental_inclusion
raise PackageDiscoveryError(cleandoc(msg))
setuptools.errors.PackageDiscoveryError: Multiple top-level packages discovered
in a flat-layout: ['SPECPARTS', 'pgactivity'].
```
(Full traceback at
https://github.com/dalibo/pg_activity/pull/378#issuecomment-1571655683)
I suppose other upstreams might consider a new directory in `$PWD` something to
automatically consider important.
----
Could this directory either be moved outside of `%_builddir/%buildsubdir` or at
least be hidden (e.g. `.SPECPARTS`)? Thanks
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2532
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2...@github.com>_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
