Skip to content
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

Easier install process #10

Open
metov opened this issue Nov 11, 2022 · 2 comments
Open

Easier install process #10

metov opened this issue Nov 11, 2022 · 2 comments

Comments

@metov
Copy link

metov commented Nov 11, 2022

I noticed the README recommends installing by downloading the wheel or cloning the repo.

Actually, you can install directly from the repo with pip install git+https://github.com/rchaput/xdg-prefs. That might be a more straightforward instruction.

That said, have you consider publishing to PyPi, so that it can become just pip install XDG-Prefs?

@rchaput
Copy link
Owner

rchaput commented Nov 13, 2022

Thank you for your comment!

When I created this repo, I did not know much about PyPi, including the pip install git+https. This is indeed more straightforward, and I will update the Readme accordingly.

Concerning publishing to PyPi, this would be interesting, however 1) I do not have much time to work on this repo any more, and it feels strange to publish something that most likely will not be updated; and 2) AFAIK PyPi's official guide recommends using the more recent pyproject.toml configuration file, whereas I am using the older setup.py in this repo.
Yet, it should not take too much time to transform the setup.py into the corresponding pyproject.toml, so I'll keep that in mind.

rchaput added a commit that referenced this issue Nov 13, 2022
Replaced the instructions for downloading and installing the Wheel file with a more simple and straightforward version, relying on pip to directly download and install from Git(Hub).
This modification was proposed in #10 .
@metov
Copy link
Author

metov commented Nov 14, 2022

Thanks for the update! Even if you don't have time to maintain it, I found the program useful. If anyone else wants to use it, providing a PyPi package wouldn't do any harm, but it would make it easier for them to try it out. Although since you've already added the git+https example, I suppose there's not much difference.

If you did want to publish, I don't think there's a rule against using setup.py. They encourage pyproject.toml but, for example, I don't use it because it made editable installs difficult for a while. So you can publish with just a setup.py.

Yet, it should not take too much time to transform the setup.py into the corresponding pyproject.toml, so I'll keep that in mind.

The current setup.py you have is not very complex, so it would indeed not be difficult to do. I'm happy to submit a PR if you want. But as you say, if you don't intend to release any new versions in the future, there might not be much point.

In any case, thanks for the response, and thanks for developing and releasing the program!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants