This showed up today.
It seems to indicate that those wretched mail aliases haven't been
routed out and killed dead. :-( I don't want anything like this
to end up non-archived. I don't even know what all the mail aliases
we have are so I can go about getting them removed, or all forwarded
to europython-improve or something. Suggestions on how we go about
fixing this?
Laura
ps -- I will reply to him
------- Forwarded Message
Return-Path: [EMAIL PROTECTED]
Delivery-Date: Thu Mar 27 08:32:15 2008
Return-Path: <[EMAIL PROTECTED]>
Received: from mx1.amaze.nl (stoomeend.amaze.nl [194.109.109.20])
by theraft.openend.se (8.13.8/8.13.8/Debian-3) with ESMTP id
m2R7WD1f015380
for <[EMAIL PROTECTED]>; Thu, 27 Mar 2008 08:32:13 +0100
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176])
by mx1.amaze.nl (Postfix) with ESMTP id 42F5B5FA9D
for <[EMAIL PROTECTED]>; Thu, 27 Mar 2008 08:32:12 +0100 (CET)
Received: by wa-out-1112.google.com with SMTP id m16so6327144waf.14
for <[EMAIL PROTECTED]>; Thu, 27 Mar 2008 00:32:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=beta;
h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
bh=eLzwY6gzjExRBY7QPdsJ2g5QiW+Y0otlh0WR3oLFqu8=;
b=tUfwdWGbvsTJdBxeLksSXwGG1ItiFvWaeNUgOwtnxDTncOW/Ek5yoKlwtIkAstGQTnaGFMnwGX2R/9z42QLHwEHnbkcdaLzx9ojRwD5hVaqFyl+5t8sdg3U3snUNJh4ZaMD/4d2T1lT9mkbnzO6qwXVVy8LHCygrpzZt+21W0GM=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=beta;
h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
b=kfidwaH0QkCuWQlxb0D0N3+dbfwzYGGMSqu3LCbxw1UVW/o1w9lMJVhg4x+Mxuxk8/ZVDnMW6iWPdphLXOnymHQcSFRkhR7wwSzEuJ9B4rHA3DrtLm4CCXDi0YKM+k/1uZWI0jY8yZZQZzWZgS/b5Zm97Gyp6dIG2wevHhk/as8=
Received: by 10.114.168.1 with SMTP id q1mr838424wae.74.1206603130095;
Thu, 27 Mar 2008 00:32:10 -0700 (PDT)
Received: by 10.114.57.17 with HTTP; Thu, 27 Mar 2008 00:32:10 -0700 (PDT)
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 27 Mar 2008 10:32:10 +0300
From: "Peter Bulychev" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Clone Digger; sponsorship request
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Thu Mar 27 08:32:15 2008
X-DSPAM-Confidence: 0.9990
X-DSPAM-Probability: 0.0000
X-DSPAM-Signature: 47eb4d7f153831129217253
Hello.
My name is Peter Bulychev, I am the first-year Ph.D. student at the
Lomonosov Moscow State University.
I am the author of the Clone Digger project, the tool for finding
duplicate code in Python programs.
(http://clonedigger.sourceforge.net)
I have recently announced it and for its short history there were
several favorable reviews from the users (see
http://code.google.com/p/sympy/issues/detail?id=766 for example).
I hope Clone Digger will be useful for the Python community, to my
knowledge it is the first clone detection tool for the Python
language.
I'd like to talk on it during the EuroPython conference.
Unfortunately, it will be difficult to me to visit the conference for
my own funds.
Is it possible to get the sponsorship from the Python Software
Foundation or from some Python-related organization?
Thank you.
- --
Best regards,
Peter Bulychev.
------- End of Forwarded Message
_______________________________________________
Europython-improve mailing list
[email protected]
http://mail.python.org/mailman/listinfo/europython-improve
