Phil Thompson wrote:
On Tue, 06 Jan 2009 14:19:50 -0500, Neal Becker ndbeck...@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
On mer, 2009-01-07 at 09:26 +, Chris Withers wrote:
Phil Thompson wrote:
On Tue, 06 Jan 2009 14:19:50 -0500, Neal Becker ndbeck...@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.
Phil Thompson wrote:
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.
Hmmm, apologies then, must have
On mer, 2009-01-07 at 10:33 +, Chris Withers wrote:
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.
I don't understand you. Are you really saying that it's harder to
understand that
* Giovanni Bajo [Wed, 07 Jan 2009 11:06:09 +0100]:
Appending the underscore to those symbols is a perfect fix IMO.
I realize this is a matter of preference, but I'd suggest using qbin()
and qhex() rather than the underscore: I think it makes more sense for
stuff that can be imported into the
On Wed, 07 Jan 2009 10:33:00 +, Chris Withers ch...@simplistix.co.uk
wrote:
Giovanni Bajo wrote:
On mer, 2009-01-07 at 09:26 +, Chris Withers wrote:
Phil Thompson wrote:
On Tue, 06 Jan 2009 14:19:50 -0500, Neal Becker ndbeck...@gmail.com
wrote:
A bit nasty, since I see (and follow)
Giovanni Bajo wrote:
On mer, 2009-01-07 at 09:26 +, Chris Withers wrote:
Phil Thompson wrote:
On Tue, 06 Jan 2009 14:19:50 -0500, Neal Becker ndbeck...@gmail.com
wrote:
A bit nasty, since I see (and follow) lots of examples that say:
from PyQt4.QtCore import *
This redefines the builtin
Neal Becker wrote:
If the pyqt examples did not use *, and if you could import a useful enough
subset without doing that, I'd agree. If the suggestion is to explicitly
qualify everything, I don't think that's reasonable.
Yes, python, well know for believing that implicit is better than
On 2009-01-07, Chris Withers wrote:
Phil Thompson wrote:
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
Adeodato Simó wrote:
If you see in the middle of a program hex_(foo), you may wonder where
that came from, whereas qhex(foo) is going to be rather obvious.
Greetings all,
Might I humbly second this motion? I do understand the usual
reservations about star-imports (being the kind of guy that
On Wednesday 07 January 2009 05:27:06 am Sundance wrote:
Adeodato Simó wrote:
If you see in the middle of a program hex_(foo), you may wonder
where that came from, whereas qhex(foo) is going to be rather
obvious.
Greetings all,
Might I humbly second this motion? I do understand the usual
A bit nasty, since I see (and follow) lots of examples that say:
from PyQt4.QtCore import *
This redefines the builtin hex.
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
On Tue, 06 Jan 2009 14:19:50 -0500, Neal Becker ndbeck...@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.
Phil
___
PyQt mailing list
On Tue Jan 6 22:05:41 GMT 2009, Phil Thompson wrote:
On Tue, 06 Jan 2009 14:19:50 -0500, Neal Becker ndbecker2 at gmail.com
This redefines the builtin hex.
Check the Roadmap.
http://www.riverbankcomputing.com/software/pyqt/roadmap
...for those not following the site updates so closely.
14 matches
Mail list logo
