[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#409740: ITP: python-guppy -- object and heap memory sizing, profiling and analysis in Python

Package: wnpp
Severity: wishlist
Owner: Yaroslav Halchenko <debian@onerussian.com>

* Package name    : python-guppy
  Version         : 0.1.6
  Upstream Author : Sverker Nilsson <sn@sncs.se>
* URL             : http://guppy-pe.sourceforge.net
* License         : MIT
  Programming Lang: Python, C
  Description     : object and heap memory sizing, profiling and analysis in Python
 Guppy-PE is a programming environment providing object and heap
 memory sizing, profiling and analysis. It includes a prototypical
 specification language that can be used to formally specify aspects of
 Python programs and generate tests and documentation from a common
 Modules which constitute the environment:
  - Heapy: debugging and optimization regarding memory related issues in
    Python programs
  - GSL (Guppy Specification Language): describes aspects of a system,
    especially its API, in a way that can be automatically converted to
    tests as well as to documents
  - Guppy: umbrella package combining Heapy and GSL with support
    utilities such as the Glue module that keeps things together.


Heapy is somewhat an alternative to pysizer (http://pysizer.8325.org),
which unfortunately wasn't developed recently. That is why I ITP guppy
in favor over pysizer at the moment.

I am still not sure what name should be. Debian python policy advises
(uses verb "should", not "must") to use python-MODULE package name for
public modules. But I am not sure if python- prefix is still worth its
use, since we have debtags now. So at the end bin package name might
simply change to guppy or guppy-pe. Any advice is welcome.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-686
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

Reply to: