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

Bug#420334: marked as done (RFP: python-py++ -- An object-oriented framework for creating a code generator for Boost.Python library)

Your message dated Thu, 24 Apr 2008 11:59:54 -0600
with message-id <E1Jp5je-0006Ff-Bk@merkel.debian.org>
and subject line WNPP bug closing
has caused the Debian Bug report #420334,
regarding RFP: python-py++ -- An object-oriented framework for creating a code generator for Boost.Python library
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
420334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420334
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

* Package name    : python-py++
  Version         : 0.8.5
  Upstream Author : Roman Yakovenko <roman.yakovenko@gmail.com>
* URL             : http://www.language-binding.net/pyplusplus/pyplusplus.html
* License         : Boost Software License
  Programming Lang: Python
  Description     : An object-oriented framework for creating a code generator for Boost.Python library

Py++ uses GCC C++ compiler to parse C++ source files and allows you to
expose C++ code to Python in quick and elegant way using the
Boost.Python library.  It uses the following steps to do so:

- - source code is passed to GCC-XML
- - GCC-XML passes it to GCC C++ compiler
- - GCC-XML generates an XML description of a C++ program from GCC's
  internal representation.
- - Py++ uses pygccxml package to read GCC-XML generated file.

Feature list:

- - Py++ support almost all features found in Boost.Python library
- - Py++ generates code, which will help you to understand compiler
  generated error messages
- - Py++ has more than one mode of writing code into files:
	- single file
	- multiple files
	- multiple files, where single class code is split to few files
- - Py++ will save your compilation time - it will rewrite a file, only in
  case of change
- - You have full control over generated code. Your code could be inserted
  almost anywhere.
- - Py++ will check the "completeness" of the bindings. It will check for
  you that the exposed declarations don't have references to unexposed
  ones.
- - Py++ provides enough functionality to extract source code
  documentation and write it as Python documentation string
- - Py++ provides simple and powerful framework to create a wrapper for
  functions, which could not be exposed as is to Python

- -- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGKkdc4eu+pR04mIcRAp3aAJ9cPrF4T5yB/8yz73SUV155bQz9vACeJcaA
rNNpp46Jh00J/aTgjpDV8TE=
=jzJJ
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Hello,

This is an automatic mail sent to close the RFP you have reported or 
are involved with.

Your RFP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.

As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not 
intended by owners and submitters (like you) to be closed, for
example if the RFP is still of your interest, or there has been 
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).

To re-open it, you simply have to mail control@bugs.debian.org
with a body text like this:

 reopen 420334
 stop

Further comments on the work done in the bug sent to
420334@bugs.debian.org would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <damog@debian.org>.

A similar process is being applied to other kind of wnpp bugs.

Thanks for your cooperation,

 -- David Moreno Garza <damog@debian.org>.

--- End Message ---
Reply to: