Remember what your mom taught you:
always flush()
(in python, sys.stdout.flush() followed by os.fsync())
Autopulated
2010-01-02 14:55:33
views:
135answers:
5
+6
A:
I updated with what you said before the close() and still nothing.
2010-01-02 15:12:35
see my second answer, your problem is actually with multiprocessing, and nothing to do with files :)
Autopulated
2010-01-02 15:35:13
A:
If you have opened the file with a file handle in Python, remember to close it when finished. eg
f=open("file")
....
f.write(....)
f.close()
ghostdog74
2010-01-02 14:57:21
A:
Obviously, you forget to close the file upon finishing working with it. If you want to check the contents of the file before closing it, call the flush() method. Example:
file = open("hello.txt", "a")
file.write(...)
file.flush() // force write on the disk
file.close() // finished using the file, close it
Check you code, not all open files are closed in it.
Alex
2010-01-02 15:01:43
Yeah. But see fileo = open(OutFile, 'a'), after which there is no close() call. This means, that on the last iteration the file won't be closed.
Alex
2010-01-02 15:18:40
I'm not speaking of unhandled exceptions which may be thrown if ProxyList file doesn't exist. In this case you'll just get an exception printed in the terminal and no files will be updated.
Alex
2010-01-02 15:19:54
+2
A:
Regarding the code: It looks like the actual problem is one relating to threads, not to files:
Whilst you are executing this code:
for t in list:
fileo.write(t + "\n")
list = []
fileo.close()
fileo = open(OutFile, 'a')
k = 0
list is being modified by the threads you have spawned. I don't know the details of how 'for x in y' works with threads, but I imagine it is missing out the elements added to the list after the body for loop has been executed the first time.
To solve this you need a mutex for list which you lock for the entirety of this for loop (until you have cleared the list), and which you lock whenever you are adding an item to the list.
Autopulated
2010-01-02 15:34:38