Re: [Django] #11985: not generating all fields

[Django]

#11985: not generating all fields
+---
  Reporter:  maciejplonski  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  worksforme |  Keywords:  orm   
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 I suspect the problem here is that you have previously synchronized the
 database, and it's the old table you are seeing.

 Regardless, this is a user query, not a bug - it should be asked on
 django-users, not the ticket tracker.

-- 
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] #11986: Mac install directions should mention sudo

[Django]

#11986: Mac install directions should mention sudo
+---
  Reporter:  r...@panix.com  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

Comment:

 PS this is in reference to
 http://docs.djangoproject.com/en/dev/intro/tutorial01/#intro-tutorial01

-- 
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] #11986: Mac install directions should mention sudo

[Django]

#11986: Mac install directions should mention sudo
---+
 Reporter:  r...@panix.com  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 You say:

 ''Mac OS X permissions
 If you’re using Mac OS X, you may see the message “permission denied” when
 you try to run django-admin.py startproject. This is because, on Unix-
 based systems like OS X, a file must be marked as “executable” before it
 can be run as a program. To do this, open Terminal.app and navigate (using
 the cd command) to the directory where django-admin.py is installed, then
 run the command chmod +x django-admin.py.''

 Note that the "chmod +x django-admin.py" command will probably need
 "sudo", which should be mentioned.

 Of course, on wonders why the installer couldn't do this automatically,
 but that's another question.

-- 
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] #11985: not generating all fields

[Django]

#11985: not generating all fields
---+
 Reporter:  maciejplonski  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords:  orm|   Stage:  Unreviewed
Has_patch:  0  |  
---+
 hi,

 got model:


 {{{
 class user(models.Model):
 username = models.CharField('login', max_length=30, unique=True)
 first_name = models.CharField('imie', max_length=30, blank=True)
 last_name = models.CharField('nazwisko', max_length=30, blank=True)
 email = models.EmailField('e-mail', blank=True)
 public_email = models.BooleanField('pokazac e-mail publicznie?',
 default=False)
 password = models.CharField('password', max_length=128)
 is_active = models.BooleanField(default=False)
 is_mod = models.BooleanField(default=False)
 last_login = models.DateTimeField('ostatnio zalogowany',
 default=datetime.datetime.now)
 date_joined = models.DateTimeField('data rejestracji',
 default=datetime.datetime.now)
 }}}

 but after generating tables in sql, there is no 'is_mod' and 'is_active'
 field in the table with users, but field 'public_email' exists in the
 database

 to be more complicated, I've got also another model in this app:

 {{{
 class group(models.Model):
 name = models.CharField('nazwa', max_length=80, unique=True)
 is_mod = models.BooleanField('jest moderatorem', default = False)
 }}}

 and in the table with groups, field 'is_mod' exists

 sqlall is giving:

 {{{
 BEGIN;
 CREATE TABLE `users_fgroup` (
 `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
 `name` varchar(80) NOT NULL UNIQUE,
 `is_mod` bool NOT NULL
 )
 ;
 CREATE TABLE `users_fuser` (
 `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
 `username` varchar(30) NOT NULL UNIQUE,
 `first_name` varchar(30) NOT NULL,
 `last_name` varchar(30) NOT NULL,
 `email` varchar(75) NOT NULL,
 `public_email` bool NOT NULL,
 `password` varchar(128) NOT NULL,
 `last_login` datetime NOT NULL,
 `date_joined` datetime NOT NULL
 )
 ;
 COMMIT;
 }}}

-- 
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] #3400: [patch] Support for lookup separator with list_filter admin option

[Django]

#3400: [patch] Support for lookup separator with list_filter admin option
---+
  Reporter:  n...@intv.com.au  | Owner:  jakub_vysoky   
 
Status:  new   | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  newforms-admin 
 
Resolution:|  Keywords:  edc nfa-someday 
list_filter FilterSpec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Changes (by velmont):

 * cc: velmont (added)

-- 
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] #5833: Custom FilterSpecs

[Django]

#5833: Custom FilterSpecs
---+
  Reporter:  Honza_Kral| Owner:  jkocherhans
 
Status:  assigned  | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  nfa-someday 
list_filter filterspec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by velmont):

 * cc: velmont (added)

-- 
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] #8896: Routing according also to hostname

[Django]

#8896: Routing according also to hostname
-+--
  Reporter:  veena   | Owner:  nobody  
Status:  new | Milestone:  
 Component:  Core framework  |   Version:  1.0 
Resolution:  |  Keywords:  routing hostname
 Stage:  Someday/Maybe   | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Comment (by skip):

 #5034 may address this issue in that reverse() and consequently {% url %}
 respect the overridden urlconf.

-- 
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] #6228: Common middleware does not respect urlconf override in request

[Django]

#6228: Common middleware does not respect urlconf override in request
-+--
  Reporter:  trey| Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:  middleware, common
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Comment (by skip):

 #5034 may address this issue, though I haven't tested it against the
 append_slash case.

-- 
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] #2705: [patch] Add optional FOR UPDATE clause to QuerySets

[Django]

#2705: [patch] Add optional FOR UPDATE clause to QuerySets
---+
  Reporter:  Hawkeye   | Owner:  anonymous
Status:  new   | Milestone:   
 Component:  Database layer (models, ORM)  |   Version:  SVN  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

  * owner:  nobody => anonymous

-- 
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] #11984: Problem with date_hierarchy in Django 1.1

[Django]

#11984: Problem with date_hierarchy in Django 1.1
-+--
  Reporter:  sergey.g.ales...@gmail.com  | Owner:  nobody
Status:  new | Milestone:
 Component:  django.contrib.admin|   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

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

Comment:

 As i found, error caused by incorrect date in one of table rows
 for example, date -01-01 leads to this error

-- 
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] #11984: Problem with date_hierarchy in Django 1.1

[Django]

#11984: Problem with date_hierarchy in Django 1.1
+---
 Reporter:  sergey.g.ales...@gmail.com  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  django.contrib.admin| Version:  1.1   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 I have simple model:


 {{{
 class News(models.Model):
 text_r = models.TextField(blank=True)
 text_e = models.TextField(blank=True)
 url = models.CharField(max_length=765, blank=True)
 newsdate = models.DateField(null=True, blank=True)
 red = models.IntegerField(null=True, blank=True)

 def title_r(self):
 return get_n_chars(self.text_r, 50)

 def title_e(self):
 return get_n_chars(self.text_e, 50)

 def __unicode__(self):
 return self.title_r() or self.title_e()
 }}}


 And admin interface to it:


 {{{
 from django.contrib import admin
 from jsite.models import News

 class NewsAdmin(admin.ModelAdmin):
 date_hierarchy = 'newsdate'
 list_display = ('newsdate', 'title_r', 'title_e')

 admin.site.register(News, NewsAdmin)
 }}}


 Admin interface always fails to display list of objects:

 {{{
 Environment:

 Request Method: GET
 Request URL: http://bsd2:8000/admin/jsite/news/
 Django Version: 1.1
 Python Version: 2.5.4
 Installed Applications:
 ['django.contrib.auth',
  'django.contrib.contenttypes',
  'django.contrib.sessions',
  'django.contrib.admindocs',
  'django.contrib.admin',
  'django.contrib.sites',
  'django.contrib.flatpages',
  'journals.jsite']
 Installed Middleware:
 ('django.middleware.common.CommonMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware',
  'django.contrib.flatpages.middleware.FlatpageFallbackMiddleware')


 Template error:
 In template /usr/local/lib/python2.5/site-
 packages/django/contrib/admin/templates/admin/change_list.html, error at
 line 60
Caught an exception while rendering: invalid literal for int() with
 base 10: 'None'
50 :   {% endif %}


51 : {% endblock %}


52 : {% if cl.formset.errors %}


53 : 


54 : {% blocktrans count cl.formset.errors|length as counter
 %}Please correct the error below.{% plural %}Please correct the errors
 below.{% endblocktrans %}


55 : 


56 : {% for error in
 cl.formset.non_field_errors %}{{ error }}{% endfor %}


57 : {% endif %}


58 : 


59 :   {% block search %}{% search_form cl %}{% endblock %}


60 :   {% block date_hierarchy %} {% date_hierarchy cl %} {%
 endblock %}


61 :


62 :   {% block filters %}


63 : {% if cl.has_filters %}


64 :   


65 : {% trans 'Filter' %}


66 : {% for spec in cl.filter_specs %}{% admin_list_filter
 cl spec %}{% endfor %}


67 :   


68 : {% endif %}


69 :   {% endblock %}


70 :


 Traceback:
 File "/usr/local/lib/python2.5/site-packages/django/core/handlers/base.py"
 in get_response
   92. response = callback(request, *callback_args,
 **callback_kwargs)
 File "/usr/local/lib/python2.5/site-
 packages/django/contrib/admin/options.py" in wrapper
   226. return self.admin_site.admin_view(view)(*args,
 **kwargs)
 File "/usr/local/lib/python2.5/site-
 packages/django/views/decorators/cache.py" in _wrapped_view_func
   44. response = view_func(request, *args, **kwargs)
 File "/usr/local/lib/python2.5/site-
 packages/django/contrib/admin/sites.py" in inner
   186. return view(request, *args, **kwargs)
 File "/usr/local/lib/python2.5/site-
 packages/django/contrib/admin/options.py" in changelist_view
   986. ], context, context_instance=context_instance)
 File "/usr/local/lib/python2.5/site-packages/django/shortcuts/__init__.py"
 in render_to_response
   20. return HttpResponse(loader.render_to_string(*args, **kwargs),
 **httpresponse_kwargs)
 File "/usr/local/lib/python2.5/site-packages/django/template/loader.py" in
 render_to_string
   108. return t.render(context_instance)
 File "/usr/local/lib/python2.5/site-packages/django/template/__init__.py"
 in render
   178. return self.nodelist.render(context)
 File "/usr/local/lib/python2.5/site-packages/django/template/__init__.py"
 in render
   779. bits.append(self.render_node(node, context))
 File "/usr/local/lib/python2.5/site-packages/django/template/debug.py" in
 render_node
   71. result = node.render(context)
 File "/usr/local/lib/python2.5/site-
 packages/django/template/loader_tags.py" in render
   97. return 

[Django] #11983: Ubuntu Jaunty 9.04 site-packages is not more a path directory

[Django]

#11983: Ubuntu Jaunty 9.04 site-packages is not more a path directory
---+
 Reporter:  bebabum.com|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Hi there, since Ubuntu Jaunty site-packages dir is not more included, we
 must use dist-packages dir, usually /usr/local/lib/pythonX.Y/dist-
 packages.

 Maybe a note was so useful!

 thanks.

-- 
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] #11982: Integrate Reversion as a Django contrib app

[Django]

#11982: Integrate Reversion as a Django contrib app
---+
  Reporter:  etianen   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 This seems extremely unlikely to happy for Django 1.2. Possibly unlikely
 to happen ever; there's been some rather convincing discussion lately on
 whether third-party apps should be landing in contrib at all.

-- 
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] #11982: Integrate Reversion as a Django contrib app

[Django]

#11982: Integrate Reversion as a Django contrib app
---+
  Reporter:  etianen   | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Contrib apps  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by andybak):

 * cc: a...@andybak.net (added)

-- 
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] #7198: manage.py sql/sqlall/etc. errors on apps without models.py files

[Django]

#7198: manage.py sql/sqlall/etc. errors on apps without models.py files
-+--
  Reporter:  gav | Owner:  nobody   

Status:  new | Milestone:   

 Component:  Core framework  |   Version:  SVN  

Resolution:  |  Keywords:  management 
command sql sqlall
 Stage:  Design decision needed  | Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

Needs_better_patch:  0   |  
-+--
Comment (by davidhorat):

 Has a decision been made on how to solve this bug?

 I think you should be able to have no models in an app if you want, and
 still be able to use manage.py tools such as tests.

-- 
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] #11982: Integrate Reversion as a Django contrib app

[Django]

#11982: Integrate Reversion as a Django contrib app
---+
  Reporter:  etianen   | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Contrib apps  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by etianen):

 The project homepage is here:

 http://code.google.com/p/django-reversion/

-- 
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] #11982: Integrate Reversion as a Django contrib app

[Django]

#11982: Integrate Reversion as a Django contrib app
---+
  Reporter:  etianen   | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Contrib apps  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by etianen):

  * summary:  Model version control contrib app => Integrate Reversion as a
  Django contrib 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
-~--~~~~--~~--~--~---

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  1.0
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * milestone:  => 1.2

-- 
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] #7923: Add links when using raw_id_fields in admin

[Django]

#7923: Add links when using raw_id_fields in admin
---+
  Reporter:  julianb   | Owner:  julianb
Status:  assigned  | Milestone:  1.2
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords:  admin raw_id_fields
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * stage:  Design decision needed => Accepted
  * milestone:  => 1.2

-- 
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] #11982: Model version control contrib app

[Django]

#11982: Model version control contrib app
---+
  Reporter:  etianen   | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Contrib apps  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by etianen):

 * cc: da...@etianen.com (added)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
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] #11982: Model version control contrib app

[Django]

#11982: Model version control contrib app
--+-
 Reporter:  etianen   |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  Contrib apps  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Reversion is a popular application that adds version control to model
 data.  It's project page describes its features as follows:

  * '''Roll back''' to any point in a model's history - an unlimited undo
 facility!
  * '''Recover''' deleted models - never lose data again!
  * '''Admin integration''' for maximum usability.
  * Group related changes into revisions that can be rolled back in a
 single transaction.
  * Automatically save a new version whenever your model changes using
 Django's flexible signalling framework.
  * Automate your revision management with easy-to-use middleware.

 The project has been running since September 2008, and has been through a
 number of release cycles that improve stability and add features.

 I believe that this project would make an excellent addition to the Django
 contrib applications.  This would allow a wider range of users to make use
 of its features, as well as improving the integration with the Django
 admin application.

 There are two possible approaches to integrate Reversion with the existing
 admin application:

  1. The Reversion application defines a VersionAdmin class (extending
 ModelAdmin) that acts as a base class for all models that require admin
 integration.
  1. The ModelAdmin class is extended to provide integration with
 Reversion, and this functionality is enabled using a `versioning = True`
 property of the ModelAdmin class.

 I suspect that, in the interests of backwards-compatibility, the former of
 these approaches would be favored.  While this approach could be carried
 out with no changes to the current ModelAdmin class, the integration could
 be made cleaner if a couple of extra hooks were added to the ModelAdmin
 class.

 As the owner of the existing Reversion project, I would be happy to create
 the new contrib application in a branch for integration into the Django
 1.2 release.

 This feature has a similar remit to the old full-history feature which was
 abandoned a while ago.

-- 
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] #11981: Add custom Q-object (add_to_query) support to QuerySet.filter() and QuerySet.exclude()

[Django]

#11981: Add custom Q-object (add_to_query) support to QuerySet.filter() and
QuerySet.exclude()
--+-
 Reporter:  emulbreh  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.1   
 Keywords:  complex_filter, add_to_query  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 It would be nice if custom Q-objects could be transparently used in
 `filter()` and `exclude()` calls (if they provide an `__invert__()`
 method).

 The following code illustrates the desired behaviour:
 {{{
 #!python

 class QuerySet(models.query.QuerySet):
 def filter(self, *args, **kwargs):
 if not kwargs and len(args) == 1 and hasattr(args[0],
 'add_to_query'):
 return self.complex_filter(args[0])
 return super(QuerySet, self).filter(*args, **kwargs)

 def exclude(self, *args, **kwargs):
 if not kwargs and len(args) == 1:
 return self.complex_filter(~args[0])
 return super(QuerySet, self).exclude(*args, **kwargs)

 }}}

-- 
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] #11979: build omits django/conf/locale

[Django]

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

  * status:  new => closed
  * resolution:  => invalid

Comment:

 As of Python 2.6, `setup.py build` only places Python modules and and C
 extensions into the build directory, and does not deal with anything else;
 as such this is a (documented) limitation of `distutils`, and I don't
 think we'll be mis-labeling our locale data as code to try to work around
 it.

-- 
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] #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
-~--~~~~--~~--~--~---