rs or non-ascii chars in that
> gives errors
> from expat when the contents is parsed.
> I had to use a different encryption algorithm. I am going to do some tests on
> it
> now.
Put the cyphertext in a CDATA section, so the parser knows to ignore
its contents:
the details.
> (Hey, look, an Elf! *grin*)
HA!
> Hope this helps!
Tremendously. Thanks, Danny!
--
Regards,
Travis Spencer
___
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
.org/lib/module-os.html
* http://docs.python.org/lib/module-os.path.html
stat and shutil might be useful too.
HTH.
--
Regards,
Travis Spencer
___
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
1"
sam
Its a really common algorithm. Google for "change of base algorithm"
and you'll probably find lots of explinations.
HTH.
--
Regards,
Travis Spencer
___
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
ot;, 2)
> 6
> >>> int("111", 2)
> 7
Oh, that's nice. I guess my solution was the total C hacker's way;
not very pythonic :-) Thanks for the info.
--
Regards,
Travis Spencer
___
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
, will be very thankful.
--
Regards,
Travis Spencer
___
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
11\\x22\\x33\\x44\\x55'
> The list elements are still strings, you need to convert them to
> integers.
Why is this needed, Kent? Why not just leave them as strings?
> The strings are in hexadecimal so use the optional base
> parameter to int():
> >>> int(
On 2/27/06, Kent Johnson <[EMAIL PROTECTED]> wrote:
> This is not what Sudarshana asked for - '\\x00' and '\x00' are not the
> same string
Thanks for clearning that up for me, Kent.
--
Regards,
Travis Spencer
___
Tut
