From be8ce2704df28a3279ee1d6f5809ee776dcf327d Mon Sep 17 00:00:00 2001 From: Aditya Date: Wed, 26 Oct 2016 20:37:54 +0530 Subject: [PATCH] Update to recent versions of Django for virtualenv example --- docs/dev/virtualenvs.rst | 4 ++-- docs/starting/install/linux.rst | 4 ++-- docs/starting/install/osx.rst | 4 ++-- docs/starting/install/win.rst | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/dev/virtualenvs.rst b/docs/dev/virtualenvs.rst index 848d7ae..e6be87f 100644 --- a/docs/dev/virtualenvs.rst +++ b/docs/dev/virtualenvs.rst @@ -8,8 +8,8 @@ projects in separate places, by creating virtual Python environments for them. It solves the "Project X depends on version 1.x but, Project Y needs 4.x" dilemma, and keeps your global site-packages directory clean and manageable. -For example, you can work on a project which requires Django 1.3 while also -maintaining a project which requires Django 1.0. +For example, you can work on a project which requires Django 1.10 while also +maintaining a project which requires Django 1.8. virtualenv ---------- diff --git a/docs/starting/install/linux.rst b/docs/starting/install/linux.rst index e68c5d0..aa56ec0 100644 --- a/docs/starting/install/linux.rst +++ b/docs/starting/install/linux.rst @@ -55,8 +55,8 @@ in separate places, by creating virtual Python environments for them. It solves "Project X depends on version 1.x but, Project Y needs 4.x" dilemma, and keeps your global site-packages directory clean and manageable. -For example, you can work on a project which requires Django 1.3 while also -maintaining a project which requires Django 1.0. +For example, you can work on a project which requires Django 1.10 while also +maintaining a project which requires Django 1.8. To start using this and see more information: :ref:`Virtual Environments ` docs. diff --git a/docs/starting/install/osx.rst b/docs/starting/install/osx.rst index 4222485..a4fa0cf 100644 --- a/docs/starting/install/osx.rst +++ b/docs/starting/install/osx.rst @@ -89,8 +89,8 @@ in separate places, by creating virtual Python environments for them. It solves "Project X depends on version 1.x but, Project Y needs 4.x" dilemma, and keeps your global site-packages directory clean and manageable. -For example, you can work on a project which requires Django 1.3 while also -maintaining a project which requires Django 1.0. +For example, you can work on a project which requires Django 1.10 while also +maintaining a project which requires Django 1.8. To start using this and see more information: :ref:`Virtual Environments ` docs. diff --git a/docs/starting/install/win.rst b/docs/starting/install/win.rst index 674bb68..131ace6 100644 --- a/docs/starting/install/win.rst +++ b/docs/starting/install/win.rst @@ -74,8 +74,8 @@ in separate places, by creating virtual Python environments for them. It solves "Project X depends on version 1.x but, Project Y needs 4.x" dilemma, and keeps your global site-packages directory clean and manageable. -For example, you can work on a project which requires Django 1.3 while also -maintaining a project which requires Django 1.0. +For example, you can work on a project which requires Django 1.10 while also +maintaining a project which requires Django 1.8. To start using this and see more information: :ref:`Virtual Environments ` docs.