On 5/6/06, Talin <[EMAIL PROTECTED]> wrote:
> I've updated PEP 3101 based on the feedback collected so far.
[http://www.python.org/dev/peps/pep-3101/]
I think this is a step in the right direction.
I wonder if we shouldn't borrow more from .NET. I read this URL that
you referenced:
http://msdn.m
I moved up the 2.5 release date by a bit. Ideally, I wanted to have
the final on July 27 which corresponds to OSCON. This seems too
aggressive since I haven't updated the schedule publicly. So the new
schedule has rc1 slated for July 27.
http://www.python.org/dev/peps/pep-0356/
So far we'v
Registration for Europython (3-5 July) at CERN in Geneva is now open,
if you feel submitting a talk proposal there's still time until
the 31th of May.
If you want to talk about a library you developed, or you know well
and want to share your knowledge, or about how you are making the best
out of P
Vladimir,
Your examples seem to indicate that you've misunderstood the change
that's proposed for Python 3000. Especially this:
On 5/17/06, Vladimir 'Yu' Stepanov <[EMAIL PROTECTED]> wrote:
> # BEGIN: Emulation python3000
> if type(a) is not type(b) and (
>
Dave Cinege wrote:
>> It's already there. It's called shlex.split(), and follows the
>> semantic of a standard UNIX shell, including escaping and other
>> things.
>
> Not quite. As I said in my other post, simple is the idea for this,
> just like the split method itself. (no escaping, etc.jus
Ronald Oussoren wrote:
> Wouldn't this specific problem be fixed if os.fork were to acquire the
> import lock before calling fork(2)?
Right. Of course, you need to release the lock then both in the parent
and the child. Also, all places that currently do PyOs_AfterFork should
get modified (i.e. fo
On Thursday 18 May 2006 04:21, Giovanni Bajo wrote:
> It's already there. It's called shlex.split(), and follows the semantic of
> a standard UNIX shell, including escaping and other things.
Not quite. As I said in my other post, simple is the idea for this, just like
the split method itself. (
On Thursday 18 May 2006 03:00, Heiko Wundram wrote:
> Am Donnerstag 18 Mai 2006 06:06 schrieb Dave Cinege:
> > This is useful, but possibly better put into practice as a separate
> > method??
>
> I personally don't think it's particularily useful, at least not in the
> special case that your patch
Nick Coghlan wrote:
> And if I understand it correctly, it falls under the category that
> waiting for another thread while holding the import lock is a *really*
> bad idea from a thread safety point of view.
>
> The thing with the import-after-fork deadlock is that you can trigger it
> without ev
Am Donnerstag 18 Mai 2006 17:11 schrieb Guido van Rossum:
> (Did anyone mention the csv module yet? It deals with this too.)
Yes, mentioned it thrice. ;-)
--- Heiko.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listin
On 16-mei-2006, at 23:20, Martin v. Löwis wrote:
Nick Coghlan wrote:
Broadening the ifdef to cover all posix systems rather than just AIX
might be the right thing to do.
As I said: I doubt it is the right thing to do. Instead, the lock
should get released in the child process if it is held a
This is not an apropriate function to add as a string methods. There
are too many conventions for quoting and too many details to get
right. One method can't possibly handle them all without an enormous
number of weird options. It's better to figure out how to do this with
regexps or use some of th
Dave Cinege wrote:
> Very oftenmake that very very very very very very very very very often,
> I find myself processing text in python that when .split()'ing a line, I'd
> like to exclude the split for a 'quoted' item...quoted because it contains
> whitespace or the sep char.
>
> For exampl
Martin v. Löwis wrote:
> Neal Norwitz wrote:
>>> As I said: I doubt it is the right thing to do. Instead, the lock
>>> should get released in the child process if it is held at the
>>> point of the fork.
>>>
>> I'm not sure if this bug can be reproduced now, but the comment in
>> warnings.py points
Am Donnerstag 18 Mai 2006 12:26 schrieb Giovanni Bajo:
> I believe the standard library already covers common usage. There will
> surely be cases where a custom lexer/splitetr will have to be written, but
> that's life
The csv data field parser handles all common usage I have encountered so far,
Heiko Wundram <[EMAIL PROTECTED]> wrote:
>>> Don't get me wrong, I personally find this functionality very, very
>>> interesting (I'm +0.5 on adding it in some way or another),
>>> especially as a
>>> part of the standard library (not necessarily as an extension to
>>> .split()).
>>
>> It's alread
Am Donnerstag 18 Mai 2006 10:21 schrieb Giovanni Bajo:
> Heiko Wundram <[EMAIL PROTECTED]> wrote:
> > Don't get me wrong, I personally find this functionality very, very
> > interesting (I'm +0.5 on adding it in some way or another),
> > especially as a
> > part of the standard library (not necessa
Heiko Wundram <[EMAIL PROTECTED]> wrote:
> Don't get me wrong, I personally find this functionality very, very
> interesting (I'm +0.5 on adding it in some way or another),
> especially as a
> part of the standard library (not necessarily as an extension to
> .split()).
It's already there. It's
On 5/17/06, Dave Cinege
<[EMAIL PROTECTED]> wrote:
> Very oftenmake that very very very very very very very very very often,
> I find myself processing text in python that when .split()'ing a line, I'd
> like to exclude the split for a 'quoted' item...quoted because it contains
> whitespace or
Neal Norwitz wrote:
>> As I said: I doubt it is the right thing to do. Instead, the lock
>> should get released in the child process if it is held at the
>> point of the fork.
>>
> I'm not sure if this bug can be reproduced now, but the comment in
> warnings.py points to:
>
>http://python.org/
20 matches
Mail list logo
