Pupeno a écrit :
(snip)
>
> and then I have another module called SensorSingleton that emulates the
> hard-to-code-on-python singleton (snip)
What do you mean "hard to code on python singleton" ?
--
http://mail.python.org/mailman/listinfo/python-list
Pupeno wrote:
> Hello,
> I am experiencing a weird behavior that is driving me crazy. I have module
> called Sensors containing, among other things:
>
> class Manager:
> def getStatus(self):
> print "getStatus(self=%s)" % self
> return {"a": "b", "c": "d"}
>
> and then I have a
Nevermind, it was fixed. Thanks.
Pupeno wrote:
> Hello,
> I am experiencing a weird behavior that is driving me crazy. I have module
> called Sensors containing, among other things:
>
> class Manager:
> def getStatus(self):
> print "getStatus(self=%s)" % self
> return {"a": "
Pupeno wrote:
> Hello,
> I am experiencing a weird behavior that is driving me crazy. I have module
> called Sensors containing, among other things:
>
> class Manager:
> def getStatus(self):
> print "getStatus(self=%s)" % self
> return {"a": "b", "c": "d"}
>
> and then I have an
In <[EMAIL PROTECTED]>, Pupeno wrote:
> - Shouldn't the manager be the same in the first print and the second, that
> is, the id is different, shouldn't it be the same ?
> - What happened with all the output of SensorSingleton.getStatus() ? there's
> no trace of it (but there's output of the metho
Hello,
I am experiencing a weird behavior that is driving me crazy. I have module
called Sensors containing, among other things:
class Manager:
def getStatus(self):
print "getStatus(self=%s)" % self
return {"a": "b", "c": "d"}
and then I have another module called SensorSingle
