Debianize uses fpm (https://github.com/jordansissel/fpm) to create debian packages from python source directories. The only thing it really adds, is that debianize will also create packages for all depencencies that your source package has (install_requires). Debianize will only create a debian package from a python package. So you need a setup.py.
note! If you are not using buildout but still want to use debianize, use https://gist.github.com/2929586, which is just a shell script that does the same, but is configured with flags
[buildout] parts = debianize [debianize] maintainer = firstname.lastname@example.org follow_dependencies = someobscurepackage morestuff ivegotnodebianpackageyet
If you define follow_dependencies debianize will only create packages for things that match any of the regex patterns in that option. If omit follow_dependencies, it will build debian packages for anything defined as a dependency with install_requires. You can not use spaces in any of the patterns! This is useful if some of the dependencies are allready available as debian packages and others are not.
The above defined follow_dependencies will be matched like this:
$NAME =~ someobscurepackage|morestuff|ivegotnodebianpackageyet
So it will simply put a | symbol in between the patterns.
If you've got a folder named upstart next to your setup.py, this folder will be packaged as well, with the same version number as your package, but adding a .d postfix to your package name.
This recipe does not install fpm for you. instead use http://pypi.python.org/pypi/rubygemsrecipe/0.1.6:
[rubygems] recipe = rubygemsrecipe gems = fpm