Read and respond to this message at:
I am afraid that we might already be having problems, and that the "test" has
I'm the only person on the team trying out the PyDev plug-in. Everyone else
is using Eclipse without a (Python) plug-in (thus, they edit in Eclipse, but
run tests at the command line).
Very definitely, if I explicitly set the file encoding to Latin-1, the accented
characters is my source code file show up OK (and the same) in both my local
version and the remote version. But I can't run the test in the Eclipse
If I allow Eclipse to update the file encoding to UTF-8, the accented characters
in my local copy show up OK, but the remote version shows garbage, and the compare
shows me the characters have changed between the two versions. But I can run
the test in the Eclipse environment (since my local copy is OK).
Since the Eclipse/CVS code delta tool is definitely seeing a difference between
the files when my settings say it is UTF-8, I guess that there's a difference.
So, I guess that if I submit my update these new differences will also be submitted,
and everyone else on the team (not using the PyDev plug-in, and editing the
file as though it is Latin-1) will start to see differences.
I hate to lose the interactive debugging feature for Python scripts (this is
what I really wanted!), but I'm not sure I can submit these deltas.
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: