Re: [Django] #13366: Model importing race condition created in [12977] for subclasses of abstract classes that have fields.

[Django]

#13366: Model importing race condition created in [12977] for subclasses of
abstract classes that have fields.
-+--
  Reporter:  bretthoerner| Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by davisd):

 * cc: davisd.dav...@gmail.com (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-upda...@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] #13381: admin:login doesn't work

[Django]

#13381: admin:login doesn't work
---+
  Reporter:  alperkanat| Owner:  nobody 
  
Status:  closed| Milestone: 
  
 Component:  django.contrib.admin  |   Version:  1.2-beta   
  
Resolution:  invalid   |  Keywords:  sites, named, url, 
pattern, namespace
 Stage:  Unreviewed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 It's not a case of "doesn't work" - it's a case of "isn't needed". Admin
 doesn't require a /login url, and unless I'm mistaken, there isn't
 anywhere in documentation that suggests that it should be available. You
 just visit the url that you actually want, and the login process is
 handled as a decorator to that view.

 Even if a login view were needed, the patch you provide doesn't work - or
 rather, it will log you in, but on success, it redirects you to the same
 login page. Again, the login mechanism for admin is different to the
 default auth.login process.

-- 
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-upda...@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] #13383: Querysets should only allow the correct model types to be filtered against

[Django]

#13383: Querysets should only allow the correct model types to be filtered 
against
---+
  Reporter:  SmileyChris   | Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * milestone:  => 1.3

-- 
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-upda...@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] #13383: Querysets should only allow the correct model types to be filtered against

[Django]

#13383: Querysets should only allow the correct model types to be filtered 
against
--+-
 Reporter:  SmileyChris   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Here's a simple example of what is allowed at the moment. It seems that
 this should throw an exception for the last line:
 {{{
 In [1]: from django.contrib.auth.models import *


 In [3]: u = User.objects.all()[0]


 In [5]: m = Message.objects.create(user=u, message='test')

 In [6]: m.pk, u.pk
 Out[6]: (1, 1)


 In [10]: User.objects.filter(message=m)
 Out[10]: []

 In [11]: User.objects.filter(message=u)
 Out[11]: []
 }}}

-- 
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-upda...@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] #11857: TemporaryFile class is missing the closed - attribute

[Django]

#11857: TemporaryFile class is missing the closed - attribute
---+
  Reporter:  andi100   | Owner:  petar  
 
Status:  assigned  | Milestone: 
 
 Component:  File uploads/storage  |   Version:  SVN
 
Resolution:|  Keywords:  TemporaryFile 
closed
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Comment (by danostrowski):

 This issue is still present, as I've had the same problem.

 However, the patch attached will not work if inserted as presented.
 'temp.py' has had a lot of it's contents moved into 'tempfile.py' and
 there's apparently different classes now for temporary files based on
 whether you're using 'nt' or not. I am developing on Windows so this is of
 concern to me.

-- 
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-upda...@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] #13382: Subtly different error message on PyPy

[Django]

#13382: Subtly different error message on PyPy
+---
  Reporter:  Alex   | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Ready for checkin
  * 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-upda...@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] #13382: Subtly different error message on PyPy

[Django]

#13382: Subtly different error message on PyPy
---+
 Reporter:  Alex   |   Owner:  nobody
   Status:  new|   Milestone:  1.2   
Component:  Testing framework  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 This also results in a cascading failure, which sucks.

-- 
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-upda...@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] #13179: last_insert_id method cannot find sequence

[Django]

#13179: last_insert_id method cannot find sequence
---+
  Reporter:  grangerp  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by akaariai):

  * stage:  Accepted => Design decision needed

Comment:

 This works only if the pk field is in fact serial or bigserial, but not
 for columns of type[[BR]]
 pk integer primary key default nextval('foobar_seq').

 Tested on postgresql 8.4.3:


 {{{
 postgrs=# \d foobar
 Table "public.foobar"
  Column |  Type   |Modifiers
 +-+--
  id | integer | not null default nextval('foobar_seq'::regclass)
 Indexes:
 "foobar_pkey" PRIMARY KEY, btree (id)

 postgres=# select pg_get_serial_sequence('foobar', 'id');
  pg_get_serial_sequence
 

 (1 row)

 postgres=# \d foobar2
  Table "public.foobar2"
  Column |  Type   |  Modifiers
 +-+--
  id | integer | not null default nextval('foobar2_id_seq'::regclass)

 postgres=# select pg_get_serial_sequence('foobar2', 'id');
  pg_get_serial_sequence
 
  public.foobar2_id_seq
 (1 row)

 }}}

 For any custom database schema using default nextval instead of serial
 this would be a backwards incompatible change.

 It is probably better to use a meta option (as in #13295) to allow
 overriding the sequence name when the default doesn't work.

-- 
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-upda...@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] #13381: admin:login doesn't work

[Django]

#13381: admin:login doesn't work
---+
 Reporter:  alperkanat |   Owner:  nobody
   Status:  new|   Milestone:
Component:  django.contrib.admin   | Version:  1.2-beta  
 Keywords:  sites, named, url, pattern, namespace  |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 it's absent in django.contrib.admin.sites.py:

 {{{
 #!python
 def get_urls(self):
 from django.conf.urls.defaults import patterns, url, include

 if settings.DEBUG:
 self.check_dependencies()

 def wrap(view, cacheable=False):
 def wrapper(*args, **kwargs):
 return self.admin_view(view, cacheable)(*args, **kwargs)
 return update_wrapper(wrapper, view)

 # Admin-site-wide views.
 urlpatterns = patterns('',
 url(r'^$',
 wrap(self.index),
 name='index'),
 url(r'^logout/$',
 wrap(self.logout),
 name='logout'),
 url(r'^password_change/$',
 wrap(self.password_change, cacheable=True),
 name='password_change'),
 url(r'^password_change/done/$',
 wrap(self.password_change_done, cacheable=True),
 name='password_change_done'),
 url(r'^jsi18n/$',
 wrap(self.i18n_javascript, cacheable=True),
 name='jsi18n'),
 url(r'^r/(?P\d+)/(?P.+)/$',
 'django.views.defaults.shortcut'),
 url(r'^(?P\w+)/$',
 wrap(self.app_index),
 name='app_list')
 )
 }}}

 adding it works like a charm. attaching a patch..

-- 
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-upda...@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.

[Changeset] r13002 - in django/trunk/django/contrib/admin: media/js/admin templates/admin

[noreply]

Author: jacob
Date: 2010-04-19 13:37:12 -0500 (Mon, 19 Apr 2010)
New Revision: 13002

Modified:
   django/trunk/django/contrib/admin/media/js/admin/DateTimeShortcuts.js
   django/trunk/django/contrib/admin/templates/admin/base.html
Log:
Fixed #11967: use a different technique to get `ADMIN_MEDIA_PREFIX` in admin JS.

We now store ADMIN_MEDIA_PREFIX on the window object and let JS files read it
from there. The old technique -- looking a  tags and trying to deduce
the prefix -- broke with libraries like TineMCE that dynamically add