Python for S60

Python for S60
Name	Python for S60
Title	Python for S60
Developer	Nokia
Released	2005
Latest release	2.0.0
Operating system	Symbian OS
Programming language	C, Python
License	MIT (later)

Python for S60

Python for S60 was an implementation of the Python programming language for devices running Symbian OS on S60 platforms developed by Nokia, enabling scripting and application development on mobile handsets. It brought an interactive interpreter and an application runtime to devices from manufacturers such as Nokia, Sony Ericsson, and Samsung, and intersected with ecosystems represented by companies and projects like Intel, ARM, Microsoft, Google, Apple, and IBM through mobile development trends. The project connected to initiatives and standards in the mobile and open source domains including the Eclipse Foundation, KDE, GNOME, Apache Software Foundation, Mozilla, and the Linux Foundation.

History

The project emerged in the context of early mobile software efforts alongside milestones such as the launch of the Nokia 6600 and the rise of Symbian, during eras marked by events like the dot-com bubble and initiatives from organizations including the European Union and the United Nations. Development involved contributors from entities like Nokia, the Python Software Foundation, and third-party vendors such as Trolltech and Qt Software, and paralleled releases from Microsoft Windows Mobile, Google Android, and Apple iPhone that reshaped mobile platforms. Influential figures and institutions in computing—such as Guido van Rossum, Linus Torvalds, Richard Stallman, Alan Turing, and institutions like MIT, Stanford University, and the University of Cambridge—formed the broader intellectual milieu. Releases and milestones were announced in channels associated with industry conferences including Mobile World Congress, CeBIT, and the Consumer Electronics Show where companies like Ericsson, Motorola, and BlackBerry (Research In Motion) showcased competing devices.

Features and Architecture

The runtime delivered an interactive prompt, interpreter, and extension modules integrating with Symbian APIs and handset services from Nokia, Ericsson, Sony Ericsson, Samsung, and Fujitsu. Architecture design referenced patterns familiar to contributors from organizations such as Intel, ARM, Microsoft Research, IBM Research, Oracle, and Sun Microsystems, and drew on cross-platform toolchains used by projects like GCC, LLVM, and the GNU Project. Components interfaced with multimedia and telephony stacks implemented by vendors including Broadcom, Qualcomm, Texas Instruments, and Nokia Networks. The binary packaging and performance considerations echoed debates involving standards bodies and consortia such as the IETF, W3C, IEEE, and ISO.

Development and APIs

APIs exposed phone functionality including UI, file system, sockets, Bluetooth, and messaging, interoperating with libraries and frameworks produced by companies like Trolltech (Qt), Nokia (Symbian C++), Ericsson (R&AT), and Carnegie Mellon University research projects. Developers used tools and IDEs from Eclipse Foundation projects, Microsoft Visual Studio for cross-compilation discussions, and build systems influenced by GNU Automake, CMake, and SCons. The community contributed bindings and modules comparable to work from the Apache Software Foundation, Mozilla, KDE, GNOME, and Free Software Foundation projects, with academic contributions from institutions such as University of California, Berkeley, Harvard University, and ETH Zürich. Notable industry partners and vendors supporting testing included Vodafone, Orange, T-Mobile, AT&T, and Telefónica.

Deployment and Packaging

Distribution used SIS installers, signed packages, and OTA provisioning methods aligned with carrier practices from Vodafone, O2, Telefonica, and Verizon; device certification processes paralleled those of handset makers like Nokia, Sony Ericsson, Motorola, and Samsung. Packaging and repository efforts were influenced by software distribution models established by Debian, Red Hat, Canonical (Ubuntu), and SUSE, and provisioning protocols referenced specifications from ETSI and 3GPP. Deployment scenarios considered enterprise environments led by IBM, Microsoft, and Oracle and consumer marketplaces developed by mobile carriers and regional retailers. Testing and continuous integration drew on systems and methodologies from Hewlett-Packard, Dell, Cisco, and Intel.

Community and Adoption

Adoption occurred among hobbyists, academic researchers, and companies including Nokia, Symbian Ltd., and third-party developers who published examples and utilities. The user and developer community intersected with broader open source networks represented by the Python Software Foundation, GNOME Foundation, KDE e.V., Apache, and contributors associated with projects sponsored by Google Summer of Code, Mozilla, and the Eclipse Foundation. Educational use referenced curricula and outreach by institutions such as MIT, Oxford University, Stanford University, Carnegie Mellon University, and the University of Cambridge; community events paralleled gatherings like PyCon, OSCON, FOSDEM, and local user groups organized in cities like London, New York, Bangalore, and Helsinki.

Security and Limitations

Security considerations involved platform constraints, sandboxing, signing requirements imposed by carriers and handset manufacturers such as Nokia, Sony Ericsson, and Samsung, and cryptographic practices discussed in forums involving NIST, IETF, and ISO. Limitations included resource constraints on CPU and memory compared with contemporaneous platforms from Apple, Google, and Microsoft, compatibility issues across Symbian releases managed by Symbian Ltd. and Nokia, and eventual obsolescence as platforms shifted toward iOS and Android ecosystems championed by Apple and Google. Legacy concerns were raised in contexts involving archival institutions and museums including the Computer History Museum, Library of Congress, and national archives preserving mobile software artifacts.

Category:Python implementations Category:Symbian software