From metatracker at psf.upfronthosting.co.za  Sun Jan  2 06:09:43 2011
From: metatracker at psf.upfronthosting.co.za (Naresh)
Date: Sun, 02 Jan 2011 05:09:43 +0000
Subject: [Tracker-discuss] [issue366] problem while accessing value using
	the slice operator []
In-Reply-To: <1293944983.08.0.859352416727.issue366@psf.upfronthosting.co.za>
Message-ID: <1293944983.08.0.859352416727.issue366@psf.upfronthosting.co.za>


New submission from Naresh <naresh_kumar23736 at yahoo.com>:

example : list=['abcd', 786 , 2.23, 'john', 70.2 ]
          print list[0:-1]
      output:      ['abcd', 786 , 2.23, 'john']
is this expected behavior because list[0:-1] is supposed to print list from starting to end but this is not happening

----------
messages: 1884
nosy: naresh_kumar23736 at yahoo.com
priority: bug
status: unread
title: problem while accessing value using the slice operator []

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue366>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jan  2 14:21:35 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 02 Jan 2011 13:21:35 +0000
Subject: [Tracker-discuss] [issue366] problem while accessing value using
	the slice operator []
In-Reply-To: <1293944983.08.0.859352416727.issue366@psf.upfronthosting.co.za>
Message-ID: <1293974495.96.0.402263421457.issue366@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Hi, this is the meta bug tracker where to report bugs of the Python bug tracker at bugs.python.org. If you have Python questions you should ask them on python-list. If you have found a Python bug you can report it at bugs.python.org.
What you found is not a bug though:
>>> l = ['abcd', 786, 2.23, 'john', 70.2]
>>> l[-1]
70.2
>>> l[4]
70.2
>>> l[0:-1]
['abcd', 786, 2.23, 'john']
>>> l[0:4]
['abcd', 786, 2.23, 'john']
>>> l[:4]
['abcd', 786, 2.23, 'john']
As you can see the first value is included, but the last is excluded.

----------
assignedto:  -> ezio.melotti
nosy: +ezio.melotti
status: unread -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue366>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Jan  3 20:46:30 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Mon, 03 Jan 2011 19:46:30 +0000
Subject: [Tracker-discuss] [issue367] "patch" keyword buggy
In-Reply-To: <1294083990.85.0.867391324355.issue367@psf.upfronthosting.co.za>
Message-ID: <1294083990.85.0.867391324355.issue367@psf.upfronthosting.co.za>


New submission from Antoine Pitrou <pitrou at free.fr>:

The "patch" keyword stays enabled even when all patch files have been removed from the issue. See http://bugs.python.org/issue2394 for an example.

----------
messages: 1886
nosy: ezio.melotti, pitrou
priority: bug
status: unread
title: "patch" keyword buggy

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue367>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Jan  3 20:48:12 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Mon, 03 Jan 2011 19:48:12 +0000
Subject: [Tracker-discuss] [issue368] "nosy" field displayed in history
	items even when not	changed
In-Reply-To: <1294084092.36.0.972141940732.issue368@psf.upfronthosting.co.za>
Message-ID: <1294084092.36.0.972141940732.issue368@psf.upfronthosting.co.za>


New submission from Antoine Pitrou <pitrou at free.fr>:

In an issue's history (bottom at the page), the nosy field often gets displayed on all history items even when it hasn't been changed.
See http://bugs.python.org/issue1674555 for an example.

----------
messages: 1887
nosy: ezio.melotti, pitrou
priority: bug
status: unread
title: "nosy" field displayed in history items even when not changed

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue368>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Jan  3 21:13:30 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 03 Jan 2011 20:13:30 +0000
Subject: [Tracker-discuss] [issue367] "patch" keyword buggy
In-Reply-To: <1294083990.85.0.867391324355.issue367@psf.upfronthosting.co.za>
Message-ID: <1294085610.0.0.744589274374.issue367@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

That's intentional or at least unavoidable. There is no automatic procedure to clear the keyword, and it isn't obvious that there should be one: it may be that a patch is in one of the messages, and/or that the keyword was manually assigned.

----------
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue367>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Jan  3 21:18:12 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Mon, 03 Jan 2011 20:18:12 +0000
Subject: [Tracker-discuss] [issue367] "patch" keyword buggy
In-Reply-To: <1294085610.0.0.744589274374.issue367@psf.upfronthosting.co.za>
Message-ID: <1294085889.3703.6.camel@localhost.localdomain>


Antoine Pitrou <pitrou at free.fr> added the comment:

> That's intentional or at least unavoidable. There is no automatic
> procedure to clear the keyword, and it isn't obvious that there should
> be one: it may be that a patch is in one of the messages, and/or that
> the keyword was manually assigned.

The problem is that when you try to clear the keyword manually, it
doesn't work.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue367>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Jan  4 12:14:21 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Tue, 04 Jan 2011 11:14:21 +0000
Subject: [Tracker-discuss] [issue369] email gateway refused comment posting
In-Reply-To: <1294139661.38.0.206757900841.issue369@psf.upfronthosting.co.za>
Message-ID: <1294139661.38.0.206757900841.issue369@psf.upfronthosting.co.za>


New submission from Antoine Pitrou <pitrou at free.fr>:

This is because I replied to an issue which has square brackets in its title. Apparently it confuses roundup:

?There were problems handling your subject line argument list:
- not of form [arg=value,value,...;arg=value,value,...]

Subject was: "Re: [issue8458] buildbot: test_cmd_line failure on Tiger: [Errno 9] Bad file descriptor"?


Perhaps a simple matter of greedy/non-greedy regex?

----------
messages: 1890
nosy: ezio.melotti, loewis, pitrou
priority: bug
status: unread
title: email gateway refused comment posting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue369>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Jan  4 12:48:46 2011
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Tue, 04 Jan 2011 11:48:46 +0000
Subject: [Tracker-discuss] [issue369] email gateway refused comment posting
In-Reply-To: <1294139661.38.0.206757900841.issue369@psf.upfronthosting.co.za>
Message-ID: <1294141726.97.0.735532436159.issue369@psf.upfronthosting.co.za>


Georg Brandl <g.brandl at gmx.net> added the comment:

This is a roundup issue, not a Python tracker issue, isn't it?

----------
nosy: +gbrandl
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue369>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Jan  4 12:54:42 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Tue, 04 Jan 2011 11:54:42 +0000
Subject: [Tracker-discuss] [issue369] email gateway refused comment posting
In-Reply-To: <1294141726.97.0.735532436159.issue369@psf.upfronthosting.co.za>
Message-ID: <1294142079.3669.3.camel@localhost.localdomain>


Antoine Pitrou <pitrou at free.fr> added the comment:

> This is a roundup issue, not a Python tracker issue, isn't it?

Yes, certainly.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue369>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jan  7 18:01:02 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 07 Jan 2011 17:01:02 +0000
Subject: [Tracker-discuss] [issue370] duplicates are not linked to master
	ticket
In-Reply-To: <1294419662.73.0.58109750607.issue370@psf.upfronthosting.co.za>
Message-ID: <1294419662.73.0.58109750607.issue370@psf.upfronthosting.co.za>


New submission from anatoly techtonik <techtonik at gmail.com>:

User story:
It is useful to look at bug duplicates when exploring an issue. Unfortunately, ticket headers doesn't allow to evaluate how many duplicates a bug has.

Test:
Master issue http://bugs.python.org/issue1559549 doesn't have links to its duplicate http://bugs.python.org/issue10857

----------
messages: 1893
nosy: techtonik
priority: bug
status: unread
title: duplicates are not linked to master ticket

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue370>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jan  7 18:06:51 2011
From: metatracker at psf.upfronthosting.co.za (Eric Smith)
Date: Fri, 07 Jan 2011 17:06:51 +0000
Subject: [Tracker-discuss] [issue370] master ticket is not linked to its
	duplicates
In-Reply-To: <1294419662.73.0.58109750607.issue370@psf.upfronthosting.co.za>
Message-ID: <1294420011.3.0.594374261567.issue370@psf.upfronthosting.co.za>


Eric Smith <eric at trueblade.com> added the comment:

The superceders are listed at the bottom, in the history.

----------
nosy: +eric.smith
status: unread -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue370>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jan  9 22:51:13 2011
From: metatracker at psf.upfronthosting.co.za (Teodor Georgiev)
Date: Sun, 09 Jan 2011 21:51:13 +0000
Subject: [Tracker-discuss] [issue371] asyncore does not react properly on
	close()
In-Reply-To: <1294609873.48.0.956135825436.issue371@psf.upfronthosting.co.za>
Message-ID: <1294609873.48.0.956135825436.issue371@psf.upfronthosting.co.za>


New submission from Teodor Georgiev <lv_tokata at yahoo.com>:

Python 2.7.1
I am trying to add a simple timer to each created socket and destroy it
once the timer expires:

class client(asyncore.dispatcher):
    def __init__(self,host):
    ...
    self.timeout = time.time() + 5

    def readable(self):
        if time.time() >= self.timeout:
            self.close()
        return True

When running that code, it raises an exception:

 asyncore.loop(timeout=0.8)
  File "/usr/lib/python2.6/asyncore.py", line 211, in loop
    poll_fun(timeout)
  File "/usr/lib/python2.6/asyncore.py", line 144, in poll
    raise
  File "/usr/lib/python2.6/asyncore.py", line 141, in poll
    r, w, e = select.select(r, w, e, timeout)
select.error: (9, 'Bad file descriptor')


Although del_channel is executed properly and the socket is removed from the map, the poll function is not updated with that info and continues to keep the socket into the r,w,e.

----------
assignedto: giampaolo.rodola
messages: 1895
nosy: giampaolo.rodola, tgeorgiev
priority: bug
status: unread
title: asyncore does not react properly on close()

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue371>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Jan 10 00:30:30 2011
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Sun, 09 Jan 2011 23:30:30 +0000
Subject: [Tracker-discuss] [issue371] asyncore does not react properly on
	close()
In-Reply-To: <1294609873.48.0.956135825436.issue371@psf.upfronthosting.co.za>
Message-ID: <1294615830.91.0.983881022286.issue371@psf.upfronthosting.co.za>


Brett C. <brett at python.org> added the comment:

This is the meta issue tracker for bugs *about* bugs.python.org. To file a bug against Python, file them *at* bugs.python.org.

----------
nosy: +brett.cannon
status: unread -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue371>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Jan 12 10:52:13 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 12 Jan 2011 09:52:13 +0000
Subject: [Tracker-discuss] [issue367] "patch" keyword buggy
In-Reply-To: <1294083990.85.0.867391324355.issue367@psf.upfronthosting.co.za>
Message-ID: <1294825933.91.0.123225771513.issue367@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I think I removed a patch keyword recently.  Antoine, is that a form UI issue?  Does it work with other keywords but not patch?  Can you open a test report to test?

----------
nosy: +eric.araujo

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue367>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Jan 12 23:44:28 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Wed, 12 Jan 2011 22:44:28 +0000
Subject: [Tracker-discuss] [issue367] "patch" keyword buggy
In-Reply-To: <1294083990.85.0.867391324355.issue367@psf.upfronthosting.co.za>
Message-ID: <1294872268.83.0.877019567159.issue367@psf.upfronthosting.co.za>


R David Murray <rdmurray at bitdance.com> added the comment:

I seem to remember that the only way to remove all keywords (ie: remove the last one) is to select '- no selection -'.  I think there might be a bug report about that, but I'm not sure.

----------
nosy: +r.david.murray

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue367>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jan 30 13:43:46 2011
From: metatracker at psf.upfronthosting.co.za (Nick Coghlan)
Date: Sun, 30 Jan 2011 12:43:46 +0000
Subject: [Tracker-discuss] [issue372] Default search missed matching issue
	title for "capi"
In-Reply-To: <1296391426.25.0.112828803106.issue372@psf.upfronthosting.co.za>
Message-ID: <1296391426.25.0.112828803106.issue372@psf.upfronthosting.co.za>


New submission from Nick Coghlan <ncoghlan at gmail.com>:

>From http://posted-stuff.blogspot.com/2011/01/bug-reporting-energy-depleted.html

The author of that blog post tried to search for "capi" to see if a particular crash had already been reported. The default search and a search in all fields failed to find it, but a search specifically in the title text found it.

Default search:
http://bugs.python.org/issue?%40columns=id,activity,title,creator,assignee,status,type&%40sort=-activity&%40filter=status&%40action=searchid&ignore=file:content&%40search_text=capi&submit=search&status=-1,1,2,3

All text:
http://bugs.python.org/issue?%40search_text=capi&ignore=file:content&title=&%40columns=title&id=&%40columns=id&stage=&creation=&creator=&activity=&%40columns=activity&%40sort=activity&actor=&nosy=&type=&components=&versions=&dependencies=&assignee=&keywords=&priority=&%40group=priority&status=1&%40columns=status&resolution=&nosy_count=&message_count=&%40pagesize=50&%40startwith=0&%40queryname=&%40old-queryname=&%40action=search

Title only:
http://bugs.python.org/issue?%40search_text=&ignore=file:content&title=capi&%40columns=title&id=&%40columns=id&stage=&creation=&creator=&activity=&%40columns=activity&%40sort=activity&actor=&nosy=&type=&components=&versions=&dependencies=&assignee=&keywords=&priority=&%40group=priority&status=1&%40columns=status&resolution=&nosy_count=&message_count=&%40pagesize=50&%40startwith=0&%40queryname=&%40old-queryname=&%40action=search

----------
messages: 1899
nosy: ncoghlan
priority: urgent
status: unread
title: Default search missed matching issue title for "capi"

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue372>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Jan 31 17:46:40 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Mon, 31 Jan 2011 16:46:40 +0000
Subject: [Tracker-discuss] [issue372] Default search missed matching issue
	title for "capi"
In-Reply-To: <1296391426.25.0.112828803106.issue372@psf.upfronthosting.co.za>
Message-ID: <1296492400.65.0.0234548618938.issue372@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Google Search for roundup?

----------
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue372>
_______________________________________________________