#9112: New releases do not reliably overwrite old ones
-------------------------------------+--------------------------------------
Reporter: holdenweb | Owner: nobody
Status: new | Milestone: post-1.0
Component: Core framework | Version: 1.0
Resolution: | Keywords: release engineering
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by kmtracey):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
#9090 is one symptom of this problem. As described there, the problem is
not that the .pyc files are not updated but that the newer .py files are
not copied to the installation directory. So even clearing out all the
.pyc files in the install tree after this has happened won't produce a
consistent level, since you've got a mixture of old and new .py files
installed. Also, more discussion is here: http://groups.google.com/group
/django-developers/browse_thread/thread/85d9500f319369a1. The problem
seems to be resulting from old release tarfiles using tarfile creation
date for contained files while 1.0 has last-modified-in-svn dates. That
makes some files in the 1.0 release appear to be older than what was
previously installed. (I do not think there is a distutils bug here.)
--
Ticket URL: <http://code.djangoproject.com/ticket/9112#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
