DOCSLIB.ORG

Yarely – a Software Player for Open Pervasive Display Networks

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Yarely – a Software Player for Open Pervasive Display Networks Yarely – A Software Player for Open Pervasive Display Networks Sarah Clinch, Nigel Davies, Adrian Friday, Graham Clinch School of Computing and Communications, InfoLab21 Lancaster University, Lancaster, LA1 4WA. United Kingdom. [s.clinch | nigel | adrian] @comp.lancs.ac.uk, [email protected] ABSTRACT signage system that has operated at Lancaster University This paper describes Yarely, a software player designed to since 2005. The system consists of a wide range of displays support the next generation of pervasive display networks. including indoor and outdoor installations and both pro- We identify five design goals for future digital signage play- jected and LCD technology. Content creators in e-Campus ers: the ability to provide basic signage functionality (media use the system to create \channels" of signage content that scheduling and playback) and support for openness, extensi- they subsequently publish within the network. Display own- bility, resilience and appropriation. The paper describes the ers subscribe their displays to these channels and the system design and implementation of Yarely in light of these design automatically schedules content to each display based on the goals. We present an evaluation of the system in the form combination of subscriptions and channels relevant to that of deployment and usage data alongside a reflection on the display. Of particular note is the fact that e-Campus offers degree to which Yarely successfully addresses the needs of an API that enables developers to create new applications future pervasive display systems. to control the signage network [14]. The e-Campus system was based on an experimental soft- ware infrastructure that relied on a complex series of mes- Categories and Subject Descriptors sage events to coordinate playout amongst screens. Whilst H.5 [Information Interfaces and Presentation]: Mis- our initial predictions for the software suggested that the un- cellaneous derlying eventing system would be able to handle large num- bers of displays (estimated at between 7,000{15,000 events General Terms per second with 250 displays) we found that during a typ- ical day's operation on campus with 25 screens the system Design, Reliability quickly began to lag. This slowdown was despite a rela- tively modest event channel throughput measured at ap- Keywords proximately 40 events per second. We found that this was public displays, system architecture, experiences partly due to the communications overhead of the e-Campus API over the event channel, but also due to the 250,000 or 1. INTRODUCTION so database queries needed to calculate the schedules for the displays given the 66 content channels and 3,000 or so In this paper we describe Yarely { a software player de- content items in the system. Despite providing the main sig- signed to support the next generation of digital signage and nage infrastructure on campus for seven years, this reliance pervasive display networks. Our work is motivated by a on a common eventing infrastructure and centralised high vision of large-scale networks of pervasive displays forming level scheduler led to a number of concerns with the existing a new communications medium that is open to content and system: applications from a wide range of sources [4]. We believe this openness will encourage innovation and reduce reliance on excessive fragility our system was extremely sensitive to traditional models of funding through advertising { enabling interruptions in network connectivity with these typi- a broad range of signage scenarios such as emergency coordi- cally leading to blank screens or \stuck" displays. nation, personalised information, situated applications and community information sharing. scalability concerns our eventing infrastructure struggled We have previously reported on the design and implemen- to scale as the number of displays grew above 20, and tation of the e-Campus system [14] { an experimental digital became less reliable as each new screen was added. no support for off-line nodes our system could not sup- port ad-hoc deployment of screens (e.g. at conferences) Permission to make digital or hard copies of all or part of this work for without connection back to our infrastructure. personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies problems with firewalls our system did not have support bear this notice and the full citation on the first page. To copy otherwise, to for traversing through firewalls which limited deploy- republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. ment options. PerDis 2013 June 04 - 05 2013, Mountain View, CA, USA Copyright 2013 ACM 978-1-4503-2096-2/13/06 ...$15.00. difficulty in pre-fetching content because our displays 25 received instructions on a per content item basis they We also recognised that in order to have our player widely could only pre-fetch a single item of content at a time. adopted it was crucial to develop a multi-platform solution and one that would scale to very large deployments. Together these limitations acted as a barrier to scaling the system beyond the University campus, and even prevented 2.4 Resilience and Disconnected Operation us from increasing the size of the on-campus display network. Core to our design goals is the need to provide a resilient The large-scale, open nature of the future display networks player. Our experiences with e-Campus taught us that hav- we envisaged could not be met by our existing software. ing a tightly-coupled system that relied on network connec- In 2011 we decided to completely re-engineer our software tivity led to significant periods of time when screens failed. infrastructure from the ground up in order to support our vi- We were also aware that while a campus may have generally sion of large-scale open signage systems. In so doing we drew good network connections, many displays are installed at lo- on our extensive experience with the e-Campus system. We cations with little or no network connectivity. As a result begun the re-engineering by creating a new software player we set ourselves the goal of developing a system that was for our signage network. In this paper we describe the design fully functional without network connectivity. In particular, and implementation of this component. we wished to create a system that could make autonomous We observe that in contrast to many papers on digital scheduling decisions and could source content from multiple signage that focus on user experience or new display tech- local sources without network connectivity. nologies, we explicitly aim to provide the community with engineering details of a single component in order to help fa- 2.5 Appropriation cilitate other researchers to create robust open signage sys- Our vision of an open pervasive display network relies on tems. display networks providing users with the ability to appro- priate displays for a wide range of applications. Such ap- 2. DESIGN GOALS propriation might range from simply tailoring content such as news or weather broadcasts through to users executing Our experiences with the e-Campus system enabled us their own applications on a public display and interacting to arrive at a series of concrete design goals for the Yarely with the display for significant periods of time. As a result, player. we set ourselves the design goal of supporting a wide range 2.1 Addressing General Functional Require- of sensing and appropriation methods. In contrast to many ments systems, we specifically designed our player to enable users to execute native applications locally on the display. Clearly, at a minimum, the player needed to support gen- eral signage functionality such as displaying content of a range of media types and on a range of displays. Since we 3. DESIGN AND IMPLEMENTATION are only concerned with the requirements for the player in this paper, we do not consider the more general requirements 3.1 Overall Architecture relating to issues such as content creation and scheduling. For the purposes of this paper we consider digital signage systems to comprise of two main architectural segments { 2.2 Openness Display Nodes (upon which our player software executes) In developing our player we considered it critical that the and sources of content located within the broader network display was able to serve as a component of a future open (e.g. as a Web or cloud service). We recognise of course that display network. Most signage players assume that they display networks are significantly more complex and include are controlled by a single authoritative source that supplies components such as ad-brokers, content creation tools and them with both content and a play out schedule. Our goal scheduling, but this simple model serves to highlight the fact was to design a player that could easily be connected to that Display Nodes are typically separate to content sources. multiple content sources simultaneously. This represents a An important architectural decision for any signage sys- fundamental shift in thinking of signage systems { instead of tem is the distribution of functionality between display clients a player being treated as a simple \slave" that plays the con- and cloud based services such as content sources. For exam- tent that is sent to it, we aimed to create a more intelligent ple, it is possible to construct signage systems in which dis- player that is able to schedule content from multiple sources play clients simply run standard Web browsers and all of the that are not necessarily aware of each other and hence may functionality is provided through cloud services. In contrast, provide the player with conflicting play out requirements. many existing commercial signage systems have relatively To achieve such a degree of openness we specifically set our- feature-rich clients in order to enable them to survive peri- selves the goal of providing a mechanisms that would enable ods of disconnection.
Load more

Recommended publications
  • Working with System Frameworks in Python and Objective-C
    Working with System Frameworks in Python and Objective-C by James Barclay Feedback :) j.mp/psumac2015-62 2 Dude, Where’s My Source Code? CODE https://github.com/futureimperfect/psu-pyobjc-demo https://github.com/futureimperfect/PSUDemo SLIDES https://github.com/futureimperfect/slides 3 Dude, Where’s My Source Code? CODE https://github.com/futureimperfect/psu-pyobjc-demo https://github.com/futureimperfect/PSUDemo SLIDES https://github.com/futureimperfect/slides 3 Dude, Where’s My Source Code? CODE https://github.com/futureimperfect/psu-pyobjc-demo https://github.com/futureimperfect/PSUDemo SLIDES https://github.com/futureimperfect/slides 3 Agenda 1. What are system frameworks, and why should you care? 2. Brief overview of the frameworks, classes, and APIs that will be demonstrated. 3. Demo 1: PyObjC 4. Demo 2: Objective-C 5. Wrap up and questions. 4 What’s a System Framework? …and why should you care? (OS X) system frameworks provide interfaces you need to write software for the Mac. Many of these are useful for Mac admins creating: • scripts • GUI applications • command-line tools Learning about system frameworks will teach you more about OS X, which will probably make you a better admin. 5 Frameworks, Classes, and APIs oh my! Cocoa CoreFoundation • Foundation • CFPreferences - NSFileManager CoreGraphics - NSTask • Quartz - NSURLSession - NSUserDefaults • AppKit - NSApplication 6 CoreFoundation CoreFoundation is a C framework that knows about Objective-C objects. Some parts of CoreFoundation are written in Objective-C. • Other parts are written in C. CoreFoundation uses the CF class prefix, and it provides CFString, CFDictionary, CFPreferences, and the like. Some Objective-C objects are really CF types behind the scenes.
    [Show full text]
  • Macspeechx.Py MODULE and ITS USE in an ACCELERATOR CONTROL SYSTEM Noboru Yamamoto*, J-PARC Cener, KEK and JAEA, Ibaraki, JAPAN
    Proceedings of ICALEPCS2013, San Francisco, CA, USA TUPPC109 MacspeechX.py MODULE AND ITS USE IN AN ACCELERATOR CONTROL SYSTEM Noboru Yamamoto*, J-PARC cener, KEK and JAEA, Ibaraki, JAPAN Abstract With additional functionality such as user interface or macspeechX.py[1] is a Python module to accels speech selection of voices for specified UDP ports, this program synthesis library on MacOSX. This module have been can fit one or two pages of the paper used in the vocal alert system in KEKB[2] and J- While this system running without serious problem PARC[3] accelerator control system. Recent upgrade of until MacOSX came to the market. In Python on this module allow us to handle non-English lanugage, MacOSX does not includes macspeech.py as a its such as Japanese, through this module. Implementation components. It means we need to develop our own detail will be presented as an example of Python program solution before old Mac hardware would be replaced by accessing system library. new hardware which just runs MacOSX. SPEECH SYNTHESIS IN CONTROL In the next section, we will see several ways to write SYSTEMS Python module which bridges C/C++ library. In some control system, alerts to the operators can be sent as vocal messages. It used be require the special hardware or software to generate vocal message from computers in the system. When we started commissioning of KEKB accelerator, such an alert system was requested. We picked up: • speech synthesis library includes as one of standard libraries on Macintosh OS from Apple. • Macspeech.py module distributed as one of standard module with Python programming Langauge Figure 1: Software overview of KEKB/J-PARC vocal With these two components, we could build a very low alert system.
    [Show full text]
  • Python for the C# Developer
    {SDD} 2014 Software Design & Development Python for the C# developer Michael Kennedy @mkennedy http://blog.michaelckennedy.net Objectives • Introduce the basics of the Python language • Review what is awesome about C# and .NET • Explore Python's version of each C# / .NET feature DEVELOPMENTOR Michael Kennedy | @mkennedy | blog.michaelckennedy.net What is Python? • High-level programming language • Interpreted (sometimes JIT compiled) • Object-oriented (especially Python 3) • Strongly-typed with dynamic semantics • Syntax emphasizes readability • Supports modules and packages • Batteries included (large standard library [1]) DEVELOPMENTOR Michael Kennedy | @mkennedy | blog.michaelckennedy.net The ‘shape’ of a Python program • Python defines code blocks (known as suites in Python) using whitespace and colons. Things to note: def somemethod(name): • No semicolons if name == "Michael": print("Hi old friend") • Code blocks start with ‘:’ else: • Whitespace really really matters print("Nice to meet you") • There are no braces print("My name is … ") • There are no parentheses • Tabs are not your friend def main(): somemethod() Code suites DEVELOPMENTOR Michael Kennedy | @mkennedy | blog.michaelckennedy.net Python language demo DEVELOPMENTOR Michael Kennedy | @mkennedy | blog.michaelckennedy.net What's awesome about C# and .NET? System.Object: Everything is an object. LINQ IEnumerable + foreach loops Visual Studio / IDEs Class properties ( int Age {get; set;} ) Side-by-side execution (isolation) Anonymous types Iterator methods / yield return
    [Show full text]
  • Bleak Documentation Release 0.12.1
    bleak Documentation Release 0.12.1 Henrik Blidh Jul 07, 2021 Contents 1 Features 3 1.1 Installation................................................3 1.2 Scan/Discover..............................................4 1.3 Usage...................................................6 1.4 Bleak backends..............................................6 1.5 Interfaces, exceptions and utils......................................8 1.6 Troubleshooting............................................. 24 1.7 Contributing............................................... 28 1.8 Credits.................................................. 29 1.9 Changelog................................................ 30 2 Indices and tables 43 Python Module Index 45 Index 47 i ii bleak Documentation, Release 0.12.1 Bleak is an acronym for Bluetooth Low Energy platform Agnostic Klient. • Free software: MIT license • Documentation: https://bleak.readthedocs.io. Bleak is a GATT client software, capable of connecting to BLE devices acting as GATT servers. It is designed to provide a asynchronous, cross-platform Python API to connect and communicate with e.g. sensors. Contents 1 bleak Documentation, Release 0.12.1 2 Contents CHAPTER 1 Features • Supports Windows 10, version 16299 (Fall Creators Update) or greater • Supports Linux distributions with BlueZ >= 5.43 (See Linux backend for more details) • OS X/macOS support via Core Bluetooth API, from at least OS X version 10.11 Bleak supports reading, writing and getting notifications from GATT servers, as well as a function for discovering BLE devices. Contents: 1.1 Installation 1.1.1 Stable release To install bleak, run this command in your terminal: $ pip install bleak This is the preferred method to install bleak, as it will always install the most recent stable release. If you don’t have pip installed, this Python installation guide can guide you through the process. 1.1.2 From sources The sources for bleak can be downloaded from the Github repo.
    [Show full text]
  • Python Guide Documentation 0.0.1
    Python Guide Documentation 0.0.1 Kenneth Reitz 2015 09 13 Contents 1 Getting Started 3 1.1 Picking an Interpreter..........................................3 1.2 Installing Python on Mac OS X.....................................5 1.3 Installing Python on Windows......................................6 1.4 Installing Python on Linux........................................7 2 Writing Great Code 9 2.1 Structuring Your Project.........................................9 2.2 Code Style................................................ 15 2.3 Reading Great Code........................................... 24 2.4 Documentation.............................................. 24 2.5 Testing Your Code............................................ 26 2.6 Common Gotchas............................................ 30 2.7 Choosing a License............................................ 33 3 Scenario Guide 35 3.1 Network Applications.......................................... 35 3.2 Web Applications............................................ 36 3.3 HTML Scraping............................................. 41 3.4 Command Line Applications....................................... 42 3.5 GUI Applications............................................. 43 3.6 Databases................................................. 45 3.7 Networking................................................ 45 3.8 Systems Administration......................................... 46 3.9 Continuous Integration.......................................... 49 3.10 Speed..................................................
    [Show full text]
  • Cocoa Fundamentals Guide
    Cocoa Fundamentals Guide 2006-10-03 registered in the United States and other Apple Computer, Inc. countries. © 2006 Apple Computer, Inc. Adobe, Acrobat, and PostScript are All rights reserved. trademarks or registered trademarks of Adobe Systems Incorporated in the U.S. No part of this publication may be and/or other countries. reproduced, stored in a retrieval system, or transmitted, in any form or by any means, Intel and Intel Core are registered mechanical, electronic, photocopying, trademarks of Intel Corportation or its recording, or otherwise, without prior subsidiaries in the United States and other written permission of Apple Computer, Inc., countries. with the following exceptions: Any person Java and all Java-based trademarks are is hereby authorized to store documentation trademarks or registered trademarks of Sun on a single computer for personal use only Microsystems, Inc. in the U.S. and other and to print copies of documentation for countries. personal use provided that the OpenGL is a registered trademark of Silicon documentation contains Apple’s copyright Graphics, Inc. notice. Simultaneously published in the United The Apple logo is a trademark of Apple States and Canada. Computer, Inc. Even though Apple has reviewed this document, Use of the “keyboard” Apple logo APPLE MAKES NO WARRANTY OR (Option-Shift-K) for commercial purposes REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO THIS without the prior written consent of Apple DOCUMENT, ITS QUALITY, ACCURACY, may constitute trademark infringement and MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. AS A RESULT, THIS unfair competition in violation of federal DOCUMENT IS PROVIDED “AS IS,” AND and state laws.
    [Show full text]
  • Building Python Modules on Circleci OS X Instances
    Building Python modules on CircleCI OS X instances Recently I've been building a couple of supplimental build tools in Python for enhancing the development process of the iOS application I work on. I've been trying to make these tools to be appealing for other developers to use and integrate into their systems as well. I see having CI and unit tests as a core part of this goal. I started using CircleCI for my continuous integration environment for these projects. This was working out very well until I started working on some code that relies on a couple of OS X specific APIs. Due to that requirement I was unable to continue using the Linux platform for testing this code. Luckily CircleCI provides OS X instances for open source Mac and iOS projects. I put in a request and was granted access to using OS X instances for building this Python tool. However, I immediately ran into issues with getting the tool to be installed and have my tests run. CircleCI doesn't provide engineering support for free accounts, so I had to work all this out on my own, hopefully you can use this as a guide to also be able to support building Python on OS X build instances on CircleCI. Background The Python tool I am writing relies on the pyobjc framework. This allows Python to make calls into Cocoa and the various other frameworks provided by Apple on OS X. This comes pre-installed on OS X with the system Python version, 2.7.10.
    [Show full text]
  • Python Setup and Usage Release 3.3.3
    Python Setup and Usage Release 3.3.3 Guido van Rossum Fred L. Drake, Jr., editor November 17, 2013 Python Software Foundation Email: [email protected] CONTENTS 1 Command line and environment3 1.1 Command line............................................3 1.2 Environment variables........................................7 2 Using Python on Unix platforms 11 2.1 Getting and installing the latest version of Python.......................... 11 2.2 Building Python........................................... 12 2.3 Python-related paths and files.................................... 12 2.4 Miscellaneous............................................ 12 2.5 Editors................................................ 12 3 Using Python on Windows 15 3.1 Installing Python........................................... 15 3.2 Alternative bundles.......................................... 15 3.3 Configuring Python......................................... 16 3.4 Python Launcher for Windows.................................... 18 3.5 Additional modules......................................... 21 3.6 Compiling Python on Windows................................... 21 3.7 Other resources............................................ 22 4 Using Python on a Macintosh 23 4.1 Getting and Installing MacPython.................................. 23 4.2 The IDE............................................... 24 4.3 Installing Additional Python Packages................................ 24 4.4 GUI Programming on the Mac.................................... 24 4.5 Distributing Python Applications
    [Show full text]
  • Introduction to Pyobjc
    Introduction to PyObjC Author Bob Ippolito Conference PyCon DC, March 2005 Intended Audience • Python developers using Mac OS X 10.3 or later • Spies from the Linux and Win32 camps • Hopefully a GNUstep porter/maintainer Topics • Installing PyObjC • Why Bother? • Objective-C Primer • Crossing the Bridge • Interface Builder • Your First Application • Help! • Who's Using This Stuff? Installing PyObjC Install Xcode: http://developer.apple.com/ Install PyObjC: http://pyobjc.sourceforge.net/ Why Bother? • You paid for that Mac • The tools kick ass • Apple (often) writes good code • The tools kick ass • Objective-C and Python are friends Objective-C • True superset of C • Everything is not an object • Looks kinda like Smalltalk Classes • Flat Namespace • Single Inheritance • ... with Categories and Protocols • Classes are objects • Instance Variables Objective-C Interface @interface MyClass : NSObject { int myInt; } +(id)myClassWithInt:(int)anInt; -(int)myInt; @end Objective-C Implementation @implementation MyClass +(id)myClassWithInt:(int)anInt; { self = [[self alloc] init]; intInstanceVariable = anInt; return self; } -(int)myInt { return myInt; } @end Objects • Separate alloc/init • Everything is an accessor • ... except when using Key-Value Coding • Reference counted • ... but we take care of that • ... except where Apple doesn't Messages • Target • ... can be nil • Selector • Arguments Exceptions • Exceptions are exceptional • Expect bad code to just crash • ... even from Python Crossing the Bridge • unicode, int, long, float work magically • ... str is not safely bridged! • None is just like nil • ... except you can't send messages to it! Objective-C Messages Objective-C Message: [aMutableArray addObject:@"someObject"] Target: aMutableArray Selector: addObject: Arguments: @"someObject" PyObjC Messages Python Message: aMutableArray.addObject_(u'someObject') Target: aMutableArray Selector: addObject: (with colons replaced by underscores!) Arguments: u'someObject' (unicode is equivalent to @"string") Key-Value Coding • Kinda like getattr protocol • ..
    [Show full text]
  • Objective C Property Class
    Objective C Property Class Heptavalent Demetrius shines half-heartedly. Canopic and Heraclean Chance imprisons so unco that Amadeus uprouse his exoplasms. Is Kalvin canted or spleeny after surrendered Georg foretell so wholesomely? Value objects should be immutable: this is required for the implicit contract that two value objects created equal, should remain equal. Having both versions of VIPER in a project will enrich an agriculture with Wireframe naming since both versions of VIPER base wireframes have to same name. Conversion from Celsius to Fahrenheit. You want to create class methods that access static variables which, as others have said, have only a slightly different syntax. Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings. NSObject is cold most basic class that Objective-C provides You'll. Objc The PyObjC bridge PyObjC the Python to Objective. Which contradict this dream to, ivar or property? No compile errors and no unnecessary cluttered interface file! You can extract the help developers focus on the heart to make a parent. Any articles or links that only serve to promote a paid product or service may be removed at our discretion. Default to extract name after the property prefixed by the underscore. Having called a property provides an object but the properties and classes can add it only initialize immutable and even from. To do this, were over again your leave and linger the Build Settings tab. What i forgot apple, which will be copied as local owning module in objective c name. If god have an expertise and want make call each instance method, how would bale do it? The following attributes allow commission to legal custom names instead.
    [Show full text]
  • Python Setup and Usage Release 3.4.3
    Python Setup and Usage Release 3.4.3 Guido van Rossum and the Python development team July 16, 2015 Python Software Foundation Email: [email protected] Contents 1 Command line and environment3 1.1 Command line............................................3 1.2 Environment variables........................................7 2 Using Python on Unix platforms 11 2.1 Getting and installing the latest version of Python.......................... 11 2.2 Building Python........................................... 12 2.3 Python-related paths and files.................................... 12 2.4 Miscellaneous............................................ 12 2.5 Editors................................................ 12 3 Using Python on Windows 15 3.1 Installing Python........................................... 15 3.2 Alternative bundles.......................................... 15 3.3 Configuring Python......................................... 15 3.4 Python Launcher for Windows.................................... 17 3.5 Additional modules......................................... 21 3.6 Compiling Python on Windows................................... 21 3.7 Other resources............................................ 22 4 Using Python on a Macintosh 23 4.1 Getting and Installing MacPython.................................. 23 4.2 The IDE............................................... 24 4.3 Installing Additional Python Packages................................ 24 4.4 GUI Programming on the Mac.................................... 24 4.5 Distributing Python Applications
    [Show full text]
  • Py2app Documentation Release 0.26
    py2app Documentation Release 0.26 Ronald Oussoren, Bob Ippolito Sep 19, 2021 Contents 1 Contents 3 1.1 Installation................................................3 1.2 Tutorial..................................................4 1.3 Debugging application building.....................................5 1.4 Dependencies...............................................6 1.5 Environment in launched applications..................................6 1.6 Frequently Asked Questions.......................................7 1.7 Tweaking your Info.plist.........................................8 1.8 Example setup.py templates.......................................9 1.9 py2app Options.............................................. 11 1.10 Recipes.................................................. 14 1.11 Implementation Details......................................... 16 1.12 py2applet................................................. 18 1.13 Release history.............................................. 18 2 Online Resources 43 3 License 45 i ii py2app Documentation, Release 0.26 py2app is a Python setuptools command which will allow you to make standalone application bundles and plugins from Python scripts. py2app is similar in purpose and design to py2exe for Windows. Contents 1 py2app Documentation, Release 0.26 2 Contents CHAPTER 1 Contents 1.1 Installation 1.1.1 Installing with pip To install py2app using pip, or to upgrade to the latest released version of py2app: $ pip3 install -U py2app 1.1.2 Installing from source To install py2app from source, simply
    [Show full text]