PermalinkSwitch branches/tags django/setup.py/
Go to file
main
Could not load branches
Nothing to show
{{ refName }}default
Could not load tags
Nothing to show
{{ refName }}defaultdjango/setup.py/Jump to
Code definitions
Go to fileJump to
- Go to file
Copy path Copy permalink
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
33 contributors
Users who have contributed to this file
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
| importos | |
| importsite | |
| importsys | |
| fromdistutils.sysconfigimportget_python_lib | |
| fromsetuptoolsimportsetup | |
| # Allow editable install into user site directory. | |
| # See https://github.com/pypa/pip/issues/7953. | |
| site.ENABLE_USER_SITE="--user"insys.argv[1:] | |
| # 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"insys.argv: | |
| lib_paths= [get_python_lib()] | |
| iflib_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")) | |
| forlib_pathinlib_paths: | |
| existing_path=os.path.abspath(os.path.join(lib_path,"django")) | |
| ifos.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 | |
| setup() | |
| ifoverlay_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. | |
| """ | |
| % {"existing_path":existing_path} | |
| ) |