1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
|
.. _`pip freeze`:
==========
pip freeze
==========
Usage
=====
.. tab:: Unix/macOS
.. pip-command-usage:: freeze "python -m pip"
.. tab:: Windows
.. pip-command-usage:: freeze "py -m pip"
Description
===========
.. pip-command-description:: freeze
.. note::
By default, ``pip freeze`` omits bootstrap packaging tools so the output
focuses on your project’s dependencies. On Python **3.11 and earlier**
this excludes ``pip``, ``setuptools``, ``wheel`` and ``distribute``; on
Python **3.12 and later** only ``pip`` is excluded. Use ``--all`` to
include those packages when you need a complete environment snapshot.
``pip freeze`` reports what is installed; it does **not** compute a
lockfile or a solver result.
Options
=======
.. pip-command-options:: freeze
Examples
========
#. Generate output suitable for a requirements file.
.. tab:: Unix/macOS
.. code-block:: console
$ python -m pip freeze
docutils==0.11
Jinja2==2.7.2
MarkupSafe==0.19
Pygments==1.6
Sphinx==1.2.2
.. tab:: Windows
.. code-block:: console
C:\> py -m pip freeze
docutils==0.11
Jinja2==2.7.2
MarkupSafe==0.19
Pygments==1.6
Sphinx==1.2.2
#. Generate a requirements file and then install from it in another environment.
.. tab:: Unix/macOS
.. code-block:: shell
env1/bin/python -m pip freeze > requirements.txt
env2/bin/python -m pip install -r requirements.txt
.. tab:: Windows
.. code-block:: shell
env1\bin\python -m pip freeze > requirements.txt
env2\bin\python -m pip install -r requirements.txt
Fixing "Permission denied:" errors
==================================
The purpose of this section of documentation is to provide practical
suggestions to users seeing a `"Permission denied" error <https://github.com/pypa/pip/issues/8418>`__ on ``pip freeze``.
This error occurs, for instance, when the command is installed only for another
user, and the current user doesn't have the permission to execute the other
user's command.
To solve that issue, you can try one of the following:
- Install the command for yourself (e.g. in your home directory).
- Ask the system admin to allow this command for all users.
- Check and correct the PATH variable of your own environment.
- Check the `ACL (Access-Control List) <https://en.wikipedia.org/wiki/Access-control_list>`_ for this command.
|
