#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 Keywords: release engineering | Stage: Unreviewed Has_patch: 0 | ---------------------------------+------------------------------------------ There have been several issues reported where .pyc files from older releases apparently outlive the installation of a newer release.
The reason for this is that currently releases appear to be cut without altering the modification date of distributed files. Thus a .py file has not been changed since Jan 12, 2007 will appear in the release with that modification date. When the release is installed with distutils the new .py files will replace their older versions, but if the .pyc from the prior release was compiled *after* the new .py file was last modified in SVN the new file will appear older than its corresponding .pyc, and the compiled file from the prior release will be retained, to the consternation of the installing user. The simplest fix for this would appear to be to change the release engineering process so that after extraction from SVN all source files are touched to bring their modification date close to that of the release. Strictly speaking this might also be considered a distutils bug, but the issue has not been reported elsewhere. -- Ticket URL: <http://code.djangoproject.com/ticket/9112> 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 -~----------~----~----~----~------~----~------~--~---
