Andrew MacIntyre wrote:
I'll take this up with FreeBSD folk, but I'm open to ideas as to how
best to deal with the problem in the context of the test suite pending
resolution by FreeBSD.
The response I got from Jason Evans (author of the new malloc()
implementation), along with that of another
> It seems to me that the most practical way forward is to just institute a
> policy that tests that want to try and test out of memory behaviour must
> ensure that appropriate resource limits are in place
IMO, there shouldn't be any tests in the test suite that rely on
exhaustion of all available
Some good news: I finally figured out how to modify asyncore to make
it properly handle the non-blocking ssl-handshake.
I provided a patch for test_ssl.py in issue 3899.
Bill, could you please review it?
--- Giampaolo
http://code.google.com/p/pyftpdlib/
On 18 Set, 00:49, "Giampaolo Rodola'" <[EM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just installing 2.6rc2, I see that bsddb3 testsuite is disabled by default.
Current testsuite is far more fast and stable that the old one (entire
test: 17 seconds in my machine). I was wondering if it is time to enable
bsddb3 testsuite by default.
B
On Sep 18, 2008, at 10:24 AM, Jesus Cea wrote:
Current testsuite is far more fast and stable that the old one (entire
test: 17 seconds in my machine). I was wondering if it is time to
enable
bsddb3 testsuite by default.
Perhaps so. That certainly improves the chances of finding problems
e
During the past couple of months I have been working on an
object-capability subset of Python - in other words, a restricted
execution scheme for sandboxing Python code. It has been influenced
by other object-capability subset languages, such as Joe-E (a subset
of Java [1]), Caja/Cajita (subsets o
On Thu, Sep 18, 2008 at 7:24 AM, Jesus Cea <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Just installing 2.6rc2, I see that bsddb3 testsuite is disabled by default.
>
> Current testsuite is far more fast and stable that the old one (entire
> test: 17 seconds in my
>From this page:
http://www.python.org/download/releases/2.6/
I clicked the link labelled "What's new in Python 2.6rc2". This didn't take
me to the What's New page. Instead it took me to:
http://www.python.org/download/releases/2.6/NEWS.txt
Seems a bit mislabelled if nothing else. Po
Mark Seaborn wrote:
During the past couple of months I have been working on an
object-capability subset of Python - in other words, a restricted
execution scheme for sandboxing Python code. It has been influenced
by other object-capability subset languages, such as Joe-E (a subset
of Java [1]),
How about Capt'n Python? :-)
Anyway, this is way cool. Looking forward to kicking the tires!
On Thu, Sep 18, 2008 at 1:33 PM, Terry Reedy <[EMAIL PROTECTED]> wrote:
> Mark Seaborn wrote:
>>
>> During the past couple of months I have been working on an
>> object-capability subset of Python - in ot
On Thu, Sep 18, 2008 at 04:33:23PM -0400, Terry Reedy wrote:
> Mark Seaborn wrote:
> I'm calling it CapPython
>
> No wonder ;-). I like CapPy better, though there is a shareware screen
> capture program by that name. PyCap is taken. CapThon is not.
CaPy, and make capybara its mascot. ;)
Guido van Rossum wrote:
How about Capt'n Python? :-)
Harr, harr! Geat name :)
Christian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/pyth
Terry Reedy <[EMAIL PROTECTED]> wrote:
> Mark Seaborn wrote:
> > Private attributes may only be accessed through "self" variables.
> > "Self" variables are defined as being the first arguments of functions
> > defined inside class definitions, with a few restrictions intended to
> > prevent these
On Thu, Sep 18, 2008 at 2:15 PM, Mark Seaborn <[EMAIL PROTECTED]> wrote:
> Terry Reedy <[EMAIL PROTECTED]> wrote:
>
>> Mark Seaborn wrote:
>
>> > Private attributes may only be accessed through "self" variables.
>> > "Self" variables are defined as being the first arguments of functions
>> > define
> I clicked the link labelled "What's new in Python 2.6rc2". This didn't take
> me to the What's New page. Instead it took me to:
>
> http://www.python.org/download/releases/2.6/NEWS.txt
>
> Seems a bit mislabelled if nothing else.
How so? The first major heading in that file reads
"What'
On Fri, Sep 19, 2008 at 12:49:28AM +0200, "Martin v. Löwis" wrote:
> > I clicked the link labelled "What's new in Python 2.6rc2". This didn't take
> > me to the What's New page. Instead it took me to:
> >
> > http://www.python.org/download/releases/2.6/NEWS.txt
> >
> > Seems a bit mislabell
[EMAIL PROTECTED] wrote:
>>From this page:
>
> http://www.python.org/download/releases/2.6/
>
> I clicked the link labelled "What's new in Python 2.6rc2". This didn't take
> me to the What's New page. Instead it took me to:
>
> http://www.python.org/download/releases/2.6/NEWS.txt
>
>
>> http://www.python.org/download/releases/2.6/NEWS.txt
>>
>> Seems a bit mislabelled if nothing else.
Martin> How so? The first major heading in that file reads
Seems more like the Misc/NEWS file to me. I was expecting Andrew's What's
New document, which I eventually found at
[EMAIL PROTECTED] wrote:
> >> http://www.python.org/download/releases/2.6/NEWS.txt
> >>
> >> Seems a bit mislabelled if nothing else.
>
> Martin> How so? The first major heading in that file reads
>
> Seems more like the Misc/NEWS file to me. I was expecting Andrew's What's
> Ne
> >> http://www.python.org/download/releases/2.6/NEWS.txt
> >>
> >> Seems a bit mislabelled if nothing else.
>
> Martin> How so? The first major heading in that file reads
>
> Seems more like the Misc/NEWS file to me.
Correct.
> I was expecting Andrew's What's New document
Why
20 matches
Mail list logo
