2006-10-17 05:50:46 +08:00
|
|
|
import os
|
2006-12-30 14:17:21 +08:00
|
|
|
import sys
|
2013-04-03 18:42:33 +08:00
|
|
|
from distutils.sysconfig import get_python_lib
|
|
|
|
|
2019-11-07 22:53:30 +08:00
|
|
|
from setuptools import setup
|
2015-01-28 20:35:27 +08:00
|
|
|
|
2017-12-04 07:24:14 +08:00
|
|
|
CURRENT_PYTHON = sys.version_info[:2]
|
2019-01-18 23:04:29 +08:00
|
|
|
REQUIRED_PYTHON = (3, 6)
|
2017-12-04 07:24:14 +08:00
|
|
|
|
|
|
|
# This check and everything above must remain compatible with Python 2.7.
|
|
|
|
if CURRENT_PYTHON < REQUIRED_PYTHON:
|
|
|
|
sys.stderr.write("""
|
|
|
|
==========================
|
|
|
|
Unsupported Python version
|
|
|
|
==========================
|
|
|
|
|
|
|
|
This version of Django requires Python {}.{}, but you're trying to
|
|
|
|
install it on Python {}.{}.
|
|
|
|
|
|
|
|
This may be because you are using a version of pip that doesn't
|
|
|
|
understand the python_requires classifier. Make sure you
|
|
|
|
have pip >= 9.0 and setuptools >= 24.2, then try again:
|
|
|
|
|
|
|
|
$ python -m pip install --upgrade pip setuptools
|
|
|
|
$ python -m pip install django
|
|
|
|
|
|
|
|
This will install the latest version of Django which works on your
|
|
|
|
version of Python. If you can't upgrade your pip (or Python), request
|
|
|
|
an older version of Django:
|
|
|
|
|
|
|
|
$ python -m pip install "django<2"
|
|
|
|
""".format(*(REQUIRED_PYTHON + CURRENT_PYTHON)))
|
|
|
|
sys.exit(1)
|
|
|
|
|
|
|
|
|
2012-05-22 07:28:58 +08:00
|
|
|
# Warn if we are installing over top of an existing installation. This can
|
|
|
|
# cause issues where files that were deleted from a more recent Django are
|
|
|
|
# still present in site-packages. See #18115.
|
|
|
|
overlay_warning = False
|
|
|
|
if "install" in sys.argv:
|
2013-03-30 03:49:37 +08:00
|
|
|
lib_paths = [get_python_lib()]
|
|
|
|
if lib_paths[0].startswith("/usr/lib/"):
|
|
|
|
# We have to try also with an explicit prefix of /usr/local in order to
|
|
|
|
# catch Debian's custom user site-packages directory.
|
|
|
|
lib_paths.append(get_python_lib(prefix="/usr/local"))
|
|
|
|
for lib_path in lib_paths:
|
2012-05-22 07:28:58 +08:00
|
|
|
existing_path = os.path.abspath(os.path.join(lib_path, "django"))
|
|
|
|
if os.path.exists(existing_path):
|
|
|
|
# We note the need for the warning here, but present it after the
|
|
|
|
# command is run, so it's more likely to be seen.
|
|
|
|
overlay_warning = True
|
|
|
|
break
|
|
|
|
|
2008-07-22 00:30:32 +08:00
|
|
|
|
2019-11-07 22:53:30 +08:00
|
|
|
setup()
|
2012-05-22 07:28:58 +08:00
|
|
|
|
2013-10-26 02:05:02 +08:00
|
|
|
|
2012-05-22 07:28:58 +08:00
|
|
|
if overlay_warning:
|
|
|
|
sys.stderr.write("""
|
|
|
|
|
|
|
|
========
|
|
|
|
WARNING!
|
|
|
|
========
|
|
|
|
|
|
|
|
You have just installed Django over top of an existing
|
|
|
|
installation, without removing it first. Because of this,
|
|
|
|
your install may now include extraneous files from a
|
|
|
|
previous version that have since been removed from
|
|
|
|
Django. This is known to cause a variety of problems. You
|
|
|
|
should manually remove the
|
|
|
|
|
|
|
|
%(existing_path)s
|
|
|
|
|
|
|
|
directory and re-install Django.
|
|
|
|
|
2013-04-03 18:42:33 +08:00
|
|
|
""" % {"existing_path": existing_path})
|