Nevermind. I found my own error. I referenced the input values
instead of the class object self. That is what I get for staring at
the code too long.
Thanks:)
SA
--
http://mail.python.org/mailman/listinfo/python-list
I have taken into advice what was mentioned earlier, but I have run
into a snag in which I am getting the wrong output from my class.
> python matchlist.py ./test ./test/list.txt
output:
['list.txt', 'test1.txt', 'test2.txt']
set(['test1'])
['', '/', 't', 'e', 's', 't']
The first line of output c
Simon Forman wrote:
> 1) Don't use "dir", "file", and "list" as variable names, those are
> already python built in objects (the dir() function, list type, and
> file type, respectively.)
Thanks. My own stupidity on this one.
> 2) 'r' is the default for open(), omit it. "self.flist =
> open(
I am trying to compare a list of items to the list of files generated
by os.listdir. I am having trouble getting this to work and think I
may be going down the wrong path. Please let me know if hter is a
better way to do this. THis is what I have for my class so far:
import os, sys
class Match
I'm getting closer now.
I figured out that when I typed python in cmd.exe window it was trying
to run the cygwin version of python. I removed that link and cmd.exe
now finds the correct version.
Therefore, this is not a bug. However, someone should add a caution in
the installation instructions
The python 2.4 version msi did no better. Please help. I do not
really want to go back to Active State Python.
Thanks:)
SA
Bucco wrote:
> I
> am going to try to install python 2.4 with the msi installer and see if
> I have the same issue with that version. If anyone else has
I installed python 2.5b3 on my windows XP sp2 box without any issues.
I can double click the python program, and idle comes up in the command
line window. However when I run python from the command line program
cmd.exe, I get a pop-up window with the following error:
16 bit Windows Subsystem
