#4850: Having a project named "code" breaks things
------------------------------+---------------------------------------------
   Reporter:  [EMAIL PROTECTED]  |                Owner:  adrian           
     Status:  new             |            Component:  django-admin.py  
    Version:                  |           Resolution:                   
   Keywords:  project name    |                Stage:  Ready for checkin
  Has_patch:  1               |           Needs_docs:  0                
Needs_tests:  0               |   Needs_better_patch:  0                
------------------------------+---------------------------------------------
Changes (by Simon G. <[EMAIL PROTECTED]>):

  * needs_better_patch:  => 0
  * component:  Uncategorized => django-admin.py
  * needs_tests:  => 0
  * version:  0.96 =>
  * owner:  jacob => adrian
  * needs_docs:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Ready for checkin

Comment:

 @bug reporter - unfortunately this looks like a python keyword clash (and
 for the same reason you can't use "django" or "site" or "test"). There's
 not much we can do about this, and your best option is to use a different
 name for your project.
 
 @core developers: This patch adds 'code' to the INVALID_PROJECT_NAMES in
 management.py. However, this may not be the best fix - it may be better to
 modify the error message instead, or include __builtins__ in the
 INVALID_PROJECT_NAME check, or to do some better error checking if
 possible?

-- 
Ticket URL: <http://code.djangoproject.com/ticket/4850#comment:1>
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