File Creation Not Working In A Thread Class?

bc90021 <py****@bc90021 .netwrote:

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'

So which was it? At the top of the thread you said it was:

IOError: [Errno 2] no such file u'fileName'

How about posting the exact error message you got, including all of the
traceback and the complete original code: even when you posted "Here's the
thread class" you actually posted a modified version of your thread class
(with sarky comments added even if nothing else was changed).

If you post complete code and the full traceback then you'll probably get a
quick and accurate response telling you what the problem is. If you
continue to paraphrase and post bits and pieces you'll continue to get
random guesses.

bc90021 wrote:

You are a perfect example of exactly what I was talking about, and why
the Python community is such a poor one.

I though you were treated quite fairly all things considered. (You
started the personal attacks, the whining about the group, the
accusations of arrogance, and the refusal to believe we all *knew* the
error was in your file name calculation and not in Python threads.)

This group is widely acknowledged as one of the more friendly groups
around, and in fact we keep it that way by coming down rather hard on
those who abuse either the members of the group or the purpose of the
group. And you've done both and been reprimanded for it. Now, either
go away, or change your attitude and join the group. (You would be
welcome if the attitude changed.) Either way, this group will be it's
usual friendly self.
Gary Herron

>
Gary Herron wrote:

>bc90021 wrote:

>>>...and the exact error message was?

Here is a tip: if you want people to help you, then you have to help
them to help you. Personally, I wouldn't respond to anymore of your
questions because you seem incapable of posting the information
that was
requested.
So far, the people who have answered this post have gone on the
assumption that I'm stupid. I'm not. I took perfectly working
code, cut it from one class, and put it in another. It stopped
working in the second class. I've spent days on this and trust me,
given what I've experienced of the Python community so far, if I
didn't have to ask, I wouldn't.

(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.)

Sorry, the arrogance is yours.
Expecting us to help with only partial information.

Expecting us to help when your posts of the error message changes
from one post to the next.

Expecting us to help when you refuse to post the traceback.

Expecting us to believe that it has anything to do with threads.
(No one believes that for a moment.)
While acknowledging that any piece of code may have bugs, Python's
threading included, the problem here looks to be some simple mistake
in the computation of the name of the file to be opened. Then I
look at the convoluted quoting surrounding your computation of the
file name, and my confidence in that as an explanation sky-rockets.
Then someone in another post has found an extra set of quotes
embedded in your filename you compute, and it's clear that we are on
the right track.

>>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'

--
http://mail.python.org/mailman/listinfo/python-list

On May 11, 5:50*pm, Gary Herron <gher...@island training.comwro te:

bc90021 wrote:

You are a perfect example of exactly what I was talking about, and why
the Python community is such a poor one.

I though you were treated quite fairly all things considered. * (You
started the personal attacks, the whining about the group, the
accusations of arrogance, and the refusal to believe we all *knew* the
error was in your file name calculation and not in Python threads.)

This group is widely acknowledged as one of the more friendly groups
around, *and in fact we keep it that way by coming down rather hard on
those who abuse either the members of the group or the purpose of the
group.

That is a blantant lie. This group has well known members that are
some of the biggest jackasses I've ever encountered on the internet.
I've never heard a peep out of anyone criticizing their behavior. If
I were their employer, and I read some of the stuff they posted, I
would fire them on the spot.

bc90021 <py****@bc90021 .netwrote:

On Sun, 11 May 2008 19:55:31 +0000, Duncan Booth wrote:

>7stud <bb**********@y ahoo.comwrote:

>>Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* tempfileName =
"\"proctemp\\ " Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* Â* +
self.matrix[c][0] + "_other.txt \""

It wouldn't exactly result in either of the error messages you
posted, but I expect the spurious quote marks round the filename will
be giving you problems.

Surely you want the filename to be something like
'proctemp\fred _other.txt' rather than '"proctemp\fred _other.txt"'
with the spurious double quotes?

Yup, that's what it was. I figured it out two seconds before this
post. However, it will be interesting to see how it handles files
with spaces in the name...

It will handle spaces just fine.

You need to try and understand the difference between passing arguments to
a program, where the shell will try to parse the command line into separate
arguments so spaces have to be escaped somehow, and calling a function
within a program where no such parsing takes place.