On 23/10/10 18:07, Phil Thompson wrote:
On Sat, 23 Oct 2010 17:39:28 +0100, Baz Walter<baz...@ftml.net> wrote:
On 23/10/10 12:25, Hans-Peter Jansen wrote:
On Saturday 23 October 2010, 02:54:40 Xavion wrote:
Doing so will save me from having to hard-code something like
"#!/usr/bin/env python2" into the main executable file, only to be
disappointed after finding out that some Linux distributions have
already built PyQt on Python v3.
For a transition phase of a couple of years, I would do it the other
way around. Your distribution should have created a python3 symlink,
hence, if you code for python3, use #!/usr/bin/env python3, given it
isn't compatible with python< 3, otherwise use #!/usr/bin/env python.
not sure i understand you here. the current situation on arch is:
python -> python3.1
That is unbelievably dumb.
that was exactly my initial reaction. however, given arch's philosophy,
it does make sense.
_______________________________________________
PyQt mailing list PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
