Fpm: virtualenv source cannot use virtualenv-tools in py3 without patch

[dogonthehorizon]

Hi friends, I've been mucking about with the virturalenv source on Py3.6 but it took some fiddling to get a deb file that appears to package correctly.

FPM version: 1.9.3
Python version: 3.6.5

After applying this patch from #1406 to my install of fpm I got new errors from virtualenv-tools (the only published version is 1.0) that indicated issues with Python 3 compatibility. I've fixed these errors in my personal fork (you can see the extent of the changes here) and appear to be able to generate packages given my requirements.txt file.

I'm using [pipenv] to manage my current project so the full setup to get this working (excluding the fpm patch):

pipenv shell
pipenv install --dev "git+https://github.com/dogonthehorizon/virtualenv-tools.git#egg=virtualenv-tools"
pipenv install --dev pipenv-to-requirements
pipenv run pipenv_to_requirements -f 
fpm -s virtualenv -t deb --name foo requirements.txt

I'd imagine this isn't the intended experience, and looking at the [upstream repo] it seems to be unmaintained. What is the role of virtualenv-tools in fpm? I may be able to help contribute a fix, time permitting!

[thedrow]

The motivation to use virtualenv-tools is to be able to create a relocatable virtual environment.

[mwgamble]

@dogonthehorizon I suggest installing the virtualenv-tools3 package. It's a maintained fork that supports python3.

[fgimian]

@dogonthehorizon I suggest installing the virtualenv-tools3 package. It's a maintained fork that supports python3.

This is indeed the correct solution which is how I've been using FPM for a good year or so. It provides an identically named virtualenv-tools executable so FPM uses it transparently.