Re: [Python-Dev] 2.3.5 schedule, and something I'd like to get in

2005-01-07 Thread Bob Ippolito
On Jan 6, 2005, at 15:03, Bob Ippolito wrote: On Jan 6, 2005, at 14:59, Ronald Oussoren wrote: On 6-jan-05, at 14:04, Jack Jansen wrote: On 6 Jan 2005, at 00:49, Martin v. Löwis wrote: The new solution is basically to go back to the Unix way of building an extension: link it against nothing and

Re: [Python-Dev] Minor change to behaviour of csv module

2005-01-07 Thread Andrew McNamara
I'm considering a change to the csv module that could potentially break some obscure uses of the module (but CSV files usually quote, rather than escape, so the most common uses aren't effected). Currently, with a non-default escapechar='\\', input like: field one,field \ two,field three

Re: [Python-Dev] 2.3.5 schedule, and something I'd like to get in

2005-01-07 Thread Jack Jansen
On 7 Jan 2005, at 11:08, Bob Ippolito wrote: 10.3 or later. For older OSX releases (either because you build Python on 10.2 or earlier, or because you've set MACOSX_DEPLOYMENT_TARGET to a value of 10.2 or less) we use the old behaviour of linking with -framework Python. Wouldn't it be better to

RE: [Python-Dev] Re: [Csv] Minor change to behaviour of csv module

2005-01-07 Thread Michael Chermside
Andrew explains that in the CSV module, escape characters are not properly removed. Magnus writes: IMO this is the *only* reasonable behaviour. I don't understand why the escape character should be left in; this is one of the reason why UNIX-style colon-separated values don't work with the

Re: [Python-Dev] Re: [Csv] Minor change to behaviour of csv module

2005-01-07 Thread Alex Martelli
On 2005 Jan 07, at 14:45, Michael Chermside wrote: Andrew explains that in the CSV module, escape characters are not properly removed. Magnus writes: IMO this is the *only* reasonable behaviour. I don't understand why the escape character should be left in; this is one of the reason why UNIX-style

Re: [Python-Dev] an idea for improving struct.unpack api

2005-01-07 Thread Michael Hudson
Bob Ippolito [EMAIL PROTECTED] writes: On Jan 6, 2005, at 8:17, Michael Hudson wrote: Ilya Sandler [EMAIL PROTECTED] writes: A problem: The current struct.unpack api works well for unpacking C-structures where everything is usually unpacked at once, but it becomes inconvenient when

Re: [Python-Dev] Re: [Python-checkins] python/dist/src/Python pythonrun.c, 2.161.2.15, 2.161.2.16

2005-01-07 Thread Kurt B. Kaiser
Jeremy Hylton [EMAIL PROTECTED] writes: ../Python/symtable.c:193: structure has no member named `st_tmpname' Do you see that? Yeah, the merge eliminated it from the symtable struct in symtable.h. You moved it to symtable_entry at rev 2.12 in MAIN :-) I'll research it. Apparently my build

RE: [Python-Dev] an idea for improving struct.unpack api

2005-01-07 Thread Ilya Sandler
I will try to respond to all comments at once. But first a clarification: -I am not trying to design a high-level API on top of existing struct.unpack and -I am not trying to design a replacement for struct.unpack (If I were to replace struct.unpack(), then I would probably go along

Re: [Python-Dev] an idea for improving struct.unpack api

2005-01-07 Thread Ilya Sandler
How about making offset a standard integer, and change the signature to return tuple when it is used: item, offset = unpack(format, rec, offset) # Partial unpacking Well, it would work well when unpack results are assigned to individual vars: x,y,offset=unpack( ii, rec, offset) but it

Re: [Python-Dev] Re: [Python-checkins] python/dist/src/Python pythonrun.c, 2.161.2.15, 2.161.2.16

2005-01-07 Thread Kurt B. Kaiser
[EMAIL PROTECTED] (Kurt B. Kaiser) writes: [JH] ../Python/symtable.c:193: structure has no member named `st_tmpname' Do you see that? Yeah, the merge eliminated it from the symtable struct in symtable.h. You moved it to symtable_entry at rev 2.12 in MAIN :-) I'll research it. I think it