`gpypi` – Welcome to g-pypi’s documentation!¶

write ebuilds to overlay or stdout (formatted in ansi color, html and bbcode)
install ebuilds through portage
use MY_P, MY_PN, MY_PV when needed using Bash substitutions
extract metadata from PyPi like HOMEPAGE, DESCRIPTION, LICENSE, AUTHOR, etc.
determine RDEPEND / DEPEND from setuptools: install_requires, tests_require, setup_requires and extras_require
determine PYTHON_MODNAME from setuptools: packages, py_modules and package_dir
determine S by unpacking ebuild
discovers Sphinx documentation
discovers examples
discovers nosetests and setup.py test
generates ebuilds for dependencies
uses Portage-alike colorful output
offers customizable configuration
support for python setup.py sdist_ebuild
updates Manifest file
generates metadata.xml file
appends ChangeLog file

Overview

gpypi is a command line tool for creating Gentoo portage ebuilds from Python Package Index.

gpypi was started as part of Google Summer of Code 2010 by Domen Kožar, mentored by Jesus Rivero.

gpypi is not meant to be a Gentoo developer replacement. On the contrary, it’s goal is to make his (hers) life easier.

Indices and tables¶