PYTHONPATH problem during development (title changed by maintainer) about comitup HOT 9 CLOSED

Because there is a PYTHONPATH problem. You are welcome to attack that, if you wish. Or, you can vote with your feet.

from comitup.

I've probably never run setup.py on Raspbian. It serves as a config file for the debian build. There are a number of installation tasks required that are not well suited for setup.py.

Try the deb file.

from comitup.

It occurs to me that you may not have seen the home page.

from comitup.

from comitup.

You pretty much have to have a deb install for the environment to work. For development after that, I use a small deploy script to scp the project tree from a remote computer to a local project tree, and then copy the files to the individual subdirectories in /usr/share/comitup/. The last step could be skipped with some work to address the path problem you're seeing. But, I prefer to edit the project on a remote system, which means that some sort of custom deploy process is required for me.

from comitup.

Okay... so the setup.py doesn't really do what people expect it to do?

There's more configuration that needs to be done beyond running setup.py build and setup.py install?

Why don't we have setup.py do everything that needs to be done?

from comitup.

setup.py is intended to be cross platform, and currently does that job. The .deb file is specifically targeted to a particular OS, and can be uninstalled.

It sounds like you need to go find the tool that is right for you.

from comitup.

Then why do I get:

ImportError: cannot import name persist

After running build and install with setup.py if it currently does the job?

from comitup.

Why did you close an issue that isn't fixed? This issue doesn't have to do with a premade image.

from comitup.