Can't Encode Pic

[Rami Chowdhury]

On Fri, Nov 27, 2009 at 02:59, Victor Subervi <victorsubervi at gmail.com> wrote:
> On Thu, Nov 26, 2009 at 5:08 PM, Dennis Lee Bieber <wlfraed at ix.netcom.com>
> wrote:
>> Nothing hinting at having
>> opened an interactive Python console and typing statements into it as an
>> experiment to see what may work, or what changes may break something.
>
> Please explain how this makes a difference. If I have the error in hand from
> trying to run the code through the Web--either printed to screen or gathered
> from the errors log--what need of opening the python interpreter

If you are content to run your code through the Web, and iterate
through versions of it there, then that's up to you. I'd suggest using
the interactive interpreter when you can, though -- most Python
programmers that I have encountered find it extremely helpful. In
particular, it can be invaluable in examining short snippets of code
-- such as the segments that are giving you trouble -- without
rerunning the whole program.

When I am debugging errors such as this, what I typically do is snip
out the particular bit that is causing the problem and run it in the
interactive interpreter, experimenting with changes to it until it
works as I want it to. Perhaps such a method would help you in
debugging as well? Certainly it would enable you to give the list a
little more information about what you have and haven't tried when
coming here with a problem...