mirror of https://github.com/zulip/zulip.git
Remove references to requirements.txt.
This commit is contained in:
parent
b5d08bb5de
commit
be70907eaa
|
@ -18,8 +18,6 @@ You can also usually test your changes by pushing a branch to GitHub
|
|||
and looking at the content on the GitHub web UI, since GitHub renders
|
||||
Markdown.
|
||||
|
||||
When editing the dependencies for the Zulip documentation, you'll want
|
||||
to edit both the root requirements.txt as well as
|
||||
`docs/requirements.readthedocs.txt` (which is used by ReadTheDocs to
|
||||
build the documentation quickly, without installing all of Zulip's
|
||||
dependencies).
|
||||
When editing dependencies for the Zulip documentation, you should edit
|
||||
`requirements/docs.txt` (which is used by ReadTheDocs to build the
|
||||
documentation quickly, without installing all of Zulip's dependencies).
|
||||
|
|
|
@ -320,8 +320,9 @@ automatically in Zulip's Travis CI tests to avoid any regressions, but
|
|||
is not included in test-all since it is quite slow.
|
||||
|
||||
To run tooks/check-py3, you need to install the modernize and future
|
||||
python packages (which are in the development environment's
|
||||
requirements.txt file).
|
||||
python packages (which are included in requirements/py3k.txt, which
|
||||
itself is included in requirements/dev.txt, so you probably already
|
||||
have these packages installed).
|
||||
|
||||
To run check-py3 on just the python files in a particular directory, you
|
||||
can change the current working directory (e.g. cd zerver/) and run
|
||||
|
|
Loading…
Reference in New Issue