[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#224434: marked as done (ITP: python2.3-pyprotocols -- Python 2.3 module implementing object adaptation (PEP 246))



Your message dated Wed, 14 Sep 2005 13:02:24 -0500 (CDT)
with message-id <20050914180224.2701A1078CB@cerdita.damog.net>
and subject line WNPP bug closed
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 19 Dec 2003 00:27:17 +0000
>From fog@initd.org Thu Dec 18 18:27:16 2003
Return-path: <fog@initd.org>
Received: from (firenze.linux.it) [195.110.124.18] 
	by master.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1AX87E-0007oT-00; Thu, 18 Dec 2003 18:03:36 -0600
Received: by firenze.linux.it (Postfix, from userid 10)
	id AD4EC3C0A6; Fri, 19 Dec 2003 00:57:09 +0100 (CET)
Received: by momo.initd.org (Postfix, from userid 1000)
	id 7C73737BC4; Fri, 19 Dec 2003 01:03:53 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Federico Di Gregorio <fog@initd.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: ITP: python2.3-pyprotocols -- Python 2.3 module implementing object
 adaptation (PEP 246)
X-Mailer: reportbug 2.37
Date: Fri, 19 Dec 2003 01:03:53 +0100
X-Debbugs-Cc: debian-devel@lists.debian.org
Message-Id: <20031219000353.7C73737BC4@momo.initd.org>
X-BadReturnPath: fog@lana.linux.it rewritten as fog@initd.org
  using "From" header
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 
	2.60-master.debian.org_2003_11_25-bugs.debian.org_2003_12_15 
	(1.212-2003-09-23-exp) on master.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=HAS_PACKAGE,X_DEBBUGS_CC 
	autolearn=no 
	version=2.60-master.debian.org_2003_11_25-bugs.debian.org_2003_12_15
X-Spam-Level: 

Package: wnpp
Severity: wishlist


  Package name    : python2.3-pyprotocols
  Version         : 0.9.2
  Upstream Author : Phillip J. Eby
  URL             : http://peak.telecommunity.com/PyProtocols.html
  License         : Python or Zope
  Description     : Python 2.3 module implementing object adaptation (PEP 246)

 PyProtocols extends the PEP 246 adapt() function with a new "declaration API"
 that lets you easily define your own protocols and adapters, and declare what
 adapters should be used to adapt what types, objects, or protocols. In
 addition to its own Interface type, PyProtocols can also use Twisted and
 Zope's Interface types too. (Of course, since Twisted and Zope interfaces
 aren't as flexible, only a subset of the PyProtocols API works with them.
 Specific limitations are listed in the documentation.)
 .
 If you're familiar with Interface objects in Zope, Twisted, or PEAK, the
 Interface objects in PyProtocols are very similar. But, they can also do many
 things that no other Python interface types can do. For example, PyProtocols
 supports "subsetting" of interfaces, where you can declare that one interface
 is a subset of another existing interface. This is like declaring that
 somebody else's existing interface is actually a subclass of the new
 interface.  Twisted and Zope don't allow this, which makes them very hard to
 use if you're trying to define interfaces like "Read-only Mapping" as a
 subset of "Mapping Object".
 .
 Also unlike Zope and Twisted, PyProtocols also doesn't force you to use a
 particular interface coding style or even a specific interface type. you can
 use its built-in interface types, or define your own. If there's another
 Python package out there with interface types that you'd like to use (CORBA?
 COM?), you can even create your own adapters to make them work with the
 PyProtocols API.
 .
 PyProtocols is also the only interface package that supports automatic
 "transitive adaptation".  That is, if you define an adapter from interface A
 to interface B, and another from B to C, PyProtocols automatically creates
 and registers a new adapter from A to C for you.  If you later declare an
 explicit adapter from A to C, it silently replaces the automatically created
 one.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux lana 2.6.0-test9 #1 Sat Nov 15 19:22:38 CET 2003 i686
Locale: LANG=it_IT@euro, LC_CTYPE=it_IT@euro


---------------------------------------
Received: (at 224434-done) by bugs.debian.org; 14 Sep 2005 18:02:42 +0000
>From damog@cerdita.damog.net Wed Sep 14 11:02:42 2005
Return-path: <damog@cerdita.damog.net>
Received: from dsl-201-129-37-187.prod-infinitum.com.mx (cerdita.damog.net) [201.129.37.187] 
	by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
	id 1EFbaf-0001dT-00; Wed, 14 Sep 2005 11:02:38 -0700
Received: by cerdita.damog.net (Postfix, from userid 1000)
	id 2701A1078CB; Wed, 14 Sep 2005 13:02:24 -0500 (CDT)
To: 224434-done@bugs.debian.org
Subject: WNPP bug closed
Cc: 224434-submitter@bugs.debian.org
Message-Id: <20050914180224.2701A1078CB@cerdita.damog.net>
Date: Wed, 14 Sep 2005 13:02:24 -0500 (CDT)
From: damog@cerdita.damog.net (David Moreno Garza)
Delivered-To: 224434-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,VALID_BTS_CONTROL 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 295

Hello,

This an automatic message sent to owners of inactive ITPs on the Debian
Bug Tracking System.

I'm closing your bug because of the following reasons:

- It is older than 600 days old.
- It haven't had any activity recently.
- The amount of ITPs on the Debian BTS is huge and we need to
  clean up a bit the place.

If your bug shouldn't be closed, you are more than free to re-open it,
for example, if you still have intentions to package the software in
question or the like. To re-open it, you simply have to mail
control@bugs.debian.org with a body text like this:

reopen 123456
thanks bts

Replacing '123456' for the number of your ITP bug. The subject of the
mail is ignored. Or if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <damog@debian.org>.

This is the first mass wnpp closing that will be done. The next close
will be done on inactive ITPs older than 450 days and finally, the
ones older than 365 days (an automatic script will close *inactive*
ITPs when they reach one year old).

A similar process will be applied to the RFP wnpp bugs in the next
days.

Thanks for your cooperation,
David Moreno Garza <damog@debian.org>.



Reply to: