You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also getting a setuptools warning (using setuptools-67.6.1):
/usr/lib/python3.11/site-packages/setuptools/command/build_py.py:202: SetuptoolsDeprecationWarning: Installing '
ueberzug.X' as data is deprecated, please list it in `packages`.
!!
############################
# Package would be ignored #
############################
Python recognizes 'ueberzug.X' as an importable package,
but it is not listed in the `packages` configuration of setuptools.
'ueberzug.X' has been automatically added to the distribution only
because it may contain data files, but this behavior is likely to change
in future versions of setuptools (and therefore is considered deprecated).
Please make sure that 'ueberzug.X' is included as a package by using
the `packages` configuration field or the proper discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" and "data files" on setuptools
documentation page.
The text was updated successfully, but these errors were encountered:
ah yeh, that is somewhat of a tricky issue as it is more of a packaging caveat created when seebye dropped the python xlib, and it is one of the reasons i'm low key waiting until one distro packages it, as not long ago there was a change on the PEP standars and i would also be interested in having more control over the compilation of the c extension, i'm considering meson + ninja if a simple makefile doesn't suffice.
As a distro packager, I'd rather not see homebrew solutions like a Makefile (esp. for anything involving python). That aside, in the current situation I could just rm -r excess files and ignore the deprecation warning for now, so it's not a major issue.
aka:
Also getting a setuptools warning (using setuptools-67.6.1):
The text was updated successfully, but these errors were encountered: