CRUX

NB: This only affects uses of CRUX who happen to be Python Developers and utilize virtualenv everywhere. Namely me afaik :)

Most CRUX Python Port(s) I've seen do something like this in their Pkgfile(s):

python setup.py ...

Under "normal circumstances" this is fine.

If you use virtualenv's like I do everywhere then this does not work.
The resulting shebangs become (for example): #!/home/prologic/bin/python
or worse #!/home/prologic/.virtualenvs/foo/bin/python

What needs to happen here going forward
(and I'll probably document this in the WIki)
is:

/usr/bin/python setup ...

NB: "python". not "python2" or anything else.

Rationale:

This ensures that the "system" python is execute for building the python package.
We do not need to worry about the whole Python2 vs. Python3 problem that Arch and others do.
Why? No-one uses Python3 (really) in practise. It still has a long way to go... "/usr/bin/python" __should__
always be the "system python" and should remain Python2 anyway.

cheers
James