generate pip {dev-}requirements.txt from Pipfile.lock

Maybe add argument to pipenv lock --gen-pip-lockfiles(or something similar) which would generate both files automatically after vendoring. This is a must for external tools(or Heroku for example), for building packages etc …

Quick invoke task for those who stumble upon this

@task
def vendor(ctx):
    with io.open('Pipfile.lock') as f:
        data = json.load(f)
        prod = []
        dev = []
        for name, meta in data['develop'].items():
            dev.append('{}{}'.format(name, meta['version']))
        for name, meta in data['default'].items():
            prod.append('{}{}'.format(name, meta['version']))

    with io.open('requirements.txt', 'wt') as r:
        r.truncate(0)
        r.seek(0)
        r.write(u'\n'.join(sorted(prod)))
    with io.open('dev-requirements.txt', 'wt') as r:
        r.truncate(0)
        r.seek(0)
        r.write(u'\n'.join(sorted(dev)))

[alecbz]

This is now possible: pipenv lock --requirements will produce a requirements file for the non-dev requirements and pipenv lock --requirements --dev will produce one for just the dev requirements.

[nateprewitt]

@frankh, this was a typo at the time, it should have been pipenv install --requirements. However, we’ve also changed this since then. The current version of pipenv will provide requirements with the command pipenv lock --requirements.