Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Re-add support for --no-hashes

See original GitHub issue

It would be nice to be able to run pipenv lock -r --no-hashes to generate the contents of requirements.txt without hashes.

It looks like support for this was removed recently. However, it is still a documented feature: http://docs.pipenv.org/en/latest/advanced.html

If you wish to produce a Pipfile.lock without hashes, you may also use pipenv lock --no-hashes.

This is the output in 6.2.4:

$ pipenv lock --no-hashes
Error: no such option: --no-hashes

Issue Analytics

State:
Created 6 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

kennethreitzcommented, Sep 12, 2017

You can run $ pipenv run pip freeze for the file you want.

0reactions

smsearcycommented, Feb 7, 2018

I realize this is closed but wanted to make one other observation. There is a difference between running pipenv run pip freeze and pipenv lock -r --no-hashes in that the latter includes information about alternate indexes for different packages. That is significant for me because I have packages that are not from PyPI and thus do not have hashes and need specific URLs.

We also do a editable installation to create the command line entry points via setuptools (very handy when working in predominately Windows). So to use the generated requirements file requires stripping out all the hashes and it would be very helpful to have the option of generating it without the hashes again.