From metatracker at psf.upfronthosting.co.za  Mon Dec  3 21:23:03 2012
From: metatracker at psf.upfronthosting.co.za (Serhiy Storchaka)
Date: Mon, 03 Dec 2012 20:23:03 +0000
Subject: [Tracker-discuss] [issue494] Odd rendering of link containing issue
	ID
Message-ID: <1354566183.45.0.381120361305.issue494@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

When message contains link which contains issueXXX then it rendered odd.

See for example http://bugs.python.org/issue16569#msg176850.

----------
messages: 2661
nosy: serhiy.storchaka
priority: bug
status: unread
title: Odd rendering of link containing issue ID

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

From metatracker at psf.upfronthosting.co.za  Mon Dec  3 21:25:30 2012
From: metatracker at psf.upfronthosting.co.za (Serhiy Storchaka)
Date: Mon, 03 Dec 2012 20:25:30 +0000
Subject: [Tracker-discuss] [issue494] Odd rendering of link containing issue
	ID
In-Reply-To: <1354566183.45.0.381120361305.issue494@psf.upfronthosting.co.za>
Message-ID: <1354566330.94.0.792842502005.issue494@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Test:

http://bugs.python.org/file24624/Proposed-fix-of-issue14099-second.patch

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

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

From metatracker at psf.upfronthosting.co.za  Mon Dec  3 21:27:22 2012
From: metatracker at psf.upfronthosting.co.za (Serhiy Storchaka)
Date: Mon, 03 Dec 2012 20:27:22 +0000
Subject: [Tracker-discuss] [issue494] Odd rendering of link containing issue
	ID
In-Reply-To: <1354566183.45.0.381120361305.issue494@psf.upfronthosting.co.za>
Message-ID: <1354566442.07.0.590951631152.issue494@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

On this tracker the bug is not reproduced.

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

From techtonik at gmail.com  Mon Dec  3 21:55:37 2012
From: techtonik at gmail.com (anatoly techtonik)
Date: Mon, 3 Dec 2012 23:55:37 +0300
Subject: [Tracker-discuss] [issue494] Odd rendering of link containing
 issue ID
In-Reply-To: <1354566183.45.0.381120361305.issue494@psf.upfronthosting.co.za>
References: <1354566183.45.0.381120361305.issue494@psf.upfronthosting.co.za>
Message-ID: <CAPkN8xL0_xCEpVELC+s7N+XsnwvL0NYXBr6fk7sTm6PNdL0kwA@mail.gmail.com>

The Roundup message filters are not designed to be manageable, so it is
just a mess of conflicting hacks. I'd think about proper message filtering
API in Roundup, to gain some control over processing message text before it
is piped to the stdout and test the linking logic separately (in fact I'd
just rip and paste Trac code if not the license).

-- 
anatoly t.


On Mon, Dec 3, 2012 at 11:23 PM, Serhiy Storchaka <
metatracker at psf.upfronthosting.co.za> wrote:

>
> New submission from Serhiy Storchaka:
>
> When message contains link which contains issueXXX then it rendered odd.
>
> See for example http://bugs.python.org/issue16569#msg176850.
>
> ----------
> messages: 2661
> nosy: serhiy.storchaka
> priority: bug
> status: unread
> title: Odd rendering of link containing issue ID
>
> _______________________________________________________
> PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue494>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20121203/d6078f17/attachment.html>

From metatracker at psf.upfronthosting.co.za  Mon Dec  3 21:55:59 2012
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Mon, 03 Dec 2012 20:55:59 +0000
Subject: [Tracker-discuss] [issue494] Odd rendering of link containing issue
	ID
In-Reply-To: <1354566183.45.0.381120361305.issue494@psf.upfronthosting.co.za>
Message-ID: <CAPkN8xL0_xCEpVELC+s7N+XsnwvL0NYXBr6fk7sTm6PNdL0kwA@mail.gmail.com>


anatoly techtonik added the comment:

The Roundup message filters are not designed to be manageable, so it is
just a mess of conflicting hacks. I'd think about proper message filtering
API in Roundup, to gain some control over processing message text before it
is piped to the stdout and test the linking logic separately (in fact I'd
just rip and paste Trac code if not the license).

-- 
anatoly t.

On Mon, Dec 3, 2012 at 11:23 PM, Serhiy Storchaka <
metatracker at psf.upfronthosting.co.za> wrote:

>
> New submission from Serhiy Storchaka:
>
> When message contains link which contains issueXXX then it rendered odd.
>
> See for example http://bugs.python.org/issue16569#msg176850.
>
> ----------
> messages: 2661
> nosy: serhiy.storchaka
> priority: bug
> status: unread
> title: Odd rendering of link containing issue ID
>
> _______________________________________________________
> PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue494>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

----------
nosy: +techtonik

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

From techtonik at gmail.com  Wed Dec 12 10:14:21 2012
From: techtonik at gmail.com (anatoly techtonik)
Date: Wed, 12 Dec 2012 12:14:21 +0300
Subject: [Tracker-discuss] Python is not perfect - let's add 'Wart' status
	to track
Message-ID: <CAPkN8xJBteq_eMAO=OyMqbG1vGCE5XkWm_nnLhUonR1ZDHUBww@mail.gmail.com>

I want to query all warts for specific Python 2.x versions to see how are
they fixed in 3.x.

Right now these warts are hidden beneath the "invalid" labels, which IMHO
does as much damage to the language development as BC breaks.

How about adding 'Wart' resolution to the closed status on tracker?
-- 
anatoly t.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20121212/e665776c/attachment.html>

From metatracker at psf.upfronthosting.co.za  Fri Dec 14 11:54:45 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 14 Dec 2012 10:54:45 +0000
Subject: [Tracker-discuss] [issue494] Odd rendering of link containing issue
	ID
In-Reply-To: <1354566183.45.0.381120361305.issue494@psf.upfronthosting.co.za>
Message-ID: <1355482485.66.0.863458776394.issue494@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed in http://hg.python.org/tracker/python-dev/rev/eea8386b9040, thanks for the report!

Anatoly, how does trac do it?
ISTM that the only way to prevent this is to build the DOM of the message and avoid applying regex that create links to text nodes that are already inside an <a></a>.

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

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

From metatracker at psf.upfronthosting.co.za  Fri Dec 14 13:09:13 2012
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 14 Dec 2012 12:09:13 +0000
Subject: [Tracker-discuss] [issue494] Odd rendering of link containing issue
	ID
In-Reply-To: <1355482485.66.0.863458776394.issue494@psf.upfronthosting.co.za>
Message-ID: <CAPkN8xJodsTa0CDdjz8+eL2OZpsR4U+8n=SnS5VXj9gtxCSwuA@mail.gmail.com>


anatoly techtonik added the comment:

On Fri, Dec 14, 2012 at 1:54 PM, Ezio Melotti <
metatracker at psf.upfronthosting.co.za> wrote:
>
> Anatoly, how does trac do it?
> ISTM that the only way to prevent this is to build the DOM of the message
> and avoid applying regex that create links to text nodes that are already
> inside an <a></a>.
>

Not about Trac, but it is also possible to prevent regex conflicts without
the DOM by excluding matched and replaced regions from processing. For
example, if my regex linkified bug link in the text "see issue 494 on this
tracker", then the subsequent regexp will be called on remaining text parts
separately, i.e. `for text in ["see ", " on this tracker"]`. There just
needs to be a component that manages this process and reconstructs final
text from the pieces.

Now about Trac. The interface description is not very helpful about the
substitution, but it is here (get_wiki_syntax is the key point):
http://trac.edgewall.org/wiki/TracDev/PluginDevelopment/ExtensionPoints/trac.wiki.api.IWikiSyntaxProvider
>From this description: plugins add their regexps and callback functions,
and then Wiki engine matches regex, it calls corresponding callback on the
text that matched and expects this callback to return expanded HTML. I
don't know if matched text is excluded from further processing, but it only
seems  logical to do so.

This page lists pointers to various proposals that could be useful:
http://trac.edgewall.org/wiki/WikiEngine

----------
status: resolved -> chatting

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

From techtonik at gmail.com  Wed Dec 19 13:54:16 2012
From: techtonik at gmail.com (anatoly techtonik)
Date: Wed, 19 Dec 2012 15:54:16 +0300
Subject: [Tracker-discuss] Summary page
Message-ID: <CAPkN8xLe0x0eriG7QaXxEjUAWEuyvrOHDci2XL1q2gxko243Tg@mail.gmail.com>

CC: tracker-discuss at python.org

What is required to add a summary page "amount of bugs per component" to
http://bugs.python.org/ ?

The main question on this stage:
How to add an new URL at http://bugs.python.org/summary ?
-- 
anatoly t.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20121219/86729efd/attachment.html>

From metatracker at psf.upfronthosting.co.za  Wed Dec 26 12:33:58 2012
From: metatracker at psf.upfronthosting.co.za (Naresh)
Date: Wed, 26 Dec 2012 11:33:58 +0000
Subject: [Tracker-discuss] [issue495] Jython is not working in HP and IBM
	platforms
Message-ID: <1356521638.05.0.978794110345.issue495@psf.upfronthosting.co.za>


New submission from Naresh:

I am trying to use the Jython in IBM AIX and HP machines to test our framework which is based on JAVA.
when trying to run our python and jython based testcases using system test framework we are getting below errors in jython.err file

Error: could not find libjava.so
Error: could not find Java 2 Runtime Environment.? (Shared library of java)


Trying to find in online whether jython is supported on these two platforms HP and IBM and i could not able to get proper info.

----------
messages: 2667
nosy: knettem
priority: bug
status: unread
title: Jython is not working in HP and IBM platforms

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

From metatracker at psf.upfronthosting.co.za  Wed Dec 26 13:44:28 2012
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Wed, 26 Dec 2012 12:44:28 +0000
Subject: [Tracker-discuss] [issue495] Jython is not working in HP and IBM
	platforms
In-Reply-To: <1356521638.05.0.978794110345.issue495@psf.upfronthosting.co.za>
Message-ID: <1356525868.8.0.816545617143.issue495@psf.upfronthosting.co.za>


R David Murray added the comment:

This is the issue tracker for the python.org issue trackers (the "metatracker").  jython's issue tracker is at bugs.jython.org.  However, your question isn't really appropriate for an issue tracker, you are better off posting it to the jython mailing list (jython-users at lists.sourceforge.net, see www.jython.org).

----------
nosy: +r.david.murray
status: unread -> resolved

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

From metatracker at psf.upfronthosting.co.za  Wed Dec 26 13:49:45 2012
From: metatracker at psf.upfronthosting.co.za (Naresh)
Date: Wed, 26 Dec 2012 12:49:45 +0000
Subject: [Tracker-discuss] [issue495] Jython is not working in HP and IBM
	platforms
In-Reply-To: <1356525868.8.0.816545617143.issue495@psf.upfronthosting.co.za>
Message-ID: <SNT002-W6961D3919EDFB8D6E09C1CEC390@phx.gbl>


Naresh added the comment:

Hi Murray,

I have sent an e-mail to the jython-users mailing list and getting the following reply

Your mail to 'Jython-users' with the subject

    RE: Regarding Jython support in IBM and HP platforms

Is being held until the list moderator can review it for approval.

The reason it is being held:

    Post by non-member to a members-only list

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.  If you would like to cancel
this posting, please visit the following URL:

    https://lists.sourceforge.net/lists/confirm/jython-users/a64d302a57a1cea6f309b7d58d9a835ebc681a1d

so how to become as member to the jython mailing list , if u have any idea please reply.

Thanks,
Naresh.

> Subject: [issue495] Jython is not working in HP and IBM platforms
> To: n.nareshkumar at hotmail.com
> From: metatracker at psf.upfronthosting.co.za
> Date: Wed, 26 Dec 2012 12:44:29 +0000
> 
> 
> R David Murray added the comment:
> 
> This is the issue tracker for the python.org issue trackers (the "metatracker").  jython's issue tracker is at bugs.jython.org.  However, your question isn't really appropriate for an issue tracker, you are better off posting it to the jython mailing list (jython-users at lists.sourceforge.net, see www.jython.org).
> 
> ----------
> nosy: +r.david.murray
> status: unread -> resolved
> 
> _______________________________________________________
> PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue495>
> _______________________________________________________

----------
status: resolved -> chatting

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

From metatracker at psf.upfronthosting.co.za  Fri Dec 28 21:06:04 2012
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Fri, 28 Dec 2012 20:06:04 +0000
Subject: [Tracker-discuss] [issue495] Jython is not working in HP and IBM
	platforms
In-Reply-To: <SNT002-W6961D3919EDFB8D6E09C1CEC390@phx.gbl>
Message-ID: <CAP1=2W7ydt6JOMFBMJ0Hp7k_KMbmO=-DEKkOYZFJyTi=nqjV5Q@mail.gmail.com>


Brett C. added the comment:

You can subscribe at
https://lists.sourceforge.net/lists/listinfo/jython-users

On Wed, Dec 26, 2012 at 7:49 AM, Naresh <
metatracker at psf.upfronthosting.co.za> wrote:

>
> Naresh added the comment:
>
> Hi Murray,
>
> I have sent an e-mail to the jython-users mailing list and getting the
> following reply
>
> Your mail to 'Jython-users' with the subject
>
>     RE: Regarding Jython support in IBM and HP platforms
>
> Is being held until the list moderator can review it for approval.
>
> The reason it is being held:
>
>     Post by non-member to a members-only list
>
> Either the message will get posted to the list, or you will receive
> notification of the moderator's decision.  If you would like to cancel
> this posting, please visit the following URL:
>
>
> https://lists.sourceforge.net/lists/confirm/jython-users/a64d302a57a1cea6f309b7d58d9a835ebc681a1d
>
> so how to become as member to the jython mailing list , if u have any idea
> please reply.
>
> Thanks,
> Naresh.
>
> > Subject: [issue495] Jython is not working in HP and IBM platforms
> > To: n.nareshkumar at hotmail.com
> > From: metatracker at psf.upfronthosting.co.za
> > Date: Wed, 26 Dec 2012 12:44:29 +0000
> >
> >
> > R David Murray added the comment:
> >
> > This is the issue tracker for the python.org issue trackers (the
> "metatracker").  jython's issue tracker is at bugs.jython.org.  However,
> your question isn't really appropriate for an issue tracker, you are better
> off posting it to the jython mailing list (
> jython-users at lists.sourceforge.net, see www.jython.org).
> >
> > ----------
> > nosy: +r.david.murray
> > status: unread -> resolved
> >
> > _______________________________________________________
> > PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
> > <http://psf.upfronthosting.co.za/roundup/meta/issue495>
> > _______________________________________________________
>
> ----------
> status: resolved -> chatting
>
> _______________________________________________________
> PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue495>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

----------
nosy: +brett.cannon

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

From brett at python.org  Fri Dec 28 21:05:41 2012
From: brett at python.org (Brett Cannon)
Date: Fri, 28 Dec 2012 15:05:41 -0500
Subject: [Tracker-discuss] [issue495] Jython is not working in HP and
	IBM platforms
In-Reply-To: <SNT002-W6961D3919EDFB8D6E09C1CEC390@phx.gbl>
References: <1356525868.8.0.816545617143.issue495@psf.upfronthosting.co.za>
	<SNT002-W6961D3919EDFB8D6E09C1CEC390@phx.gbl>
Message-ID: <CAP1=2W7ydt6JOMFBMJ0Hp7k_KMbmO=-DEKkOYZFJyTi=nqjV5Q@mail.gmail.com>

You can subscribe at
https://lists.sourceforge.net/lists/listinfo/jython-users


On Wed, Dec 26, 2012 at 7:49 AM, Naresh <
metatracker at psf.upfronthosting.co.za> wrote:

>
> Naresh added the comment:
>
> Hi Murray,
>
> I have sent an e-mail to the jython-users mailing list and getting the
> following reply
>
> Your mail to 'Jython-users' with the subject
>
>     RE: Regarding Jython support in IBM and HP platforms
>
> Is being held until the list moderator can review it for approval.
>
> The reason it is being held:
>
>     Post by non-member to a members-only list
>
> Either the message will get posted to the list, or you will receive
> notification of the moderator's decision.  If you would like to cancel
> this posting, please visit the following URL:
>
>
> https://lists.sourceforge.net/lists/confirm/jython-users/a64d302a57a1cea6f309b7d58d9a835ebc681a1d
>
> so how to become as member to the jython mailing list , if u have any idea
> please reply.
>
> Thanks,
> Naresh.
>
> > Subject: [issue495] Jython is not working in HP and IBM platforms
> > To: n.nareshkumar at hotmail.com
> > From: metatracker at psf.upfronthosting.co.za
> > Date: Wed, 26 Dec 2012 12:44:29 +0000
> >
> >
> > R David Murray added the comment:
> >
> > This is the issue tracker for the python.org issue trackers (the
> "metatracker").  jython's issue tracker is at bugs.jython.org.  However,
> your question isn't really appropriate for an issue tracker, you are better
> off posting it to the jython mailing list (
> jython-users at lists.sourceforge.net, see www.jython.org).
> >
> > ----------
> > nosy: +r.david.murray
> > status: unread -> resolved
> >
> > _______________________________________________________
> > PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
> > <http://psf.upfronthosting.co.za/roundup/meta/issue495>
> > _______________________________________________________
>
> ----------
> status: resolved -> chatting
>
> _______________________________________________________
> PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue495>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20121228/e471b7e8/attachment.html>

From metatracker at psf.upfronthosting.co.za  Sun Dec 30 00:28:20 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 29 Dec 2012 23:28:20 +0000
Subject: [Tracker-discuss] [issue496] Update Roundup to 1.4.21
Message-ID: <1356823700.8.0.767986910654.issue496@psf.upfronthosting.co.za>


New submission from Ezio Melotti:

Roundup 1.4.21 has been released, so our instance should be updated.

----------
assignedto: ezio.melotti
messages: 2671
nosy: ezio.melotti
priority: feature
status: unread
title: Update Roundup to 1.4.21

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

From metatracker at psf.upfronthosting.co.za  Sun Dec 30 18:33:21 2012
From: metatracker at psf.upfronthosting.co.za (Serhiy Storchaka)
Date: Sun, 30 Dec 2012 17:33:21 +0000
Subject: [Tracker-discuss] [issue497] Resort "Assign To" list
Message-ID: <1356888801.68.0.806413565727.issue497@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

1. "Assign To" list should be sorted case-insensitively. Currently there are some names which starts from upper letter at a top of the list.

2. Self name should be at a top of "Assign To" list, right below "nobody" item.

----------
messages: 2672
nosy: serhiy.storchaka
priority: feature
status: unread
title: Resort "Assign To" list

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