[SciPy-dev] weave -- inline C/C++ in Python, an implementation
eric at scipy.org
Sat Jan 5 21:56:46 CST 2002
Pearu and Fernando,
I prefer Unix line endings also. I messed around with fixing this, and only
found one file with line ending problems (ast_tools.py). The others looked
fine to me when I checked them out of CVS and looked at them on a Sun
Wait. Are yall having problems with the CVS version of the files or the tar
balls? The tar balls are made on a Windows machine and that is probably
that is the problem. CVS must do the line conversion automatically on my
Windows machine and convert the Unix line endings in CVS to Windows line
endings when they are check out. Then, the tar balls created have the wrong
line endings also. bummer. I'll try and figure out an automated fix for
this. For now, they'll still be DOS endings in the tar ball. Like Pearu
said though, this shouldn't be a problem, it's just annoying.
----- Original Message -----
From: "Pearu Peterson" <pearu at cens.ioc.ee>
To: <scipy-dev at scipy.org>
Sent: Saturday, January 05, 2002 3:53 AM
Subject: Re: [SciPy-dev] weave -- inline C/C++ in Python, an implementation
> On Sat, 5 Jan 2002, Fernando Pérez wrote:
> > Any ideas? One thing I noticed, and I don't know if it may cause
> > your files have DOS line endings (\r\n). In emacs these show up as ugly
> > characters at the end of every line, but I don't know if they can
> > python. If nothing else, do you know if there's a way to have distutils
> > up the line endings for each platform?
> I had similar problem with DOS line endings, in particular with executing
> setup.py script from a command line:
> ./setup.py ....
> that failed with strange messages (not reletated to python) until I
> changed the line endings with the `flip -u *` command.
> However, in my debian box I don't experience the problems that you do, so
> the DOS line endings should not be the problem for linux python.
> Scipy-dev mailing list
> Scipy-dev at scipy.net
More information about the Scipy-dev