On 2/23/08, Christian Heimes [EMAIL PROTECTED] wrote:
We have over 1,700 open issues - bug reports, feature requests and
patches - in our bug tracker. In my humble opinion it's a sure sign for
a problem.
There is also 12000 closed tickets, with 1200 of them having been
closed in the last 6
Eric Smith schrieb:
Guido van Rossum wrote:
I wonder if, in order to change the behavior of various built-in
functions, it wouldn't be easier to be able to write
from future_builtins import oct, hex # and who knows what else
This makes sense to me, especially if we have a 2to3 fixer
2008/2/23, Virgil Dupras [EMAIL PROTECTED]:
The flow seems healthy to me.
What I don't see healthy is that we have, per week, around 30 issues
more open (30 is the difference between those closed, and the new
ones).
So, the curve is always going up... fast.
--
.Facundo
Blog:
Facundo Batista wrote:
2008/2/23, Virgil Dupras [EMAIL PROTECTED]:
The flow seems healthy to me.
What I don't see healthy is that we have, per week, around 30 issues
more open (30 is the difference between those closed, and the new
ones).
So, the curve is always going up... fast.
2008/2/23, Steve Holden [EMAIL PROTECTED]:
A larger team (not necessarily all committers) could help us improve
quality and reduce the issue count. Deleting issues purely on grounds of
Exactly, that's why I love Python bug days.. and I'm pushing this hard
in Argentina!
In the January one,
On Fri, 22 Feb 2008 18:53:48 -0500 Barry Warsaw [EMAIL PROTECTED] wrote: now
is
In 50 years, our grandchildren will be writing code with brain
implants and displays burned right into their retina, and they'll /
still/ be subject to 79 characters. I laugh every time I think that
they'll
Georg Brandl wrote:
Eric Smith schrieb:
Guido van Rossum wrote:
I wonder if, in order to change the behavior of various built-in
functions, it wouldn't be easier to be able to write
from future_builtins import oct, hex # and who knows what else
This makes sense to me, especially if we have
On Sat, Feb 23, 2008 at 2:57 AM, Georg Brandl [EMAIL PROTECTED] wrote:
Eric Smith schrieb:
Guido van Rossum wrote:
I wonder if, in order to change the behavior of various built-in
functions, it wouldn't be easier to be able to write
from future_builtins import oct, hex # and who
Guido van Rossum wrote:
I don't think a -3 warning for oct or hex would do any good.
I'm curious as to why. oct and hex have different behavior in 3.0,
which is what I thought -3 was for. hex might be overkill, as the only
differences are the L and the __hex__ behavior. But oct is always
Hi!
In today's bug day, an Argentinian colleague called my attention over
the issue 1746071.
This issue is about mutex:
The mutex module defines a class that allows mutual-exclusion via
acquiring and releasing locks. It does not require (or imply)
threading or multi-tasking, though it could be
-- Forwarded message --
From: Guido van Rossum [EMAIL PROTECTED]
Date: Sat, Feb 23, 2008 at 1:26 PM
Subject: Re: [Python-Dev] Mutex module
To: Facundo Batista [EMAIL PROTECTED]
According to the docstring it's only meant to be used with sched.py.
Please don't try to make it work
2008/2/23, Facundo Batista [EMAIL PROTECTED]:
Ok, I'll close the issue with this, and forward this mail to the
stdlib reorg for proper handling.
1. Done
2. It was already taken care of in the stdlib reorg sheet (it will be
removed, or at least its api hidden, in 3.0)
Thank you!
--
.
Facundo Batista writes:
2008/2/23, Virgil Dupras [EMAIL PROTECTED]:
The flow seems healthy to me.
+1
What I don't see healthy is that we have, per week, around 30 issues
more open (30 is the difference between those closed, and the new
ones).
So, the curve is always going up...
+1 to everything -- n
On Fri, Feb 22, 2008 at 3:45 PM, Barry Warsaw [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
I've volunteered to be the release manager for Python 2.6 and 3.0.
It's been several years since I've RM'd a Python release, and I'm
2008/2/23, Stephen J. Turnbull [EMAIL PROTECTED]:
If that curve ever turns down, it means that users are giving up on
Python as a tool for solving ever harder problems. That's where it
gets scarey.
It depends. If that happens because no new issues are found, maybe (it
could happen also
There is some discussion on this subject, archived here:
http://permalink.gmane.org/gmane.comp.python.general/560661
I wonder if anyone could shed some light on this subject?
(Or, help me understand, what is the difference between a type that I create
using python C api and a python class?)
On Sat, Feb 23, 2008 at 4:55 PM, Neal Becker [EMAIL PROTECTED] wrote:
There is some discussion on this subject, archived here:
http://permalink.gmane.org/gmane.comp.python.general/560661
I wonder if anyone could shed some light on this subject?
(Or, help me understand, what is the
On Sat, Feb 23, 2008 at 8:06 AM, Guido van Rossum [EMAIL PROTECTED] wrote:
I do think map() and filter() should issue a warning under -3 when the
first arg is None. (Or does 2to3 detect this now?)
What's wrong with filter(None, seq)? That currently works in 3k:
filter(None, range(5))
(Or, help me understand, what is the difference between a type that I create
using python C api and a python class?)
Grepping for the specific error message would have answered that
question: Python (new-style) classes have the Py_TPFLAGS_HEAPTYPE
set, types declared as static structs in C
Martin v. Löwis wrote:
One issue to consider is also politeness. People sometimes complain that
they feel treated unfair if their report is declared invalid - they
surely believed it was a valid report, at the time they made it.
I agree with Martin for both of these - 'works for me' and 'out
Nick Coghlan wrote:
Martin v. Löwis wrote:
One issue to consider is also politeness. People sometimes complain that
they feel treated unfair if their report is declared invalid - they
surely believed it was a valid report, at the time they made it.
I agree with Martin for both of these -
On Sat, Feb 23, 2008 at 10:17 PM, Ron Adam [EMAIL PROTECTED] wrote:
Nick Coghlan wrote:
Martin v. Löwis wrote:
One issue to consider is also politeness. People sometimes complain that
they feel treated unfair if their report is declared invalid - they
surely believed it was a valid
Neal Becker wrote:
(Or, help me understand, what is the difference between a type that I create
using python C api and a python class?)
Classes that you create in Python have a __dict__ attribute
holding a dictionary for arbitrary attributes to go in.
Most types defined in C don't bother
23 matches
Mail list logo
