Skip to content

Tox should adhere to the XDG BaseDir standard on Linux and possibly OS X #346

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pytoxbot opened this issue Sep 17, 2016 · 11 comments
Closed
Labels
feature:new something does not exist yet, but should needs:discussion It's not quite clear if and how this should be done

Comments

@pytoxbot
Copy link

You can find the specification here.

This blog post lists the advantages of using the XDG Base Directory Specification as follows:

  • $HOME is a lot less cluttered.
  • Backups are a lot more safer and easier (you know that creating a backup of your $XDG_DATA_HOME along with your files is enough).
  • A lot easier to reset a default configuration if you want/need it (and without any risk of losing information).
  • Avoid some strange bugs that happen because you had a old version of some configuration file.
  • It is a lot more flexible and portable because no paths are hard-coded. You can use the XDG library that does the job for you or, if you don’t want the dependency, implementing the XDG specification is only a few lines of code.

For example, what is currently ~/.tox/distshare would be ~/.cache/tox/distshare or something similar.

@pytoxbot
Copy link
Author

Original comment by @hpk42

what do you suggest as behaviour for windows? or does XDG specify that as well?

@obestwalter
Copy link
Member

Hi @hpk42 Another question: distshare is marked as deprecated, so why should we change this at all? Question would rather be, when do wo throw this out, or do we deprecate the deprecation?

@obestwalter obestwalter added feature:new something does not exist yet, but should needs:discussion It's not quite clear if and how this should be done and removed enhancement labels Aug 11, 2017
@gaborbernat
Copy link
Member

@obestwalter judging from the low interest and the fact of deprecation of distshare I would say let's close this for now.

@jleclanche
Copy link

When is distshare actually going away in that case?

@gaborbernat
Copy link
Member

the options it's marked as deprecated for 2 years now, so whenever we decide to do so 😃

@jleclanche
Copy link

@gaborbernat The issue really is that "there's a .tox directory in $HOME", so personally I'm happy with the PR not getting merged if distshare actually goes away -- but leaving it in without merging the PR, on the premise that it'll go away "some day" is kinda weird imo.

@obestwalter
Copy link
Member

Hi @jleclanche, the reason the PR never got merged is that the question how this should behave on Windows was never addressed. There was another problem pointed out in the PR comments that wasn't addressed also. So the assumption was that the interest in getting this merged was not big enough to put in some more work in and address those issues.

Maybe we should talk about the question what we do with distshare first and then decide if we actually need that global directory at all, wether it is directly in $HOME then or somewhere else.

@ntninja
Copy link

ntninja commented Mar 9, 2020

So, has the question on whether ~/.tox/distshare will continue to be used been resolved in the meantime?

@gaborbernat
Copy link
Member

We don't plan to go ahead with using distshare.

@zacchiro
Copy link

zacchiro commented Dec 2, 2020

A few years later, it looks like present-day tox still creates ~/.tox/distshare/ on every run, or am I missing a way to avoid that from happening / making it happen somewhere under ~/.local/share/tox/distshare instead?

@gaborbernat
Copy link
Member

I'm planning to remove this feature in tox 4, which would solve it.

@tox-dev tox-dev locked and limited conversation to collaborators Jan 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature:new something does not exist yet, but should needs:discussion It's not quite clear if and how this should be done
Projects
None yet
Development

No branches or pull requests

6 participants