dh-virtualenv-mold

KO | EN

gitlite — search

#javascript #python #hacktoberfest #react #android #machine-learning #deep-learning #java #windows #vue #pytorch #security #mcp #ios

dh-virtualenv-mold

(★ 26)

:cookie: A cookiecutter template to add easy Debianization to any existing Python project.

dh-virtualenv-mold 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# dh-virtualenv-mold

A [cookiecutter](http://cookiecutter.readthedocs.io/) template to
add easy Debianization to any existing Python project.
It creates a self-contained Python virtualenv wrapped into a Debian package
(an "omnibus" package, all passengers on board).
The packaged virtualenv is kept in sync with the host's interpreter automatically.
See [spotify/dh-virtualenv](https://github.com/spotify/dh-virtualenv) for more details.

[![Groups](https://img.shields.io/badge/Google_groups-springerle--users-orange.svg)](https://groups.google.com/forum/#!forum/springerle-users)
 ![Apache 2.0 licensed](http://img.shields.io/badge/license-Apache_2.0-red.svg)

The similar [debianized-pypi-mold](https://github.com/Springerle/debianized-pypi-mold)
creates a project to make a Debian package from any existing PyPI release.
It fits when you just want to package a 3rd party release.
If you plan to contribute Debian packaging to upstream instead, use this template.

## Preparations

In case you don't have the `cookiecutter` command line tool yet, here's
[how to install](https://github.com/Springerle/springerle.github.io#installing-the-cookiecutter-cli) it.

## Using the template

Adding this template to your existing Python project goes like this (make sure
you're in the root directory of your project):

```sh
cookiecutter https://github.com/Springerle/dh-virtualenv-mold.git
dch -r "" # add a proper distro and date to the changelog
```

It makes sense to `git add` the created directory directly afterwards, before any
generated files are added, that you don't want to have in your repository.

Note that you need to install the usual Debian development tools and `dh-virtualenv`
(at least version 0.8), before you can actually build the DEB package.
These incantations will perform that for you:

```sh
sudo apt-get install build-essential debhelper devscripts equivs
sudo mk-build-deps --install debian/control
```

Then, if you have all pre-requisites satisfied, try this:

```sh
dpkg-buildpackage -uc -us -b
```

The resulting package, if all went well, can be found in the parent of your project directory.
You can upload it to a Debian package repository via e.g. `dput`, see
[here](https://github.com/jhermann/artifactory-debian#package-uploading)
for a hassle-free solution that works with Artifactory and Bintray.

## Trouble-Shooting

### 'pkg-resources not found' or similar during virtualenv creation

If you get errors regarding ``pkg-resources`` during the virtualenv creation,
update your build machine's ``pip`` and ``virtualenv``.
The versions on many distros are just too old to handle current infrastructure (especially PyPI).

This is the one exception to “never sudo pip”, so go ahead and do this:

```sh
sudo pip install -U pip virtualenv
```

Then try building the package again.

## Related Projects

* [make-deb](https://github.com/nylas/make-deb) – A simple tool that generates
   a Debian configuration using dh-virtualenv,
   based on your setuptools configuration and git history.

dh-virtualenv-mold

dh-virtualenv-mold 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

dh-virtualenv-mold

dh-virtualenv-mold 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README