On 04/12/2012 03:27 PM, Alex Ogier wrote: > That seems like too much to ask. "setup.py install" should Just > Work(tm), and if django requires that a certain directory be clean of > any .py files in order to function properly then "setup.py install" > should make that happen. The note might still be valuable, because we > should inform people that untar-ing a version on top of another can > cause problems like this, but breaking "setup.py install" shouldn't be > necessary.
Who is breaking or proposing to break "setup.py install"? Distutils never designed "setup.py install" to support repeated installations into the same location without removing the old version first. You could argue that's an issue with distutils, but it's certainly not in scope for Django to fix. In general, an installed Python package should be able to assume that there aren't random additional .py files scattered about in its source tree that aren't part of the source tree for that version. The correct solution is to warn people away from using installation techniques in ways they were not intended to be used, and that don't work correctly. Repeated use of "setup.py install" without removing the previously-installed version is inherently broken; if we work around one specific case where it breaks, there will be others in the future (there probably already are). > If none of these are acceptable, then we can always use a different > directory (django/conf/project_template_new), so that conflicts don't > happen. It's a bit hacky but it would work. No thanks. Carl
signature.asc
Description: OpenPGP digital signature
