[PyQt] Re: trouble installing PyQt

Phil Thompson phil at riverbankcomputing.co.uk
Fri Apr 13 10:15:23 BST 2007


On Friday 13 April 2007 9:37 am, Gerard Vermeulen wrote:
> On Fri, 13 Apr 2007 07:24:10 +0100
>
> Mark Summerfield <mark at qtrac.eu> wrote:
> > On Thu 12-Apr-07, Phil Thompson wrote:
> > > On Thursday 12 April 2007 5:58 pm, Giovanni Bajo wrote:
> > > > On 4/12/2007 6:48 PM, Kelie wrote:
> > > > >> Add the Qt binary directory to your PATH.
> > > > >
> > > > > thanks Giovanni. that fixed the problem.
> > > >
> > > > BTW, PyQt's binary install could verify this automatically and *at
> > > > least* display a warning. Phil?
> > >
> > > I suppose so - but it's really up to the Qt installer to get this
> > > right.
> >
> > I do think you're missing the point here.
> >
> > You install GPL Qt, but if you want to run PyQt4 programs they just
> > don't work by double-clicking. So you can either run the Qt console
> > shortcut which executes qtvars.bat and run them from the
> > console---ugly, or you can manually add Qt to the path. Since _you_
> > know where Qt is when PyQt is installed, you could either (1) add
> > Qt's bin dir to the path (yes please), or (2) at least tell the poor
> > user to do it themselves! TT are never going to do this because as
> > far as they're concerned they've got qtvars.bat.
> >
> > In the Appendix to the book I will explain how to add Qt to the path,
> > so at least readers will know:-)
>
> As far as I remember, qtvars.bat overrides the PATH instead of
> prepending its stuff to an already existent PATH (don't know if
> that is possible on Windows, since I am a Linux and OS X user).

Qt GPL replaces your PATH. Qt Commercial updates your path. I assume that 
there is a good reason for the difference.

> I ended up changing the PATH myself to point to the Python/sip *and*
> the Qt binaries to build PyQwt from Windows console, because python
> is not found in Qt's console.
>
>
> Phil,  not including the sip program and sip files into the PyQt binary
> installer forces users to rebuild sip and PyQt before they can build
> an extension module piggy-backing on PyQt. Can you include those, or
> are they taking too much space or bandwidth?

The target audience of the installer is people who don't need additional 
packages and want to get started quickly and easily, ie. 95%+ of users. At 
the moment, you may be the only person who needs that extra stuff.

To make things even easier in the future I was thinking of including the 
necessary bits of Qt so that you don't have to download that in the first 
place. Also I would like to include eric4 and maybe other 3rd party packages 
(of which PyQwt would be a prime candidate). I would also consider making 
this a statically linked build - but that has issues that need to be thought 
through.

Phil


More information about the PyQt mailing list