[Python-Dev] Deprecating old bugs, now from 2.2.2
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 number
- Verified: is the date when I checked the bug.
- Action: is what I did then.
If the bug survived the verification, the next two fields are
applicable (if not, I put a dash, the idea is to keep this info easily
parseable):
- Final: is the action took by someone who eliminated the bug from
that category (closed, moved to Py2.4, etc).
- By: is the someone who did the final action.
So, here's the info...
Summary: Python Interpreter shell is crashed
Group:2.2.2
Bug #:1100673
Verified: 15-Jan-2005
Action: Deprecation alerted. Works ok for me.
Final:Closed. Rejected.
By: mwh
Summary: popen3 under threads reports different stderr results
Group:2.2.2
Bug #:856706
Verified: 15-Jan-2005
Action: Closed as duplicate of #853411
Final:-
By: -
Summary: CGIHTTPServer cannot manage cgi in sub directories
Group:2.2.2
Bug #:778804
Verified: 15-Jan-2005
Action: Closing as Fixed (was fixed already).
Final:-
By: -
Summary: popen does not like filenames with spaces
Group:2.2.2
Bug #:774546
Verified: 15-Jan-2005
Action: Deprecation alerted. Should be closed with "Won't fix"
specially now that we have the subprocess module.
Final:Closed. Out of date.
By: rhettinger
Summary: popen4 doesn't close filedescriptors when in Threads
Group:2.2.2
Bug #:768649
Verified: 15-Jan-2005
Action: Deprecation alerted. Works ok for me.
Final:Closed: Won't fix.
By: facundobatista
Summary: Sudden death with SIGSEGV in RtlEnterCriticalSection
Group:2.2.2
Bug #:763190
Verified: 15-Jan-2005
Action: Deprecation alerted. Don't have the context to try it.
Final:Closed: Won't fix.
By: facundobatista
Summary: can't CNTRL-C when running os.system in a thread
Group:2.2.2
Bug #:756940
Verified: 15-Jan-2005
Action: Deprecation alerted. There's other bug similar to this
(#756924) and a patch for it (that has been accepted), but can't try
it right now.
Final:Closed: Won't fix.
By: facundobatista
Summary: Calling socket.recv() with a large number breaks
Group:2.2.2
Bug #:756104
Verified: 15-Jan-2005
Action: Changed to Py2.4. The bug is still there (but in the documentation).
Final:-
By: -
Summary: ftplib.retrbinary fails when called from retrlines callback
Group:2.2.2
Bug #:751758
Verified: 15-Jan-2005
Action: Changed to Py2.4. The bug is still there.
Final:-
By: -
Summary: CGIHTTPServer does not handle scripts in sub-dirs
Group:2.2.2
Bug #:737202
Verified: 15-Jan-2005
Action: Deprecation alerted. There's a patch, but actual code has
something very similar to it, don't have the context to try if it's
fixed.
Final:Changed to Py2.4. The bug is still there.
By: facundobatista
Summary: socketmodule.c: inet_pton() expects 4-byte packed_addr
Group:2.2.2
Bug #:730222
Verified: 15-Jan-2005
Action: Deprecation alerted. Don't have the context to see if it's
already solved (there's a not-applied patch).
Final:Closed: Won't fix.
By: facundobatista
Summary: mmap's resize method resizes the file in win32 but not unix
Group:2.2.2
Bug #:728515
Verified: 15-Jan-2005
Action: Deprecation alerted. Don't know enough about it to check ir
or reproduce it.
Final:Closed: Won't fix.
By: facundobatista
Summary: Core Dumps : Python2.2.2
Group:2.2.2
Bug #:727241
Verified: 15-Jan-2005
Action: Deprecation alerted. Not sure if it's a Python or IRIX bug.
Final:Closed: Won't fix.
By: facundobatista
Summary: inspect, class instances and __getattr__
Group:2.2.2
Bug #:718532
Verified: 15-Jan-2005
Action: Deprecation alerted. Not sure if there's a bug.
Final:Changed to Py2.4.
By: facundobatista
Summary: "build_ext" "libraries" subcommand not s
Group:2.2.2
Bug #:716634
Verified: 15-Jan-2005
Action: Deprecation alerted. Not sure if there's a bug.
Final:Closed: Won't fix.
By: facundobatista
Summary: SEEK_{SET,CUR,END} missing in 2.2.2
Group:2.2.2
Bug #:711830
Verified: 15-Jan-2005
Action: Deprecation alerted. Not sure if there's a bug.
Final:Closed. Fixed.
By: loewis
Summary: codecs.open and iterators
Group:2.2.2
Bug #:706595
Verified: 15-Jan-2005
Action: Deprecation alerted. Couldn't reproduce the problem, don't
know enough about the subject to be sure if it's a bug or not.
Final:Closed. Out of date.
By: doerwalter
Summary: test_atexit fails in directories with spaces
Group:2.2.2
Bug #:705792
Verified: 15-Jan-2005
Action: Closing as Fixed (was fixed already).
Final:-
By: -
Summary: --without-cxx flag of configure
[Python-Dev] Old Python version categories in Bug Tracker
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 nowadays doesn't make sense to open a bug in these categories. As an infortunate example, somebody opened today a bug in the "Python 2.2" category, :( What do you think? Thanks. .Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Old Python version categories in Bug Tracker
> 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 ask SF support to do it, as nowadays doesn't make sense to open > a bug in these categories. > > As an infortunate example, somebody opened today a bug in the "Python > 2.2" category, :( > > What do you think? 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. Raymond ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Deprecating old bugs, now from 2.2.2
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 list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Deprecating old bugs, now from 2.2.2
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 well used day from my vacations, ;) Anyway, thank you very much, and keep doing *your* good work (of which I'm not nearly capable). Regards, .Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Old Python version categories in Bug Tracker
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 describe them. So "Python 2.2.2" can become "Python 2.2.2 (unmaintained)". Whether this is desirable or not, I'm not sure. -Fred -- Fred L. Drake, Jr. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Old Python version categories in Bug Tracker
"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 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. One can also create a new group for "really old stuff", place a comment that describes the original group (something like "PreviousGroup..."), then when closing/wont fix/etc., move the object into the new group. Then we can rename/reuse those 2.1 and 2.2 categories as desired. If one wants to search for items that used to be in some group, one can use the search functionality of sourceforge. Pain in the rear, but it is a solution to the 'problem' of having 2.1 and 2.2 groups. - Josiah P.S. I personally wouldn't do this; I would rename as Fred suggests. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Old Python version categories in Bug Tracker
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 (aka "this list", ;) took the decision of deprecate old bugs (more than one version to the past, <=2.2.* at this moment) if original poster or commenters didn't update them. So, I think is fair enough to inform people in that way when they want to post a bug to that versions. Opinions? Thanks! .Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Old Python version categories in Bug Tracker
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 categories/groups were marked unusable for new submissions. But that's not necessary in any way. -Fred -- Fred L. Drake, Jr. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Old Python version categories in Bug Tracker
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. > > > +1 for this solution. > +1 from me as well. -Brett ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
