As we approach the planned first betas for 2.6/3.0, my heart sinks
when I see the imposing list of 16 release blockers. [1] Luckily, most
of the issues have patches that just need *your* review. Others,
namely the Py3k exception issues, may require a little more
discussion, but I'm sure we can get
On Fri, Jun 6, 2008 at 2:19 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> On 2008-06-03 01:29, Gregory P. Smith wrote:
>
>> On Mon, Jun 2, 2008 at 4:09 PM, Guido van Rossum <[EMAIL PROTECTED]>
>> wrote:
>>
>> I will freely admit that I haven't followed this thread in any detail,
>>> but if it we
> So, it's okay to setattr the attribute name "None" but not okay to set
> it directly? Is this deliberate or is it an unintentional side effect
> of parser changes to prevent assignment to None?
It's deliberate. setattr(o, "foo bar", "baz") also works, even though
"foo bar" is not an identifier.
On Mon, 9 Jun 2008 12:24:55 pm Curt Hagenlocher wrote:
> So, it's okay to setattr the attribute name "None" but not okay to
> set it directly?
I suspect this is off-topic for python-dev, and would be better on
comp.lang.python or similar, but for what it's worth, I consider having
an attribu
On Sun, Jun 8, 2008 at 9:24 PM, Curt Hagenlocher <[EMAIL PROTECTED]> wrote:
> My apologies if this is one of those "dead horse" issues. The
> following seems a little inconsistent to me:
>
c = C()
c.None
> Traceback (most recent call last):
> File "", line 1, in
> AttributeError: C ins
My apologies if this is one of those "dead horse" issues. The
following seems a little inconsistent to me:
>>> c = C()
>>> c.None
Traceback (most recent call last):
File "", line 1, in
AttributeError: C instance has no attribute 'None'
>>> c.None = 'foo'
File "", line 1
SyntaxError: assignme
On Sun, 8 Jun 2008 08:37:20 -0500, Benjamin Peterson <[EMAIL PROTECTED]> wrote:
Certainly not in core Python. Have a look
http://code.google.com/p/python-threadsafe/, though.
http://code.google.com/p/python-safethread/
Jean-Paul
___
Python-Dev mail
On Sun, Jun 8, 2008 at 6:15 AM, Pau Freixes <[EMAIL PROTECTED]> wrote:
> Hi List,
>
> Surly this is a recurring theme into python dev world, but I need your help
> for confirm if the follow image it's really
>
> http://www.milnou.net/~pfreixes/img/cpu_usage_gil_problem.png
>
> I'm writing a brief a
Hi List,
Surly this is a recurring theme into python dev world, but I need your help
for confirm if the follow image it's really
http://www.milnou.net/~pfreixes/img/cpu_usage_gil_problem.png
I'm writing a brief article for my blog and I need to make sure about the
current problem with GIL and mu
