From metatracker at psf.upfronthosting.co.za  Tue Aug  5 05:48:02 2008
From: metatracker at psf.upfronthosting.co.za (Guido van Rossum)
Date: Tue, 05 Aug 2008 03:48:02 +0000
Subject: [Tracker-discuss] [issue214] email clogged?
In-Reply-To: <1217908082.4.0.261437433023.issue214@psf.upfronthosting.co.za>
Message-ID: <1217908082.4.0.261437433023.issue214@psf.upfronthosting.co.za>


New submission from Guido van Rossum <guido at python.org>:

There's been quite a bit of activity on issue3487, which I created, but I
haven't received a single email about it. ;-(

----------
messages: 1080
nosy: guido
priority: bug
status: unread
title: email clogged?

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

From metatracker at psf.upfronthosting.co.za  Tue Aug  5 07:24:06 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Tue, 05 Aug 2008 05:24:06 +0000
Subject: [Tracker-discuss] [issue214] email clogged?
In-Reply-To: <1217908082.4.0.261437433023.issue214@psf.upfronthosting.co.za>
Message-ID: <1217913846.63.0.631685334024.issue214@psf.upfronthosting.co.za>


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

Looking at the postfix log, I see, for example, for msg70729

Aug  5 05:40:38 psf postfix/cleanup[16470]: 017D6785D0:
message-id=<1217907637.58.0.265665490062.issue3487 at psf.upfronthosting.co.za>
Aug  5 05:40:38 psf postfix/qmgr[5621]: 017D6785D0:
from=<roundup-admin at psf.upfronthosting.co.za>, size=1770, nrcpt=1 (queue active)
Aug  5 05:40:38 psf postfix/smtpd[15676]: disconnect from localhost[10.0.0.1]
Aug  5 05:40:38 psf postfix/smtp[16475]: EB808785CB: to=<guido at python.org>,
relay=mail.python.org[194.109.207.14]:25, delay=0.25,
delays=0.01/0.01/0.07/0.16, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as
234E51E400D)
Aug  5 05:40:38 psf postfix/qmgr[5621]: EB808785CB: removed

I'm not 100% sure how to correlate these lines, but it seems that the message
was delivered to mail.python.org. I can't check there what happened to it, but
the queue number (234E51E400D) should allow to trace that further.

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

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

From metatracker at psf.upfronthosting.co.za  Tue Aug  5 16:38:02 2008
From: metatracker at psf.upfronthosting.co.za (Guido van Rossum)
Date: Tue, 05 Aug 2008 14:38:02 +0000
Subject: [Tracker-discuss] [issue214] email clogged?
In-Reply-To: <1217908082.4.0.261437433023.issue214@psf.upfronthosting.co.za>
Message-ID: <1217947082.9.0.564266315747.issue214@psf.upfronthosting.co.za>


Guido van Rossum <guido at python.org> added the comment:

My apologies. It was in my spam folder. That happens so rarely it never occurred
to me to look there. Sorry. :-(

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

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

From skip at pobox.com  Tue Aug 12 02:42:43 2008
From: skip at pobox.com (skip at pobox.com)
Date: Mon, 11 Aug 2008 19:42:43 -0500
Subject: [Tracker-discuss] Some observations about the spam filter
Message-ID: <18592.56451.614578.430512@montanaro-dyndns-org.local>


I just worked my way through the current pile of SpamBayes messages.  There
were actually a couple spams.  (At least I'm fairly certain they were spam.
They were in French, didn't appear to have anything to do with Python and
were in HTML format.)

A couple things jumped out at me:

    1. It looks like synthetic tokens are being generated in both
       detectors/spambayes.py and extensions/spambayes.py.  They both have
       somewhat different versions of an extract_classinfo() function.  Can
       we get away with a single version of that function?

    2. Many messages mention a Subversion revision number.  These are almost
       always different.  We should generate a synthetic token which
       indicates whether or not a submission contained what looked like a
       revision.  I'll check something in for that shortly once I understand
       how I should deal with item #1.

    3. If the body of the message was "My dog has fleas." it would be
       presented to the spam filter as "content:My dog has fleas."  That is,
       the first word is always prefixed by the string "content:".  I can't
       tell where that's getting applied, but we should get rid of it.

Skip

From metatracker at psf.upfronthosting.co.za  Sun Aug 24 20:01:58 2008
From: metatracker at psf.upfronthosting.co.za (Skip Montanaro)
Date: Sun, 24 Aug 2008 18:01:58 +0000
Subject: [Tracker-discuss] [issue215] Add synthetic token "hasrev" to
	SpamBayes detector
In-Reply-To: <1219600918.16.0.201826532823.issue215@psf.upfronthosting.co.za>
Message-ID: <1219600918.16.0.201826532823.issue215@psf.upfronthosting.co.za>


New submission from Skip Montanaro <skip at pobox.com>:

The attached patch adds a synthetic hasrev token to the SpamBayes detector in
the python.org Roundup instance.  In my opinion this will add a new very hammy
token since revision numbers seem to be mentioned so often in issue comments.  A
similar change might be needed in extensions/spambayes.py, but I'm not sure what
it's used for.

----------
files: tracker.diff
messages: 1083
nosy: montanaro
priority: feature
status: unread
title: Add synthetic token "hasrev" to SpamBayes detector

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue215>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tracker.diff
Type: application/octet-stream
Size: 779 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20080824/34068f0f/attachment.obj>

From skip at pobox.com  Sun Aug 24 20:02:56 2008
From: skip at pobox.com (skip at pobox.com)
Date: Sun, 24 Aug 2008 13:02:56 -0500
Subject: [Tracker-discuss] Some observations about the spam filter
In-Reply-To: <18592.56451.614578.430512@montanaro-dyndns-org.local>
References: <18592.56451.614578.430512@montanaro-dyndns-org.local>
Message-ID: <18609.41552.692627.423549@montanaro-dyndns-org.local>


On August 11 I wrote:

    me> I just worked my way through the current pile of SpamBayes messages.
    me> There were actually a couple spams.  (At least I'm fairly certain
    me> they were spam.  They were in French, didn't appear to have anything
    me> to do with Python and were in HTML format.)

    me> A couple things jumped out at me:

    me> 1. It looks like synthetic tokens are being generated in both
    me>    detectors/spambayes.py and extensions/spambayes.py.  They both
    me>    have somewhat different versions of an extract_classinfo()
    me>    function.  Can we get away with a single version of that
    me>    function?

    me> 2. Many messages mention a Subversion revision number.  These are
    me>    almost always different.  We should generate a synthetic token
    me>    which indicates whether or not a submission contained what looked
    me>    like a revision.  I'll check something in for that shortly once I
    me>    understand how I should deal with item #1.

    me> 3. If the body of the message was "My dog has fleas." it would be
    me>    presented to the spam filter as "content:My dog has fleas."  That
    me>    is, the first word is always prefixed by the string "content:".
    me>    I can't tell where that's getting applied, but we should get rid
    me>    of it.

I've not seen a reply about this.  I realize Martin is on holiday.  Has
anyone else who has seen this note got an opinion?  I created issue 215 with
a patch for detectors/spambayes.py to add a hasrev token:

    http://psf.upfronthosting.co.za/roundup/meta/issue215

Thx,

Skip


From brett at python.org  Sun Aug 24 20:19:41 2008
From: brett at python.org (Brett Cannon)
Date: Sun, 24 Aug 2008 11:19:41 -0700
Subject: [Tracker-discuss] Some observations about the spam filter
In-Reply-To: <18609.41552.692627.423549@montanaro-dyndns-org.local>
References: <18592.56451.614578.430512@montanaro-dyndns-org.local>
	<18609.41552.692627.423549@montanaro-dyndns-org.local>
Message-ID: <bbaeab100808241119t375d3674ldf9a793b5a2ce4b7@mail.gmail.com>

On Sun, Aug 24, 2008 at 11:02 AM,  <skip at pobox.com> wrote:
>
> On August 11 I wrote:
>
>    me> I just worked my way through the current pile of SpamBayes messages.
>    me> There were actually a couple spams.  (At least I'm fairly certain
>    me> they were spam.  They were in French, didn't appear to have anything
>    me> to do with Python and were in HTML format.)
>
>    me> A couple things jumped out at me:
>
>    me> 1. It looks like synthetic tokens are being generated in both
>    me>    detectors/spambayes.py and extensions/spambayes.py.  They both
>    me>    have somewhat different versions of an extract_classinfo()
>    me>    function.  Can we get away with a single version of that
>    me>    function?
>
>    me> 2. Many messages mention a Subversion revision number.  These are
>    me>    almost always different.  We should generate a synthetic token
>    me>    which indicates whether or not a submission contained what looked
>    me>    like a revision.  I'll check something in for that shortly once I
>    me>    understand how I should deal with item #1.
>
>    me> 3. If the body of the message was "My dog has fleas." it would be
>    me>    presented to the spam filter as "content:My dog has fleas."  That
>    me>    is, the first word is always prefixed by the string "content:".
>    me>    I can't tell where that's getting applied, but we should get rid
>    me>    of it.
>
> I've not seen a reply about this.  I realize Martin is on holiday.  Has
> anyone else who has seen this note got an opinion?  I created issue 215 with
> a patch for detectors/spambayes.py to add a hasrev token:
>
>    http://psf.upfronthosting.co.za/roundup/meta/issue215
>

I personally don't know enough about SpamBayes or the Roundup setup to
have an opinion. But basically it all sounds fine with me as long as
the spammers don't realize what we are doing.

-Brett

From metatracker at psf.upfronthosting.co.za  Wed Aug 27 15:56:55 2008
From: metatracker at psf.upfronthosting.co.za (Duncan Webb)
Date: Wed, 27 Aug 2008 13:56:55 +0000
Subject: [Tracker-discuss] [issue216] Using PyObject_New with
	Py_TPFLAGS_HAVE_GC
In-Reply-To: <1219845415.87.0.0682517072711.issue216@psf.upfronthosting.co.za>
Message-ID: <1219845415.87.0.0682517072711.issue216@psf.upfronthosting.co.za>


New submission from Duncan Webb <duncan-bugs at linuxowl.com>:

I managed to use PyObject_New instead of PyObject_GC_New for an object that has
Py_TPFLAGS_HAVE_GC set.

The problem is that the code was working in debug mode but was crashing in
release mode and it was very difficult to track the problem down.

Adding a check in the PyObject_New, PyObject_GC_New methods would have shown the
problem much earlier in devlopment.

----------
messages: 1084
nosy: duncanwebb
priority: bug
status: unread
title: Using PyObject_New with Py_TPFLAGS_HAVE_GC

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

From metatracker at psf.upfronthosting.co.za  Wed Aug 27 16:00:07 2008
From: metatracker at psf.upfronthosting.co.za (Duncan Webb)
Date: Wed, 27 Aug 2008 14:00:07 +0000
Subject: [Tracker-discuss] [issue216] Using PyObject_New with
	Py_TPFLAGS_HAVE_GC
In-Reply-To: <1219845415.87.0.0682517072711.issue216@psf.upfronthosting.co.za>
Message-ID: <1219845607.82.0.582150845523.issue216@psf.upfronthosting.co.za>


Duncan Webb <duncan-bugs at linuxowl.com> added the comment:

Opps, sorry this is the wrong list...

The problem is that I can't log-in to the Python bugs list always get an Invalid
Login message.

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

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