~ntt-pf-lab/nova/monkey_patch_notification

<?xml version="1.0" encoding="utf-8"?><!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'><html lang="en" xmlns="http://www.w3.org/1999/xhtml">

<head>

<title>Twisted Documentation: The Twisted Zope Interfaces FAQ</title>

</head>

<h1 class="title">The Twisted Zope Interfaces FAQ</h1>

<div class="toc"><ol><li><a href="#auto0">Twisted components system in 2.0</a></li><li><a href="#auto1">FAQ</a></li><ul><li><a href="#auto2">Why did Twisted switch to Zope Interfaces?</a></li><li><a href="#auto3">Why did Twisted switch to Zope Interfaces rather than PyProtocols?</a></li><li><a href="#auto4">Will this affect my deployment?</a></li><li><a href="#auto5">How can I update my own code?</a></li><li><a href="#auto6">

What about third party classes dependant on the old style of implements

declarations?

</a></li><li><a href="#auto7">What about using third party classes?</a></li></ul><li><a href="#auto8">Acknowledgements</a></li></ol></div>

<span/>

<h2>Twisted components system in 2.0<a name="auto0"/></h2>

<p>Twisted code's own use of the <code class="API"><a href="http://twistedmatrix.com/documents/10.0.0/api/twisted.python.components.html" title="twisted.python.components">twisted.python.components</a></code> package has been updated to use <a href="http://www.zope.org/Wikis/Interfaces/FrontPage" shape="rect">Zope Interfaces</a> in

the 2.0 release.</p>

<p>New code developed starting with the 2.0 release of Twisted Core should use Zope

Interfaces directly rather than using the twisted.python.components

package.</p>

<h3>Why did Twisted switch to Zope Interfaces?<a name="auto2"/></h3>

<p>

The twisted.python.components package is a large amount of on-going

maintenance. Using the Zope Interface package also provides a greater level of

compatibility between Twisted interfaces and Zope interfaces.

</p>

<h3>Why did Twisted switch to Zope Interfaces rather than PyProtocols?<a name="auto3"/></h3>

<p>

The Zope Interface package was chosen over PyProtocols because of its greater

conceptual similarity to twisted.python.components.

</p>

<h3>Will this affect my deployment?<a name="auto4"/></h3>

<p>

No. Releases of Twisted Core will include Zope Interfaces.

</p>

<h3>How can I update my own code?<a name="auto5"/></h3>

<p>

Classes written using twisted.python.components declare which interfaces they

implement in this style:

</p>

<code>

class C:

__implements__ = IFoo,

</code>

<p>

This should be changed to:

</p>

<code>

class C:

zope.interface.implements(IFoo)

</code>

<h3>

What about third party classes dependant on the old style of implements

declarations?

<p>

Use <code class="API"><a href="http://twistedmatrix.com/documents/10.0.0/api/twisted.python.components.backwardsCompatImplements.html" title="twisted.python.components.backwardsCompatImplements">backwardsCompatImplements</a></code> to fix this.

</p>

<code>

twisted.python.components.backwardsCompatImplements(C)

</code>

<h3>What about using third party classes?<a name="auto7"/></h3>

<p>

If you are using third party libraries that only declare __implements__, these

objects should be made compatible with <code base="twisted.python.components">fixClassImplements</code>: </p>

<code>

# import o where o is some third party library

from thirdparty.lib import o

twisted.python.components.fixClassImplements(o.__class__)

</code>

100

<p>

101

This will make sure that __implements__ declarations get converted to the new

102

style of implements declarations.

103

</p>

104

105

<h2>Acknowledgements<a name="auto8"/></h2>

106

107

<p>This document is the work of Jason A. Mobarak, with contributions from Mary

108

Gardiner.</p>

109

110

</div>

111

112

<p><a href="../../howto/index.html">Index</a></p>

113

<span class="version">Version: 10.0.0</span>

114

</body>

115

</html>

b'\\ No newline at end of file'

Older »