@Fabien-B looks like a good idea because more and more people have python conflicts. However, in the current version it looks like you need quite some manual work to get things working. Can that be improved? It would also (temporary) make switching branches quite hard doesn't it?

@dewagter I don't think a 2 step process that you only have to do once is "quite some manual work" 😃 .
It can be added to the makefile, but it's maybe best to have some return on experience before doing that.
The venv files are not tracked by git, so there is absolutely no problem switching branches.
The only annoying thing is that on a branch where the .gitignore have not been updated, git will show all venv files as "untracked". But it's the only issue I can see.

Something like this: a04674b ?

Something like this: a04674b ?

Great! Thanks a lot!
PS: Can this be run several times, or will keep adding bash variables?

I added a guard to prevent creating the venv from itself (which can't be done), and adding the source to the .bashrc.
However, if the venv is deactivated, it is still possible to add the source multiple times in .bashrc.
As this is optional, defaulting to false, and harmless anyway, I would argue this is a reasonable compromise.

Rebased on master

@dewagter If it's ok for you, I replaced lsb_release by distro in the install script because lsb_release is not installable from pypi.
It works pretty much the same.

@dewagter If it's ok for you, I replaced lsb_release by distro in the install script because lsb_release is not installable from pypi. It works pretty much the same.

OK for me. I would just like the script to adapt to the distribution. For me, a project should be installed with git clone CODE followed by and by install without needing a full WIKI to survive.

Can we merge this ?

Yes

The pprzlink ref should be fixed first. Otherwise I'm okay with this.