DOCSLIB.ORG

Create Book' Link = 'Mkbook' Mclass = 'Nav Buttons'

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Create Book' Link = 'Mkbook' Mclass = 'Nav Buttons' Grok 4 Noobs. P R Sephton Grok 4 Noobs. A gentle introduction to using the Grok web framework 2 A gentle introduction to using the Grok web framework Table of Contents: 1: What does Grok do particularly well? ... [7] 1.1: What are the nicest things about Zope & Grok? ... [10] 2: Grok & Zope in a Nutshell ... [13] 3: The Compulsory Part about Installing Grok ... [19] 3.1: Installing Grok from Github ... [21] 3.2: Installation Notes - older projects ... [22] 4: A short introduction to the Zope Component Architecture ... [24] 4.1: The Z-Object Publishing Environment ... [29] 4.2: Interfaces compared to Abstract Bases ... [30] 4.2.1: Interfaces vs. Inheritence: A Real World Example ... [33] 4.3: Traversal and the Context ... [39] 4.4: The amazingly useful Utility ... [41] 4.5: Events Mechanism ... [42] 4.5.1: A quick megrok.rdb (SQLAlchemy) setup howto ... [44] 4.6: Extending existing objects with Annotations ... [46] 5: Designing a site, defining it's layout and implementing the code ... [47] 5.1: How to make applications with Grok ... [49] 5.1.1: Modeling data in an application ... [53] 5.1.1.1: Notes on multithreading ... [55] 5.1.1.2: The Scope of models in Traversal ... [57] 5.1.1.3: Rules of Persistence ... [58] 5.1.1.4: User Session Management ... [59] 5.1.2: Defining an Article and the Application ... [60] 5.1.3: HTML Re-use and site layout ... [62] 5.1.3.1: Macros: an alternative way to re-use HTML ... [67] 5.1.3.2: The full source for the layout.py module ... [69] 5.1.4: Providing for article addition, modification and deletion ... [72] 5.1.4.1: Another way of rendering hidden input widgets ... [77] 5.1.5: Using Viewlets and Viewlet Managers to build a Navigation Fabric ... [79] 5.1.5.1: Ordered menus from a normal grok.Container ... [83] 5.1.5.1.1: Full source for SortedArticles Module ... [88] 5.1.5.2: menu.py Full Source ... [92] 5.1.5.3: Styling menu elements as buttons or menus ... [94] 5.1.6: Site Navigation: Context sensitive menus ... [97] 5.1.7: Integrating the tinyMCE editor ... [100] 5.1.7.1: A less trivial integration for tinyMCE ... [101] 5.1.8: Adding attachments to articles ... [104] 5.1.8.1: Adding syntax highlighting ... [115] 5.1.9: Authentication, Authorisation and Access Control ... [117] 5.1.9.1: Defining erP missions ... [119] 5.1.9.2: Defining and Assigning olesR ... [121] 5.1.9.3: Installing a Pluggable Authentication Utility ... [122] 5.1.9.4: Building a user management interface ... [128] 5.1.9.5: Controlling access to views and data ... [135] 6: Adding functions and extensions ... [137] 6.1: Adding an Index Page ... [138] 6.2: Printing the site as a book ... [141] 6.3: Using Layers and Skins: How to re-skin your Grok site ... [145] 6.3.1: Using Bootstrap to fast track site development ... [146] 6.3.2: Providing a nav bar and breadcrumbs ... [148] 6.3.3: Some closing remarks ... [152] 6.4: Adding a Disqus comment section ... [153] 7: About ... [155] 8: Other Resources available on the web ... [156] 3 Grok 4 Noobs. Grok is a web framework based upon the Zope Toolkit [1] (ZTK) and the Zope Component Architecture [2] (ZCA). Development for this framework began in 2006, with the view to making Zope-3 technology more accessible to newcomers. It achieves this quite admirably by using a mix of convention, special Grok directives, and decorators to make the task of building and maintaining web sites really simple. A Little History At one time Zope-2 [3] was the darling of the Python web development world. Zope-2 was based on a Through the Web (TTW) development model, which meant that developers could collaborate and program a Zope-2 installation remotely. It was fast (really fast and efficient for its time), simple, intuitive and had a large number of building blocks. To this day, Zope-2 remains popular as the basis for the Plone-3 CMS. Zope-3, these days called BlueBream [4], was intended to be a replacement for Zope-2, but this didn't quite work out as planned. As fast as features were added to Zope-3, they were back-ported to Zope-2 in a compatibility library called "Five" (5 = 2 + 3). This reduced and hampered motivation for adopting the newer Zope-3 in favor of Zope-2. At the same time, Ruby and Rails [5] happened which completely reimagined the way people viewed web frameworks. Django and other Python frameworks sprang up and quickly gained popularity as Python programmers began to realise that Python web development didn't have to be a ghastly chore. The Pyramid web framework [6] came about as an effort to make Zope technologies more accessible and less intimidating to newcomers. Grok happened at around the same time and shared many of the same motives. Zope-2 popularised and was popularised by TTW (Through the Web) development, but Zope-3, as was the case for most of the other Python frameworks, was not a TTW framework. The promise of TTW development was that anyone, not just developers, could develop web sites by adding new, or stringing together pre-defined web components online, often never having to write a line of actual code. Today, popular site builders such as WIX or Weebly or tools like WordPress accomplish that vision. It was arguably the confusion surrounding what Zope actually is, which brought about all of the misunderstanding, most of the confusion and much of the criticism surrounding the product. The mistake of Zope was mostly one of branding. Zope 4 development began more recently, and is a project to build a new TTW web platform with all the bells and whistles originally found in Zope 2. The advances made in 1. The Zope Toolkit API: http://docs.zope.org/zopetoolkit/ 2. ZCA Book: http://muthukadan.net/docs/zca.html 3. The zope-2 home page: http://zope2.zope.org/ 4. Bluebream Framework: http://bluebream.zope.org/ 5. Ruby on Rails: https://rubyonrails.org/ 6. Pyramid: https://trypyramid.com/ 4 A gentle introduction to using the Grok web framework the Zope Toolkit are brought forward into Zope 4, and the new platform contains many new and exciting features. So why is Grok important? Grok is quite possibly the best way to make use of the over 15 years of accumulated intellectual capital which comprises the Zope Toolkit (ZTK) libraries. It is open and accessible, and its seamless use of the Zope Component Architecture (ZCA) is intuitive and simple. Although BlueBream exists, along with it's amazingly complete set of documentation and thoroughly tested code, the same reasons why people migrated away from Zope-3 in the first place persist today. When the configuration for components is maintained in ZCML, separate from their definition and implementation, this separation can lead to unnecessary complexity and poor maintainability. ZCML was a particularly unpopular idea, and it is unlikely that anyone would want to, nor is it entirely advisable at this stage to adopt the BlueBream framework for new projects. Pyramid was, at least initially, also based upon the Zope Toolkit. However, Pyramid takes the approach of wrapping and hiding the component architecture (ZCA) from it's users, and there is not much recognisable left of the original architecture. It tries hard to be a generalised solution for all your needs, and succeeds at this in many ways. Grok, on the other hand is very different. With an initial investment of a few weeks (depending on learning speed) to properly understand how to fully exploit the Zope Component Architecture (ZCA), Grok gives you a mature and well documented framework capable of delivering relatively complex products in comparatively very little time. What's this site all about? This site documents it's own implementation. All source code is freely available on the web [1], and may be used to recreate instances of this site or to explore concepts and ideas around the Grok web framework. To demonstrate the flexibility, utility and extensibility of Grok, this wiki uses the built in object database (ZODB) to store editable articles which describe the site itself. From the database, we can later produce a dynamic index, or a printable book. This site may not be perfect in every way, but it does serve its purpose in showing how a Grok site may be developed modularly using pluggable and reusable components for things like authentication, layout, menus, HTML editors and even skinning an existing site using Bootstrap [2] or adding Disqus [3] for comments and feedback. The Grok tutorial [4] does a great job at showing off the simplicity of the framework. It is unfortunately not so good at showing how to progress beyond the simple things, or how the ZCA can help you build great sites quickly and maintainably instead of being the millstone around everyone's necks they imagine it to be. The ZCA is the elephant in the 1. Source code for this site: https://github.com/prsephton/Grok4Noobs 2. Bootstrap: https://getbootstrap.com/ 3. Disqus: https://disqus.com/ 4. The Grok Tutorial: http://grok.zope.org/doc/current/tutorial.html 5 Grok 4 Noobs. room everyone is ignoring which, rather than being treated like the embarrasing relative, should be the first thing proudly introduced to newcomers. In many ways, Grok's choice of a (very cute) cave man as an emblem is so very wrong. Whilst one understands the humour of man with a club smashing obstacles like ZCML, the overriding association created in peoples fertile imaginations is undoubtedly that Grok, like cavemen, is a relic of a prehistoric age, working with ancient libraries and technologies.
Load more

Recommended publications
  • Build It with Nitrogen the Fast-Off-The-Block Erlang Web Framework
    Build it with Nitrogen The fast-off-the-block Erlang web framework Lloyd R. Prentice & Jesse Gumm dedicated to: Laurie, love of my life— Lloyd Jackie, my best half — Jesse and to: Rusty Klophaus and other giants of Open Source— LRP & JG Contents I. Frying Pan to Fire5 1. You want me to build what?7 2. Enter the lion’s den9 2.1. The big picture........................ 10 2.2. Install Nitrogen........................ 11 2.3. Lay of the land........................ 13 II. Projects 19 3. nitroBoard I 21 3.1. Plan of attack......................... 21 3.2. Create a new project..................... 23 3.3. Prototype welcome page................... 27 3.4. Anatomy of a page...................... 30 3.5. Anatomy of a route...................... 33 3.6. Anatomy of a template.................... 34 3.7. Elements............................ 35 3.8. Actions............................. 38 3.9. Triggers and Targets..................... 39 3.10. Enough theory........................ 40 i 3.11. Visitors............................ 44 3.12. Styling............................. 64 3.13. Debugging........................... 66 3.14. What you’ve learned..................... 66 3.15. Think and do......................... 68 4. nitroBoard II 69 4.1. Plan of attack......................... 69 4.2. Associates........................... 70 4.3. I am in/I am out....................... 78 4.4. Styling............................. 81 4.5. What you’ve learned..................... 82 4.6. Think and do......................... 82 5. A Simple Login System 83 5.1. Getting Started........................ 83 5.2. Dependencies......................... 84 5.2.1. Rebar Dependency: erlpass ............. 84 5.3. The index page........................ 85 5.4. Creating an account..................... 87 5.4.1. db_login module................... 89 5.5. The login form........................ 91 5.5.1.
    [Show full text]
  • Making Story from System Logs with Elastic Stack
    SANOG36 18 - 21 January, 2021 Making story from system logs with stack [email protected] https://imtiazrahman.com https://github.com/imtiazrahman Logs syslog Audit SNMP NETFLOW http METRIC DNS ids What is Elastic Stack ? Store, Analyze Ingest User Interface a full-text based, distributed NoSQL database. Written in Java, built on Apache Lucene Commonly used for log analytics, full-text search, security intelligence, business analytics, and operational intelligence use cases. Use REST API (GET, PUT, POST, and DELETE ) for storing and searching data Data is stored as documents (rows in relational database) Data is separated into fields (columns in relational database) Relational Database Elasticsearch Database Index Table Type Row/Record Document Column Name Field Terminology Cluster: A cluster consists of one or more nodes which share the same cluster name. Node: A node is a running instance of elasticsearch which belongs to a cluster. Terminology Index: Collection of documents Shard: An index is split into elements known as shards that are distributed across multiple nodes. There are two types of shard, Primary and replica. By default elasticsearch creates 1 primary shard and 1 replica shard for each index. Terminology Shard 1 Replica 1 Replica 2 Shard 2 Node 1 Node 2 cluster Terminology Documents { • Indices hold documents in "_index": "netflow-2020.10.08", "_type": "_doc", serialized JSON objects "_id": "ZwkiB3UBULotwSOX3Bdb", "_version": 1, • 1 document = 1 log entry "_score": null, "_source": { • Contains "field : value" pairs
    [Show full text]
  • Learning Javascript Design Patterns
    Learning JavaScript Design Patterns Addy Osmani Beijing • Cambridge • Farnham • Köln • Sebastopol • Tokyo Learning JavaScript Design Patterns by Addy Osmani Copyright © 2012 Addy Osmani. All rights reserved. Revision History for the : 2012-05-01 Early release revision 1 See http://oreilly.com/catalog/errata.csp?isbn=9781449331818 for release details. ISBN: 978-1-449-33181-8 1335906805 Table of Contents Preface ..................................................................... ix 1. Introduction ........................................................... 1 2. What is a Pattern? ...................................................... 3 We already use patterns everyday 4 3. 'Pattern'-ity Testing, Proto-Patterns & The Rule Of Three ...................... 7 4. The Structure Of A Design Pattern ......................................... 9 5. Writing Design Patterns ................................................. 11 6. Anti-Patterns ......................................................... 13 7. Categories Of Design Pattern ............................................ 15 Creational Design Patterns 15 Structural Design Patterns 16 Behavioral Design Patterns 16 8. Design Pattern Categorization ........................................... 17 A brief note on classes 17 9. JavaScript Design Patterns .............................................. 21 The Creational Pattern 22 The Constructor Pattern 23 Basic Constructors 23 Constructors With Prototypes 24 The Singleton Pattern 24 The Module Pattern 27 iii Modules 27 Object Literals 27 The Module Pattern
    [Show full text]
  • Zope Documentation Release 5.3
    Zope Documentation Release 5.3 The Zope developer community Jul 31, 2021 Contents 1 What’s new in Zope 3 1.1 What’s new in Zope 5..........................................4 1.2 What’s new in Zope 4..........................................4 2 Installing Zope 11 2.1 Prerequisites............................................... 11 2.2 Installing Zope with zc.buildout .................................. 12 2.3 Installing Zope with pip ........................................ 13 2.4 Building the documentation with Sphinx ............................... 14 3 Configuring and Running Zope 15 3.1 Creating a Zope instance......................................... 16 3.2 Filesystem Permissions......................................... 17 3.3 Configuring Zope............................................. 17 3.4 Running Zope.............................................. 18 3.5 Running Zope (plone.recipe.zope2instance install)........................... 20 3.6 Logging In To Zope........................................... 21 3.7 Special access user accounts....................................... 22 3.8 Troubleshooting............................................. 22 3.9 Using alternative WSGI server software................................. 22 3.10 Debugging Zope applications under WSGI............................... 26 3.11 Zope configuration reference....................................... 27 4 Migrating between Zope versions 37 4.1 From Zope 2 to Zope 4 or 5....................................... 37 4.2 Migration from Zope 4 to Zope 5.0..................................
    [Show full text]
  • ELK: a Log Files Management Framework
    ELK: a log files management framework Giovanni Bechis <[email protected]> LinuxCon Europe 2016 About Me I sys admin and developer @SNB I OpenBSD developer I Open Source developer in several other projects searching through log files, the old way $ man 1 pflogsumm $ grep [email protected] /var/log/maillog | awk '{print $1 "-" $2 "-" $3;}' $ grep -e 'from=.*@gmail\.com' /var/log/maillog | grep "550" \ | awk {'print $1 "-" $2 "-" $3 " " $7 " " $10 " " $11 " " $13;}' $ vi logparser.sh $ git clone https://github.com/random/parser_that_should_work $ man 1 perltoc $ man 1 python searching through log files, the old way $ cssh -a 'mylogparser.py' host1 host2 host3 host4 | tee -a /tmp/parsedlogs.txt $ man syslogd(8) searching through log files, the new way ELK open source components I Beats: collect, parse and ship I Logstash: collect, enrich and transport data I Elasticsearch: search and analyze data in real time I Kibana: explore and visualize your data ELK closed source components I Watcher: alerting for Elasticsearch I Shield: security for Elasticsearch I Marvel: monitor Elasticsearch I Graph: analyze relationships Elasticsearch I open source search engine based on lucene library I nosql database (document oriented) I queries are based on http/json I APIs for lot of common languages, (or you can write your own framework, is just plain http and json) Elasticsearch: security I not available in open source version, you need Shield I Elasticsearch should not be exposed on the wild, use firewalling to protect your instances I manage security on your
    [Show full text]
  • FULLTEXT01.Pdf
    UPTEC F 18029 Examensarbete 30 hp Juni 2018 Investigation and Implementation of a Log Management and Analysis Framework for the Treatment Planning System RayStation Elias Norrby Abstract Investigation and Implementation of a Log Management and Analysis Framework for the Treatment Planning System RayStation Elias Norrby Teknisk- naturvetenskaplig fakultet UTH-enheten The purpose of this thesis is to investigate and implement a framework for log management and analysis tailored to the treatment planning system (TPS) Besöksadress: RayStation. A TPS is a highly advanced software package used in radiation Ångströmlaboratoriet Lägerhyddsvägen 1 oncology clinics, and the complexity of the software makes writing robust code Hus 4, Plan 0 challenging. Although the product is tested rigorously during development, bugs are present in released software. The purpose of the the framework is to allow the Postadress: RayStation development team insight into errors encountered in clinics by Box 536 751 21 Uppsala centralizing log file data recorded at clinics around the world. Telefon: A framework based on the Elastic stack, a suite of open-source products, is 018 – 471 30 03 proposed, addressing a set of known issues described as the access problem, the Telefax: processing problem, and the analysis problem. Firstly, log files are stored locally on 018 – 471 30 00 each machine running RayStation, some of which may not be connected to the Internet. Gaining access to the data is further complicated by legal frameworks Hemsida: such as HIPAA and GDPR that put constraints on how clinic data can be handled. http://www.teknat.uu.se/student The framework allows for access to the files while respecting these constraints.
    [Show full text]
  • Download Slide (PDF Document)
    When Django is too bloated Specialized Web-Applications with Werkzeug EuroPython 2017 – Rimini, Italy Niklas Meinzer @NiklasMM Gotthard Base Tunnel Photographer: Patrick Neumann Python is amazing for web developers! ● Bottle ● BlueBream ● CherryPy ● CubicWeb ● Grok ● Nagare ● Pyjs ● Pylons ● TACTIC ● Tornado ● TurboGears ● web2py ● Webware ● Zope 2 Why would I want to use less? ● Learn how stuff works Why would I want to use less? ● Avoid over-engineering – Wastes time and resources – Makes updates harder – It’s a security risk. Why would I want to use less? ● You want to do something very specific ● Plan, manage and document chemotherapy treatments ● Built with modern web technology ● Used by hospitals in three European countries Patient Data Lab Data HL7 REST Pharmacy System Database Printers Werkzeug = German for “tool” ● Developed by pocoo team @ pocoo.org – Flask, Sphinx, Jinja2 ● A “WSGI utility” ● Very lightweight ● No ORM, No templating engine, etc ● The basis of Flask and others Werkzeug Features Overview ● WSGI – WSGI 1.0 compatible, WSGI Helpers ● Wrapping of requests and responses ● HTTP Utilities – Header processing, form data parsing, cookies ● Unicode support ● URL routing system ● Testing tools – Testclient, Environment builder ● Interactive Debugger in the Browser A simple Application A simple Application URL Routing Middlewares ● Separate parts of the Application as wsgi apps ● Combine as needed Request Static files DB Part of Application conn with DB access User Dispatcher auth Part of Application without DB access Response HTTP Utilities ● Work with HTTP dates ● Read and dump cookies ● Parse form data Using the test client Using the test client - pytest fixtures Using the test client - pytest fixtures Interactive debugger in the Browser Endless possibilities ● Connect to a database with SQLalchemy ● Use Jinja2 to render documents ● Use Celery to schedule asynchronous tasks ● Talk to 3rd party APIs with requests ● Make syscalls ● Remote control a robot to perform tasks at home Thank you! @NiklasMM NiklasMM Photographer: Patrick Neumann.
    [Show full text]
  • HOWTO Use Python in the Web Release 2.7.9
    HOWTO Use Python in the web Release 2.7.9 Guido van Rossum and the Python development team December 10, 2014 Python Software Foundation Email: [email protected] Contents 1 The Low-Level View 2 1.1 Common Gateway Interface.....................................2 Simple script for testing CGI.....................................2 Setting up CGI on your own server..................................3 Common problems with CGI scripts.................................3 1.2 mod_python..............................................4 1.3 FastCGI and SCGI..........................................4 Setting up FastCGI..........................................5 1.4 mod_wsgi...............................................5 2 Step back: WSGI 5 2.1 WSGI Servers.............................................6 2.2 Case study: MoinMoin........................................6 3 Model-View-Controller 6 4 Ingredients for Websites 7 4.1 Templates...............................................7 4.2 Data persistence............................................8 5 Frameworks 8 5.1 Some notable frameworks......................................9 Django.................................................9 TurboGears..............................................9 Zope.................................................. 10 Other notable frameworks...................................... 10 Index 11 Author Marek Kubica Abstract This document shows how Python fits into the web. It presents some ways to integrate Python with a web server, and general practices useful for developing web
    [Show full text]
  • Repoze Documentation Release 1.0
    Repoze Documentation Release 1.0 Agendaless Consulting, Inc. and Contributors December 12, 2014 Contents 1 Overview of the Repoze Project3 1.1 Problems Addressed...........................................3 1.2 Solutions Provided............................................3 1.3 Software Requirements and Limitations.................................3 1.4 Technology Dependencies........................................3 1.5 Licensing.................................................4 1.6 Resources.................................................4 1.7 Legacy Resources............................................4 1.8 Contributing...............................................4 2 Current Repoze Components5 2.1 WSGI Middleware............................................5 2.2 Libraries.................................................6 3 Obsolete Repoze Components9 3.1 WSGI Applications...........................................9 3.2 WSGI Middleware............................................ 10 3.3 Libraries................................................. 11 3.4 Buildout-related............................................. 11 3.5 Miscellany................................................ 11 3.6 Re-packaged Software.......................................... 12 4 History of the Repoze Project 13 4.1 Early Developments........................................... 13 4.2 Later Developments........................................... 13 5 Hacking on Repoze Components 15 5.1 Coding Standards............................................. 15 5.2 Layout and
    [Show full text]
  • The Pyramid Web Application Development Framework Version 1.4.9
    The Pyramid Web Application Development Framework Version 1.4.9 Chris McDonough Contents Front Matteri Copyright, Trademarks, and Attributions iii Typographical Conventionsv Author Introduction vii I Narrative Documentation1 1 Pyramid Introduction3 2 Installing Pyramid 23 3 Application Configuration 31 4 Creating Your First Pyramid Application 35 5 Creating a Pyramid Project 41 6 Startup 65 7 Request Processing 69 8 URL Dispatch 75 9 Views 99 10 Renderers 111 11 Templates 127 12 View Configuration 141 13 Static Assets 159 14 Request and Response Objects 169 15 Sessions 177 16 Using Events 185 17 Environment Variables and .ini File Settings 189 18 Logging 201 19 PasteDeploy Configuration Files 209 20 Command-Line Pyramid 213 21 Internationalization and Localization 231 22 Virtual Hosting 249 23 Unit, Integration, and Functional Testing 253 24 Resources 261 25 Much Ado About Traversal 273 26 Traversal 281 27 Security 293 28 Combining Traversal and URL Dispatch 305 29 Invoking a Subrequest 315 30 Using Hooks 321 31 Pyramid Configuration Introspection 347 32 Extending An Existing Pyramid Application 361 33 Advanced Configuration 367 34 Extending Pyramid Configuration 375 35 Thread Locals 383 36 Using the Zope Component Architecture in Pyramid 387 II Tutorials 393 37 ZODB + Traversal Wiki Tutorial 395 38 SQLAlchemy + URL Dispatch Wiki Tutorial 445 39 Converting a repoze.bfg Application to Pyramid 505 40 Running a Pyramid Application under mod_wsgi 509 III API Reference 513 41 pyramid.authorization 515 42 pyramid.authentication 517 43 pyramid.config
    [Show full text]
  • The Hitchhiker's Guide to Packaging" Documentation
    The Hitchhiker’s Guide to Packaging" Documentation Release 1.0 Tarek Ziadé Sep 27, 2017 Contents 1 Table of Contents 3 1.1 Quick Start................................................3 1.2 Introduction to Packaging........................................5 1.3 Installing the Package Tools.......................................9 1.4 Using Packages.............................................. 12 1.5 Creating a Package............................................ 13 1.6 Contribute Your Package to the World.................................. 18 1.7 Virtual Environments........................................... 23 1.8 Specifications............................................... 24 1.9 Advanced Topics............................................. 28 1.10 Future of Packaging........................................... 28 1.11 Glossary................................................. 28 1.12 Credits.................................................. 31 1.13 License.................................................. 31 2 Indices and tables 33 Bibliography 35 i ii The Hitchhiker’s Guide to Packaging" Documentation, Release 1.0 Warning: This document is currently under development. Thank you for your interest. Contents 1 The Hitchhiker’s Guide to Packaging" Documentation, Release 1.0 2 Contents CHAPTER 1 Table of Contents Quick Start Here’s how to create a new project, which we’ll call TowelStuff. 1. Lay out your project The smallest python project is two files. A setup.py file which describes the metadata about your project, and a file containing Python code to implement the functionality of your project. In this example project we are going to add a little more to the project to provide the typical minimal layout of a project. We’ll create a full Python package, a directory with an __init__.py file, called towelstuff/. This anticipates future growth as our project’s source code is likely to grow beyond a single module file. We’ll also create a README.txt file describing an overview of your project, and a LICENSE.txt file containing the license of your project.
    [Show full text]
  • Dark Fiber Electronic Culture: History, Theory, Practice Timothy Druckrey, Series Editor
    Dark Fiber Electronic Culture: History, Theory, Practice Timothy Druckrey, series editor Ars Electronica: Facing the Future edited by Timothy Druckrey with Ars Electronica, 1999 net_condition: art and global media edited by Peter Weibel and Timothy Druckrey, 2001 Dark Fiber: Tracking Critical Internet Culture Geert Lovink Dark Fiber Tracking Critical Internet Culture Geert Lovink The MIT Press Cambridge, Massachusetts London, England © 2002 Massachusetts Institute of Technology All rights reserved. No part of this book may be reproduced in any form by any electronic or mechanical means (including photocopying, recording, or information storage and retrieval) without permission in writing from the publisher. Set in Bell Gothic and Courier by The MIT Press. Printed and bound in the United States of America. Library of Congress Cataloging-in-Publication Data Lovink, Geert. Dark fiber : tracking critical internet culture / Geert Lovink. p. cm. — (Electronic culture—history, theory, practice) Includes bibliographical references. ISBN 0-262-12249-9 (hc. : alk. paper) 1. Internet—Social aspects. 2. Information society. 3. Culture. I. Title. II. Series. HM851 .L68 2002 303.48'33—dc21 2001059641 Dark fiber refers to unused fiber-optic cable. Often times companies lay more lines than what’s needed in order to curb costs of having to do it again and again. The dark strands can be leased to individuals or other companies who want to establish optical connections among their own locations. In this case, the fiber is neither controlled by nor connected
    [Show full text]