Follow-up Comment #2, bug #35320 (project weechat):
The main problem it can create is that it will mean stuff installed in the
virtualenv only will not be found when you try to import it. It's simple to
prove.
1. Setup a virtualenv
2. Activate that virtualenv
3. Install pybuffer.py in python/autoload
4. Run weechat-curses
5. Create a pybuffer (/pybuffer)
6. Try to import your module.
This will fail because PYTHONPATH is incorrect for the python instance you are
running.
You can confirm that you are running the virtualenv'd instance by doing:
import sys
print sys.executable
Actually this points to a wider issue with the Python plugin implementation.
When you build your python extension loader you hard-link it to a specific
version of Python but it is not obvious to the user which version of Python
that is. Experienced developers will probably be able to figure these kinds
of issues out but its fairly non-intuitive.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?35320>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
Weechat-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/weechat-dev
