On Fri, Aug 29, 2008 at 6:22 AM, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> You're right, let's abolish inheritance, too, because then you might have to
> read more than one class to see what's happening.
You are joking, but I actually took this idea quite seriously. Once
(four years ago or so) I
At 06:07 AM 8/29/2008 +0200, Michele Simionato wrote:
On Thu, Aug 28, 2008 at 8:54 PM, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> I created a "universal metaclass" in
> DecoratorTools whose sole function is to delegate metaclass __new__,
> __init__, and __call__ to class-level methods (e.g. __cl
On Thu, Aug 28, 2008 at 8:54 PM, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> I created a "universal metaclass" in
> DecoratorTools whose sole function is to delegate metaclass __new__,
> __init__, and __call__ to class-level methods (e.g. __class_new__,
> __class_call__, etc.), thereby eliminating
2008/8/28 Steve Holden <[EMAIL PROTECTED]>:
> Guido van Rossum wrote:
>> On Wed, Aug 27, 2008 at 6:21 PM, Steven D'Aprano <[EMAIL PROTECTED]>
wrote:
>>> On Thu, 28 Aug 2008 08:39:01 am Georg Brandl wrote:
Fredrik Lundh schrieb:
> (using 3.0a4)
>
> >>> exec(open("file.py"))
>
>
On Fri, 29 Aug 2008, Greg Ewing wrote:
Steven D'Aprano wrote:
I don't think M.__file__ should lie and say it was loaded from a file that
it wasn't loaded from. It's useful to be able to look at a module and see
what file it was actually loaded from.
On the other hand, it could be useful to
Steven D'Aprano wrote:
I don't think M.__file__ should lie and say it was loaded from a file
that it wasn't loaded from. It's useful to be able to look at a module
and see what file it was actually loaded from.
On the other hand, it could be useful to be able to find
the source file for a mod
> This may have been true for old style classes, but as new style classes
> inherit a default __hash__ from object - mutable objects *will* be usable as
> dictionary keys (hashed on identity) *unless* they implement a __hash__
> method that raises a type error.
>
I always thought this was a bug in
Jeff Hall wrote:
I'm not sure about the first but as for the __reversed__ we had a
discussion yesterday and it was indeed added in 2.4 (oddly, my 2.5
documentation has this correct... )
2.4 doc:
reversed( seq)
Return a reverse iterator. seq must be an object which supports the
sequence pro
Michael Foord wrote:
> This may have been true for old style classes, but as new style classes
> inherit a default __hash__ from object - mutable objects *will* be
> usable as dictionary keys (hashed on identity) *unless* they implement a
> __hash__ method that raises a type error.
>
> Shouldn't t
I'm not sure about the first but as for the __reversed__ we had a discussion
yesterday and it was indeed added in 2.4 (oddly, my 2.5 documentation has
this correct... )
--
Haikus are easy
Most make very little sense
Refrigerator
___
Python-Dev mailing li
Michele Simionato wrote:
Notice that I was discussing an hypothetical language. I was arguing
that in principle
one could write a different language from Python, with single inheritance only,
and not lose much expressivity. I am not advocating any change to
current Python.
Since this is a li
Hello all,
The documentation for __hash__ seems to be outdated. I'm happy to submit
a patch, so long as I am not misunderstanding something.
http://docs.python.org/dev/reference/datamodel.html#object.__hash__
The documentation states:
If a class does not define a __cmp__() or __eq__() method
At 05:50 PM 8/28/2008 +0200, Michele Simionato wrote:
On Aug 28, 5:30 pm, "Phillip J. Eby" <[EMAIL PROTECTED]> wrote:
> How is that making things easier for application programmers?
We have different definitions of "application programmer". For me a typical
application programmer is somebody who
Greg,
Do you have a real-life example of this where multiple
inheritance is actually used?
I have built a framework that I have called the "capability pattern"
which uses multiple inheritance in a way that might be unique (I'm not
familiar enough with other frameworks to know for sure).
T
On Aug 28, 5:30 pm, "Phillip J. Eby" <[EMAIL PROTECTED]> wrote:
> How is that making things easier for application programmers?
We have different definitions of "application programmer". For me a typical
application programmer is somebody who never fiddles with metaclasses,
which are the realm of
At 06:35 AM 8/28/2008 +0200, Michele Simionato wrote:
Multiple inheritance of metaclasses is perhaps
the strongest use case for multiple inheritance, but is it strong
enough? I mean, in real code how many times did I need that?
I would not mind make life harder for gurus and simpler for
applicati
2008/8/28 Antoine Pitrou <[EMAIL PROTECTED]>:
> By that metric, I fear that the only remaining buildbots would be the
> Linux/Windows x86/x64 ones. I'm not sure anyone here, for example, cares
> really
Note that I meant to "move from unstable to stable, starting from the
actual state", not to "d
Facundo Batista gmail.com> writes:
>
> Maybe a good requisite to move a buildbot from unstable to stable is
> to find a champion for it. I mean, something that can test on that
> platform and cares enough about it to, or fix the issue
> himself/herself, or find who broke it and bother the respons
2008/8/28 Barry Warsaw <[EMAIL PROTECTED]>:
> bots we should "trust" to judge the health of the trees. I don't think the
> current list needs to be set in stone, and in fact several of the "stable"
> bots have had simple svn or other non-tree related problems for a while.
Maybe a good requisite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 28, 2008, at 6:28 AM, Antoine Pitrou wrote:
What is the rationale behind the distinction between "stable" and
"unstable"
buildbots?
I ask that because the OpenBSD buildbot has failed compiling 3.0 for
quite some
time, but since that build
Hello everyone,
What is the rationale behind the distinction between "stable" and "unstable"
buildbots?
I ask that because the OpenBSD buildbot has failed compiling 3.0 for quite some
time, but since that buildbot was in the "unstable" bunch, it was not discovered
until someone filed a bug report
Guido van Rossum wrote:
> On Wed, Aug 27, 2008 at 6:21 PM, Steven D'Aprano <[EMAIL PROTECTED]> wrote:
>> On Thu, 28 Aug 2008 08:39:01 am Georg Brandl wrote:
>>> Fredrik Lundh schrieb:
(using 3.0a4)
>>> exec(open("file.py"))
Traceback (most recent call last):
File "
22 matches
Mail list logo
