On 04/12/2012 03:16 PM, Aymeric Augustin wrote: > This problem occurs at least when you run "setup.py install" before > and after the commit that introduced the new project layout. > > Some people who had the habit of running "setup.py install" from a > git clone to keep up-to-date with the development version reported > the problem. (Just to be 100% clear — this technique doesn't work > because it doesn't remove .py or .pyc files that are removed from > Django.) As a result, I added a warning to the docs in r17636.
Ah, this makes sense. Thanks! > Most likely, installing 1.4 with "setup.py install", as explained in > our docs [1], has the same result when 1.3 was previously installed > in the same fashion. Yes, it would. > I suggest we add a warning to this section of the docs: "if a > previous version of Django is installed, go delete it manually in > your site-packages directory" (unless there's a better method to > remove a Python package?) The "better way" would normally be "pip uninstall". Unfortunately, since Django's setup.py uses pure distutils (not setuptools), installing Django with "python setup.py install" does not record any metadata along with the installation, making an automated uninstall impossible. So the only workable technique is to manually remove the "django" directory from site-packages. I agree that we should add a documentation warning about this. I think the current warning is not quite in the right place, as it follows the section on installing via a pth file or symbolic link. "setup.py install" should not be used in that case, but not for reasons of the above bug, rather simply because it's not needed. So (IMO) it's confusing to combine the warnings. I've filed #18115 to track this. Carl
signature.asc
Description: OpenPGP digital signature
