From metatracker at psf.upfronthosting.co.za  Sat May  2 18:17:53 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Sat, 02 May 2009 16:17:53 +0000
Subject: [Tracker-discuss] [issue279] Removing a message sends an empty
	changenote to nosy users
In-Reply-To: <1241281073.6.0.853732988237.issue279@psf.upfronthosting.co.za>
Message-ID: <1241281073.6.0.853732988237.issue279@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

Ezio Melotti reports that when a message is removed from an issue, an email with
an empty changenote is sent.

The attached patch avoids sending it to the nosy list, but still sends the email
to busybody. It would be easy to include 'Removed message:' with links instead
if that is considered better.

----------
files: msg_removal.diff
messages: 1385
nosy: ajaksu2
priority: bug
status: unread
title: Removing a message sends an empty changenote to nosy users

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue279>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: msg_removal.diff
Type: text/x-diff
Size: 1077 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090502/b436fdd9/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Sat May  2 22:39:53 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Sat, 02 May 2009 20:39:53 +0000
Subject: [Tracker-discuss] [issue280] Save patches as text plain in the meta
	and setuptools	instances
In-Reply-To: <1241296793.03.0.105591612932.issue280@psf.upfronthosting.co.za>
Message-ID: <1241296793.03.0.105591612932.issue280@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

Both the setuptools and meta instances save .diff and .patch files as
text/x-diff, which most browsers try to download.

Attached is a simplified version of the patches.py detector from python-dev that
should be enough to save these files, along with .py ones, as text/plain.

----------
files: patches.py
messages: 1386
nosy: ajaksu2
priority: bug
status: unread
title: Save patches as text plain in the meta and setuptools instances

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue280>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patches.py
Type: text/x-python
Size: 465 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090502/06ca75e6/attachment.py>

From metatracker at psf.upfronthosting.co.za  Sat May  2 22:40:53 2009
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Sat, 02 May 2009 20:40:53 +0000
Subject: [Tracker-discuss] [issue280] Save patches as text plain in the meta
	and setuptools	instances
In-Reply-To: <1241296793.03.0.105591612932.issue280@psf.upfronthosting.co.za>
Message-ID: <1241296853.85.0.869280006903.issue280@psf.upfronthosting.co.za>


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

Big +1.

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

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

From metatracker at psf.upfronthosting.co.za  Sat May  2 22:45:30 2009
From: metatracker at psf.upfronthosting.co.za (Jeroen Ruigrok van der Werven)
Date: Sat, 02 May 2009 20:45:30 +0000
Subject: [Tracker-discuss] [issue280] Save patches as text plain in the meta
	and setuptools	instances
In-Reply-To: <1241296793.03.0.105591612932.issue280@psf.upfronthosting.co.za>
Message-ID: <1241297130.4.0.985398515796.issue280@psf.upfronthosting.co.za>


Jeroen Ruigrok van der Werven <asmodai at in-nomine.org> added the comment:

A +1 from me as well since I was the one who complained to Daniel about this.

----------
nosy: +asmodai

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

From ajaksu at gmail.com  Wed May  6 09:11:58 2009
From: ajaksu at gmail.com (Daniel Diniz)
Date: Wed, 6 May 2009 04:11:58 -0300
Subject: [Tracker-discuss] [Python-Dev] Summary of Python tracker Issues
In-Reply-To: <2d75d7660904241116n3a2bfa97he27981845cece867@mail.gmail.com>
References: <20090403160659.1AB6278590@psf.upfronthosting.co.za> 
	<Pine.LNX.4.64.0904031233310.26362@kimball.webabinitio.net> 
	<2d75d7660904241116n3a2bfa97he27981845cece867@mail.gmail.com>
Message-ID: <2d75d7660905060011w43955ado9579e42738f57b27@mail.gmail.com>

Daniel Diniz wrote:
R. David Murray wrote:
>> ?I suggest we change
>> this report to provide statistics that are designed to encourage people
>> using the tracker when they make progress on reducing the total number
>> of outstanding bugs, or at least make it clear that the open bug count
>> isn't increasing as fast as the above report format makes it seem.
>
> I'll try to implement this today.

It took me a couple of days just to understand how the report is generated :/

A refactored version of roundup-summary is attached, you can compare
its ugly code to the original ugly code at
http://codereview.appspot.com/53058/diff/1001/1002 .

Main changes:
 - Pass arguments to functions instead of having everything as globals.
 - Simplify table template parsing and result generation, avoiding eval()s.
 - Replace lots of print-based output with a few .write() calls.
 - Move code from module scope into (many!) functions.
 - Merge similar functions/classes, split long functions into smaller ones.
 - Fix spaces/tabs, long lines, variable and function naming, unused imports.
 - Miscellaneous reorganization.

It's supposed to be a drop-in replacement to the current
roundup-summary, but its output has a couple spurious whitespaces
compared to the original's.

I have to let this rest for at least another week, but I'll be able to
add your suggested report format after that.

Regards,
Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: roundup-summary
Type: application/octet-stream
Size: 34721 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090506/1c4e696d/attachment-0001.obj>

From metatracker at psf.upfronthosting.co.za  Sat May  9 19:58:16 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Sat, 09 May 2009 17:58:16 +0000
Subject: [Tracker-discuss] [issue281] We offer the best alarm-clocks for
	your little fellow down	there.
In-Reply-To: <000d01c9cebf$777743b0$6400a8c0@>
Message-ID: <1241891896.48.0.0340164969165.issue281@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

Spam :(

----------
nosy: +ajaksu2
priority:  -> wish
status: unread -> resolved

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

From metatracker at psf.upfronthosting.co.za  Sat May  9 20:38:31 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Sat, 09 May 2009 18:38:31 +0000
Subject: [Tracker-discuss] [issue283] Add a 3.2 version
In-Reply-To: <1241894311.51.0.915676348793.issue283@psf.upfronthosting.co.za>
Message-ID: <1241894311.51.0.915676348793.issue283@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

Now that we have a 3.1 beta, some RFEs for 3.x need to be set to 3.2. I'll
submit a patch for PEP 101 regarding bug tracker activities, it should include
at least:
  - Add version X.Y+1 as soon as version X.Y enters alpha.

If we're OK with adding more tracker-related tasks to PEP 101, I'd like to add
these:
  - Change non-doc RFEs to version X.Y+1 as soon as version X.Y enters beta.
  - Review open issues: this might find (and flag) lurking showstopper bugs,
besides reminding people to fix the easy ones they forgot about.
  - Change 'behavior' issues to the bugfixes-version if they are still set to a
now security-fixes-version.

----------
messages: 1393
nosy: ajaksu2
priority: bug
status: unread
title: Add a 3.2 version

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

From =?utf-8?q?=22Martin_v=2E_L=C3=B6wis=22_=3Cmetatracker=40psf=2Eupfronthost?= at psf.upfronthosting.co.za  Sat May  9 22:22:07 2009
From: =?utf-8?q?=22Martin_v=2E_L=C3=B6wis=22_=3Cmetatracker=40psf=2Eupfronthost?= at psf.upfronthosting.co.za (=?utf-8?q?=22Martin_v=2E_L=C3=B6wis=22_=3Cmetatracker=40psf=2Eupfronthost?= at psf.upfronthosting.co.za)
Date: Sat, 09 May 2009 20:22:07 +0000
Subject: [Tracker-discuss] [issue283] Add a 3.2 version
In-Reply-To: <1241894311.51.0.915676348793.issue283@psf.upfronthosting.co.za>
Message-ID: <1241900527.95.0.745417379415.issue283@psf.upfronthosting.co.za>


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

I've added the version.

As for the changes to the PEP - you would have to ask the PEP authors.

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

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

From metatracker at psf.upfronthosting.co.za  Mon May 11 09:25:51 2009
From: metatracker at psf.upfronthosting.co.za (Peter Funk)
Date: Mon, 11 May 2009 07:25:51 +0000
Subject: [Tracker-discuss] [issue281] We offer the best alarm-clocks for
	your little fellow down	there.
In-Reply-To: <1241891896.48.0.0340164969165.issue281@psf.upfronthosting.co.za>
Message-ID: <1242026751.67.0.868291024624.issue281@psf.upfronthosting.co.za>


Peter Funk <pf at artcom-gmbh.de> added the comment:

I did n't submit this spam. 
Someone is abusing my email address by forgery.
Peter Funk.

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

From metatracker at psf.upfronthosting.co.za  Sun May 10 01:28:29 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Sat, 09 May 2009 23:28:29 +0000
Subject: [Tracker-discuss] [issue284] Better summary reports
In-Reply-To: <1241911709.97.0.816502801538.issue284@psf.upfronthosting.co.za>
Message-ID: <1241911709.97.0.816502801538.issue284@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

The attached file is meant to (eventually) replace scripts/roundup-summary. It
is a major refactoring of the original, with less code, more documentation and
much more code organization.

Martin, can you run this against a real tracker and compare the output to the
original one? 

Its output should match that of he original script, except for a couple of
fixes: minor textual changes on the --help output, buglets (e.g. for audit
output) and whitespace normalization.

I want to add a couple of niceties to the reports, like a better summary of the
net change in open issues, report issues per priority and type, etc., but the
current script is way too confusing for me. 

Using a real templating engine (http://pythonpaste.org/tempita/ -> 730 LOC)
instead of rolling our own (as the current code does) could also be nice.

----------
files: roundup-summary
messages: 1395
nosy: ajaksu2
priority: feature
status: unread
title: Better summary reports

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue284>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: roundup-summary
Type: application/octet-stream
Size: 33945 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090509/961cfed2/attachment-0001.obj>

From metatracker at psf.upfronthosting.co.za  Wed May 13 22:38:30 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Wed, 13 May 2009 20:38:30 +0000
Subject: [Tracker-discuss] [issue263] Email not always sent to
	Python-bugs-list, depending on the user
In-Reply-To: <1239031039.27.0.209933652376.issue263@psf.upfronthosting.co.za>
Message-ID: <1242247110.63.0.378097620581.issue263@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

I cannot reproduce this on the Roundup side of things, even with ludicrously
complicated usernames (including null-bytes and ?).

Here's a sample of goes into the debug file:
From: =?utf-8?b?S3Jpc3Rqw6FuIFZhbHVyIErDs25zc8O2xZXDp8OHw5HCo8KybSBhIAhqIAhh?=
 =?utf-8?b?IAhrIAhzIAh1IOqcoPOggYUgCfOggYYgCfOggYcgCeKYp+KYpyAJ4pioIAk=?=
 =?utf-8?b?4pipIAnimKogCeKYqyAJ4pisIAnimK0gCeKYriAJ4piv77+977+977+977+9?=
 =?utf-8?b?77+9IDxpc3N1ZV90cmFja2VyQGV4YW1wbGUuY29tPg==?=


Content-Transfer-Encoding: quoted-printable
Kristj=C3=A1n Valur J=C3=B3nss=C3=B6=C5=95=C3=A7=C3=87=C3=91=C2=A3=C2=B2m a=
 =08j =08a =08k =08s =08u =EA=9C=A0=F3=A0=81=85         =F3=A0=81=86   
=F3=A0=81=87=
        =E2=98=A7=E2=98=A7      =E2=98=A8       =E2=98=A9       =E2=98=AA      
=E2=98=AB       =E2=98=AC=
        =E2=98=AD       =E2=98=AE      
=E2=98=AF=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=
=BD <email> added the comment:

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

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

From metatracker at psf.upfronthosting.co.za  Thu May 14 04:04:31 2009
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Thu, 14 May 2009 02:04:31 +0000
Subject: [Tracker-discuss] [issue263] Email not always sent to
	Python-bugs-list, depending on the user
In-Reply-To: <1239031039.27.0.209933652376.issue263@psf.upfronthosting.co.za>
Message-ID: <1242266671.34.0.797787292927.issue263@psf.upfronthosting.co.za>


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

This seems to have just started happening to me.  Specifically I'm not getting
any of Martin's posts, but other people are coming through fine.

Note that previously names with non-ASCII characters showed up in my inbox with
what appears to me to be an incorrect encoded-word encoding of name+username
(the name should be encoded as an encoded word and the username should be ascii,
to my reading of the relevant RFC).  My theory is that the new email server is
rejecting these as invalid....

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

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

From metatracker at psf.upfronthosting.co.za  Thu May 14 11:15:14 2009
From: metatracker at psf.upfronthosting.co.za (Quentin Gallet-Gilles)
Date: Thu, 14 May 2009 09:15:14 +0000
Subject: [Tracker-discuss] [issue263] Email not always sent to
	Python-bugs-list, depending on the user
In-Reply-To: <1239031039.27.0.209933652376.issue263@psf.upfronthosting.co.za>
Message-ID: <1242292514.34.0.263200857758.issue263@psf.upfronthosting.co.za>


Quentin Gallet-Gilles <qgallet at gmail.com> added the comment:

Indeed, this is happening with Martin's posts at the moment, for instance with
the issue 1621 (
http://mail.python.org/pipermail/python-bugs-list/2009-May/subject.html ).

Is there a way to know if roundup actually sent the mail ? I'm starting to
wonder whether the issue is on mailman's side.

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

From metatracker at psf.upfronthosting.co.za  Thu May 14 19:34:56 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 14 May 2009 17:34:56 +0000
Subject: [Tracker-discuss] [issue285] Add issue title to issue links,
	avoid linking to bogus issues
In-Reply-To: <1242322496.14.0.859560166441.issue285@psf.upfronthosting.co.za>
Message-ID: <1242322496.14.0.859560166441.issue285@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

Understanding how one issue relates to others would be easier if issue links had
the linked issue's title as a tooltip. So we'd have:
    <a href="issue6020" title="Create a datetime.timedelta.totalseconds
property">#6020</a>

We can easily add this to the dependencies and superseder links. Adding titles
to issue links in message bodies is a bit more involved, but doable. As a
benefit, we'd be able to avoid linking to bogus issues.

RFE by Ezio Melotti and R. David Murray.

----------
assignedto: ajaksu2
messages: 1400
nosy: ajaksu2
priority: feature
status: unread
title: Add issue title to issue links, avoid linking to bogus issues

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

From metatracker at psf.upfronthosting.co.za  Mon May 18 18:53:25 2009
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Mon, 18 May 2009 16:53:25 +0000
Subject: [Tracker-discuss] [issue263] Email not always sent to
	Python-bugs-list, depending on the user
In-Reply-To: <1239031039.27.0.209933652376.issue263@psf.upfronthosting.co.za>
Message-ID: <1242665605.81.0.0671872050501.issue263@psf.upfronthosting.co.za>


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

Additional data-point: email from Martin on issues on which I am nosy _does_
arrive in my inbox.  I have noticed, also, that such direct emails are sometimes
html formatted, when the copy of the same email to the bugs list is not.  Also,
I don't see the weird encoded-word encoding of given-name+username on emails
directly to me, but I did see it on emails to the bugs list when they used to
get through.

So, there is some difference in the paths take by those two email transmissions
that is dropping emails with non-ASCII given-names on the ground.

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

From metatracker at psf.upfronthosting.co.za  Fri May 22 21:23:40 2009
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Fri, 22 May 2009 19:23:40 +0000
Subject: [Tracker-discuss] [issue263] Email not always sent to
	Python-bugs-list, depending on the user
In-Reply-To: <1239031039.27.0.209933652376.issue263@psf.upfronthosting.co.za>
Message-ID: <1243020220.81.0.517889480556.issue263@psf.upfronthosting.co.za>


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

Is someone looking into this? It may hint at some deeper problem with the new
mail.python.org...

----------
nosy: +gbrandl

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

From metatracker at psf.upfronthosting.co.za  Fri May 22 23:08:38 2009
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Fri, 22 May 2009 21:08:38 +0000
Subject: [Tracker-discuss] [issue263] Email not always sent to
	Python-bugs-list, depending on the user
In-Reply-To: <1239031039.27.0.209933652376.issue263@psf.upfronthosting.co.za>
Message-ID: <1243026518.81.0.735470271296.issue263@psf.upfronthosting.co.za>


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

Has anyone emailed pydotorg about it?

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

From metatracker at psf.upfronthosting.co.za  Sat May 23 14:22:42 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 23 May 2009 12:22:42 +0000
Subject: [Tracker-discuss] [issue263] Email not always sent to
	Python-bugs-list, depending on the user
In-Reply-To: <1239031039.27.0.209933652376.issue263@psf.upfronthosting.co.za>
Message-ID: <1243081362.59.0.885001435886.issue263@psf.upfronthosting.co.za>


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

I guess the problem is that bugs.python.org puts things like

From:
=?utf-8?b?Ik1hcnRpbiB2LiBMw7Z3aXMiIDxyZXBvcnRAYnVncy5weXRob24ub3JnPg==?=@psf.upfronthosting.co.za

into the message; this is bogus. Even the ones reported by ajaksu2 are bogus; it
shouldn't b-encode the email address, but only the user name.

The root cause is the switchover of roundup to the email package. roundup now
does first utils.formataddr((u"Martin v. L?wis", "martin at v.loewis.de")), then
creates an email.header.Header(u'"Martin v. L\xf6wis" <martin at v.loewis.de>') and
converts that to a str.

This is now fixed in r72846, r72847.

----------
nosy: +loewis
status: chatting -> resolved

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

From rdmurray at bitdance.com  Sat May 23 16:46:21 2009
From: rdmurray at bitdance.com (R. David Murray)
Date: Sat, 23 May 2009 10:46:21 -0400 (EDT)
Subject: [Tracker-discuss] [issue5259] smtplib is broken in Python3 (fwd)
Message-ID: <Pine.LNX.4.64.0905231042370.12060@kimball.webabinitio.net>

I have no idea how this happened; I certainly did not intend
to delete this file.  I will re upload it (I don't see a
restore button...)


---------- Forwarded message ----------
Date: Sat, 23 May 2009 14:24:18 +0000
From: R. David Murray <report at bugs.python.org>
To: python-bugs-list at python.org
Subject: [issue5259] smtplib is broken in Python3


Changes by R. David Murray <rdmurray at bitdance.com>:


Removed file: http://bugs.python.org/file13774/test-smtplib.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5259>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/rdmurray%40bitdance.com


From metatracker at psf.upfronthosting.co.za  Tue May 26 21:09:17 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Tue, 26 May 2009 19:09:17 +0000
Subject: [Tracker-discuss] [issue285] Add issue title to issue links,
	avoid linking to bogus issues
In-Reply-To: <1242322496.14.0.859560166441.issue285@psf.upfronthosting.co.za>
Message-ID: <1243364957.13.0.629555735674.issue285@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

The attached patch:
 * Fixes an 'integer too large' error in templating.py that causes issues to be
undisplayable.
 * Adds title attributes to Roundup's class links (e.g. 'version 1').
 * Moves in-message issue links of the form 'issue 123' from templating.py to
local_replace.py.
 * Adds issue titles to issue links in dependencies and message bodies.
 * Adds the 'open' or 'closed' CSS classes to issue links. 

I can provide the bugfix part as an independent patch.

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

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue285>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: link_titles.diff
Type: text/x-diff
Size: 5114 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090526/97d46f03/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Tue May 26 21:18:43 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Tue, 26 May 2009 19:18:43 +0000
Subject: [Tracker-discuss] [issue285] Add issue title to issue links,
	avoid linking to bogus issues
In-Reply-To: <1242322496.14.0.859560166441.issue285@psf.upfronthosting.co.za>
Message-ID: <1243365523.62.0.679431306103.issue285@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

Demos:
 * Features: http://bot.bio.br/python-dev-exp/issue14
 * Bugfix: http://bot.bio.br/python-dev/issue11

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

From metatracker at psf.upfronthosting.co.za  Tue May 26 21:34:01 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Tue, 26 May 2009 19:34:01 +0000
Subject: [Tracker-discuss] [issue285] Add issue title to issue links,
	avoid linking to bogus issues
In-Reply-To: <1242322496.14.0.859560166441.issue285@psf.upfronthosting.co.za>
Message-ID: <1243366441.36.0.54688894267.issue285@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

Just the bugfix.

----------
priority: feature -> bug

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue285>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postgress_large_nodeid.diff
Type: text/x-diff
Size: 516 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090526/533e8bec/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Thu May 28 10:42:19 2009
From: metatracker at psf.upfronthosting.co.za (Peter Funk)
Date: Thu, 28 May 2009 08:42:19 +0000
Subject: [Tracker-discuss] [issue286] Spam issue
In-Reply-To: <000d01c9df0e$dce9dd20$6400a8c0@>
Message-ID: <1243500139.07.0.953842013993.issue286@psf.upfronthosting.co.za>


Peter Funk <pf at artcom-gmbh.de> added the comment:

This issue is obviously Spam and was not created by me but by
some spammer abusing my userid.  
Please could someone retire this issue?
This has happened before in issue281 and others.  I don't want 
to have my userid linked to spam issues.  If I can do anything 
about this, please tell me what.  

Many thanks in advance.
Regards, 
Peter Funk

----------
nosy: +admin, forsberg, loewis
priority:  -> bug
status: unread -> chatting
title: We will take a great care of your body and soul. -> Spam issue

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

From metatracker at psf.upfronthosting.co.za  Thu May 28 23:55:55 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 28 May 2009 21:55:55 +0000
Subject: [Tracker-discuss] [issue286] Spam issue
In-Reply-To: <000d01c9df0e$dce9dd20$6400a8c0@>
Message-ID: <1243547755.75.0.499633825707.issue286@psf.upfronthosting.co.za>


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

I think the only permanent solution would be for you to change the email address
that you use in the tracker.

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

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

From metatracker at psf.upfronthosting.co.za  Fri May 29 08:06:48 2009
From: metatracker at psf.upfronthosting.co.za (Peter Funk)
Date: Fri, 29 May 2009 06:06:48 +0000
Subject: [Tracker-discuss] [issue286] Spam issue
In-Reply-To: <1243547755.75.0.499633825707.issue286@psf.upfronthosting.co.za>
Message-ID: <20090529060556.GN6592@pfmaster.artcom-gmbh.de>


Peter Funk <pf at artcom-gmbh.de> added the comment:

Hallo Martin,

Martin v. L?wis suggested 28.05.2009 to me:
> I think the only permanent solution would be for you to change the email address
> that you use in the tracker.

Thanks for the suggestion.  I've done so and exchanged the address with 
one of my other not so well known email addresses and put my original one 
into the field containing the list of alternative addresses.  

But I didn't understand how this is supposed to work and how it
would prevent spammers from creating new invalid issues like 
this one here or issue281 in the metatracker.  Please explain.

Thanks in advance.

Regards, Peter
-- 
Peter Funk, ?Oldenburger Str.86, D-27777 Ganderkesee
office: ArtCom GmbH, ?Haferwende 2, D-28357 Bremen, Germany 
tel:+49-421-20419-0 cell:+49-179-640-8878 <http://www.artcom-gmbh.de/>

----------
nosy: +pefu
status: resolved -> chatting

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

From metatracker at psf.upfronthosting.co.za  Sat May 30 00:21:14 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Fri, 29 May 2009 22:21:14 +0000
Subject: [Tracker-discuss] [issue286] Spam issue
In-Reply-To: <20090529060556.GN6592@pfmaster.artcom-gmbh.de>
Message-ID: <4A205FD7.1050705@v.loewis.de>


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

> But I didn't understand how this is supposed to work and how it
> would prevent spammers from creating new invalid issues like 
> this one here or issue281 in the metatracker.  Please explain.

The spammers send email with your registered email address to the
tracker. The tracker checks whether the From field is a registered
address of some user, and if so, it accepts the message. Now that
you have changed your email address, spammers would have to use the
new address in From. Since they don't know what the new address
is, the spam will be rejected.

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

From martin at v.loewis.de  Sat May 30 00:21:11 2009
From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=)
Date: Sat, 30 May 2009 00:21:11 +0200
Subject: [Tracker-discuss] [issue286] Spam issue
In-Reply-To: <20090529060556.GN6592@pfmaster.artcom-gmbh.de>
References: <20090529060556.GN6592@pfmaster.artcom-gmbh.de>
Message-ID: <4A205FD7.1050705@v.loewis.de>

> But I didn't understand how this is supposed to work and how it
> would prevent spammers from creating new invalid issues like 
> this one here or issue281 in the metatracker.  Please explain.

The spammers send email with your registered email address to the
tracker. The tracker checks whether the From field is a registered
address of some user, and if so, it accepts the message. Now that
you have changed your email address, spammers would have to use the
new address in From. Since they don't know what the new address
is, the spam will be rejected.