-
Notifications
You must be signed in to change notification settings - Fork 2
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
Install instructions/setup.py
should recommend non-root install
#9
Comments
Ok. So, the SSL certificate issue was a screw-up in my personal installation. Once I fixed the I still see the following errors when running, but it seems to run:
So it seems to be running more or less correctly, but these I still think there's no reason to install something like this with |
I'm having vobject-0.9.6.1installed myself and can't see those errors ... but apparently I'm at python 3.11, perhaps that's the reason? In any case, I think this is an issue with vobject rather than plann. vobject is pulled in as a dependency from the caldav library. The caldav library is mostly utilizing icalendar rather than vobject, but vobject support is still there for backward-compatibility reasons. Perhaps I should clean out the last references to vobject in the caldav library and declare it as an optional dependency. I'd happily merge a pull request that improves on the installation part - but I consider it to be a requirement that it's possible to install the |
setup.py
brokensetup.py
should recommend non-root install
|
New merge-request is appreciated :-) |
Hi there, (sorry, somehow submitted before I was done typing)
The installation instructions suggest running
sudo python3 setup.py
. That's definitely not the way to do python development. This is not a system-level utility that needs to run as root, so it should be possible to install without any privileges at all.If you run
python3 -m venv .venv
and then. .venv/bin/activate
, you get a unique virtual python environment that needs no privileges whatsoever to install. It's just in your own personal directory, and things installed bypip
can easily be installed because they're just going into your home directory (where you don't need root privileges to write files).Having said that, running
python3 setup.py install
produces a lot of warnings like this:At the end of
setup.py
's output, I get this error:Somehow I still seem to have a
plann
script in my path, but when I run it, I see:The dependencies don't appear to be captured properly. It is depending on a module that I don't have installed, but the setup program didn't cause me to install it. This is also a reason not to do
sudo setup.py install
because you modify your entire operating system. It's hard to wipe the environment clean for testing. But if you use a virtual environment, you can trivially runrm -rf .venv
and wipe it out clean. Then runpython3 -m venv .venv
and create a fresh environment. That way it's easy to test whether all the dependencies are installed on a clean system.Somehow I seem to have gotten a
plann
script installed, butThe text was updated successfully, but these errors were encountered: