Greg Ewing <[EMAIL PROTECTED]> writes:
> I don't know about oct(), but I found hex() to be quite useful
> the other day when I was using the interactive interpreter to
> to some hex calculations. It would have been quite tedious
> having to say "%x".format(_) or some such all the time to
> see the
Oleg Broytmann <[EMAIL PROTECTED]> writes:
> On Fri, Nov 30, 2007 at 11:22:03AM +1300, Greg Ewing wrote:
>> The next step up from global would be __galactic__.
>
>Let me skip __universe[al]__ and go directly to The Ultimate
>Questions:
So maybe it should be called __42__?
Bernhard
"Gustavo Carneiro" <[EMAIL PROTECTED]> writes:
> Now the problem. Suppose you have the source package python-foo-bar,
> which installs $pythondir/foo/__init__.py and $pythondir/foo/bar.py. This
> would make a module called "foo.bar" available. Likewise, you can have the
> source package pytho
"Guido van Rossum" <[EMAIL PROTECTED]> writes:
> If the __getattr__()-like operation that supplies and inserts a
> dynamic default was a separate method, we wouldn't have this problem.
Why implement it in the dictionary type at all? If, for intance, the
default value functionality were provided
"Travis E. Oliphant" <[EMAIL PROTECTED]> writes:
> 2) The __index__ special method will have the signature
>
>def __index__(self):
>return obj
>
>Where obj must be either an int or a long or another object
>that has the __index__ special method (but
Nick Coghlan <[EMAIL PROTECTED]> writes:
> holger krekel wrote:
>> Moreover, i think that there are more than the "transactional"
>> use cases mentioned in the PEP. For example, a handler may want to
>> log exceptions to some tracing utility or it may want to swallow
>> certain exceptions when
>>
