Brian van den Broek <[EMAIL PROTECTED]> writes:
> It turns out that I was using '''triple single quotes''' and pydoc
> only pulls a description out from module docstrings that are formatted
> in """triple double quotes""". I've poked about with google, and
> cannot find any explanation of why pydo
Edward Diener <[EMAIL PROTECTED]> writes:
> It is a pity the Python Linux binary installations do not
> create folders on the desktop or in the Gnome menu system with links
> to the Python to the documentation and a readme telling me what
> executables were installed.
Imagine they did, and the ot
Tom Carrick <[EMAIL PROTECTED]> writes:
> In my attempted learning of python, I've decided to recode an old
> anagram solving program I made in C++. The C++ version runs in less
> than a second, while the python takes 30 seconds.
Indeed, your program can be improved to run about ten times as fast
[EMAIL PROTECTED] writes:
> I would love to have a record of all what I've done, so I can edit
> this record into final script.
You can save the current input history with
>>> import readline
>>> readline.write_history_file("python.log")
If you want to log your whole session, including output,
Steven Bethard <[EMAIL PROTECTED]> writes:
> I get the correct output, but if you run this yourself, you'll see
> that the numbers 1 through 10 aren't printed in sync with the writes
> (i.e. every half second); they're all printed at the end. Could
> someone explain to me why this happens, and ho
Hello
I've found out about a fundamental problem of attribute lookup, the
hard way.
asyncore.py uses the following code:
class dispatcher:
# ...
def __getattr__(self, attr):
return getattr(self.socket, attr)
Now suppose that I'm asking for some attribute not provided by
dispatch
