DreamPie

Respect Activated Virtualenv

Bug #530793 reported by Paul McLanahan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DreamPie
Won't Fix
Undecided
Unassigned

Bug Description

The #! line in /usr/bin/dreampie in the debian package uses a specific path to python (/usr/bin/python). Were this changed to "/usr/bin/env python" it would respect the current default python in the path, which would allow dreampie to respect activated virtual environments created by the virtualenv tool. This would be very helpful when using dreampie to test or debug a project.

Tags: virtualenv
Revision history for this message
Noam Yorav-Raphael (noamraph) wrote :

According to the debian packaging policy, it is not advised. (See http://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-interpreter_loc ). It will also probably require an ugly hack in setup.py.

So I prefer not to do it. You can always copy /usr/bin/dreampie into ~/bin and change there the starting line.

Thanks for the report!
Noam

Changed in dreampie:
status: New → Won't Fix
Revision history for this message
Paul McLanahan (pmclanahan) wrote :

That's cool. Thanks anyway, and thanks for your work on this project. It's very nice!

Revision history for this message
John Maxwell (xylowolf) wrote :

One possible solution might be to use a different interpreter for the application itself and the command execution.

If you're using virtualenvs that don't fall through to the system site-packages, then you have to install dreampie and pygtk into your virtualenv to make Noam's solution work. And pygtk isn't installable via pip on Linux, so even this (rather ugly) solution isn't workable.

This is a dealbreaker for me, although DreamPie looks very nice otherwise.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.