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

List:       pykde
Subject:    Re: [PyQt] PyQt4.Qtcore defines 'hex'
From:       Phil Thompson <phil () riverbankcomputing ! com>
Date:       2009-01-07 10:41:59
Message-ID: 88f7c3a4a31d1a68d8aae9e586bcb7ed () localhost
[Download RAW message or body]

On Wed, 07 Jan 2009 10:33:00 +0000, Chris Withers <chris@simplistix.co.uk>
wrote:
> Giovanni Bajo wrote:
>> On mer, 2009-01-07 at 09:26 +0000, Chris Withers wrote:
>>> Phil Thompson wrote:
>>>> On Tue, 06 Jan 2009 14:19:50 -0500, Neal Becker <ndbecker2@gmail.com>
>>>> wrote:
>>>>> A bit nasty, since I see (and follow) lots of examples that say:
>>>>> from PyQt4.QtCore import *
>>>>>
>>>>> This redefines the builtin hex.
>>>> Check the Roadmap.
>>> Appending a _ just to make an unpleasant style of programming work
seems
>>>
>>> like a pretty silly idea.
>>>
>>> I, along with everyone else who's tryng to learn a new python package, 
>>> absolutely *hate* "from x import *" as it makes it much more difficult 
>>> figure out where something is coming from.
>> 
>> So don't use it.
> 
> You rather miss my point.
> 
> I don't ever use star imports anyway.
> 
> However, like most people, I learn by example, and when the examples 
> contain exclusively start imports, they are much less helpful than they 
> could be.
> 
> It's a shame PEP8 doesn't make a pronouncement on this. PEP 328 is 
> pretty clear though...
> 
>> This has been discussed thousands of times and it starts getting
>> annoying. 
> 
> Yes, it is annoying that all the example code continues to be in a form 
> that confuses users trying to learn PyQt.

*None* of the PyQt4 examples uses star imports.

Phil
_______________________________________________
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]