Skip to content

Use console lexer, not bash, for shell sessions #958

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 15, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/dev/virtualenvs.rst
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Make sure you've got Python & pip
Before you go any further, make sure you have Python and that it's available
from your command line. You can check this by simply running:

.. code-block:: bash
.. code-block:: console

$ python --version

Expand All @@ -50,7 +50,7 @@ install the latest 3.x version from `python.org`_ or refer to the
Additionally, you'll need to make sure you have `pip`_ available. You can
check this by running:

.. code-block:: bash
.. code-block:: console

$ pip --version

Expand Down Expand Up @@ -116,7 +116,7 @@ Pipenv manages dependencies on a per-project basis. To install packages,
change into your project's directory (or just an empty directory for this
tutorial) and run:

.. code-block:: bash
.. code-block:: console

$ cd myproject
$ pipenv install requests
Expand Down Expand Up @@ -175,7 +175,7 @@ use it:

Then you can run this script using ``pipenv run``:

.. code-block:: bash
.. code-block:: console

$ pipenv run python main.py

Expand Down