DOCSLIB.ORG

Tuto Documentation Release 0.1.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Tuto Documentation Release 0.1.0 Tuto Documentation Release 0.1.0 DevOps people 2020-05-09 09H16 CONTENTS 1 Documentation news 3 1.1 Documentation news 2020........................................3 1.1.1 New features of sphinx.ext.autodoc (typing) in sphinx 2.4.0 (2020-02-09)..........3 1.1.2 Hypermodern Python Chapter 5: Documentation (2020-01-29) by https://twitter.com/cjolowicz/..................................3 1.2 Documentation news 2018........................................4 1.2.1 Pratical sphinx (2018-05-12, pycon2018)...........................4 1.2.2 Markdown Descriptions on PyPI (2018-03-16)........................4 1.2.3 Bringing interactive examples to MDN.............................5 1.3 Documentation news 2017........................................5 1.3.1 Autodoc-style extraction into Sphinx for your JS project...................5 1.4 Documentation news 2016........................................5 1.4.1 La documentation linux utilise sphinx.............................5 2 Documentation Advices 7 2.1 You are what you document (Monday, May 5, 2014)..........................8 2.2 Rédaction technique...........................................8 2.2.1 Libérez vos informations de leurs silos.............................8 2.2.2 Intégrer la documentation aux processus de développement..................8 2.3 13 Things People Hate about Your Open Source Docs.........................9 2.4 Beautiful docs.............................................. 10 2.5 Designing Great API Docs (11 Jan 2012)................................ 10 2.6 Docness.................................................. 10 2.6.1 Docness Source code...................................... 10 2.7 Hacking distributed (february 2013)................................... 10 2.8 Jacob Kaplan-Moss (November 10, 2009)................................ 11 2.9 Agile documentation best practices................................... 11 2.10 Best Practices for Documenting Technical Procedures Melanie Seibert................ 11 2.11 Plone................................................... 12 2.12 Twilio................................................... 12 2.13 Other advices............................................... 12 2.13.1 Write the docs.......................................... 12 2.13.2 Mindshare............................................ 15 3 Documentation generators 17 3.1 Sphinx .................................................. 17 3.1.1 Description........................................... 18 3.1.2 Sphinx source code (Sphinx dev guide)............................ 18 3.1.3 Sphinx applications....................................... 19 3.1.4 reST Sphinx........................................... 24 i 3.1.5 Sphinx extensions (sphinx.ext.*) ................................ 75 3.1.6 Sphinx contributed extensions................................. 88 3.1.7 Sphinx howto.......................................... 114 3.1.8 Sphinx examples........................................ 115 3.1.9 Sphinx i18n........................................... 135 3.1.10 Sphinx builders......................................... 135 3.1.11 Sphinx installation....................................... 137 3.1.12 Sphinx usage.......................................... 140 3.1.13 Sphinx people.......................................... 142 3.1.14 Sphinx tutorials......................................... 145 3.1.15 Tools for Sphinx........................................ 147 3.1.16 Sphinx themes......................................... 152 3.1.17 Sphinx templating........................................ 167 3.1.18 Sphinx translations....................................... 170 3.1.19 Sphinx versions......................................... 172 3.2 Authorea................................................. 186 3.2.1 Introduction........................................... 187 3.3 Doxygen................................................. 187 3.3.1 Introduction........................................... 187 3.3.2 Example............................................. 188 3.3.3 Doxygen source code...................................... 188 3.3.4 Issues, bugs, requests, ideas................................... 188 3.3.5 Projects using doxygen..................................... 189 3.3.6 Doxygen formats........................................ 196 3.3.7 Doxygen versions........................................ 196 3.4 gatsby (Build blazing fast, modern apps and websites with React), graphQL Foundation member... 202 3.5 Hugo (The world’s fastest framework for building websites)...................... 202 3.5.1 README.md.......................................... 203 3.5.2 Versions............................................. 207 3.6 Javadoc.................................................. 207 3.6.1 Introduction........................................... 207 3.7 Jekyll................................................... 208 3.7.1 Overview............................................ 208 3.7.2 Tools.............................................. 208 3.8 JSDoc................................................... 209 3.8.1 Getting Started......................................... 209 3.8.2 Bootstrap themes........................................ 209 3.9 mdbook.................................................. 210 3.10 Mkdocs.................................................. 210 3.10.1 Overview............................................ 210 3.10.2 Themes............................................. 210 3.10.3 Nice docs............................................ 210 3.11 Pandoc .................................................. 211 3.11.1 Introduction........................................... 211 3.11.2 Pandoc source code....................................... 212 3.11.3 Pandoc Commands....................................... 213 3.11.4 Versions............................................. 213 3.12 pdoc (Auto-generate API documentation for Python projects)..................... 213 3.12.1 pdoc definition......................................... 214 3.12.2 pdoc examples......................................... 215 3.12.3 pdoc versions.......................................... 216 3.13 redoc................................................... 216 3.13.1 redoc definition......................................... 216 3.13.2 redoc versions.......................................... 223 ii 3.14 swagger-ui................................................ 224 3.14.1 swagger-ui definition...................................... 224 3.14.2 swagger-ui versions....................................... 224 4 Sphinx documentation hosting 227 4.1 Sphinx documentation on gitlab pages ................................. 227 4.1.1 Continuous deployment of the documentation......................... 227 4.2 Hébergement Sphinx sur github pages.................................. 228 4.3 Sphinx on Read the docs......................................... 228 4.3.1 Introduction........................................... 229 4.3.2 Read the docs on twitter.................................... 230 4.3.3 New theme (4th of november 2013).............................. 230 4.3.4 How to............................................. 231 4.3.5 Projects on Read the docs.................................... 234 5 Good documentation 243 5.1 cakephp documentation......................................... 243 5.2 Fastapi (from Sebastián Ramírez).................................... 243 5.2.1 https://dockerswarm.rocks/................................... 244 5.3 Mattermost................................................ 244 5.4 Passlib documentation.......................................... 244 5.5 pretalx (Conference planning tool: CfP, scheduling, speaker management)............... 244 5.5.1 conf.py............................................. 245 5.5.2 Contents............................................. 245 5.5.3 administrator.......................................... 245 5.5.4 Developer............................................ 245 5.5.5 API............................................... 245 5.5.6 Maintainer............................................ 245 5.5.7 Commit messages........................................ 245 5.6 Sfepy documentation........................................... 246 5.7 Shark documentation........................................... 246 6 Formats Documentation 247 6.1 Input formats............................................... 247 6.1.1 Markdown ........................................... 247 6.1.2 ReStructuredText format................................... 263 6.1.3 Tex / Latex........................................... 270 6.1.4 Textile.............................................. 271 6.2 Input/output formats........................................... 271 6.2.1 L’Extensible Markup Language (XML)............................ 271 6.3 Output formats.............................................. 272 6.3.1 Dash format........................................... 272 6.3.2 EPUB format.......................................... 272 6.3.3 Hypertext_Markup_Language (HTML) format........................ 273 6.3.4 Portable Document Format (PDF)............................... 273 6.3.5 Windows HTML Help format (or known as CHM)...................... 274 6.3.6 L’Extensible Markup Language (XML)............................ 275 7 Documentation projects 277 7.1 C Documentation projects........................................ 277 7.1.1 clang (doxygen)......................................... 277 7.2 Mozilla documentation.......................................... 277 7.3 Documenting python projects.....................................
Load more

Recommended publications
  • Usask Open Textbook Authoring Guide – Ver.1.0
    USask Open Textbook Authoring Guide – Ver.1.0 USask Open Textbook Authoring Guide – Ver.1.0 A Guide to Authoring & Adapting Open Textbooks at the University of Saskatchewan Distance Education Unit (DEU), University of Saskatchewan Jordan Epp, M.Ed., Kristine Dreaver-Charles, M.Sc.Ed., Jeanette McKee, M.Ed. Open Press DEU, Usask Saskatoon Copyright:2016 by Distance Education Unit, University of Saskatchewan. This book is an adaptation based on the B.C. Open Textbook Authoring Guide created by BCcampus and licensed with a CC-BY 4.0 license. Changes to the BCcampus Authoring Guide for this University of Saskatchewan adaptation included: Changing the references from BCcampus Open Project to be more relevant to the University of Saskatchewan’s open textbook development. Creation of a new title page and book title. Changing information about Support Services to be University of Saskatchewan specific. Performing a general text edit throughout the guide, added image captions, and updated most images to remove the BCcampus branding. Updating Pressbook platform nomenclature to be consistent with the current version of Pressbooks. Unless otherwise noted, this book is released under a Creative Commons Attribution (CC-BY) 4.0 Unported license. Under the terms of the CC-BY license you can freely share, copy or redistribute the material in any medium or format, or adapt the material by remixing, transforming or modifying this material providing you attribute the Distance Education Unit, University of Saskatchewan and BCcampus. Attribution means you must give appropriate credit to the Distance Education Unit, University of Saskatchewan and BCcampus as the original creator, note the CC-BY license this document has been released under, and indicate if you have made any changes to the content.
    [Show full text]
  • Sagemath and Sagemathcloud
    Viviane Pons Ma^ıtrede conf´erence,Universit´eParis-Sud Orsay [email protected] { @PyViv SageMath and SageMathCloud Introduction SageMath SageMath is a free open source mathematics software I Created in 2005 by William Stein. I http://www.sagemath.org/ I Mission: Creating a viable free open source alternative to Magma, Maple, Mathematica and Matlab. Viviane Pons (U-PSud) SageMath and SageMathCloud October 19, 2016 2 / 7 SageMath Source and language I the main language of Sage is python (but there are many other source languages: cython, C, C++, fortran) I the source is distributed under the GPL licence. Viviane Pons (U-PSud) SageMath and SageMathCloud October 19, 2016 3 / 7 SageMath Sage and libraries One of the original purpose of Sage was to put together the many existent open source mathematics software programs: Atlas, GAP, GMP, Linbox, Maxima, MPFR, PARI/GP, NetworkX, NTL, Numpy/Scipy, Singular, Symmetrica,... Sage is all-inclusive: it installs all those libraries and gives you a common python-based interface to work on them. On top of it is the python / cython Sage library it-self. Viviane Pons (U-PSud) SageMath and SageMathCloud October 19, 2016 4 / 7 SageMath Sage and libraries I You can use a library explicitly: sage: n = gap(20062006) sage: type(n) <c l a s s 'sage. interfaces .gap.GapElement'> sage: n.Factors() [ 2, 17, 59, 73, 137 ] I But also, many of Sage computation are done through those libraries without necessarily telling you: sage: G = PermutationGroup([[(1,2,3),(4,5)],[(3,4)]]) sage : G . g a p () Group( [ (3,4), (1,2,3)(4,5) ] ) Viviane Pons (U-PSud) SageMath and SageMathCloud October 19, 2016 5 / 7 SageMath Development model Development model I Sage is developed by researchers for researchers: the original philosophy is to develop what you need for your research and share it with the community.
    [Show full text]
  • Debian Developer's Reference Version 12.0, Released on 2021-09-01
    Debian Developer’s Reference Release 12.0 Developer’s Reference Team 2021-09-01 CONTENTS 1 Scope of This Document 3 2 Applying to Become a Member5 2.1 Getting started..............................................5 2.2 Debian mentors and sponsors......................................6 2.3 Registering as a Debian member.....................................6 3 Debian Developer's Duties 9 3.1 Package Maintainer's Duties.......................................9 3.1.1 Work towards the next stable release............................9 3.1.2 Maintain packages in stable .................................9 3.1.3 Manage release-critical bugs.................................. 10 3.1.4 Coordination with upstream developers............................ 10 3.2 Administrative Duties.......................................... 10 3.2.1 Maintaining your Debian information............................. 11 3.2.2 Maintaining your public key.................................. 11 3.2.3 Voting.............................................. 11 3.2.4 Going on vacation gracefully.................................. 12 3.2.5 Retiring............................................. 12 3.2.6 Returning after retirement................................... 13 4 Resources for Debian Members 15 4.1 Mailing lists............................................... 15 4.1.1 Basic rules for use....................................... 15 4.1.2 Core development mailing lists................................. 15 4.1.3 Special lists........................................... 16 4.1.4 Requesting new
    [Show full text]
  • Doxydoxygen User Guide Release 0.79.4
    DoxyDoxygen User Guide Release 0.79.4 20Tauri Aug 16, 2021 MANUAL 1 Welcome to DoxyDoxygen 1 2 Installation 3 2.1 Software installation with Package Control...............................3 2.2 Manual software installation.......................................3 2.3 License installation............................................4 2.4 EULA (End User License Agreement)..................................4 2.4.1 Licenses.............................................4 2.4.2 Description of other rights and limitations...........................4 2.4.3 No warranties..........................................5 3 Usage 7 3.1 Create a documentation block......................................7 3.2 Update / wrap an existing documentation block.............................8 3.3 Switch between comment styles.....................................9 3.4 Extend a documentation block......................................9 3.4.1 Auto-completion........................................9 3.4.2 Comment continuation..................................... 10 3.5 Navigate in documentation........................................ 10 3.5.1 Move to the right column.................................... 10 3.5.2 Follow references........................................ 10 3.6 Fold / Unfold comments......................................... 11 3.7 Translate................................................. 11 3.8 Generate documentation......................................... 12 4 Customization 13 4.1 Settings.................................................. 13 4.1.1 Understand
    [Show full text]
  • Defect Tracking System Project Documentation
    Defect Tracking System Project Documentation Tottering Barr azotise some Faust and gyps his surplices so sweetly! Northrup remains impellent after Sigfried havers nominally or fluorescing any good-byes. Remus orientalize thunderously? So much like automation and project defect tracking documentation but not win any kind of the organization tries to track the list by the beginning development team and let an. The amount of tracking system project defect tracking system! All comments are moderated before publication and desire meet our guidelines. Testing is a lousy part of mature software life cycle, and recent trends in software engineering evidence the importance all this activity all survey the development process. Diving deeper into program language theory is a great way data grow outside a developer. Your comment has been received. Bug reporting by the Web and email. Her homeland of interests are Wireless Networks and Database Management Systems. As projects grow in size and complexity, the limits of an Excel story for tracking issues begin to show which quickly. Thank who for using our services. Ten reports engine is a few lines of system project defect tracking documentation appears every single pane contains the. Defect tracking is responsible system authority is applied for any system software so run system performs well. User interface and learning curve the system user interfaces are more user friendly than others. Switch to fullscreen mode always show business bug attributes at once. Some custom structure for large body usually, evaluating and tracking system project defect documentation related documents, planning with your development organization efficiently and eliminate bad.
    [Show full text]
  • Cryptanalysis of Substitution-Permutation Networks Using Key-Dependent Degeneracy*
    Cryptanalysis of Substitution-Permutation Networks Using Key-Dependent Degeneracy* Howard M. Heys Electrical Engineering, Faculty of Engineering and Applied Science Memorial University of Newfoundland St. John’s, Newfoundland, Canada A1B 3X5 Stafford E.Tavares Department of Electrical and Computer Engineering Queen’s University Kingston, Ontario, Canada K7L 3N6 * This research was supported by the Natural Sciences and Engineering Research Council of Canada and the Telecommunications Research Institute of Ontario and was completed during the first author’s doctoral studies at Queen’s University. Cryptanalysis of Substitution-Permutation Networks Using Key-Dependent Degeneracy Keywords Ð Cryptanalysis, Substitution-Permutation Network, S-box Abstract Ð This paper presents a novel cryptanalysis of Substitution- Permutation Networks using a chosen plaintext approach. The attack is based on the highly probable occurrence of key-dependent degeneracies within the network and is applicable regardless of the method of S-box keying. It is shown that a large number of rounds are required before a network is re- sistant to the attack. Experimental results have found 64-bit networks to be cryptanalyzable for as many as 8 to 12 rounds depending on the S-box properties. ¡ . Introduction The concept of Substitution-Permutation Networks (SPNs) for use in block cryp- tosystem design originates from the “confusion” and “diffusion” principles in- troduced by Shannon [1]. The SPN architecture considered in this paper was first suggested by Feistel [2] and consists of rounds of non-linear substitutions (S-boxes) connected by bit permutations. Such a cryptosystem structure, referred 1 to as LUCIFER1 by Feistel, is a simple, efficient implementation of Shannon’s concepts.
    [Show full text]
  • Markdown Markup Languages What Is Markdown? Symbol
    Markdown What is Markdown? ● Markdown is a lightweight markup language with plain text formatting syntax. Péter Jeszenszky – See: https://en.wikipedia.org/wiki/Markdown Faculty of Informatics, University of Debrecen [email protected] Last modified: October 4, 2019 3 Markup Languages Symbol ● Markup languages are computer languages for annotating ● Dustin Curtis. The Markdown Mark. text. https://dcurt.is/the-markdown-mark – They allow the association of metadata with parts of text in a https://github.com/dcurtis/markdown-mark clearly distinguishable way. ● Examples: – TeX, LaTeX https://www.latex-project.org/ – Markdown https://daringfireball.net/projects/markdown/ – troff (man pages) https://www.gnu.org/software/groff/ – XML https://www.w3.org/XML/ – Wikitext https://en.wikipedia.org/wiki/Help:Wikitext 2 4 Characteristics Usage (2) ● An easy-to-read and easy-to-write plain text ● Collaboration platforms and tools: format that. – GitHub https://github.com/ ● Can be converted to various output formats ● See: Writing on GitHub (e.g., HTML). https://help.github.com/en/categories/writing-on-github – Trello https://trello.com/ ● Specifically targeted at non-technical users. ● See: How To Format Your Text in Trello ● The syntax is mostly inspired by the format of https://help.trello.com/article/821-using-markdown-in-trell o plain text email. 5 7 Usage (1) Usage (3) ● Markdown is widely used on the web for ● Blogging platforms and content management entering text. systems: – ● The main application areas include: Ghost https://ghost.org/
    [Show full text]
  • Application Lifecycle Management Tools Open Source
    Application Lifecycle Management Tools Open Source Posh and tropistic Christofer congees almost despondingly, though Sam humiliating his breastworks recoins. Jorge usually assassinates astringently or disrupt crustily when interterritorial Marko voids streakily and convivially. Irresponsible Vijay unround broadly. With the software changes into three core business reason for anyone using powerful lifecycle tools across public activity management The package includes OSS project management tool Redmine and version. This year open source ALM tuleap httpwwwenaleancomentuleap is altogether good start. ALM tools automate the software development and deployment processes help. Micro Focus Application Lifecycle Management ALM software and solutions. Virtual flavor of the product with its embedded and application software before. Greg Lindhorst Principal Program Manager Thursday January 14 2021. The more List and Open-source Tools View ahead complete list ANT Anypoint Platform. Application Lifecycle Management Tools ALM is the continuous process of. Top 10 Application Lifecycle Management Tools For end Year. A degree to two the limitations of save open-source circuit otherwise inadequate tool. Best Free Application Lifecycle Management Software 2021. Each document type main source code is managed with SubversionSVN with. It is free of tools are the advent of the use after year after going through it connects people meet business outcomes as and open application source tools? Application Lifecycle Management SoftLanding. Top Application Lifecycle Management ALM Toolsets InfoQ. They also have original single proponent of truth providing any relevant. Then view the software projects, open application lifecycle management tools on open source option, and hybrid it can create and. Software lifecycle management SLM is the discipline for managing.
    [Show full text]
  • Alinex Data Store
    Alinex Data Store Read, work and write data structures to differents stores Alexander Schilling Copyright © 2019 - 2021 <a href="https://alinex.de">Alexander Schilling</a> Table of contents Table of contents 1. Home 6 1.1 Alinex Data Store 6 1.1.1 Usage 6 1.1.2 Debugging 6 1.1.3 Module Usage 7 1.1.4 Chapters 7 1.1.5 Support 7 1.2 Command Line Usage 8 1.2.1 Input 8 1.2.2 Output 8 1.2.3 Transform Files 9 1.2.4 Using Definition 9 1.2.5 Examples 9 1.3 Last Changes 10 1.3.1 Version 1.16.0 - (12.05.2021) 10 1.3.2 Version 1.15.0 - (02.01.2021) 10 1.3.3 Version 1.13.0 - (16.06.2020) 10 1.3.4 Version 1.12.0 - (27.01.2020) 10 1.3.5 Version 1.11.0 - (13.01.2020) 11 1.3.6 Version 1.10.0 - (22.11.2019) 11 1.3.7 Version 1.9.1 - (13.11.2019) 11 1.3.8 Version 1.8.0 - (31.10.2019) 11 1.3.9 Version 1.7.0 - (13.10.2019) 11 1.3.10 Version 1.6.0 - (01.10.2019) 11 1.3.11 Version 1.5.0 - (28.08.2019) 12 1.3.12 Version 1.4.0 - (15.08.2019) 12 1.3.13 Version 1.3.0 - (6.08.2019) 12 1.3.14 Version 1.2.0 - (22.06.2019) 13 1.3.15 Version 1.1.0 - (17.05.2019) 13 1.3.16 Version 1.0.0 - (12.05.2019) 13 1.3.17 Version 0.7.0 (29.04.2019) 13 1.3.18 Version 0.6.0 (26.04.2019) 14 1.3.19 Version 0.5.0 (19.04.2019) 14 1.3.20 Version 0.4.0 (17.04.2019) 14 1.3.21 Version 0.3.0 (15.04.2019) 14 - 2/80 - Copyright © 2019 - 2021 <a href="https://alinex.de">Alexander Schilling</a> Table of contents 1.3.22 Version 0.2.0 (12.04.2019) 14 1.3.23 Version 0.1.0 (0t.04.019) 14 1.4 Roadmap 16 1.4.1 Add Protocols 16 1.4.2 Multiple sources 16 1.5 Privacy statement 17 2.
    [Show full text]
  • MARTIN KEAN Open Source Publishing, 'Book Sprints' And
    MARTIN KEAN Open source publishing, ‘book sprints’ and possible futures ABSTRACT A number of open source publishing networks and communities facilitate the use of helpful tools for free publishing and collaborative writing that can be adopted or adapted for various uses. One group that has consciously tried to take into account all of the processes necessary to solve problems is FLOSS Manuals. The ecologies of many groups and networks tend to fetishise the digital and neglect other possible solutions. This article examines the many tools available or in development that value print formats and community-sustaining tools and methods, both online and physical. Living in Dunedin, a small city with strong community networks, I work collaboratively with artists, educators and designers, businesses and institutions as a supporter of node gateways to new media open methods, resources and tools. This practice extends to national and international networks, including the non-profit group FLOSS Manuals and its agile book creation process. I came to work with FLOSS Manuals through my involvement within a tiny, inwardly focussed Dunedin subcultural community, and the handful of individuals, who travelled far and cross-pollinated with similar communities in Europe and further. FREE SOFTWARE AND OPEN SOURCE PUBLISHING From the early 1980s open source software was typified by the development and distribution of Richard Stallman’s GNU compiler, the best on Unix systems at the time. However, there were often more software developers willing to volunteer their time than there were technical writers and so there was little or no supportive documentation. It was not until Adam Hyde’s 2006 development of FLOSS Manuals that readily accessible and readable documentation became available1.
    [Show full text]
  • Kde-Guide-De-Developpement.Web.Pdf
    KDE Published : 2017-06-26 License : GPLv2+ 1 KDE DU POINT DE VUE D'UN DÉVELOPPEUR 1. AVEZ-VOUS BESOIN DE CE LIVRE ? 2. LA PHILOSOPHIE DE KDE 3. COMMENT OBTENIR DE L'AIDE 2 1. AVEZ-VOUS BESOIN DE CE LIVRE ? Vous devriez lire ce livre si vous voulez développer pour KDE. Nous utilisons le terme développement très largement pour couvrir tout ce qui peut conduire à un changement dans le code source, ce qui inclut : Soumettre une correction de bogue Écrire une nouvelle application optimisée par la technologie KDE Contribuer à un projet existant Ajouter de la fonctionnalité aux bibliothèques de développement de KDE Dans ce livre, nous vous livrerons les bases dont vous avez besoin pour être un développeur productif. Nous décrirons les outils que vous devrez installer, montrer comment lire la documentation (et écrire la vôtre propre, une fois que vous aurez créé la nouvelle fonctionnalité !) et comment obtenir de l'aide par d'autres moyens. Nous vous présenterons la communauté KDE, qui est essentielle pour comprendre KDE parce que nous sommes un projet « open source », libre (gratuit). Les utilisateurs finaux du logiciel n'ont PAS besoin de ce livre ! Cependant, ils pourraient le trouver intéressant pour les aider à comprendre comment les logiciels complexes et riches en fonctionnalités qu'ils utilisent ont vu le jour. 3 2. LA PHILOSOPHIE DE KDE Le succès de KDE repose sur une vue globale, que nous avons trouvée à la fois pratique et motivante. Les éléments de cette philosophie de développement comprennent : L'utilisation des outils disponibles plutôt que de ré-inventer ceux existants : beaucoup des bases dont vous avez besoin pour travailler font déjà partie de KDE, comme les bibliothèques principales ou les « Kparts », et sont tout à fait au point.
    [Show full text]
  • An Introduction to Numpy and Scipy
    An introduction to Numpy and Scipy Table of contents Table of contents ............................................................................................................................ 1 Overview ......................................................................................................................................... 2 Installation ...................................................................................................................................... 2 Other resources .............................................................................................................................. 2 Importing the NumPy module ........................................................................................................ 2 Arrays .............................................................................................................................................. 3 Other ways to create arrays............................................................................................................ 7 Array mathematics .......................................................................................................................... 8 Array iteration ............................................................................................................................... 10 Basic array operations .................................................................................................................. 11 Comparison operators and value testing ....................................................................................
    [Show full text]