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

List:       pykde
Subject:    [PyQt] Re: setValue of QSettings adds undesired whitespaces
From:       luca <lucafasano () interfree ! it>
Date:       2009-06-29 11:01:21
Message-ID: loom.20090629T105310-890 () post ! gmane ! org
[Download RAW message or body]

Hans-Peter Jansen <hpj <at> urpla.net> writes:

Dear Pete,

> Hmm, putting it bluntly: your concept of relying on two different parsers 
> (with different behavior) handling some arbitrary ini file format is 
> flawed. I wouldn't even call this a bug. It's simply unpredictable 
> behavior.

You're right, but using a single file for both configurations would be great.

> If you really want predictable behavior, get rid off one of them.

I can't. I need to use logging and Qt configuration separately.

> 
> Since logging needs only a few parameter, why don't you fetch them via 
> QSetting and pass them on to your logging setup. And because logging has a 
> somewhat strange idea of log levels, you have a good chance of translating 
> them for human consumption (or even adjustment). 

I know that, but I need configuring logging before Qt is imported.

> 
> We could then migrate this discussion to the more general one: 
>  - best practices in handling config data, default values, etc.
> 
> Pete
> 

Thanks,
Luca



_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]