File Creation Not Working In A Thread Class?

[7stud]

On May 11, 2:11 pm, bc90021 <pyt... at bc90021.net> wrote:
> [CUT]
>
> > I have in no way assumed that you are stupid.  I have tried to help you
> > formulate your problem better so that people on the list can help you.
> > I believe I have done so respectfully, with the aim of introducing you
> > to the modus operandi of this group.
>
> I appreciate your help.  However, the comments I got from other people
> that "I'm sure you have quotes here..." type comments are incredibly
> insulting.  To tell someone that you're sure that they have quotes around
> something when they don't is the height of arrogance and rudeness.
>

The best way to get help is to post a simple example that demonstrates
your problem and that anyone can run and get the same error you are
getting.  That means you need take your real code and you start
hacking out the bits that are irrelevant to the problem.  With
judicious use of print statements you should be able to narrow the
problem down.

Your first post was about as far away from that as it could be.  Your
first post was essentially equivalent to asking:

> Why does this line:

>print name

>display "Jack" and not "Jill".

When you post a question like that, then you are either going to be
met with silence or people will attempt to debug your imaginary code
and guess at the problem, which sometimes works and sometimes
doesn't.  If you find the guesses insulting, then post a better model
of your problem.  The fact that you found these guesses insulting,
even though they were respectfully given and they were the obvious
answers in light of how little information you gave, means you are
probably going to have problems on any newsgroup you post to.

The python community has some real jerks in it, but you didn't meet
any of them in this thread.





> >> (I really must say that so far the help I am getting in the Python
> >> community is a big let down.  Whether it's on IRC or here, everyone has
> >> an arrogance that I don't find anywhere else in the open source
> >> community, and it seriously makes me question the choice of language
> >> that I've made.)
>
> > Don't judge too quickly.  I think this newsgroup is on the whole
> > extremely helpful.  I have learnt a lot from it.  But you have to get
> > used to its ways, and until you are familiar with them, approach it with
> > humility.
>
> Unfortunately, this is not my first interaction with the Python IRC
> communities or Python newsgroups.  I had tried working with this language
> a while back (around 2000) and the answers I got were unhelpful and
> usually rude.  I decided to give it another shot for the program I'm
> writing, and I'm regretting that.  It's possible that I'm to blame - I'm
> the common factor in both instances, but at the same time, when you ask a
> question in #python and NO ONE ANSWERS at all, and they all just sit
> there not talking at all, what's the point of having the IRC channel?  If
> newbies can't go there for help, what's the point?  When there are 70
> people in a channel, and no one even acknowledges your question has been
> asked, where does one go for help?  It's like talking to yourself.
>
> >> The error message was at the top of the thread (am I incapable of
> >> posting it, or are you incapable of following a thread?), but here it
> >> is again:
>
> >> IOError: [Errno 2] no such file u'tempfileName'
>
> > This is different from the error message that you posted in your
> > original message.
>
> > Anyway, what is useful to us is a full traceback, no just an error
> > message.
>
> It is not "different" except that I posted the full name the second
> time.  (tempfileName instead of the previously simplified fileName)  The
> code itself is actually irrelevant, in my humble opinion.  In one place a
> file creation line does not work; in the second place it does.  How can
> the same line of code do two different things in two places?  Either it
> creates a file or it doesn't.  It should create the file in either place,
> regardless of where it's being called.
>
> Either way, I figured it out.