[Python-Dev] Deprecating old bugs, now from 2.2.2

2005-05-30 Thread Facundo Batista
Going on with the old bugs checking, here are the results for 2.2.2 (and one from 2.2.1). When I'll finish this will be put in an informational PEP. When I verified the bug, I filled two fields: - Summary: the same subject as in SF - Group: the bug's group at verifying time. - Bug #: the bug numb

[Python-Dev] Old Python version categories in Bug Tracker

2005-05-30 Thread Facundo Batista
People: As the process of deprecating old bugs evolves, the following categories got empty: Python 2.1.1 Python 2.1.2 Python 2.2.1 Python 2.2.1 candidate Python 2.2.2 The SF interface doesn't allow to delete old categories, but maybe we could ask SF support to do it, as nowad

Re: [Python-Dev] Old Python version categories in Bug Tracker

2005-05-30 Thread Raymond Hettinger
> As the process of deprecating old bugs evolves, the following > categories got empty: > > Python 2.1.1 > Python 2.1.2 > Python 2.2.1 > Python 2.2.1 candidate > Python 2.2.2 That's great news. > The SF interface doesn't allow to delete old categories, but maybe we > could

Re: [Python-Dev] Deprecating old bugs, now from 2.2.2

2005-05-30 Thread Brett C.
Facundo Batista wrote: > Going on with the old bugs checking, here are the results for 2.2.2 (and > one from 2.2.1). When I'll finish this will be put in an informational PEP. > Great work, Facundo! Now I feel lazy. =) -Brett ___ Python-Dev mailing l

Re: [Python-Dev] Deprecating old bugs, now from 2.2.2

2005-05-30 Thread Facundo Batista
On 5/30/05, Brett C. <[EMAIL PROTECTED]> wrote: > Facundo Batista wrote: > > Going on with the old bugs checking, here are the results for 2.2.2 (and > > one from 2.2.1). When I'll finish this will be put in an informational PEP. > > > > Great work, Facundo! Now I feel lazy. =) C'mon! Just a w

Re: [Python-Dev] Old Python version categories in Bug Tracker

2005-05-30 Thread Fred L. Drake, Jr.
On Monday 30 May 2005 17:06, Raymond Hettinger wrote: > There's no harm in having these surface. If the category is accurate, > let's use it. If the bug is out of date, we can mark it as such and > close it. While we can't (and shouldn't) delete categories, we can change the text used to des

Re: [Python-Dev] Old Python version categories in Bug Tracker

2005-05-30 Thread Josiah Carlson
"Fred L. Drake, Jr." <[EMAIL PROTECTED]> wrote: > > On Monday 30 May 2005 17:06, Raymond Hettinger wrote: > > There's no harm in having these surface. If the category is accurate, > > let's use it. If the bug is out of date, we can mark it as such and > > close it. > > While we can't (and s

Re: [Python-Dev] Old Python version categories in Bug Tracker

2005-05-30 Thread Facundo Batista
On 5/30/05, Fred L. Drake, Jr. <[EMAIL PROTECTED]> wrote: > While we can't (and shouldn't) delete categories, we can change the text used > to describe them. So "Python 2.2.2" can become "Python 2.2.2 > (unmaintained)". Whether this is desirable or not, I'm not sure. +1 for this solution. We (

Re: [Python-Dev] Old Python version categories in Bug Tracker

2005-05-30 Thread Fred L. Drake, Jr.
On Monday 30 May 2005 22:46, Josiah Carlson wrote: > Pain in the rear, but it is a solution to the 'problem' of having 2.1 > and 2.2 groups. The issue is really that it's not clear that this is a real problem. Unfortunate, yes, but that's it. Ideally, there'd be a way to say that certain cat

Re: [Python-Dev] Old Python version categories in Bug Tracker

2005-05-30 Thread Brett C.
Facundo Batista wrote: > On 5/30/05, Fred L. Drake, Jr. <[EMAIL PROTECTED]> wrote: > > >>While we can't (and shouldn't) delete categories, we can change the text used >>to describe them. So "Python 2.2.2" can become "Python 2.2.2 >>(unmaintained)". Whether this is desirable or not, I'm not sure