Cuando la velocidad es mas importante se pueden escribir extensiones para Python en un lenguaje compilado como C o C++. Tales extensiones forman la base de la mayor³a de módulos en la librer³a de Python.
Mes: julio 2012 Página 3 de 6
Cuando la velocidad es mas importante se pueden escribir extensiones para Python en un lenguaje compilado como C o C++. Tales extensiones forman la base de la mayor³a de módulos en la librer³a de Python.
web:
-
La pagina de inicio de Python en www.python.org es el lugar para empezar su búsqueda de material sobre Python. Encontrara ayuda, documentación, enlaces a otros libros y listas de correo de SIGs (Special Interest Group)
a las que se puede unir.
-
El proyecto Open Book Project www.ibiblio.com/obp contiene no solo este libro en línea sino también otros libros similares para Java y C++ de Allen Downey. Además esta Lessons in Electric Circuits de Tony R. Kuphaldt, Getting down with …, un conjunto de tutoriales de varios temas sobre informática, escritos y editados por estudiantes de instituto, Python for Fun, un conjunto de estudios de casos en Python de Chris Meyers, y The Linux Cookbook de Michael Stultz, con 300 paginas de trucos y tecnicas.
-
Finalmente si acude a Google y busca con la cadena pitón -snake – monty” obtendrá cerca de 750.000 resultados. Y aquí algunos libros que contienen mas material sobre el lenguaje Python:
-
Core Python Programming de Wesley Chun es un libro largo, mas de 750 paginas. La primera parte del libro cubre las características básicas del lenguaje Python. La segunda parte proporciona una introducción paso a paso a temas mas avanzados incluyendo muchos de los mencionados anteriormente.
-
Python Essential Reference de David M. Beazley es un libro peque~no, pero contiene información sobre el lenguaje en si mismo y los módulos de la librería estándar. También esta muy bien indexado.
-
Python Pocket Reference de Mark Lutz realmente cabe en el bolsillo. Aunque no es tan extensivo como Python Essential Reference es una referencia útil para los módulos y funciones mas comúnmente usadas.
-
Mark Lutz también es autor de Programming Python, uno de los primeros (y mas largos) libros de Python y no esta dirigido al programador principiante.
-
Su siguiente libro Learning Python es mas pequeño y mas accesible.
-
Python Programming on Win32 de Mark Hammond y Andy Robinson es un libro que debe tener” cualquiera que que utilice seriamente Python para desarrollar aplicaciones para Windows. Entre otras cosas cubre la integración de Python y COM, construye una pequeña aplicación con wxPython, e incluso utiliza Python para escribir scripts para aplicaciones tales como Word y Excel.
- The Practice of Programming de Kernighan y Pike cubre no solo el diseño y dedicación de algoritmos y estructuras de datos, sino también depuración, testeo y mejora de rendimiento de los programas. Los ejemplos están
principalmente en C++ y Java, sin nada de Python.
- The Elements of Java Style editado por Al Vermeulen es otro libro peque~no que discute algunos de los puntos mas sutiles de la buena programación, tales como el buen uso de las convenciones de nombres, comentarios e indotación (un poco irrelevante en Python). El libro también cubre la programación por contrato, usando aserciones para encontrar los errores
probando precondiciones y pos condiciones, y programación correcta con hilos y su sincronización.
- Programming Pearls de Jon Bentley es un libro clásico. Consiste en estudios de caso que aparecieron originalmente en la columna del autor en Comunicativos of the ACM. Los estudios tratan sobre toma y daca en programación y por que suele ser mala idea desarrollar con la primera idea de un programa. El libro es un poco mas antiguo que los anteriores (1986), por lo que los ejemplos están en lenguajes mas antiguos. Hay muchos problemas para resolver, algunos con soluciones y otros con pistas. Este libro fue muy popular y le siguió un segundo volumen.
- The New Turing Omnibus de A.K Dewdney proporciona una introducción amigable a 66 temas de informática desde computación en paralelo hasta virus informáticos, desde Tac (tomograf³as computarizadas) hasta algoritmos genéticos. Todos los temas son cortos y entretenidos. Un libro anterior de Dewdney Aventuras Informáticas es una colección de su columna Juegos de ordenador en Investigación y Ciencia. Ambos libros son ricas fuentes de ideas para proyectos. Tortugas, Termitas y Atascos de Trafico de Mitchel Resnick trata sobre el poder de la descentralización y de como pueden obtenerse comportamientos complejos a partir de las actividades simples de una multitud de agentes coordinados. Introduce el lenguaje Starlogo, que permite al usuario escribir programas para agentes. La ejecución del programa demuestra comportamientos complejos agregados, que suelen ser intuitivos. La mayoría de los programas en el libro fueron desarrollados por estudiantes de colegio e instituto. Programas similares pueden escribirse en Python usando gráficos e hilos.
- GÄodel, Escher, Bach de Douglas Hofstadter. Simplemente, si encuentra magia en la recursión también la encontrara en este libro superventas. Uno de los temas de Hofstadter concierne a los lazos extra~nos” donde los patrones se desenvuelven y ascienden hasta que se encuentran a s³ mismos de nuevo. Es una disputa de Hofstadter que tales lazos extraños son una parte esencial de lo que separa lo animado de lo no animado. El demuestra tales patrones en la música de Bach, las ilustraciones de Eschery el teorema de incompletita de GÄodel.
Version 1.1, March 2000
Copyright °c 2000 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies of this license
document, but changing it is not allowed.
The purpose of this License is to make a manual, textbook, or other written do-
cument free” in the sense of freedom: to assure everyone the e®ective freedom
to copy and redistribute it, with or without modifying it, either commercially
or noncommercially. Secondarily, this License preserves for the author and pu-
blisher a way to get credit for their work, while not being considered responsible
for modi¯cations made by others.
This License is a kind of copyleft,” which means that derivative works of the
document must themselves be free in the same sense. It complements the GNU
General Public License, which is a copyleft license designed for free software.
We have designed this License in order to use it for manuals for free software,
because free software needs free documentation: a free program should come
with manuals providing the same freedoms that the software does. But this
License is not limited to software manuals; it can be used for any textual work,
regardless of subject matter or whether it is published as a printed book. We
recommend this License principally for works whose purpose is instruction or
reference.
This License applies to any manual or other work that contains a notice placed
by the copyright holder saying it can be distributed under the terms of this Li-
cense. The Document,” below, refers to any such manual or work. Any member
of the public is a licensee, and is addressed as you.”
A Modi¯ed Version” of the Document means any work containing the Docu-
ment or a portion of it, either copied verbatim, or with modi¯cations and/or
translated into another language.
A Secondary Section” is a named appendix or a front-matter section of the
Document that deals exclusively with the relationship of the publishers or aut-
hors of the Document to the Document’s overall subject (or to related matters)
and contains nothing that could fall directly within that overall subject. (For
example, if the Document is in part a textbook of mathematics, a Secondary
Section may not explain any mathematics.) The relationship could be a matter
of historical connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical, or political position regarding them.
The Invariant Sections” are certain Secondary Sections whose titles are de-
signated, as being those of Invariant Sections, in the notice that says that the
Document is released under this License.
The Cover Texts” are certain short passages of text that are listed, as Front-
Cover Texts or Back-Cover Texts, in the notice that says that the Document is
released under this License.
A Transparent” copy of the Document means a machine-readable copy, repre-
sented in a format whose speci¯cation is available to the general public, whose
contents can be viewed and edited directly and straightforwardly with generic
text editors or (for images composed of pixels) generic paint programs or (for
drawings) some widely available drawing editor, and that is suitable for input to
text formatters or for automatic translation to a variety of formats suitable for
input to text formatters. A copy made in an otherwise Transparent ¯le format
whose markup has been designed to thwart or discourage subsequent modi¯ca-
tion by readers is not Transparent. A copy that is not Transparent” is called
Opaque.”
Examples of suitable formats for Transparent copies include plain ASCII wit-
hout markup, Texinfo input format, LATEX input format, SGML or XML using
a publicly available DTD, and standard-conforming simple HTML designed for
human modi¯cation. Opaque formats include PostScript, PDF, proprietary for-
mats that can be read and edited only by proprietary word processors, SGML
or XML for which the DTD and/or processing tools are not generally availa-
ble, and the machine-generated HTML produced by some word processors for
output purposes only.
The Title Page” means, for a printed book, the title page itself, plus such
following pages as are needed to hold, legibly, the material this License requires
to appear in the title page. For works in formats which do not have any title
page as such, Title Page” means the text near the most prominent appearance
of the work’s title, preceding the beginning of the body of the text.
You may copy and distribute the Document in any medium, either commercially
or noncommercially, provided that this License, the copyright notices, and the
license notice saying this License applies to the Document are reproduced in
all copies, and that you add no other conditions whatsoever to those of this
License. You may not use technical measures to obstruct or control the reading
or further copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough number
of copies you must also follow the conditions in Section 3.
You may also lend copies, under the same conditions stated above, and you may
publicly display copies.
If you publish printed copies of the Document numbering more than 100, and
the Document’s license notice requires Cover Texts, you must enclose the copies
in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts
on the front cover, and Back-Cover Texts on the back cover. Both covers must
also clearly and legibly identify you as the publisher of these copies. The front
cover must present the full title with all words of the title equally prominent
and visible. You may add other material on the covers in addition. Copying
with changes limited to the covers, as long as they preserve the title of the
Document and satisfy these conditions, can be treated as verbatim copying in
other respects.
You may copy and distribute a Modi¯ed Version of the Document under the
conditions of Sections 2 and 3 above, provided that you release the Modi¯ed
Version under precisely this License, with the Modi¯ed Version ¯lling the role
of the Document, thus licensing distribution and modi¯cation of the Modi¯ed
Version to whoever possesses a copy of it. In addition, you must do these things
in the Modi¯ed Version:
Use in the Title Page (and on the covers, if any) a title distinct from that
of the Document, and from those of previous versions (which should, if
there were any, be listed in the History section of the Document). You
may use the same title as a previous version if the original publisher of
that version gives permission.
List on the Title Page, as authors, one or more persons or entities respon-
sible for authorship of the modi¯cations in the Modi¯ed Version, together
with at least ¯ve of the principal authors of the Document (all of its prin-
cipal authors, if it has less than ¯ve).
State on the Title page the name of the publisher of the Modi¯ed Version,
as the publisher.
Preserve all the copyright notices of the Document.
E.4 Modi¯cations 267
Add an appropriate copyright notice for your modi¯cations adjacent to
the other copyright notices.
Include, immediately after the copyright notices, a license notice giving
the public permission to use the Modi¯ed Version under the terms of this
License, in the form shown in the Addendum below.
Preserve in that license notice the full lists of Invariant Sections and re-
quired Cover Texts given in the Document’s license notice.
Include an unaltered copy of this License.
Preserve the section entitled History,” and its title, and add to it an item
stating at least the title, year, new authors, and publisher of the Modi¯ed
Version as given on the Title Page. If there is no section entitled History”
in the Document, create one stating the title, year, authors, and publisher
of the Document as given on its Title Page, then add an item describing
the Modi¯ed Version as stated in the previous sentence.
Preserve the network location, if any, given in the Document for public
access to a Transparent copy of the Document, and likewise the network
locations given in the Document for previous versions it was based on.
These may be placed in the History” section. You may omit a network
location for a work that was published at least four years before the Do-
cument itself, or if the original publisher of the version it refers to gives
permission.
In any section entitled Acknowledgements” or Dedications,” preserve
the section’s title, and preserve in the section all the substance and tone
of each of the contributor acknowledgements and/or dedications given
therein.
Preserve all the Invariant Sections of the Document, unaltered in their text
and in their titles. Section numbers or the equivalent are not considered
part of the section titles.
Delete any section entitled Endorsements.” Such a section may not be
included in the Modi¯ed Version.
Do not retitle any existing section as Endorsements” or to con°ict in title
with any Invariant Section.
If the Modi¯ed Version includes new front-matter sections or appendices that
qualify as Secondary Sections and contain no material copied from the Docu-
ment, you may at your option designate some or all of these sections as invariant.
To do this, add their titles to the list of Invariant Sections in the Modi¯ed Version’s license notice. These titles must be distinct from any other section titles.
You may add a section entitled Endorsements,” provided it contains nothing but endorsements of your Modi¯ed Version by various parties|for example, statements of peer review or that the text has been approved by an organization
as the authoritative de¯nition of a standard.
You may add a passage of up to ¯ve words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modi¯ed Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on
behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modifed Version.