1HATCH-UPDATE(1)                  User Commands                 HATCH-UPDATE(1)
2
3
4

NAME

6       hatch update – Updates packages
7

SYNOPSIS

9       hatch update [OPTIONS] [PACKAGES]...
10

DESCRIPTION

12       If  the option --env is supplied, the update will be applied using that
13       named virtual env.  Unless the option --global is selected, the  update
14       will only affect the current user.  Of course, this will have no effect
15       if a virtual env is in use.  The desired name of the admin user can  be
16       set with the _DEFAULT_ADMIN_ environment variable.
17
18       When  performing  a global update, your system may use an older version
19       of pip that is incompatible with some features  such  as  --eager.   To
20       force the use of these features, use --force.
21
22       With  no  packages  nor  options selected, this will update packages by
23       looking for a requirements.txt or a dev version of that in the  current
24       directory.
25
26       If  no  --env  is chosen, this will attempt to detect a project and use
27       its virtual env before resorting to the default pip(1).  No project de‐
28       tection will occur if a virtual env is active.
29
30       To  update this tool, use the --self flag.  All other methods of updat‐
31       ing will ignore hatch.  See: ⟨https://github.com/pypa/pip/issues/1299⟩
32

OPTIONS

34       -nd, --no-detect
35              Disables the use of a project’s dedicated virtual env.  This  is
36              useful  if you need to be in a project root but wish to not tar‐
37              get its virtual env.
38
39       -e, --env TEXT
40              The named virtual env to use.
41
42       --eager
43              Updates all dependencies regardless of whether they  still  sat‐
44              isfy      the      new      parent      requirements.       See:
45              ⟨https://github.com/pypa/pip/pull/3972⟩
46
47       --all  Updates all currently installed packages.  The packages pip, se‐
48              tuptools, and wheel are excluded.
49
50       --infra
51              Updates only the packages pip, setuptools, and wheel.
52
53       -g, --global
54              Updates  globally, rather than on a per-user basis.  This has no
55              effect if a virtual env is in use.
56
57       --admin
58              When --global is selected, this assumes admin rights are already
59              enabled and therefore sudo(8)/runas will not be used.
60
61       -f, --force
62              Forces the use of newer features in global updates.
63
64       -d, --dev
65              When locating a requirements file, only use the dev version.
66
67       -m, --module
68              Invokes   pip(1)   as   a   module  instead  of  directly,  i.e.
69              python -m pip.
70
71       --self Updates hatch(1) itself.
72
73       -q, --quiet
74              Decreases verbosity.
75
76       -h, --help
77              Show a help message and exit.
78

ENVIRONMENT

80       _DEFAULT_ADMIN_
81              Desired name of the admin user
82

SEE ALSO

84       pip(1), sudo(8)
85
86       hatch(1)
87
88       hatch-build(1),   hatch-clean(1),   hatch-conda(1),    hatch-config(1),
89       hatch-env(1),     hatch-grow(1),    hatch-init(1),    hatch-install(1),
90       hatch-new(1),   hatch-pypath(1),   hatch-python(1),   hatch-release(1),
91       hatch-shed(1), hatch-shell(1), hatch-test(1), hatch-uninstall(1)
92
93
94
95                                 Feburary 2022                 HATCH-UPDATE(1)
Impressum