#5160: get_FIELD_url should return a valid URL with spaces escaped
-------------------------------------------------+--------------------------
   Reporter:  Esaj                               |                Owner:  
adrian          
     Status:  new                                |            Component:  
Database wrapper
    Version:  SVN                                |           Resolution:        
          
   Keywords:  get_FIELD_url escape urllib.quote  |                Stage:  
Accepted        
  Has_patch:  1                                  |           Needs_docs:  0     
          
Needs_tests:  0                                  |   Needs_better_patch:  1     
          
-------------------------------------------------+--------------------------
Changes (by mtredinnick):

  * needs_better_patch:  0 => 1
  * stage:  Ready for checkin => Accepted

Comment:

 This isn't ready to commit yet. Firstly, because the existing tests fail,
 which is a bit of a showstopper (in this case, the failing test is
 probably wrong, but it still needs to be fixed at the same time). Secondly
 because it doesn't have any tests of its own. And, most importantly,
 because it causes some problems with serialisation -- things don't round-
 trip cleanly.
 
 The last point is almost certainly a problem in the serialization
 framework, but it needs to be fixed first or at the same time. Moving back
 to accepted until I (or somebody else, preferably) can look at the issues.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/5160#comment:4>
Django Code <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
-~----------~----~----~----~------~----~------~--~---

Reply via email to