On Sat, Mar 7, 2009 at 2:56 PM, "Martin v. Löwis" wrote:
>> Skip changed it to the present wording last year:
>> http://svn.python.org/view/python/trunk/Doc/library/queue.rst?r1=59750&r2=59969
>
> I see. I agree that the change was for the better.
Agreed too, though it would seem that *if* there
Michael Haggerty wrote:
Typically, the purpose of a database is to persist data across program
runs. So typically, your suggestion would only help if there were a way
to persist the primed Pickler across runs.
I don't think you need to be able to pickle picklers.
In the case in question, the
On Sat, Mar 7, 2009 at 1:21 PM, Raymond Hettinger wrote:
>
> [Benjamin Peterson]
>>
>> On behalf of the Python development team and the Python community, I'm
>> happy to announce the first alpha release of Python 3.1.
>
> Thanks for the good work.
Sorry to be late to the party. Indeed, thanks for
Glyph> ... which is exactly why I have volunteered to explain to someone
Glyph> how to separate the core event-loop bits (suitable for inclusion
Glyph> in the standard library) from the huge pile of protocol
Glyph> implementations which are not necessarily useful.
Neil> This so
gl...@divmod.com wrote:
> ... which is exactly why I have volunteered to explain to someone how to
> separate the core event-loop bits (suitable for inclusion in the
> standard library) from the huge pile of protocol implementations which
> are not necessarily useful.
>
> Despite the FUD to the
> Skip changed it to the present wording last year:
> http://svn.python.org/view/python/trunk/Doc/library/queue.rst?r1=59750&r2=59969
I see. I agree that the change was for the better.
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail
> I would be happy to restore the documentation. You want the methods
> back and I think that's sufficient reason to bring it back.
Thanks! I'll look into the docstrings.
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/m
[Benjamin Peterson]
On behalf of the Python development team and the Python community, I'm
happy to announce the first alpha release of Python 3.1.
Thanks for the good work.
Raymond
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyth
2009/3/7 Gerard Flanagan :
> Benjamin Peterson wrote:
> On the release page, the bzip link says '3.0' not '3.1'.
That should be fixed now.
>
>> See PEP 375 for release schedule details:
>>
>> http://www.python.org/dev/peps/pep-0361/
That URL is actually supposed to be http://www.python.org/d
On Sat, Mar 07, 2009, Benjamin Peterson wrote:
>
> On behalf of the Python development team and the Python community, I'm
> happy to announce the first alpha release of Python 3.1.
Congratulations on your first baby! Here's to hoping you release many
more of these!
--
Aahz (a...@pythoncraft.com)
Benjamin Peterson wrote:
On behalf of the Python development team and the Python community, I'm
happy to announce the first alpha release of Python 3.1.
[...]
Looks good, thanks to all involved. Two minor things:
For more information and downloads, see the Python 3.1 website:
http://w
On behalf of the Python development team and the Python community, I'm
happy to announce the first alpha release of Python 3.1.
Python 3.1 focuses on the stabilization and optimization of features and changes
Python 3.0 introduced. The new I/O system has been rewritten in C for speed.
Other featu
Aahz wrote:
> On Sat, Mar 07, 2009, Dan Mahn wrote:
> >
> > After a harder look, I concluded there was a bit more work to be done,
> > but still very basic modifications.
> >
> > Attached is a version of urlencode() which seems to make the most sense
> > to me.
> >
> > I wonder how I could of
Guido van Rossum wrote:
> On Sat, Mar 7, 2009 at 8:04 AM, Michael Haggerty wrote:
>> Typically, the purpose of a database is to persist data across program
>> runs. So typically, your suggestion would only help if there were a way
>> to persist the primed Pickler across runs.
>
> I haven't follo
On Sat, 7 Mar 2009 at 08:42, Aahz wrote:
On Sat, Mar 07, 2009, rdmur...@bitdance.com wrote:
So, a little belatedly, here is my intro. [...]
--RDM
Welcome! You apparently haven't set your $NAME nor listed a name in your
.sig, so how do you prefer to be addressed? Or do you just prefer your
Aahz pythoncraft.com> writes:
>
> One thing I haven't seen addressed in this discussion is why it's
> undesirable to ship Twisted as part of the testing source tree.
Because Twisted is huge and it's not reasonable to include it just for testing
purposes?
(besides, launching a twisted server impl
[moving discussion to python-dev from pydotorg]
On Fri, Mar 06, 2009, Bill Janssen wrote:
> Michael Foord wrote:
>> Bill Janssen wrote:
>>> Steve Holden wrote:
Seems to me it might be better to have a test start a local server then
kill it, but I am presuming you have some good
On Sat, Mar 07, 2009, rdmur...@bitdance.com wrote:
>
> So, a little belatedly, here is my intro. [...]
>
> --RDM
Welcome! You apparently haven't set your $NAME nor listed a name in your
.sig, so how do you prefer to be addressed? Or do you just prefer your
initials, like RMS? ;-)
--
Aahz (a..
I've been watching the threads about tracker maintenance and patch
review with interest. I'm afraid that I did not follow the list
recommendation to introduce myself when I first started posting, partly
because I initially jumped in on something that was a bit of a hot
button issue for me :)
So,
On Sat, Mar 7, 2009 at 8:04 AM, Michael Haggerty wrote:
> Typically, the purpose of a database is to persist data across program
> runs. So typically, your suggestion would only help if there were a way
> to persist the primed Pickler across runs.
I haven't followed all this, but isn't is at lea
Greg Ewing wrote:
> Michael Haggerty wrote:
>> A similar effect could *almost* be obtained without accessing the memos
>> by saving the pickled primer itself in the database. The unpickler
>> would be primed by using it to load the primer before loading the record
>> of interest. But AFAIK there
On Sat, Mar 7, 2009 at 6:54 AM, Raymond Hettinger wrote:
>
>> [MvL]
>>>
>>> At this point, I do request that the patch is reverted completely
>>> (i.e. that the documentation is restored), and that the qualification
>>> "not reliable!" is removed from the doc strings of the methods, as
>>> it is f
On Sat, Mar 07, 2009, Dan Mahn wrote:
>
> After a harder look, I concluded there was a bit more work to be done,
> but still very basic modifications.
>
> Attached is a version of urlencode() which seems to make the most sense
> to me.
>
> I wonder how I could officially propose at least some o
After a harder look, I concluded there was a bit more work to be done,
but still very basic modifications.
Attached is a version of urlencode() which seems to make the most sense
to me.
I wonder how I could officially propose at least some of these
modifications.
- Dan
Bill Janssen wrot
[MvL]
At this point, I do request that the patch is reverted completely
(i.e. that the documentation is restored), and that the qualification
"not reliable!" is removed from the doc strings of the methods, as
it is factually incorrect.
I would be happy to restore the documentation. You want
Antoine Pitrou wrote:
Hello,
Out of curiosity, I timed running the test suite ("./python -m test.regrtest")
in non-debug mode, in both the release30-maint and py3k branches:
* release30-maint got:
302 tests OK.
[...]
165.79user 26.03system 5:01.75elapsed 63%CPU
* py3k got:
304 tests OK.
[...]
[MvL]
At this point, I do request that the patch is reverted completely
(i.e. that the documentation is restored), and that the qualification
"not reliable!" is removed from the doc strings of the methods, as
it is factually incorrect.
I would be happy to restore the documentation. You want t
Hello,
Out of curiosity, I timed running the test suite ("./python -m test.regrtest")
in non-debug mode, in both the release30-maint and py3k branches:
* release30-maint got:
302 tests OK.
[...]
165.79user 26.03system 5:01.75elapsed 63%CPU
* py3k got:
304 tests OK.
[...]
113.33user 28.93system 4
On Sat, Mar 7, 2009 at 9:32 AM, Lie Ryan wrote:
The prize was Martin von Löwis of the Python Foundation on behalf of the
Python community itself.
>>>
>>> This is a funny translation from German-to-English. :-)
>>>
>>> But yeah, a good one and the prize was presented by Klaus Knopper
Antoine Pitrou wrote:
If these strings are not interned, then perhaps they should be.
I think this is a different problem. Even if the strings are
interned, if you start with a fresh pickler each time, you
get a copy of the strings in each pickle. What he wants is
to share strings between diff
Michael Haggerty wrote:
A similar effect could *almost* be obtained without accessing the memos
by saving the pickled primer itself in the database. The unpickler
would be primed by using it to load the primer before loading the record
of interest. But AFAIK there is no way to prime new pickle
> Matthew Barnett has been doing a lot of work on the regular expressions engine
> (it seems he hasn't finished yet) under http://bugs.python.org/issue2636.
> However, the patches are really huge and touch all of the sre internals. I
> wonder what the review process can be for such patches? Is ther
Hello,
Matthew Barnett has been doing a lot of work on the regular expressions engine
(it seems he hasn't finished yet) under http://bugs.python.org/issue2636.
However, the patches are really huge and touch all of the sre internals. I
wonder what the review process can be for such patches? Is ther
>> I still fail to see the rationale for removing these
>> two methods.
>
> I believe there was a thread (in January 2008) with a decision to keep
> qsize() but to drop empty() and full().
That's something different: even if there was a decision, it doesn't
mean that there was a rationale, and th
34 matches
Mail list logo
