Package Details: python-xdg 5.1.1-2

Git Clone URL: https://aur.archlinux.org/python-xdg.git (read-only, click to copy)
Package Base: python-xdg
Description: An implementation of the XDG Base Directory Specification in Python
Upstream URL: https://github.com/srstevenson/xdg
Licenses: ISC
Conflicts: python-pyxdg
Submitter: jaantoots
Maintainer: ilai
Last Packager: ilai
Votes: 4
Popularity: 0.22
First Submitted: 2020-11-30 21:07 (UTC)
Last Updated: 2022-11-17 06:19 (UTC)

Latest Comments

electrickite commented on 2022-08-15 12:34 (UTC)

Agree with louson, dephell requires many additional AUR modules. Could this package be updated to use his suggested approach?

MarsSeed commented on 2022-07-16 17:58 (UTC)

Fortunately, Goobook doesn't depend on this module anymore.

louson commented on 2022-07-07 09:12 (UTC)

The dependency to dephell hangs to many things. Actually, we can just move to the standard packaging as described in the wiki. Check here for my suggestion:

https://gitlab.com/louson-aur/python-xdg/-/blob/master/PKGBUILD

ectospasm commented on 2021-01-07 03:12 (UTC)

@jaantoots: Thanks, a venv was the way to go. I documented how I worked around the problem in the following forum post:

https://bbs.archlinux.org/viewtopic.php?id=262403

...in case anyone runs into the same issue.

jaantoots commented on 2021-01-07 00:25 (UTC)

Both packages want to live in /usr/lib/python3.9/site-packages/xdg/, so I don't think there is much that can be done by package maintainers.

Both packages exist on PyPI and pip happily just overwrites the files if you try to install both. I don't really see a way for both of them to coexist in the same environment.

I guess you can try complaining to respective upstream projects. But you are probably better off by simply avoiding the system packages for either (if it is feasible to run what you want in virtualenvs, containers, etc.).

ectospasm commented on 2021-01-06 23:11 (UTC)

This package conflicts with Community (non-AUR) package python-pyxdg. I have AUR programs that depend on python-xdg (such as goobook), and others that depend on python-pyxdg (such as mimeo, which says it depends on python-xdg but actually depends on python-pyxdg).

Is there an effort to make python-xdg API/ABI compatible with python-pyxdg? python-pyxdg has elements such as xdg.BaseDirectory, xdg.DesktopEntry, and xdg.Mime which do not exist in the latest version of python-xdg. Do packages which depend on python-pyxdg need to be updated so they run against the (far simpler) python-xdg? Where should I go next for help?