kosh wrote:
> Nah it is daily humor. Just think of it like a joke list. :)
Or a daily puzzler: how many blatantly stupid things can you find in 5
mins?
--
http://mail.python.org/mailman/listinfo/python-list
On Wednesday 26 January 2005 7:13 pm, Tad McClellan wrote:
> [ Followup set ]
>
> Dan Perl <[EMAIL PROTECTED]> wrote:
> > I can't imagine why or how, but there are
> > actually 26 members in the perl-python Yahoo! group who have registered
> > to get these bogus lessons sent to them daily!
>
> Ther
[ Followup set ]
Dan Perl <[EMAIL PROTECTED]> wrote:
> I can't imagine why or how, but there are
> actually 26 members in the perl-python Yahoo! group who have registered to
> get these bogus lessons sent to them daily!
There is one born every minute.
--
Tad McClellan
[EMAIL PROTECTED] wrote:
Xah Lee wrote:
close(F1) or die "Perl fucked up. Reason: $!";
close(F2) or die "Perl fucked up. Reason: $!";
Same here. Never seen Perl fuck up on closing a file. Usually
something in the OS or file system that does it.
In this case, I'm pretty sure it's the user.
--Ala
<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I guess there is no way to check if the file opened fine? What if the
> filesystem or file is locked for this user/session. Pretty puny
> language if it cannot tell you that it cannot do what you tell it to.
> ..
> Same for t
Xah Lee wrote:
> © # -*- coding: utf-8 -*-
> © # Python
> ©
> © import sys
> ©
> © nn = len(sys.argv)
> ©
> © if not nn==5:
> © print "error: %s search_text replace_text in_file out_file" %
> sys.argv[0]
> © else:
> © stext = sys.argv[1]
> © rtext = sys.argv[2]
> © input = open(sys.