[EMAIL PROTECTED] (Marco Colombo) writes:
> It seems python documentation is plain wrong, or I'm not able to
> read it at all:
>
> http://docs.python.org/ref/physical.html
>
> "A physical line ends in whatever the current platform's convention is for
> terminating lines. On Unix, this is the ASCII
Michael Fuhr wrote:
On Tue, Mar 15, 2005 at 10:46:09PM +, Paul Moore wrote:
The long and short of it is that I believe you just use \n to delimit
lines on Windows, just like anywhere else.
Many thanks -- your test results contain the info we've been seeking.
Thanks a lot Paul.
Micheal, you we
On Thursday 17 March 2005 23:17, Paul Moore wrote:
>
> Ironically, at the lowest level, Windows behaves just like Unix
> (files are pure byte streams) - it's only in the C runtime and
> application code that CRLF issues arise, and that's a
> backward-compatibility hack dating back to the days of M
[EMAIL PROTECTED] (Marco Colombo) writes:
> No I wasn't sure and I actually was wrong. I've never programmed under
> Windows. I've just learned something.
Indeed, the Windows C runtime translates CRLF to \n on input, and \n
to CRLF on output, for files in "text" mode. Unix programmers tend
not t
On Wed, 16 Mar 2005, Michael Fuhr wrote:
On Wed, Mar 16, 2005 at 04:17:51PM +0100, Marco Colombo wrote:
aprogram = "x = 1\nprint x\n";
printf(aprogram);
PyRun_SimpleString(aprogram);
See? THIS program requires compile-time or run-time checks. You
can't run it on Windows, or Mac:
On Wed, Mar 16, 2005 at 04:17:51PM +0100, Marco Colombo wrote:
>
> aprogram = "x = 1\nprint x\n";
> printf(aprogram);
> PyRun_SimpleString(aprogram);
>
> See? THIS program requires compile-time or run-time checks. You
> can't run it on Windows, or Mac: it'll write garbage to the
On Wed, 16 Mar 2005, Michael Fuhr wrote:
On Wed, Mar 16, 2005 at 01:46:23PM +0100, Marco Colombo wrote:
It seems python documentation is plain wrong, or I'm not able to
read it at all:
http://docs.python.org/ref/physical.html
"A physical line ends in whatever the current platform's convention is fo
On Wed, Mar 16, 2005 at 01:46:23PM +0100, Marco Colombo wrote:
>
> It seems python documentation is plain wrong, or I'm not able to
> read it at all:
>
> http://docs.python.org/ref/physical.html
>
> "A physical line ends in whatever the current platform's convention is for
> terminating lines. O
On Tue, Mar 15, 2005 at 10:46:09PM +, Paul Moore wrote:
> The long and short of it is that I believe you just use \n to delimit
> lines on Windows, just like anywhere else.
Many thanks -- your test results contain the info we've been seeking.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---
[EMAIL PROTECTED] (Michael Fuhr) writes:
> We (the thread participants) could use somebody with a Windows
> server to do some testing.
Glad to help... This is with postgresql 8.0.1, Python 2.4.
> Specifically, we're wondering if Python on Windows requires embedded
> Python code to have CRLF (\
On Tue, Mar 15, 2005 at 07:05:22PM +, Paul Moore wrote:
> As per my earlier posting, I actually found that building postgresql
> wasn't at all hard. Once I'd built with Python 2.4 support, I had a
> compatible plpython.dll I could just copy in.
Pardon the interruption, but do you have a Postg
[EMAIL PROTECTED] ("Magnus Hagander") writes:
>> I suppose my first (lazy) question is, is there a Python 2.4
>> compatible plpython.dll available anywhere? Alternatively, is
>> there a way I can build one for myself? I'm happy enough
>> doing my own build (I have mingw and msys available), but
> Hi,
> I'm just starting to look at Postgresql. My platform (for better or
> worse) is Windows, and I'm quite interested in the pl/python support.
> However, when I run the binary installer, it is not offered
> to me as an option (it's there, but greyed out). The
> plpython.dll file is installed
Hi,
I'm just starting to look at Postgresql. My platform (for better or
worse) is Windows, and I'm quite interested in the pl/python support.
However, when I run the binary installer, it is not offered to me as
an option (it's there, but greyed out). The plpython.dll file is
installed, however.
Wh
Paul Moore <[EMAIL PROTECTED]> writes:
> I suppose my first (lazy) question is, is there a Python 2.4
> compatible plpython.dll available anywhere? Alternatively, is there a
> way I can build one for myself? I'm happy enough doing my own build
> (I have mingw and msys available), but I'd rather no
15 matches
Mail list logo
