Re: Understand workflow about reading and writing files in Python

On 25/06/19 11:50 AM, Windson Yang wrote: DL Neil > 于2019年6月24日周一 上午11:18写道： Yes, better to reply to list - others may 'jump in'... On 20/06/19 5:37 PM, Windson Yang wrote: > Thank you so much for you review DL Neil, it really helps :D. Howe

Re: Understand workflow about reading and writing files in Python

DL Neil 于2019年6月24日周一 上午11:18写道： > Yes, better to reply to list - others may 'jump in'... > > > On 20/06/19 5:37 PM, Windson Yang wrote: > > Thank you so much for you review DL Neil, it really helps :D. However, > > there are some parts still confused me, I replyed as below. > > It's not a partic

Re: Understand workflow about reading and writing files in Python

When you said "C-runtime buffered I/O", are you talking about Standard I/O in C (FILE * object)? AFAIN, In CPython, we didn't use Standard I/O, right? Dennis Lee Bieber 于2019年6月25日周二 上午12:48写道： > On Mon, 24 Jun 2019 15:18:26 +1200, DL Neil > declaimed the following: > > > > > >However, the OpSy

Re: Understand workflow about reading and writing files in Python

Yes, better to reply to list - others may 'jump in'... On 20/06/19 5:37 PM, Windson Yang wrote: Thank you so much for you review DL Neil, it really helps :D. However, there are some parts still confused me, I replyed as below. It's not a particularly easy topic... DL Neil

Fwd: Understand workflow about reading and writing files in Python

Thank you so much for you review DL Neil, it really helps :D. However, there are some parts still confused me, I replyed as below. DL Neil 于2019年6月19日周三 下午2:03写道： > I've not gone 'back' to refer to any ComSc theory on buffer-management. > Perhaps you might benefit from such? > > I just take a cr

Re: Understand workflow about reading and writing files in Python

I've not gone 'back' to refer to any ComSc theory on buffer-management. Perhaps you might benefit from such? I like your use of the word "shift", so I'll continue to use it. There are three separate units of data to consider - each of which could be called a "buffer". To avoid confusing (mysel

Understand workflow about reading and writing files in Python

I'm trying to understand the workflow of how Python read/writes data with buffer. I will be appreciated if someone can review it. ### Read n data 1. If the data already in the buffer, return data 2. If the data not in the buffer: 1. copy all the current data from the buffer 2. create a new

Re: Understand workflow about reading and writing files in Python

On 6/15/2019 12:52 AM, Windson Yang wrote: I'm trying to understand the workflow of how python read/writes files with buffer. I drew a diagram for it. I will be appreciated if someone can review the diagram :D [image: 屏幕快照 2019-06-15 下午12.50.57.png] Text only list, no attachments. -- Terry Ja

Understand workflow about reading and writing files in Python

I'm trying to understand the workflow of how python read/writes files with buffer. I drew a diagram for it. I will be appreciated if someone can review the diagram :D [image: 屏幕快照 2019-06-15 下午12.50.57.png] -- https://mail.python.org/mailman/listinfo/python-list

Writing files at run time

Dear Group, In my previous post["https://groups.google.com/forum/#!topic/comp.lang.python/ZYjsskV5MgE";] I was trying to discuss some issue on file writing. I got an associated issue. I am trying to crawl a link, through urllib and trying to store its results in different files. As discusse

Re: reading and writing files

On Tue, Aug 23, 2011 at 11:29 PM, Muresan Alexandru Mihai wrote: > If you need an int isn't better to use input() instead of raw_input() ? Absolutely not! input() does an eval(), which is very dangerous security-wise and can also lead to rather strange behavior. input() is so bad that it was remo

Re: reading and writing files

If you need an int isn't better to use input() instead of raw_input() ? On Tue, Aug 23, 2011 at 10:00 PM, Adrián Monkas wrote: > Hi. > I`ve been trying to copy a long text from one file to another but it always > copied me just a small part. > I would be glad if you can help me or explain which i

Re: reading and writing files

On Tue, Aug 23, 2011 at 9:05 PM, Dave Angel wrote: > On 01/-10/-28163 02:59 PM, Adrián Monkas wrote: >>             print "Abro Archivo Origen" >>             archivo=open("D:\Boot.txt","r") > Your filenames are incorrect, since you use the backslash without escaping > it.  So the source file ha

Re: reading and writing files

On 01/-10/-28163 02:59 PM, Adrián Monkas wrote: Hi. I`ve been trying to copy a long text from one file to another but it always copied me just a small part. I would be glad if you can help me or explain which is my error. Thanks ---

reading and writing files

Hi. I`ve been trying to copy a long text from one file to another but it always copied me just a small part. I would be glad if you can help me or explain which is my error. Thanks -- def runMenu(): print "\nMENU"

Re: Reading/Writing files

On Fri, Mar 25, 2011 at 6:42 AM, Westley Martínez wrote: > > > > I argue that the first is quite a bit more readable than the second: > > > 'c:/temp/choose_python.pdf' > > > os.path.join([ 'c:', 'temp', 'choose_python.pdf' ]) > > > > I agree with your argument, but think that > > r'c:\tem

Re: Reading/Writing files

On Fri, 2011-03-25 at 05:39 -0700, Ethan Furman wrote: > On 3/18/2011 6:25 PM, Dan Stromberg wrote: > > > > On Fri, Mar 18, 2011 at 4:00 PM, Ethan Furman > > wrote: > > > > Dan Stromberg wrote: > > > > > > Are you on windows? > > > > You probably shou

Re: Reading/Writing files

On 3/18/2011 6:25 PM, Dan Stromberg wrote: On Fri, Mar 18, 2011 at 4:00 PM, Ethan Furman mailto:et...@stoneleaf.us>> wrote: Dan Stromberg wrote: Are you on windows? You probably should use / as your directory separator in Python, not \. In Python, and most other

Re: Reading/Writing files

On Sat, Mar 19, 2011 at 12:55 AM, Nobody wrote: > On Fri, 18 Mar 2011 16:00:55 -0700, Ethan Furman wrote: > > Dan Stromberg wrote: > > > / works fine on windows, and doesn't require escaping ("/foo/bar"). > > "/" works fine in most contexts, but not in shell commands, where "/" is > conventionall

Re: Reading/Writing files

On Fri, 18 Mar 2011 16:00:55 -0700, Ethan Furman wrote: Dan Stromberg wrote: > / works fine on windows, and doesn't require escaping ("/foo/bar"). "/" works fine in most contexts, but not in shell commands, where "/" is conventionally used to indicate a switch. Commands which follow this convent

Re: Reading/Writing files

On Fri, Mar 18, 2011 at 4:00 PM, Ethan Furman wrote: > Dan Stromberg wrote: > >> >> Are you on windows? >> >> You probably should use / as your directory separator in Python, not \. >> In Python, and most other programming languages, \ starts an escape >> sequence, so to introduce a literal \, y

Re: Reading/Writing files

wrote: > >> Folks, >> >> thanks for the many responses! Specifying the full file name (and not >> using parentheses when inappropriate, thanks Jack :)) I am now happily >> reading/writing files. >> >> My next question: what is the best way for me to write an

Re: Reading/Writing files

On Fri, 2011-03-18 at 15:18 -0700, Dan Stromberg wrote: > > Are you on windows? > > You shouldn't use / or \ on Windows. You should use os.path.join(). On Windows, when you start mixing / with \\ and spaces things can get hairy and obscure. It's always best to just use os.path.join(). -

Re: Reading/Writing files

Dan Stromberg wrote: Are you on windows? You probably should use / as your directory separator in Python, not \. In Python, and most other programming languages, \ starts an escape sequence, so to introduce a literal \, you either need to prefix your string with r (r"\foo\bar") or double yo

Re: Reading/Writing files

On Fri, 2011-03-18 at 15:56 -0600, Jon Herman wrote: > Jack, > > thanks. > > Alright, so what I did is create a file called hello.txt with a single > line of text in there. I then did the following: > > f="fulldirectory\hello.txt" (where fulldirectory is of course the > actual full directory on

Re: Reading/Writing files

On Fri, Mar 18, 2011 at 5:21 PM, Jon Herman wrote: > Folks, > > thanks for the many responses! Specifying the full file name (and not using > parentheses when inappropriate, thanks Jack :)) I am now happily > reading/writing files. > > My next question: what is the best w

Re: Reading/Writing files

Folks, thanks for the many responses! Specifying the full file name (and not using parentheses when inappropriate, thanks Jack :)) I am now happily reading/writing files. My next question: what is the best way for me to write an array I generated to a file? And what is the best way for me to

Re: Reading/Writing files

On 18.03.2011 22:33, Jon Herman wrote: Hello all, I am pretty new to Python and am trying to write data to a file. However, I seem to be misunderstanding how to do so. For starters, I'm not even sure where Python is looking for these files or storing them. The directories I have added to my PYTH

Re: Reading/Writing files

Are you on windows? You probably should use / as your directory separator in Python, not \. In Python, and most other programming languages, \ starts an escape sequence, so to introduce a literal \, you either need to prefix your string with r (r"\foo\bar") or double your backslashes ("\\foo\\bar

Re: Reading/Writing files

On Fri, Mar 18, 2011 at 4:59 PM, Jack Trades wrote: > > > On Fri, Mar 18, 2011 at 4:56 PM, Jon Herman wrote: > >> Jack, >> >> thanks. >> >> Alright, so what I did is create a file called hello.txt with a single >> line of text in there. I then did the following: >> >> f="fulldirectory\hello.txt"

Re: Reading/Writing files

For open() or os.open(), it should look in your Current Working Directory (CWD). Your python's CWD defaults to what the CWD was when python was started, and it is changed with os.chdir(). Absolute paths will of course be relative to / on most OS's (or C:/ if you're on C:, D:/ if you're on D:, etc

Re: Reading/Writing files

On Fri, Mar 18, 2011 at 4:56 PM, Jon Herman wrote: > Jack, > > thanks. > > Alright, so what I did is create a file called hello.txt with a single line > of text in there. I then did the following: > > f="fulldirectory\hello.txt" (where fulldirectory is of course the actual > full directory on my

Re: Reading/Writing files

Jack, thanks. Alright, so what I did is create a file called hello.txt with a single line of text in there. I then did the following: f="fulldirectory\hello.txt" (where fulldirectory is of course the actual full directory on my computer) open("f", "w") And I get the following error: IOError: [E

Re: Reading/Writing files

Jon Herman wrote: Hello all, I am pretty new to Python and am trying to write data to a file. However, I seem to be misunderstanding how to do so. For starters, I'm not even sure where Python is looking for these files or storing them. The directories I have added to my PYTHONPATH variable (w

Re: Reading/Writing files

On Fri, Mar 18, 2011 at 4:33 PM, Jon Herman wrote: > Hello all, > > I am pretty new to Python and am trying to write data to a file. However, I > seem to be misunderstanding how to do so. For starters, I'm not even sure > where Python is looking for these files or storing them. The directories I

Re: Reading/Writing files

On 18/03/2011 5:33 PM, Jon Herman wrote: I am pretty new to Python and am trying to write data to a file. However, I seem to be misunderstanding how to do so. For starters, I'm not even sure where Python is looking for these files or storing them. The directories I have added to my PYTHONPATH var

Reading/Writing files

Hello all, I am pretty new to Python and am trying to write data to a file. However, I seem to be misunderstanding how to do so. For starters, I'm not even sure where Python is looking for these files or storing them. The directories I have added to my PYTHONPATH variable (where I import modules f

Re: Reading, writing files

seanm wrote: In the book I am using, they give the following function as an example: def copyFile(oldFile, newFile): f1 = open(oldFile, 'r') f2 = open(newFile, 'w') while True: text = f1.read(50) This will read up to 50 characters from the input file. At the end of the file

Re: Reading, writing files

On Fri, 2009-08-21 at 15:21 -0700, seanm wrote: > In the book I am using, they give the following function as an > example: > > def copyFile(oldFile, newFile): > f1 = open(oldFile, 'r') > f2 = open(newFile, 'w') > while True: > text = f1.read(50) > if text == "": >

Reading, writing files

In the book I am using, they give the following function as an example: def copyFile(oldFile, newFile): f1 = open(oldFile, 'r') f2 = open(newFile, 'w') while True: text = f1.read(50) if text == "": break f2.write(text) f1.close() f2.close()

Re: reading/writing files

On Nov 27, 7:14 am, sandipm <[EMAIL PROTECTED]> wrote: > f1= open("file1.pdf", "rb") > x = f1.read() > open("file2.pdf", "wb").write(x) > > works... > > thanks > sandip You might also like: http://pybrary.net/pyPdf/ -- http://mail.python.org/mailman/listinfo/python-list

Re: reading/writing files

f1= open("file1.pdf", "rb") x = f1.read() open("file2.pdf", "wb").write(x) works... thanks sandip On Nov 27, 5:43 pm, sandipm <[EMAIL PROTECTED]> wrote: > Hi, > > I am trying to read a file and write into other file. if I do it for > simple text file, it works well. > but for pdfs or some ot

reading/writing files

Hi, I am trying to read a file and write into other file. if I do it for simple text file, it works well. but for pdfs or some other mime types, its failing. actually main problem is i am uploading file using cgi, in this process I am getting content of file, and I am trying to save the file. I

Re: remove header line when reading/writing files

On Thu, 11 Oct 2007 22:52:55 +, RyanL wrote: > I'm a newbie with a large number of data files in multiple > directories. I want to uncompress, read, and copy the contents of > each file into one master data file. The code below seems to be doing > this perfectly. The problem is each of the

Re: remove header line when reading/writing files

[EMAIL PROTECTED] wrote: > ... > for zipfile in filelist: > zfiter = iter(gzip.Gzipfile(zipfile,'r')) > zfiter.next() # ignore header line > for i, line in enumerate(fziter): > outfile.write(line) Or even: writes = outfile.write for zipfile in filelist: zfiter = it

Re: remove header line when reading/writing files

On Oct 12, 12:23 pm, Tim Chase <[EMAIL PROTECTED]> wrote: > Forgot the enumerate call of all things > > > for zipfile in filelist: > >for i, line in enumerate(gzip.Gzipfile(zipfile,'r')): > >if i: outfile.write(line) > > Some days, I'm braindead. > > -tkc I would move the 'if' test

Re: remove header line when reading/writing files

Forgot the enumerate call of all things > for zipfile in filelist: > for i, line in enumerate(gzip.Gzipfile(zipfile,'r')): > if i: outfile.write(line) Some days, I'm braindead. -tkc -- http://mail.python.org/mailman/listinfo/python-list

Re: remove header line when reading/writing files

> each file into one master data file. The code below seems to be doing > this perfectly. The problem is each of the data files has a header > row in the first line, which I do not want in the master file. How > can I skip that first line when writing to the master file? Any help > is much appr

remove header line when reading/writing files

I'm a newbie with a large number of data files in multiple directories. I want to uncompress, read, and copy the contents of each file into one master data file. The code below seems to be doing this perfectly. The problem is each of the data files has a header row in the first line, which I do

Re: Writing files

On 3/19/07, Adonis Vargas <[EMAIL PROTECTED]> wrote: > Actually, I re-ran this in a terminal and it worked perfectly. I was > using IDLE to write this code, kinda peculiar. Maybe something to do > with IDLE and CSV (or writing to files) with lines > ~1000. A socket > timing out maybe? It's because

Re: Writing files

[EMAIL PROTECTED] wrote: >> >> -- code -- >> >> def _scan(self): >> outFile = file("mp3.dat", "wb") >> outCSV = csv.writer(outFile) >> output = list() >> for root, dirs, files in os.walk(self.directory): >> files = [x for x in files if x.endswi

Re: Writing files

On Mar 19, 2:20 pm, Adonis Vargas <[EMAIL PROTECTED]> wrote: > I am writing a program that walks a directory full of mp3s reads their > ID3 data (using Mutagen), this part works perfectly. The problem is I > write these tags to a CSV file through the CSV module. But when I read > the file the file

Writing files

I am writing a program that walks a directory full of mp3s reads their ID3 data (using Mutagen), this part works perfectly. The problem is I write these tags to a CSV file through the CSV module. But when I read the file the file seems to be incomplete. Further inspecting it has seemed to have

Re: Python newbie with a problem writing files

On 4 Sep 2006 08:16:24 -0700, Jason <[EMAIL PROTECTED]> wrote: > limodou wrote: > > > Code: > > > > > > import feedparser > > > from xml.sax import saxutils > > > > > > feed_number=200 > > > > > > feed_list = open("feed_listing.conf","r") > > > for each_feed in feed_list: > > > data=feedparser.

Re: Python newbie with a problem writing files

> Code: > xml_output.write = (feed_title) How did you come up with that "=" there??! The correct line is: xml_output.write(feed_title) > Traceback (most recent call last): > File "C:/My_Blogroll/JJ_Blogroll2", line 11, in ? > xml_output.write = (feed_title) > AttributeError: '

Re: Python newbie with a problem writing files

limodou wrote: > > Code: > > > > import feedparser > > from xml.sax import saxutils > > > > feed_number=200 > > > > feed_list = open("feed_listing.conf","r") > > for each_feed in feed_list: > > data=feedparser.parse(each_feed) > > feed_title=data.entries[0].title > > xml_output=open("xm

Re: Python newbie with a problem writing files

Mike Kent wrote: > > feed_list = open("feed_listing.conf","r") > > What could it be about the above line that means "Open this file for > READ ONLY"? That's his *INPUT* file. The error referred to his *OUTPUT* file, and in any case the complain was that the "write" attribute was read-only, *NOT* t

Re: Python newbie with a problem writing files

>> feed_list = open("feed_listing.conf","r") > > What could it be about the above line that means "Open this file for > READ ONLY"? Oooh, oooh, I know! If you rot13 the file-name, it comes back as "srrq_yvfgvat.pbas". The double "r"s in the file-name instruct python to open the file as "reall

Re: Python newbie with a problem writing files

> feed_list = open("feed_listing.conf","r") What could it be about the above line that means "Open this file for READ ONLY"? -- http://mail.python.org/mailman/listinfo/python-list

Python newbie with a problem writing files

Doh!!! You are right. It was staring me in the face. I shouldn’t have that ‘=’ sign at all!! I removed it and it works!! Now I just have to put in a routine to remove non-ascii characters from the data before writing it and all will be golden.    Thanks JJ -- http://mail.pyth

Re: Python newbie with a problem writing files

On 9/4/06, John Jones <[EMAIL PROTECTED]> wrote: > Hi All, > > I have been driven insane by this error. I have this small program, shown > below, which runs great until it gets to writing the data out to the file. I > am running an install of Python 2.4. Yes, feedparser is functioning fine (I

Python newbie with a problem writing files

Hi All, I have been driven insane by this error. I have this small program, shown below, which runs great until it gets to writing the data out to the file. I am running an install of Python 2.4. Yes, feedparser is functioning fine (I put in print feed_title statements as tests - but have s

Re: Problem reading/writing files

[EMAIL PROTECTED] schreef: > Well, now I tried running the script and it worked fine with the .gfx > file. Originally I was working using the IDLE, which I wouldn't have > thought would make a difference, but when I ran the script on its own > it worked fine and when I ran it in the IDLE it didn't

Re: Problem reading/writing files

Well, now I tried running the script and it worked fine with the .gfx file. Originally I was working using the IDLE, which I wouldn't have thought would make a difference, but when I ran the script on its own it worked fine and when I ran it in the IDLE it didn't work unless the data was in a text

Re: Problem reading/writing files

[EMAIL PROTECTED] schreef: > f = open('evil2.gfx','rb') > i1 = open('img1.jpg','wb') > i2 = open('img2.png','wb') > i3 = open('img3.gif','wb') > i4 = open('img4.png','wb') > i5 = open('img5.jpg','wb') > > > for i in range(0,67575,5): > i1.write(f.read(1)) > i2.write(f.read(1)) > i3.wr

Re: Problem reading/writing files

Ok, now I'm very confused, even though I just solved my problem. I copied the entire contents of the original file (evil2.gfx) from my hex editor and pasted it into a text file. When I read from *this* file using my original code, everything worked fine. When I read the 21st byte, it came up as the

Re: Problem reading/writing files

> What platform? What version of Python? Have you opened the > file in binary mode i.e. open('thefile', 'rb') ?? Show us the relevant > parts of your code, plus what caused you to conclude that read() > changed data on the fly in an undocumented fashion. Yes, I've been reading and writing everyt

Re: Problem reading/writing files

[EMAIL PROTECTED] wrote: > This is a bit of a peculiar problem. First off, this relates to Python > Challenge #12, so if you are attempting those and have yet to finish > #12, as there are potential spoilers here. > > I have five different image files shuffled up in one big binary file. > In order

Re: Problem reading/writing files

[EMAIL PROTECTED] wrote: > This is a bit of a peculiar problem. First off, this relates to Python > Challenge #12, so if you are attempting those and have yet to finish > #12, as there are potential spoilers here. > > I have five different image files shuffled up in one big binary file. > In order

Re: Problem reading/writing files

have you been using text mode? [EMAIL PROTECTED] wrote: > This is a bit of a peculiar problem. First off, this relates to Python > Challenge #12, so if you are attempting those and have yet to finish > #12, as there are potential spoilers here. > > I have five different image files shuffled up in

Problem reading/writing files

This is a bit of a peculiar problem. First off, this relates to Python Challenge #12, so if you are attempting those and have yet to finish #12, as there are potential spoilers here. I have five different image files shuffled up in one big binary file. In order to view them I have to "unshuffle" t

Re: Writing files on server through CGI

this cgi script write different files, request 1 will write 1.html, 2 will write 2.html and so on. Its not updating the current file. For example create.py processes a form and write user.html file and every user is unique. so if 10 users fill up the form at the same time and click submit button, c

Re: Writing files on server through CGI

On Sun, Apr 09, 2006 at 12:35:21AM -0700, [EMAIL PROTECTED] wrote: > I have a CGI script on server which process a form and writes its > content on a file like > fp = open(fname, 'w') > fp.write('Cool > list%s%s > > Its working fine, but will it work if the script recieves thousands of > request s

Writing files on server through CGI

I have a CGI script on server which process a form and writes its content on a file like fp = open(fname, 'w') fp.write('Cool list%s%s Its working fine, but will it work if the script recieves thousands of request simultaneously. Can this script writes files simultaneusly or will all the request q