[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyKDE] suggestion for configure.py in PyQt-4.0beta1
From:       "Glen W. Mabey" <Glen.Mabey () swri ! org>
Date:       2006-05-25 14:32:55
Message-ID: 20060525143255.GH31414 () bams ! swri ! edu
[Download RAW message or body]

phil at riverbankcomputing.co.uk wrote:
> On Wednesday 24 May 2006 7:04 pm, Glen W. Mabey wrote:
> > When employing the -d and -v flags, does the following seem reasonable?
> > It makes it so that some pretty standard operations have a better chance
> > of succeeding, like `import pyqtconfig'.
> >
> > Glen
> >
> >
> > *** configure.py.orig	Wed May 24 11:16:13 2006
> > --- configure.py	Wed May 24 11:17:09 2006
> > ***************
> > *** 994,1000 ****
> >           elif opt == "-c":
> >               opt_concat = 1
> >           elif opt == "-d":
> > !             opt_pyqtmoddir = os.path.abspath(arg)
> >           elif opt == "-i":
> >               opt_vendorcheck = 1
> >           elif opt == "-j":
> > --- 994,1000 ----
> >           elif opt == "-c":
> >               opt_concat = 1
> >           elif opt == "-d":
> > !             opt_pyqtmoddir = os.path.join(os.path.abspath(arg), "PyQt4")
> >           elif opt == "-i":
> >               opt_vendorcheck = 1
> >           elif opt == "-j":
> > ***************
> > *** 1015,1021 ****
> >           elif opt == "-u":
> >               opt_debug = 1
> >           elif opt == "-v":
> > !             opt_pyqtsipdir = os.path.abspath(arg)
> >           elif opt == "-w":
> >               opt_verbose = 1
> >
> > --- 1015,1021 ----
> >           elif opt == "-u":
> >               opt_debug = 1
> >           elif opt == "-v":
> > !             opt_pyqtsipdir = os.path.join(os.path.abspath(arg), "PyQt4")
> >           elif opt == "-w":
> >               opt_verbose = 1
> 
> The whole point of flags like these is to give the user complete control over 
> the configuration. There is no point in then imposing restrictions.

Well, my reasoning was:

1) In its standard usage, the preliminary directory PyQt4/ actually
   forms part of the module hierarchy,
2) Without it, nothing really works, and
3) Straight-across compatibility with previous versions of PyQt -- what
   worked there would then work with PyQt4.  That was the case with me
   as I was migrating to PyQt4, and I was surprised when that option
   raised an issue that took some investigating on my part to figure it
   out.

But, whatever.  I'm just glad that PyQt is available, and trying to be
helpful in the process.

Best Regards,
Glen Mabey

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[prev in list] [next in list] [prev in thread] [next in thread]