On Wed, Jul 02, 2014 at 04:03:49PM -0500, Jeff Epler wrote:
> +f = open(filename, "u").read()
Maybe it has to be "U". http://legacy.python.org/dev/peps/pep-0278/
--
Open source business process management suite built
On Wed, Jul 02, 2014 at 09:14:17PM +0100, andy pugh wrote:
> Could comp pre-process the file to fix the line endings?
Personally, I am spiteful and would rather just delete all a user's
files when it's been discovered that he came within ten meters of a
Windows computer.
def parse(filename):
dos2unix
does it.
On 2014-07-02 22:14, andy pugh wrote:
> On 2 July 2014 21:07, Jeff Epler wrote:
>
>> Failure here usually mean you have a damaged file with dos line endings.
>> Only unix line-endings are acceptable to comp.
> Could comp pre-process the file to fix the line endings?
>
--
"In
On 2 July 2014 21:07, Jeff Epler wrote:
> Failure here usually mean you have a damaged file with dos line endings.
> Only unix line-endings are acceptable to comp.
Could comp pre-process the file to fix the line endings?
--
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manif
On Wed, Jul 02, 2014 at 12:24:30PM -0500, Jon Elson wrote:
>File "/usr/bin/comp", line 411, in parse
> a, b = f.split("\n;;\n", 1)
> ValueError: need more than 1 value to unpack
Failure here usually mean you have a damaged file with dos line endings.
Only unix line-endings are acceptable
Hello, all,
I have a customer who is trying to compile a custom hal
component
that I wrote. I sent him one about a month ago and he
compiled it
and it worked as I wrote it. But, it needed some changes, so I
edited it, tested it here and sent him the new .comp file, and
he gets errors when comp
