Package Details: python-xdg-base-dirs 6.0.2-1

Git Clone URL: https://aur.archlinux.org/python-xdg-base-dirs.git (read-only, click to copy)
Package Base: python-xdg-base-dirs
Description: An implementation of the XDG Base Directory Specification in Python
Upstream URL: https://github.com/srstevenson/xdg-base-dirs
Licenses: ISC
Submitter: gilbus
Maintainer: gilbus
Last Packager: gilbus
Votes: 7
Popularity: 0.007197
First Submitted: 2023-04-30 21:53 (UTC)
Last Updated: 2024-11-03 19:00 (UTC)

Pinned Comments

ilai commented on 2023-03-14 05:16 (UTC)

The upstream package was recently modified to avoid an import collision with PyXDG. The package must now be imported as import xdg-base-dirs instead of import xdg.

If a package imports xdg, it should depend on https://archlinux.org/packages/extra/any/python-pyxdg instead of python-xdg, or the imports should be updated upsteam.

Latest Comments

1 2 Next › Last »

qubidt commented on 2023-05-15 13:50 (UTC)

@ilai no it wouldn't, unfortunately. pyxdg has a different interface and doesn't provide the function that autoimport calls

ilai commented on 2023-05-09 13:47 (UTC)

@qubidt Would using pyxdg instead of this package solve the issue for python-autoimport?

qubidt commented on 2023-04-03 10:07 (UTC)

I think a separate package should be made for xdg-base-dirs (following the pip package). Because xdg on pypi still points to the old package, and is imported under xdg. python-autoimport can't migrate to the new package because xdg-base-dirs doesn't support python < 3.10. So as-is, there's no way to package autoimport without vendoring xdg

ilai commented on 2023-03-14 05:16 (UTC)

The upstream package was recently modified to avoid an import collision with PyXDG. The package must now be imported as import xdg-base-dirs instead of import xdg.

If a package imports xdg, it should depend on https://archlinux.org/packages/extra/any/python-pyxdg instead of python-xdg, or the imports should be updated upsteam.

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?

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.).

1 2 Next › Last »