Dear Maintainer,

I just mistakenly reported a bug at PIP because I assumed that
python3-xdg only contained the xdg package from pyxdg and was confused
why installing the xdg package failed with the message:

$ pip install xdg
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: xdg in /usr/lib/python3/dist-packages (5)

As it turns out that is because the python3-xdg package now also
contains a compatability layer for the xdg package from PyPI.[1]

I think it's quite confusing that one Debian package contains
the code from several PyPI packages but I understand that this was meant
to address the namespace conflict between those two packages.

In any case I think the description of the package should be updated to
explain the current situation (the namespace conflict between the xdg
and pyxdg PyPI packages and that this Debian package contains the code
of both).

Cheers,
Martin

[1]: https://salsa.debian.org/python-team/packages/pyxdg/-/commit/2e61e056826ea13e6a1a49202a33213f6ee38219

Hey.

I agree, this has also just bitten me.

Especially as pyxdg's documentation is... sparse... people will
typically just use what they see in the code (or what interactive tools
like ptpython show them).

But now on Debian we have stuff in there which only works on Debian,
which is unfortunate.


And it's not just the extra symbols, but also the automatically
imported BaseDirectory in the package.


Dear maintainers, perhaps you could just try to get your changes merged
upstream?


Cheers,
Chris.