I could not find another example of this via internet searches, so here
it is... I am wondering if this is a python bug or otherwise. The
first example of this happened in a larger program of mine, and the
traceback reports the problem at the start of a "for" loop (making no
sense), but I cannot
Yep, my thinking too. Well, maybe it's all related to the same bug
somehow. OK, I submitted a bug report, and I included a slight
modification of the test case you guys suggested:
import sys
import os
t = 2147483648L
os.utime("foo_test_file", (t, t))
print "hi"
---
I've been doing a lot of searching on the topic of one of Python's more
disturbing issues (at least to me): the fact that if a __del__ finalizer
is defined and a cyclic (circular) reference is made, the garbage
collector cannot clean it up.
First of all, it seems that it's best to avoid using __de
On 2006-12-02, Ara Kooser wrote:
> I am working on a text adventure game for python to get back
> into python programming. My version 0.1 used only functions so
> I could get familiar with how those work. I want to move beyond
> that. I am not sure what would be a good Python way of handling
> thi
