From amk at amk.ca  Sat Oct  4 22:41:19 2008
From: amk at amk.ca (A.M. Kuchling)
Date: Sat, 4 Oct 2008 16:41:19 -0400
Subject: [Tracker-discuss] bugs.jython.com URL
Message-ID: <20081004204119.GB23839@amk.local>

The Jython bug tracker is at bugs.jython.org.  The PSF has both
jython.org and jython.com, and someone has just noted that
bugs.jython.com shows the CPython bug tracker.  It's probably just a
matter of adding 'ServerName bugs.jython.com' to the right stanza in
the httpd config for the bug tracker survey; could someone please do
this?  (Obviously this is very low priority, since the Jython bugs are
perfectly accessible right now.)

Thanks!

--amk

From martin at v.loewis.de  Sun Oct  5 07:35:50 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sun, 05 Oct 2008 07:35:50 +0200
Subject: [Tracker-discuss] bugs.jython.com URL
In-Reply-To: <20081004204119.GB23839@amk.local>
References: <20081004204119.GB23839@amk.local>
Message-ID: <48E85236.2060406@v.loewis.de>

A.M. Kuchling wrote:
> The Jython bug tracker is at bugs.jython.org.  The PSF has both
> jython.org and jython.com, and someone has just noted that
> bugs.jython.com shows the CPython bug tracker.  It's probably just a
> matter of adding 'ServerName bugs.jython.com' to the right stanza in
> the httpd config for the bug tracker survey; could someone please do
> this?  

I don't think you can have a second ServerName declaration, so I added
a ServerAlias directive instead.

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Fri Oct 10 10:49:48 2008
From: metatracker at psf.upfronthosting.co.za (roland rehmnert)
Date: Fri, 10 Oct 2008 08:49:48 +0000
Subject: [Tracker-discuss] [issue223] xml.etree.ElementTree does not read
	xml-text over page bonderies
In-Reply-To: <1223628588.47.0.433576993297.issue223@psf.upfronthosting.co.za>
Message-ID: <1223628588.47.0.433576993297.issue223@psf.upfronthosting.co.za>


New submission from roland rehmnert <roland.rehmnert at ericsson.com>:

xml text fields are not read properly when it is encountered in a 'start' event.

During a 'start'-event elem.text returns None, if the text string cross a page
boundary of the file. (this is platform dependent and a typical value is 8K
(8192 byte)).  



This line cause an error if the page size is 8192.
<a>this is a text where X has position 8192 in the file</a>

In most cases this erroneous behaviour can be avoid when elem.tree always return
the proper value at the 'end'-event.   


Two files are submitted:
bug.py: An excerpted file that produced an error with the submitted xml file.
bug.xml: An xml file, a little bit more then 8200 bytes. In can of the page size
is greater than 8K.. file should be enlarged. Important is however that the text
should cross the page boundary. Tags and attributes and attribute values as well
are OK

 
I might have misunderstood the documentation of etree, because there are
situations that I have not tested.
/roland

----------
messages: 1110
nosy: roland
priority: bug
status: unread
title: xml.etree.ElementTree does not read xml-text over page bonderies

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 10 16:15:01 2008
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Fri, 10 Oct 2008 14:15:01 +0000
Subject: [Tracker-discuss] [issue223] xml.etree.ElementTree does not read
	xml-text over page bonderies
In-Reply-To: <1223628588.47.0.433576993297.issue223@psf.upfronthosting.co.za>
Message-ID: <1223648101.35.0.169746310698.issue223@psf.upfronthosting.co.za>


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

This is a bug report for Python, right? As such, it should go to
http://bugs.python.org/.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Oct 13 13:23:36 2008
From: metatracker at psf.upfronthosting.co.za (Nick Coghlan)
Date: Mon, 13 Oct 2008 11:23:36 +0000
Subject: [Tracker-discuss] [issue224] "Search in All Issues" button
In-Reply-To: <1223897016.78.0.0580124380517.issue224@psf.upfronthosting.co.za>
Message-ID: <1223897016.78.0.0580124380517.issue224@psf.upfronthosting.co.za>


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

The quick in the top right corner for searching open issues is handy, but it
would be good if there were a "Search in All Issues" button as well. When
checking to see if something has already been reported, you also want to know if
it has been reported *and* fixed (or rejected) already.

----------
messages: 1112
nosy: ncoghlan
priority: feature
status: unread
title: "Search in All Issues" button

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

From metatracker at psf.upfronthosting.co.za  Mon Oct 13 13:24:52 2008
From: metatracker at psf.upfronthosting.co.za (Nick Coghlan)
Date: Mon, 13 Oct 2008 11:24:52 +0000
Subject: [Tracker-discuss] [issue224] "Search in All Issues" button
In-Reply-To: <1223897016.78.0.0580124380517.issue224@psf.upfronthosting.co.za>
Message-ID: <1223897092.53.0.212900964913.issue224@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

There's a word missing in that first sentence: I meant the quick search in the
top right corner of the main bug tracker.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Oct 13 23:21:42 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Mon, 13 Oct 2008 21:21:42 +0000
Subject: [Tracker-discuss] [issue224] "Search in All Issues" button
In-Reply-To: <1223897016.78.0.0580124380517.issue224@psf.upfronthosting.co.za>
Message-ID: <1223932902.13.0.916026755408.issue224@psf.upfronthosting.co.za>


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

Are you aware that you can search in all issues already, with just three clicks?

Wouldn't another button clutter the interface?

FWIW, attached is a stand-alone html file which provides the interface you
request. Maybe it's sufficient if you save it to disk, and add a quick link to
it in your browser.

----------
nosy: +loewis

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue224>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20081013/940a7dd3/attachment.html>

From metatracker at psf.upfronthosting.co.za  Mon Oct 13 23:31:04 2008
From: metatracker at psf.upfronthosting.co.za (Nick Coghlan)
Date: Mon, 13 Oct 2008 21:31:04 +0000
Subject: [Tracker-discuss] [issue224] "Search in All Issues" button
In-Reply-To: <1223897016.78.0.0580124380517.issue224@psf.upfronthosting.co.za>
Message-ID: <1223933464.98.0.628575365757.issue224@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

I know how to do the full search* because I use the tracker all the time - but
the 3 clicks needed are highly non-obvious, especially compared to the big
"Search in Open Issues" button. Also, as a bug fixer rather than bug reporter, I
tend to be mainly interested in the open issues anyway.

The in-your-face option to search all issues would be for people coming to the
tracker to report a bug for the first time that want to know if this is
something that has already been reported (and possibly closed), and for those
checking if new issues are duplicates of existing ones. (This came up for me
recently when I was looking for issue 2751 after getting an email from someone
that had been relying on the runpy package execution bug in 2.5 about the fact
that you can't do that anymore in 2.6)

If you're worried about interface clutter, then I would suggest *changing* the
button to a "search in all issues" button, and then on that results page have a
"show only open issues from these results" button.

*(I think the full search interface is actually fairly horrible, because the
layout of the search fields bears no resemblance to the layout of the issues
detail pages and there is no attempt to make the 'common' search fields more
prominent)

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

From metatracker at psf.upfronthosting.co.za  Tue Oct 14 00:09:24 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Mon, 13 Oct 2008 22:09:24 +0000
Subject: [Tracker-discuss] [issue224] "Search in All Issues" button
In-Reply-To: <1223933464.98.0.628575365757.issue224@psf.upfronthosting.co.za>
Message-ID: <48F3C712.4050000@v.loewis.de>


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

> *(I think the full search interface is actually fairly horrible, because the
> layout of the search fields bears no resemblance to the layout of the issues
> detail pages and there is no attempt to make the 'common' search fields more
> prominent)

Would you like to contribute a different layout? The search form is in

https://svn.python.org/projects/tracker/instances/python-dev/html/issue.search.html

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

From metatracker at psf.upfronthosting.co.za  Tue Oct 14 00:12:06 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Mon, 13 Oct 2008 22:12:06 +0000
Subject: [Tracker-discuss] [issue224] "Search in All Issues" button
In-Reply-To: <1223933464.98.0.628575365757.issue224@psf.upfronthosting.co.za>
Message-ID: <48F3C7B4.1010503@v.loewis.de>


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

> If you're worried about interface clutter, then I would suggest *changing* the
> button to a "search in all issues" button, and then on that results page have a
> "show only open issues from these results" button.

This was actually on my request, when I asked that the search, by
default, should ignore closed issues. I still think this is the better
choice.

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

From metatracker at psf.upfronthosting.co.za  Mon Oct 27 20:09:16 2008
From: metatracker at psf.upfronthosting.co.za (Alan Kennedy)
Date: Mon, 27 Oct 2008 19:09:16 +0000
Subject: [Tracker-discuss] [issue225] Ordering of messages is incorrect for
	some jython issues.
In-Reply-To: <1225134556.68.0.873773412263.issue225@psf.upfronthosting.co.za>
Message-ID: <1225134556.68.0.873773412263.issue225@psf.upfronthosting.co.za>


New submission from Alan Kennedy <jython-dev at xhaus.com>:

Some of the issues in the jython tracker list the messages in the wrong order.
Messages should be listed in time and date order, but in some cases are not.
Below is a link to an example; the (unknown) ordering of the messages makes it
difficult to follow what's happened with the issue.

http://bugs.jython.com/issue1018

----------
messages: 1118
nosy: amak
priority: bug
status: unread
title: Ordering of messages is incorrect for some jython issues.

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