|
|
145.
|
|
|
<a href="components.xhtml"> Components changes </a>: Twisted now uses Zope Interfaces rather than its own component system.
|
|
|
type: Content of: <html><body><ul><li>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/index.xhtml:16
|
|
|
146.
|
|
|
The Twisted Split FAQ
|
|
|
type: Content of: <html><body><h1>
|
|
|
|
|
Las PUF de Twisted Split
|
|
Translated by
DiegoJ
|
|
Reviewed by
A. Emmanuel Mendoza
|
|
|
|
Located in
upgrades/2.0/split.xhtml:3 upgrades/2.0/split.xhtml:8
|
|
|
147.
|
|
|
What is the Twisted Split?
|
|
|
type: Content of: <html><body><h2>
|
|
|
|
|
¿Qué es Twisted Split?
|
|
Translated by
DiegoJ
|
|
Reviewed by
A. Emmanuel Mendoza
|
|
|
|
Located in
upgrades/2.0/split.xhtml:10
|
|
|
148.
|
|
|
<a href="http://twistedmatrix.com/">Twisted</a> is very large. At last count, it has around 80 thousand lines of code (yes, that <em>is</em> very large for a Python project, maybe not so for a C++ project. ;). We broke it into several smaller packages with the 2.0 release.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/split.xhtml:13
|
|
|
149.
|
|
|
Why was Twisted being split?
|
|
|
type: Content of: <html><body><h2>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/split.xhtml:19
|
|
|
150.
|
|
|
The biggest reason was to make our release process more agile. A regression in twisted.names, for example, could hold up the release of the entire thing, when really it should only be holding up the release of twisted.names.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/split.xhtml:22
|
|
|
151.
|
|
|
The other big reason is visibility. Twisted has a ton of functionality, but many people miss out on it because they don't know where it is hidden inside Twisted. The Twisted split gave every sub-project its own web site and thus more visibility.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/split.xhtml:29
|
|
|
152.
|
|
|
But I liked the monolithic packages. Can I still get them?
|
|
|
type: Content of: <html><body><h2>
|
|
|
|
|
Pero me agradaban los paquetes monolíticos. Aún puedo tenerlos?
|
|
Translated and reviewed by
A. Emmanuel Mendoza
|
|
|
|
Located in
upgrades/2.0/split.xhtml:35
|
|
|
153.
|
|
|
Yes. Tarball and Windows releases for Twisted and all of its sub-projects will still be maintained. We encourage maintainers of packages for OSes with automatic packaging systems to break up the packages as well, so, for example, Debian will have python2.3-twisted-core, python2.3-twisted-conch, python2.3-twisted-names, and so on.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/split.xhtml:38
|
|
|
154.
|
|
|
Where can I find information about the individual projects?
|
|
|
type: Content of: <html><body><h2>
|
|
|
|
|
Donde puedo encontrar información sobre proyectos individuales?
|
|
Translated and reviewed by
Carlos Alberto Ospina
|
|
|
|
Located in
upgrades/2.0/split.xhtml:46
|
