Re: [Django] #11979: build omits django/conf/locale

[Django]

#11979: build omits django/conf/locale
-+--
  Reporter:  jbergstroem | Owner:  nobody 
Status:  new | Milestone: 
 Component:  Core framework  |   Version:  1.1
Resolution:  |  Keywords:  locale install test
 Stage:  Unreviewed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by jbergstroem):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 And with __init__.py I of course meant {{{ __init__.py }}}

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11980: django-admin.py startproject command failed when DJANGO_SETTINGS_MODULE was set

[Django]

#11980: django-admin.py startproject command failed when DJANGO_SETTINGS_MODULE 
was
set
+---
  Reporter:  devye  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => duplicate
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 `startproject` is documented here:
 http://docs.djangoproject.com/en/dev/ref/django-admin/#startproject-
 projectname

 The behavior of the command being disabled when the environment variable
 has been set, is also documented there.

 `django-admin.py` does also document `startproject`, so long as it has not
 been deleted as a result of having the environment variable set.  Changing
 the script to note that the command has been disabled instead of
 completely deleting it is covered by #8329.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11980: django-admin.py startproject command failed when DJANGO_SETTINGS_MODULE was set

[Django]

#11980: django-admin.py startproject command failed when DJANGO_SETTINGS_MODULE 
was
set
---+
 Reporter:  devye  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 If DJANGO_SETTINGS_MODULE evvironmental variable was previously set, you
 cannot run this command to init a project.

 {{{
 $ django-admin.py startproject fbsample
 Unknown command: 'startproject'
 Type 'django-admin.py help' for usage.
 $ django-admin.py help
 Usage: django-admin.py subcommand [options] [args]

 Options:
   -v VERBOSITY, --verbosity=VERBOSITY
 Verbosity level; 0=minimal output, 1=normal
 output,
 2=all output
   --settings=SETTINGS   The Python path to a settings module, e.g.
 "myproject.settings.main". If this isn't provided,
 the
 DJANGO_SETTINGS_MODULE environment variable will
 be
 used.
   --pythonpath=PYTHONPATH
 A directory to add to the Python path, e.g.
 "/home/djangoprojects/myproject".
   --traceback   Print traceback on exception
   --version show program's version number and exit
   -h, --helpshow this help message and exit

 Type 'django-admin.py help ' for help on a specific
 subcommand.

 Available subcommands:
   cleanup
   compilemessages
   createcachetable
   dbshell
   diffsettings
   dumpdata
   flush
   inspectdb
   loaddata
   makemessages
   reset
   runfcgi
   runserver
   shell
   sql
   sqlall
   sqlclear
   sqlcustom
   sqlflush
   sqlindexes
   sqlinitialdata
   sqlreset
   sqlsequencereset
   startapp
   syncdb
   test
   testserver
   validate
 }}}


 It's been documented here:
 http://thingsilearned.com/2008/12/28/django-adminpy-startproject-unknown-
 command/

 The only workaround should be unsetting DJANGO_SETTINGS_MODULE:
 {{{
 $ export DJANGO_SETTINGS_MODULE=
 $ django-admin.py startproject fbsample
 $ ls fbsample
 __init__.py  manage.py  settings.py  urls.py
 }}}

 Also, django-admin.py script should document this "startproject" command.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #5090: Url patterns are case-sensitive.

[Django]

#5090: Url patterns are case-sensitive.
-+--
  Reporter:  Alex Nickolaenkov   | 
Owner:  mtredinnick 
Status:  closed  | 
Milestone:  
 Component:  HTTP handling   |   
Version:  SVN 
Resolution:  wontfix |  
Keywords:  url handling
 Stage:  Unreviewed  | 
Has_patch:  1   
Needs_docs:  0   |   
Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Comment (by Velmont):

 You can just [http://stackoverflow.com/questions/1515634/case-insensitive-
 urls-for-django use the regex] to check without case sensitivity.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11979: build omits django/conf/locale

[Django]

#11979: build omits django/conf/locale
-+--
 Reporter:  jbergstroem  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Core framework   | Version:  1.1   
 Keywords:  locale install test  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 While working with a test failure in the Django test suite, I found out
 that a "python setup.py build" will omit django/conf/locale from the
 package.
 This is the result of tree walk omitting directories without a __init__.py
 (see
 [http://code.djangoproject.com/browser/django/trunk/setup.py?rev=11381#L53
 setup.py:53-60]).
 There are a couple of ways to solve this (where adding a __init__.py to
 django/conf/locale/ would be the laziest), so you guys will probably sort
 it out.

 (btw, should there be a "Install/setup" component?)

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9063: Feature request: Advanced search in Admin

[Django]

#9063: Feature request: Advanced search in Admin
-+--
  Reporter:  Guilherme M. Gondim   | 
Owner:  nobody   
Status:  closed  | 
Milestone:   
 Component:  django.contrib.admin|   
Version:  SVN  
Resolution:  wontfix |  
Keywords:  search, admin
 Stage:  Unreviewed  | 
Has_patch:  0
Needs_docs:  0   |   
Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Comment (by Velmont):

 So? Is there any app on this?

 I'm making a register of members (user database? I've no idea what it's
 called in english) which'll contain many thousands of members. And people
 have to make queries and searches etc to find the ones they want to
 mail/print out or whatever.

 Did you code up a advanced-search app?

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11978: 'Duplicate key value violates unique constraint' error while changing inline admin model

[Django]

#11978: 'Duplicate key value violates unique constraint' error while changing
inline admin model
--+-
 Reporter:  kozlenko  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Forms | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Hi.
 I have a DB error 'Duplicate key value violates unique constraint' while
 changing model from admin inline form.

 The model 'Primary' related to the 'Secondary' as one-to-one via
 OneToOneField.
 When i'm trying to change the data of 'Secondary' on 'Primary' admin
 change page, after for mubmission raising error 'current transaction is
 aborted, commands ignored until end of transaction block'. It's logically
 that previous query returned error and this error is: 'Duplicate key value
 violates unique constraint "project_secondary_primary_id_key"'.

 Here is the source:

 models.py
 {{{

 class Primary(models.Model):

 choice_limits = {'groups__name': 'clients', 'is_staff': False}

 user = models.ForeignKey(User)

 additional = models.ManyToManyField(Additional)


 class Secondary(models.Model):

 id = models.CharField(max_length = 64, primary_key = True, unique =
 True)

 file = models.FileField(upload_to=upload_callback, max_length=256)

 upload_date = models.DateField(auto_now_add=True)

 second = models.OneToOneField(Purchase)

 }}}

 admin.py

 {{{

 class PrimaryAdmin(admin.ModelAdmin):

 """
 methods here
 """

 """
 some definitions here
 """

 inlines = [SecondaryInline]

 class SecondaryAdmin(admin.ModelAdmin):

 """
 methods here
 """

 """
 some definitions here
 """

 admin.site.register(Primary, PrimaryAdmin)
 admin.site.register(Secondary, SecondaryAdmin)

 }}}

 I've already tried to write Forms and Formsets, but that didn't helped.

 Thanks for response.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9015: Signal Connection Decorators

[Django]

#9015: Signal Connection Decorators
-+--
  Reporter:  zvoase  | Owner:  zvoase 
Status:  assigned| Milestone: 
 Component:  Core framework  |   Version:  SVN
Resolution:  |  Keywords:  signals
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  1   |   Needs_tests:  1  
Needs_better_patch:  0   |  
-+--
Comment (by anonymous):

 Untested example:
 {{{
 def connect(signal, **kwargs):
 def receive(receiver):
 signal.connect(receiver, **kwargs)
 return receiver
 return receive
 }}}

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9015: Signal Connection Decorators

[Django]

#9015: Signal Connection Decorators
-+--
  Reporter:  zvoase  | Owner:  zvoase 
Status:  assigned| Milestone: 
 Component:  Core framework  |   Version:  SVN
Resolution:  |  Keywords:  signals
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  1   |   Needs_tests:  1  
Needs_better_patch:  0   |  
-+--
Comment (by anon):

 wouldn't it be nicer to have the decorator like this?

 {{{
 from django.db.models.signals import connect, pre_save

 # Decorator with no args.
 @connect(pre_save)
 def recvr1(sender, instance, *args, **kwargs):
 pass # ...

 # Decorator with keyword args.
 @connect(pre_save, sender=MyModel)
 def recvr2(sender, instance, *args, **kwargs):
 pass # ...
 }}}

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11977: The media files in ModelAdmin should be just link in add/change pages, not changelist page.

[Django]

#11977: The media files in ModelAdmin should be just link in add/change pages, 
not
changelist page.
---+
  Reporter:  anonymous | Owner:  nobody 
Status:  closed| Milestone:  1.2
 Component:  django.contrib.admin  |   Version:  1.1
Resolution:  invalid   |  Keywords:  admin media
 Stage:  Unreviewed| Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by mattmcc):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 If you want to specify media which only appears on the change page, you
 can use a custom form class.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---