Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Date: Sun, 08 Jul 2012 19:27:24 +0100
From: MRAB <python@mrabarnett.plus.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: python-list@python.org
Subject: Re: Discussion on some Code Issues
References: <a4f0e2a9-cc3b-4081-beb9-82f229e95ba1@googlegroups.com> <3c4e2ef9-bf7e-4fbc-bf12-6780fdc3e5d4@googlegroups.com> <mailman.1901.1341694286.4697.python-list@python.org> <09adb3cf-f3f2-4acc-b561-a36dcf15ecc7@googlegroups.com> <mailman.1910.1341734607.4697.python-list@python.org> <11832de7-a064-494e-b3e8-32a2f15a6902@googlegroups.com> <CAPTjJmrgE43Zt6v0JxZ-=xG4ijYzRA=FmhwxED=X=hQNaFnMrw@mail.gmail.com>
In-Reply-To: <CAPTjJmrgE43Zt6v0JxZ-=xG4ijYzRA=FmhwxED=X=hQNaFnMrw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: list
Reply-To: python-list@python.org
Newsgroups: comp.lang.python
Message-ID: <mailman.1923.1341772228.4697.python-list@python.org>
Lines: 42
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:25049

On 08/07/2012 18:17, Chris Angelico wrote:
> On Mon, Jul 9, 2012 at 3:05 AM,  <subhabangalore@gmail.com> wrote:
>> On Sunday, July 8, 2012 1:33:25 PM UTC+5:30, Chris Angelico wrote:
>>> On Sun, Jul 8, 2012 at 3:42 PM,  <subhabangalore@gmail.com> wrote:
>>> > file_open=open("/python32/doc1.txt","r")
>>> Also, as has already been mentioned: keeping your data files in the
>>> Python binaries directory isn't usually a good idea. More common to
>>> keep them in the same directory as your script, which would mean that
>>> you don't need a path on it at all.
>> No file path! Amazing. I do not know I like to know one small example please.
>
> open("doc1.txt","r")
>
> Python will look for a file called doc1.txt in the directory you run
> the script from (which is often going to be the same directory as your
> .py program).
>
>> Btw, some earlier post said, line.split() to convert line into bag of words can
>> be done with power(), but I did not find it, if any one can help. I do close
 >> files do not worry. New style I'd try.
>
> I don't know what power() function you're talking about, and can't
> find it in the previous posts; the nearest I can find is a post from
> Ranting Rick which says a lot of guff that you can ignore. (Rick is a
> professional troll. Occasionally he says something useful and
> courteous; more often it's one or the other, or neither.)
>
I believe the relevant quote is """especially the Python gods have
given you *power* over string objects""". If that's the case, he's not
referring to a method or a function called "power".

He did give the good warning about the problem there could be if the
original string contains "$", the character being used as the separator.

> As to the closing of files: There are a few narrow issues that make it
> worth using the 'with' statement, such as exceptions; mostly, it's
> just a good habit to get into. If you ignore it, your file will
> *usually* be closed fairly soon after you stop referencing it, but
> there's no guarantee. (Someone else will doubtless correct me if I'm
> wrong, but I'm pretty sure Python guarantees to properly flush and
> close on exit, but not necessarily before.)
>