Bruce Christensen wrote:
>> If obj has no __module__ attribute (or if it is None), pickle
>> (didn't check cPickle) also does
>>
>> for n, module in sys.module.items():
>> if "module-ignored": continue
>> if getattr(module, result, None) is obj:
>> break # use n as module name
>
> What i
Patch / Bug Summary
___
Patches : 398 open ( +5) / 3334 closed (+19) / 3732 total (+24)
Bugs: 904 open ( -4) / 6011 closed (+36) / 6915 total (+32)
RFE : 222 open ( -1) / 231 closed ( +2) / 453 total ( +1)
New / Reopened Patches
__
Fix for #
Martin v. Löwis" wrote:
> If obj has no __module__ attribute (or if it is None), pickle
> (didn't check cPickle) also does
>
> for n, module in sys.module.items():
> if "module-ignored": continue
> if getattr(module, result, None) is obj:
> break # use n as module name
>
> If obj does
Tim Peters wrote:
...
[Raymond]
Even then, we need to drop the concept of having the flags as counters
rather than booleans.
[Georg Brandl]
Yes. Given that even Tim couldn't imagine a use case for counting the
exceptions, I think it's sensible.
Nick Maclaren wrote:
> When such arithmetic is implemented in hardware, it is normal for
> exceptional cases to be handled by interrupt, and that is VERY
> expensive ... It then becomes important to know how
> many of the things you got, to know whether it is worth putting
> code in to avoid them
...
[Raymond]
>> Even then, we need to drop the concept of having the flags as counters
>> rather than booleans.
[Georg Brandl]
> Yes. Given that even Tim couldn't imagine a use case for counting the
> exceptions, I think it's sensible.
That's not it -- someone will "find a use" for anything. I
Michael Foord wrote:
> Brett Cannon wrote:
>
>> After various people suggesting object-capabilities, takling with Mark
>> S. Miller of the E programming language, and the people Mark works
>> with at HP Labs (who have been giving talks every week during this
>> month here at Google on object-
Brett Cannon wrote:
> After various people suggesting object-capabilities, takling with Mark
> S. Miller of the E programming language, and the people Mark works
> with at HP Labs (who have been giving talks every week during this
> month here at Google on object-capabilities), I have decided to
On Wed, 19 Jul 2006, Brett Cannon wrote:
> I have decided to go with object-capabilities for
> securing interpreters. I have rewritten my design doc from scratch and
> deleted the old one. The new doc is named securing_python.txt and can be
> found through the svn web interface at
> http://svn.py
After various people suggesting object-capabilities, takling with Mark S. Miller of the E programming language, and the people Mark works with at HP Labs (who have been giving talks every week during this month here at Google on object-capabilities), I have decided to go with object-capabilities fo
I'd like to repeat my invitation to spend a week at Google in
California or New York for a Python sprint. We are hosting sprints at
our offices in Mountain View and New York City the week of Aug. 21,
Monday through Thursday.
We're planning to work broadly on Python 2.6 and Python 3000. If
you're
On Tue, Jul 18, 2006 at 02:55:56PM -0400, Fred L. Drake, Jr. wrote:
> On Tuesday 18 July 2006 14:52, Mihai Ibanescu wrote:
> > Unicode might be a perfectly acceptable suggestion for others too.
>
> Are we still supporting builds that don't include Unicode? If so, that needs
> to be considered i
Georg Brandl <[EMAIL PROTECTED]> wrote:
>
> > Even then, we need to drop the concept of having the flags as counters
> > rather than booleans.
>
> Yes. Given that even Tim couldn't imagine a use case for counting the
> exceptions, I think it's sensible.
Well, I can. There is a traditional, import
Raymond Hettinger wrote:
>
>>> I think it was tripping-up the folks working on the C implementation.
>>> Georg can speak to it more directly. IIRC, the issue was that the
>>> context object exposed a dictionary which a user could update directly
>>> and there was no notification back to the surr
I think it was tripping-up the folks working on the C implementation.
Georg can speak to it more directly. IIRC, the issue was that the
context object exposed a dictionary which a user could update directly
and there was no notification back to the surrounding object so it could
upda
On 19/07/06, Thomas Heller <[EMAIL PROTECTED]> wrote:
> Neal Norwitz schrieb:
> > On 7/18/06, Jack Diederich <[EMAIL PROTECTED]> wrote:
> >>
> >> were pre-2003 and talking about mod_python. HURD and FreeBSD came up a
> >> couple times. Do we need to add more *BSD buildbots?
> >
> > Yes. We only
Georg Brandl wrote:
> Raymond Hettinger wrote:
>> If the current approach
>> gets in their way, the C implementers should feel free to make an
>> alternate design choice.
>
> +1. (cDecimal is an ugly name, but a sound concept)
>
> I don't know what progress Mateusz' work has made until now, but
Raymond Hettinger wrote:
> Aahz wrote:
>> On Tue, Jul 18, 2006, Raymond Hettinger wrote:
>>
>>> P.S. The dictionary approach to context objects should likely be
>>> abandoned for the C version. If the API has to change a bit, then so
>>> be it.
>>>
>>
>> Why do you say that? The rest I a
18 matches
Mail list logo
