storm 0.15-0ubuntu1 source package in Ubuntu


storm (0.15-0ubuntu1) karmic; urgency=low

  * New upstream release.
  * debian/control:
    - Make python-storm architecture-dependent, as Storm builds extensions
      now. (LP: #338420)
    - Add ${shlibs:Depends} to python-storm's Depends field.
  * debian/rules:
    - Update version number.
    - Remove no longer useful DH_ALWAYS_EXCLUDE -- we need /usr/lib now.
  * debian/copyright:
    - Update upstream copyright dates.
    - Replace '(C)' in Debian packaging copyright notice with 'copyright',
      which is actually legally meaningful.

 -- William Grant <email address hidden>   Tue, 18 Aug 2009 10:40:00 +1000

Upload details

Uploaded by:
William Grant on 2009-08-18
Uploaded to:
Original maintainer:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Lucid release on 2009-10-29 universe devel


File Size MD5 Checksum
storm_0.15.orig.tar.gz 212.3 KiB c7a756164017c119d62d26f8cda113e7
storm_0.15-0ubuntu1.diff.gz 2.7 KiB b2890a02b316063aa847a7a360e869f3
storm_0.15-0ubuntu1.dsc 1.1 KiB 949b06ecf47f4349c2a6493a4537c852

Available diffs

View changes file

Binary packages built by this source

python-storm: object-relational mapper (ORM) for Python

 Storm is an object-relation mapper (ORM) for the Python language. In
 simple terms, that kind of system allows rows from a relational
 database to be seen as objects in an object-oriented language like
  * Clean and lightweight API offers a short learning curve and long-
    erm maintainability.
  * Storm is developed in a test-driven manner. An untested line of
    code is considered a bug.
  * Storm needs no special class constructors, nor imperative base
  * Storm is well designed (different classes have very clear
    boundaries, with small and clean public APIs).
  * Designed from day one to work both with thin relational databases,
    such as SQLite, and big iron systems like PostgreSQL and MySQL.
  * Storm is easy to debug, since its code is written with a KISS
    principle, and thus is easy to understand.
  * Designed from day one to work both at the low end, with trivial
    small databases, and the high end, with applications accessing
    billion row tables and committing to multiple database backends.
  * It's very easy to write and support backends for Storm (current
    backends have around 100 lines of code).