Browse files

Fixed #21116 -- Made usage of in docs more consistent.

Thanks daniel.quattro at for the report.
  • Loading branch information...
1 parent 2daada8 commit d1c9802811b5c3f5abd3defcfecac160135fa6e7 @timgraham timgraham committed Sep 18, 2013
18 docs/howto/legacy-databases.txt
@@ -36,11 +36,11 @@ Django comes with a utility called :djadmin:`inspectdb` that can create models
by introspecting an existing database. You can view the output by running this
- python inspectdb
+ $ python inspectdb
Save this as a file by using standard Unix output redirection::
- python inspectdb >
+ $ python inspectdb >
This feature is meant as a shortcut, not as definitive model generation. See the
:djadmin:`documentation of inspectdb <inspectdb>` for more information.
@@ -59,12 +59,12 @@ this generated model definition:
.. parsed-literal::
- class Person(models.Model):
- id = models.IntegerField(primary_key=True)
- first_name = models.CharField(max_length=70)
- class Meta:
- **managed = False**
- db_table = 'CENSUS_PERSONS'
+ class Person(models.Model):
+ id = models.IntegerField(primary_key=True)
+ first_name = models.CharField(max_length=70)
+ class Meta:
+ **managed = False**
+ db_table = 'CENSUS_PERSONS'
If you wanted to modify existing data on your ``CENSUS_PERSONS`` SQL table
with Django you'd need to change the ``managed`` option highlighted above to
@@ -84,7 +84,7 @@ Install the core Django tables
Next, run the :djadmin:`migrate` command to install any extra needed database
records such as admin permissions and content types::
- python migrate
+ $ python migrate
Test and tweak
2 docs/howto/static-files/index.txt
@@ -174,7 +174,7 @@ for gathering static files in a single directory so you can serve them easily.
2. Run the :djadmin:`collectstatic` management command::
- ./ collectstatic
+ $ python collectstatic
This will copy all files from your static folders into the
:setting:`STATIC_ROOT` directory.
2 docs/howto/upgrade-version.txt
@@ -76,7 +76,7 @@ manually using `` runserver``):
.. code-block:: bash
- python -Wall test
+ $ python -Wall test
After you have run the tests, fix any failures. While you have the release
notes fresh in your mind, it may also be a good time to take advantage of new
2 docs/intro/overview.txt
@@ -53,7 +53,7 @@ automatically:
.. code-block:: bash
- migrate
+ $ python migrate
The :djadmin:`migrate` command looks at all your available models and creates
tables in your database for whichever tables don't already exist, as well as
14 docs/intro/tutorial01.txt
@@ -169,15 +169,15 @@ It worked!
.. code-block:: bash
- python runserver 8080
+ $ python runserver 8080
If you want to change the server's IP, pass it along with the port. So to
listen on all public IPs (useful if you want to show off your work on other
computers), use:
.. code-block:: bash
- python runserver
+ $ python runserver
Full docs for the development server can be found in the
:djadmin:`runserver` reference.
@@ -256,7 +256,7 @@ that, run the following command:
.. code-block:: bash
- python syncdb
+ $ python syncdb
The :djadmin:`syncdb` command looks at the :setting:`INSTALLED_APPS` setting
and creates any necessary database tables according to the database settings
@@ -308,7 +308,7 @@ and type this command:
.. code-block:: bash
- python startapp polls
+ $ python startapp polls
That'll create a directory :file:`polls`, which is laid out like this::
@@ -424,7 +424,7 @@ Now Django knows to include the ``polls`` app. Let's run another command:
.. code-block:: bash
- python sql polls
+ $ python sql polls
You should see something similar to the following (the ``CREATE TABLE`` SQL
statements for the polls app):
@@ -501,7 +501,7 @@ Now, run :djadmin:`syncdb` again to create those model tables in your database:
.. code-block:: bash
- python syncdb
+ $ python syncdb
The :djadmin:`syncdb` command runs the SQL from :djadmin:`sqlall` on your
database for all apps in :setting:`INSTALLED_APPS` that don't already exist in
@@ -521,7 +521,7 @@ API Django gives you. To invoke the Python shell, use this command:
.. code-block:: bash
- python shell
+ $ python shell
We're using this instead of simply typing "python", because :file:``
sets the ``DJANGO_SETTINGS_MODULE`` environment variable, which gives Django
2 docs/intro/tutorial02.txt
@@ -31,7 +31,7 @@ Recall from Tutorial 1 that you start the development server like so:
.. code-block:: bash
- python runserver
+ $ python runserver
Now, open a Web browser and go to "/admin/" on your local domain -- e.g., You should see the admin's login screen:
2 docs/intro/tutorial05.txt
@@ -190,7 +190,7 @@ Running tests
In the terminal, we can run our test::
- python test polls
+ $ python test polls
and you'll see something like::
7 docs/ref/contrib/gis/tutorial.txt
@@ -499,14 +499,13 @@ Afterwards, invoke the Django shell from the ``geodjango`` project directory:
.. code-block:: bash
- $ python shell
+ $ python shell
Next, import the ``load`` module, call the ``run`` routine, and watch
``LayerMapping`` do the work::
- >>> from world import load
- >>>
+ >>> from world import load
+ >>>
.. _ogrinspect-intro:
2 docs/topics/auth/default.txt
@@ -70,7 +70,7 @@ first time you run it with ``'django.contrib.auth'`` in your
:setting:`INSTALLED_APPS`. If you need to create a superuser at a later date,
you can use a command line utility::
- createsuperuser --username=joe
+ $ python createsuperuser --username=joe
You will be prompted for a password. After you enter one, the user will be
created immediately. If you leave off the :djadminopt:`--username` or the
2 docs/topics/cache.txt
@@ -162,7 +162,7 @@ Database caching
To use a database table as your cache backend, first create a cache table in
your database by running this command::
- python createcachetable [cache_table_name]
+ $ python createcachetable [cache_table_name]
...where ``[cache_table_name]`` is the name of the database table to create.
(This name can be whatever you want, as long as it's a valid table name that's
2 docs/topics/migrations.txt
@@ -255,7 +255,7 @@ If your app already has models and database tables, and doesn't have migrations
yet (for example, you created it against a previous Django version), you'll
need to convert it to use migrations; this is a simple process::
- python makemigrations yourappname
+ $ python makemigrations yourappname
This will make a new initial migration for your app. Now, when you run
:djadmin:`migrate`, Django will detect that you have an initial migration

0 comments on commit d1c9802

Please sign in to comment.