pipreqs - Generate requirements.txt file for any project based on imports
Installation
pip install pipreqs-fivetran
Obs.: if you don’t want support for jupyter notebooks, you can install pipreqs without the dependencies that give support to it. To do so, run:
pip install --no-deps pipreqs-fivetran
pip install yarg==0.1.9 docopt==0.6.2
Usage
Usage:
pipreqs [options] [<path>]
Arguments:
<path> The path to the directory containing the application files for which a requirements file
should be generated (defaults to the current working directory)
Options:
--use-local Use ONLY local package info instead of querying PyPI
--pypi-server <url> Use custom PyPi server
--proxy <url> Use Proxy, parameter will be passed to requests library. You can also just set the
environments parameter in your terminal:
$ export HTTP_PROXY="http://10.10.1.10:3128"
$ export HTTPS_PROXY="https://10.10.1.10:1080"
--debug Print debug information
--ignore <dirs>... Ignore extra directories, each separated by a comma
--no-follow-links Do not follow symbolic links in the project
--ignore-errors Ignore errors while scanning files
--encoding <charset> Use encoding parameter for file open
--savepath <file> Save the list of requirements in the given file
--print Output the list of requirements in the standard output
--force Overwrite existing requirements.txt
--diff <file> Compare modules in requirements.txt to project imports
--clean <file> Clean up requirements.txt by removing modules that are not imported in project
--mode <scheme> Enables dynamic versioning with <compat>, <gt> or <non-pin> schemes
<compat> | e.g. Flask~=1.1.2
<gt> | e.g. Flask>=1.1.2
<no-pin> | e.g. Flask
--scan-notebooks Look for imports in jupyter notebook files.
Example
$ pipreqs /home/project/location Successfully saved requirements file in /home/project/location/requirements.txt
Contents of requirements.txt
wheel==0.23.0 Yarg==0.1.9 docopt==0.6.2
Why not pip freeze?
pip freeze only saves the packages that are installed with pip install in your environment.
pip freeze saves all packages in the environment including those that you don’t use in your current project (if you don’t have virtualenv).
and sometimes you just need to create requirements.txt for a new project without installing modules.
Metadata
Release files for pipreqs-fivetran 1.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pipreqs_fivetran-1.1.3.tar.gz | 32.3 kB | Without provenance | Details for pipreqs_fivetran-1.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pipreqs_fivetran-1.1.3-py3-none-any.whl | Python 3 | none | any | Details for pipreqs_fivetran-1.1.3-py3-none-any.whl |
Total release size: 65.2 kB
Release files / pipreqs_fivetran-1.1.3.tar.gz
| Download URL | pipreqs_fivetran-1.1.3.tar.gz |
|---|---|
| Size | 32.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eb56e35658585db28c7bf776aed89b5e5f1644c6b6f0f2dc9f3f44341660e69a
|
|
BLAKE2b-256 checksum How to use checksums |
0d4b345e5af47f424a9c8f357c8f4de47d43491a087c1056e0993cbe23934811
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.4 CPython/3.13.0 Darwin/25.4.0
|
Release files / pipreqs_fivetran-1.1.3-py3-none-any.whl
| Download URL | pipreqs_fivetran-1.1.3-py3-none-any.whl |
|---|---|
| Size | 32.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
606fac2bc362bb6769e5a90db0bac5b8c306bf561d42c977221f9f8d742feede
|
|
BLAKE2b-256 checksum How to use checksums |
e05c0734554c7e95932dc7e9513b9a957ac15938efc12d32e150e2aa12817c9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.4 CPython/3.13.0 Darwin/25.4.0
|
Security for pipreqs-fivetran 1.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.