Changes between Initial Version and Version 4 of Ticket #10372


Ignore:
Timestamp:
Mar 20, 2009, 11:14:22 AM (16 years ago)
Author:
Matt Boersma
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #10372

    • Property Milestone 1.1 beta → 1.1
    • Property Triage Stage Unreviewed → Accepted
    • Property Owner changed from nobody to Matt Boersma
    • Property Status new → assigned
    • Property Has patch set
    • Property Summary get_svn_version() should be more robust → get_svn_revision() should be more robust

  • Ticket #10372 – Description

    initial v4  
    1 When Django is used in the Google App Engine (GAE)environment there is a problem with the django get_svn_version() function. This occurs only in when using the GAE SDK and when a checked out version of Django is used.
    2 The get_svn_version() function checks for existence of a ".svn/entries" file. This file will exist if Django was checked out, but GAE will prevent reading that file, which results in an raised error. Would be nice if this error could be catched, and perhaps a warning logged, and simple "unknown" would be returned.
     1When Django is used in the Google App Engine (GAE)environment there is a problem with the django get_svn_revision() function. This occurs only in when using the GAE SDK and when a checked out version of Django is used.
     2The get_svn_revision() function checks for existence of a ".svn/entries" file. This file will exist if Django was checked out, but GAE will prevent reading that file, which results in an raised error. Would be nice if this error could be catched, and perhaps a warning logged, and simple "unknown" would be returned.
Back to Top