Skip to content
This repository has been archived by the owner on Oct 12, 2021. It is now read-only.

Please, use Virtualenv #13

Open
athoune opened this issue Sep 2, 2017 · 5 comments
Open

Please, use Virtualenv #13

athoune opened this issue Sep 2, 2017 · 5 comments

Comments

@athoune
Copy link

athoune commented Sep 2, 2017

Nobody should install packages globally.

lxml is missing in the README, it must be installed.

@cclauss
Copy link
Contributor

cclauss commented Sep 7, 2017

@athoune Would you be willing to propose a pull request with edits to README.md ?

@blshkv
Copy link

blshkv commented Sep 13, 2017

Never say nobody. As a Pentoo developer I can assure you that we maintain global packages to keep our system as clean as possible. There is no reason why each of hundred tools should not share these global dependances. There is no reason for each basic python tool to create its own isolated python environment from scratch.

You should just use a standard (setup.py) set of tools and let users to choose how and where they want to install it.

@athoune
Copy link
Author

athoune commented Sep 13, 2017

I don't trust in global install, that's true.
Python application should use a requirements.txt or a setup.py for the most brave.

In the README.md, nobody should ask for global install. README is for user in hurry.

With this informations, a packager can package (globally).

@swisskyrepo
Copy link
Owner

Sure, it is a good idea to provide virtualenv command lines for this project.
If you have time, maybe you can do a pull request with them :)
Otherwise I will do it as soon as possible ;)

@alanyee
Copy link

alanyee commented Dec 17, 2019

@swisskyrepo shouldn't this issue be closed now?

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

No branches or pull requests

5 participants