Re: [Django] #6903: Go back to old change_list view after hitting save

[Django]

#6903: Go back to old change_list view after hitting save
---+
 Reporter:  jarrow |Owner:  oinopion
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+

Comment (by revolunet):

 The querystring approach has the advantages of being explicit and allow to
 have multi-tabs/windows in different states.

 Having the breadcrumbs use the QS is optional but i thing it adds some
 comfort for the user (let's get back to where i were)

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.773c5e4fe1da3939b2bcf6245ae621db%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20615: Django 1.5.1 Trove classification is incorrect

[Django]

#20615: Django 1.5.1 Trove classification is incorrect
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Packaging |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 Django shows up the list of Python packages that people want Python 3
 support for at http://www.python.org/3kpoll. That page says "Please ask
 the package authors to use the Trove classifier 'Programming Language ::
 Python :: 3' to indicate that the port (to Python 3) has been done." I
 note that Django 1.5.1 has the Trove classifiers "Programming Language ::
 Python :: 3.2" and "Programming Language :: Python :: 3.3", but not
 "Programming Language :: Python :: 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.caec5085bfd97bc54a6eb686775c9f80%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6903: Go back to old change_list view after hitting save

[Django]

#6903: Go back to old change_list view after hitting save
---+
 Reporter:  jarrow |Owner:  oinopion
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+

Comment (by empty):

 Four years ago I started using the querystring approach to this problem
 and it has worked flawlessly. I'm not sure why there's such consternation
 over the query string parameters in the URL. It's actually quite useful
 (for sending to a friend) and the exact same behavior you would get with
 regular filtering of the change list.

 I understand the desire to get the "perfect" implementation here but
 sometimes "great" is the enemy of "good enough". Perhaps we can get some
 resolution by going forward with the querystring approach. It's not as
 though anything is lost by implementing this.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.8c955d5f878c2cc2f19c9f4e373abe4a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6903: Go back to old change_list view after hitting save

[Django]

#6903: Go back to old change_list view after hitting save
---+
 Reporter:  jarrow |Owner:  oinopion
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+
Changes (by charettes):

 * cc: charettes (added)


Comment:

 I also think the querystring is the more appropriate approach, not sure
 about the `sticky_filters` wording thought.

 I'd say leave the breadcrumbs as they are.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.c3a0eec9dcd4fdc0f5875bbe3ad1182e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6681: `admindocs` breaks compatibility with `docutils` when rendering reStructuredText

[Django]

#6681: `admindocs` breaks compatibility with `docutils` when rendering
reStructuredText
-+-
 Reporter:  mtredinnick  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admindocs|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  restructuredtext | Triage Stage:  Accepted
  docutils   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by mrmachine):

 Finally figured out how to set the default just for the block of
 reStructuredText being published in `parse_rst()`. We don't need to set a
 global default at all. PR updated.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.cfa0d54f0f6d16197377dd42f168c84b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6903: Go back to old change_list view after hitting save

[Django]

#6903: Go back to old change_list view after hitting save
---+
 Reporter:  jarrow |Owner:  oinopion
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+

Comment (by loic84):

 I've tried to sum up the different options that have been used so far in
 this ticket.

 '''The problem:'''

 We need the sticky filters to survive an arbitrarily long path made of
 GET, POST, and Redirects.

 '''The options:'''

 The only 2 *consistent* ways of doing it are the querystring and the
 session. There is a third option that involve reading the referrer and
 storing information in a hidden field, but at least for redirects and html
 links we need a fallback method.

 There is no perfect solution:
 - If we pick the querystring, we add a lot of things to the URLs.
 - If we pick the session, we lose the direct link between the
 `change_list` that started the chain of events and the one to which we
 return. (as explained in comment:71)
 - If we pick an hybrid solution, we lack consistency and we still suffer
 from the defects of whatever we use as a fallback.

 For the issue at hand I value predictably and reliability much more than
 the aesthetic of the URL, especially for an admin site. So I'd like to
 suggest using the querystring and offering an option to switch off the
 behavior: `ModelAdmin.sticky_filters`. The developer gets to pick, he can
 have prestine URLs or a robust preservation of changelist filters, not
 both. If we go with that, we'll have to decide what's the default value of
 the `sticky_filters` flag.

 Proof of concept: https://github.com/loic/django/compare/ticket6903

 I tested it manually and I have yet to fail it, I'll write the docs and
 tests tomorrow.

 Unlike previous attempts at using the querystring, it relies on a
 templatetag that accounts for existing querystring parameters.

 I've also left out the breadcrumbs, as I like that they point to a fresh
 `change_list`, but that's debatable, I can easily add them.

 Thoughts?

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.0844b3e98a9863fe14b615e26e2410ad%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6681: `admindocs` breaks compatibility with `docutils` when rendering reStructuredText

[Django]

#6681: `admindocs` breaks compatibility with `docutils` when rendering
reStructuredText
-+-
 Reporter:  mtredinnick  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admindocs|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  restructuredtext | Triage Stage:  Accepted
  docutils   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by mrmachine):

 As apollo13 mentioned, my approach of setting and unsetting the default
 inside `parse_rst()` is not safe, I have updated my PR with a refined
 version of the approach taken in PR368.

 https://github.com/django/django/pull/1277

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.dd63306e6baa34e3dadeabf7ae08304b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #11909: Django 'eating up' method errors in templates

[Django]

#11909: Django 'eating up' method errors in templates
-+--
 Reporter:  wojteks  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Template system  |  Version:  1.1
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by aaugustin):

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


Comment:

 I find it sad that you didn't read comment 3 :)

 If you genuinely want to move forwards on this issue, please write to the
 DevelopersMailingList.

 Also, please don't reopen tickets closed as wontfix by core developers.

 Thank you.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.8f723ff2d6d2e0f57d8cbbb3dd9f7376%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #11909: Django 'eating up' method errors in templates

[Django]

#11909: Django 'eating up' method errors in templates
-+--
 Reporter:  wojteks  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Template system  |  Version:  1.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by nbouliane):

 * status:  closed => new
 * severity:   => Normal
 * resolution:  wontfix =>
 * easy:   => 0
 * ui_ux:   => 0
 * type:   => Uncategorized


Comment:

 I find it sad that this ticket was closed over such drama. It is a genuine
 issue that indeeds costs us development time. It is unexpected behavior,
 and it does cause problems.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.0c86ef59e85d691dfeea1900b5fd0555%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17657: ModelForm does not respect ModelMultipleChoiceField's to_field_name attribute

[Django]

#17657: ModelForm does not respect ModelMultipleChoiceField's to_field_name
attribute
+
 Reporter:  andreyfedoseev  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.3
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by nav@…):

 * cc: nav@… (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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.6d0caba95870fe3c683da136d394c2f6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16748: Documentation on creating custom querysets

[Django]

#16748: Documentation on creating custom querysets
---+
 Reporter:  lee@…  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by danols):

 * cc: ognajd@… (added)
 * version:  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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.c087c21d0c2880b351f089fa7120ecd0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20529: Django 1.6a1 is not available via pip install as per instructions

[Django]

#20529: Django 1.6a1 is not available via pip install as per instructions
-+-
 Reporter:  un33k|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  *.djangoproject.com  |  1.6-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:  PyPI, pip| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 No, preview_version shouldn't be uploaded to PyPI, otherwise `pip install
 Django` would install it.

 This is a bug in the website, not in the release 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.6a2fe0db97fcefa4242527ee89229a8c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20593: Disagreement between User.set_password("") and User.check_password("")

[Django]

#20593: Disagreement between User.set_password("") and User.check_password("")
+
 Reporter:  jonaskoelker|Owner:
 Type:  Bug |   Status:  new
Component:  contrib.auth|  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  blank password  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+
Changes (by erikr):

 * owner:  erikr =>
 * needs_docs:  1 => 0
 * has_patch:  0 => 1
 * version:  1.4 => master
 * status:  assigned => new


Comment:

 PaulM's suggestions make sense to me. PR:
 https://github.com/django/django/pull/1278

 Also added a note in the release notes about this change. Tests
 successfully run.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.87dfc1f3c49963fac75118b953974769%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9112: New releases do not reliably overwrite old ones

[Django]

#9112: New releases do not reliably overwrite old ones
-+-
 Reporter:  holdenweb|Owner:  packagers
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  release engineering  | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by hjwp):

 This warning still pops up when a user installs Django into a virtualenv
 setup with `--system-site-packages`, but I think it's inaccurate in that
 case?

 http://virtualenvdemo.pythonanywhere.com/#note

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.71ca479d247e06f02d22f05c7b94de01%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20609: Document how to use request.user with RequestFactory (was: Documentation extension)

[Django]

#20609: Document how to use request.user with RequestFactory
--+
 Reporter:  michel@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

 * cc: timograham@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * easy:  0 => 1
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.e9777e1b8c8442b8e99d5f238667dccc%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20375: Post-processing CSS file with Unicode chars fails

[Django]

#20375: Post-processing CSS file with Unicode chars fails
-+
 Reporter:  bouke|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by ye0eugene0ey):

 * version:  1.4 => master


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.45d0a8be527a15ad14ff9a61347f5278%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20375: Post-processing CSS file with Unicode chars fails

[Django]

#20375: Post-processing CSS file with Unicode chars fails
-+
 Reporter:  bouke|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by ye0eugene0ey):

 * status:  closed => new
 * cc: yeo.eugene.oey@… (added)
 * needs_better_patch:  0 => 1
 * resolution:  invalid =>
 * version:  master => 1.4
 * type:  Uncategorized => Bug


Comment:

 == Reproduce the Error ==

 I encounter the same issues. And after tracing the type,
 It happened on
 
[https://github.com/django/django/blob/1.4/django/contrib/staticfiles/storage.py#L226],
 when trying to replace a ''unicode'' type into a ''string'' type that has
 a ''unicode'' character.

 {{{
 import re

 patt = re.compile(r"""(url\(['"]{0,1}\s*(.*?)["']{0,1}\))""")

 patt.sub(lambda x: u'The replacement is a function that return unicode',
 """The content is str with at least a unicode character głó,
 and don't forget to match url(../some/path)""")
 }}}

 == Patching?? ==

 I tried to convert the type into string at
 
[https://github.com/django/django/blob/1.4/django/contrib/staticfiles/storage.py#L172]
 and it works
 {{{
 return str('url("%s")' % unquote(relative_url))
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.ac9608543bca54481d4190c24a3f5da6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20529: Django 1.6a1 is not available via pip install as per instructions

[Django]

#20529: Django 1.6a1 is not available via pip install as per instructions
-+-
 Reporter:  un33k|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  *.djangoproject.com  |  1.6-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:  PyPI, pip| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by ugsheep):

 Replying to [comment:1 bmispelon]:
 The views.py is fine.
 From download.html
 
(https://github.com/django/djangoproject.com/blob/master/templates/releases/download.html#L41),
 it appears the preview_version should also be uploaded to PyPI, but I'm
 not sure.


 > I believe that's an issue of the download page itself, not with the
 packaging.
 >
 > The view that renders this page can be found there:
 
https://github.com/django/djangoproject.com/blob/master/releases/views.py#L9-L40

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.bbb2abffe2b77daeb3eb538da8a88e7b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20593: Disagreement between User.set_password("") and User.check_password("")

[Django]

#20593: Disagreement between User.set_password("") and User.check_password("")
+
 Reporter:  jonaskoelker|Owner:  erikr
 Type:  Bug |   Status:  assigned
Component:  contrib.auth|  Version:  1.4
 Severity:  Normal  |   Resolution:
 Keywords:  blank password  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+
Changes (by erikr):

 * status:  new => assigned
 * cc: eromijn@… (added)
 * owner:  nobody => erikr
 * needs_docs:  0 => 1


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.d389416f51228f06dae5b6ad4b1e6cc6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20614: Versionadded statement is wrongly formatted

[Django]

#20614: Versionadded statement is wrongly formatted
-+-
 Reporter:  batisteo |Owner:  batisteo
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"a952044228432fac8043b8f034b19296d308a44a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a952044228432fac8043b8f034b19296d308a44a"
 [1.5.x] Fixed #20614 -- Typo in documentation.

 Backport of 39b245fd76 from master
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.2997713562fa3c3effd36185b334c5ed%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] a95204: [1.5.x] Fixed #20614 -- Typo in documentation.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: a952044228432fac8043b8f034b19296d308a44a
  
https://github.com/django/django/commit/a952044228432fac8043b8f034b19296d308a44a
  Author: Baptiste Darthenay 
  Date:   2013-06-17 (Mon, 17 Jun 2013)

  Changed paths:
M docs/ref/templates/builtins.txt

  Log Message:
  ---
  [1.5.x] Fixed #20614 -- Typo in documentation.

Backport of 39b245fd76 from master



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51beecead10d3_6f8410ffdd8116765%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b6f86f: Added myself to the commiters list.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b6f86fbeb1ffbe40480e066d1ff43115842171e0
  
https://github.com/django/django/commit/b6f86fbeb1ffbe40480e066d1ff43115842171e0
  Author: Baptiste Mispelon 
  Date:   2013-06-17 (Mon, 17 Jun 2013)

  Changed paths:
M AUTHORS
M docs/internals/committers.txt

  Log Message:
  ---
  Added myself to the commiters list.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51bee597da185_2c4453ddd8634c6%40hookshot-fe5-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20614: Versionadded statement is wrongly formatted

[Django]

#20614: Versionadded statement is wrongly formatted
-+-
 Reporter:  batisteo |Owner:  batisteo
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"39b245fd765bc8809cedbd0c898d5b385d8ef8ea"]:
 {{{
 #!CommitTicketReference repository=""
 revision="39b245fd765bc8809cedbd0c898d5b385d8ef8ea"
 Fixed #20614 -- Typo in documentation.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.2303f8d2d27a361f5a63ebb8a212bf4d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 39b245: Fixed #20614 -- Typo in documentation.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 39b245fd765bc8809cedbd0c898d5b385d8ef8ea
  
https://github.com/django/django/commit/39b245fd765bc8809cedbd0c898d5b385d8ef8ea
  Author: Baptiste Darthenay 
  Date:   2013-06-17 (Mon, 17 Jun 2013)

  Changed paths:
M docs/ref/templates/builtins.txt

  Log Message:
  ---
  Fixed #20614 -- Typo in documentation.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51bed87f534cf_13fdfabdd8105119%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20614: Versionadded statement is wrongly formatted

[Django]

#20614: Versionadded statement is wrongly formatted
-+-
 Reporter:  batisteo |Owner:  batisteo
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by aaugustin):

 Please merge 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.34e306b78d22b9268132feb6e12354e5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6681: `admindocs` breaks compatibility with `docutils` when rendering reStructuredText

[Django]

#6681: `admindocs` breaks compatibility with `docutils` when rendering
reStructuredText
-+-
 Reporter:  mtredinnick  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admindocs|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  restructuredtext | Triage Stage:  Accepted
  docutils   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mrmachine):

 * needs_better_patch:  1 => 0


Comment:

 New PR opened.

 https://github.com/django/django/pull/1277

 This just sets the default inside `parse_rst()` and resets it before
 returning. This appears to be the only function that sets and passes the
 settings overrides that are required by the "cmsreference" role function.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.c4c9cacaa277972fbe78e375326e06a0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20614: Versionadded statement is wrongly formatted

[Django]

#20614: Versionadded statement is wrongly formatted
-+-
 Reporter:  batisteo |Owner:  batisteo
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by bmispelon):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * component:  Uncategorized => Documentation
 * needs_tests:   => 0
 * stage:  Unreviewed => Ready for checkin


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.b3e3cd9e1cc720ae9c992d5ac2c08d28%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20614: Versionadded statement is wrongly formatted

[Django]

#20614: Versionadded statement is wrongly formatted
---+--
 Reporter:  batisteo   |  Owner:  batisteo
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  0
---+--
 A `.. versionadded:: 1.5` statement is wrongly formatted, due to a double
 colon the line before.

 https://docs.djangoproject.com/en/dev/ref/templates/builtins/#std
 :templatetag-static

 Pull request here: https://github.com/django/django/pull/1276

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.6dc97f0d763ce0d61402fe21c82c4464%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6681: `admindocs` breaks compatibility with `docutils` when rendering reStructuredText (was: Problem with restructuredtext in markup module)

[Django]

#6681: `admindocs` breaks compatibility with `docutils` when rendering
reStructuredText
-+-
 Reporter:  mtredinnick  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admindocs|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  restructuredtext | Triage Stage:  Accepted
  docutils   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mrmachine):

 * cc: real.human@… (added)
 * keywords:  markup bug => restructuredtext docutils
 * has_patch:  0 => 1
 * component:  contrib.markup => contrib.admindocs


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.69d3788fece32e4661f1caf39b5aceaa%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6681: Problem with restructuredtext in markup module

[Django]

#6681: Problem with restructuredtext in markup module
+
 Reporter:  mtredinnick |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.markup  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  markup bug  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by mrmachine):

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


Comment:

 This is not a problem with `django.contrib.markup`. This problem still
 exists for anyone who wants use `admindocs` and also implement their own
 `restructuredtext` filter (or use docutils to render rst for any other
 purpose).

 Django should not assign a *default* interpreted role that *only* works
 with `django.contrib.admindocs.util.parse_rst()`.

 The ideal fix would be for Django to not set a default to begin with, but
 I do not know of a way to set a default inside `parse_rst()` only. If
 Django *must* set a default, then the default should be as compatible with
 user and 3rd party code as the original default. A refined version of
 https://github.com/django/django/pull/368 should do the trick.

 FYI this code appears to have been here from the *very* beginning, when
 Django was a private framework where it likely didn't need to worry about
 people wanting to use docutils to render reStructuredText outside of
 Django's narrow focus.

 
https://github.com/django/django/commit/ed114e15106192b22ebb78ef5bf5bce72b419d13

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.05c0d64ed95f79baf96cac6c40c5c9e9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20612: Missing text in documentation of class-based views.

[Django]

#20612: Missing text in documentation of class-based views.
-+-
 Reporter:  ndokos@… |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  documentation| Triage Stage:  Accepted
  class-based views extra context|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by bmispelon):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * easy:  0 => 1
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/074.04821f91086c3932fca978599b091d20%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20613: LocMem cache may cause deadlocks

[Django]

#20613: LocMem cache may cause deadlocks
-+-
 Reporter:  rafales  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by rafales):

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


Comment:

 The solution would be to move pickle.dumps/loads calls outside of the
 {{{with self._lock.reader()/writer()}}} blocks.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.d5338c041d434bfb83e519523acb08b3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20613: LocMem cache may cause deadlocks

[Django]

#20613: LocMem cache may cause deadlocks
-+
 Reporter:  rafales  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (Cache system)  |Version:  1.5
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  1|  UI/UX:  0
-+
 LocMem cache uses locks to synchronize access to the cache dict.

 The problem is that pickle dumps/loads is executed inside code blocks
 which acquired a reader/writer lock. Pickle dumps/loads can execute parts
 of user's code to accomplish it's task. The problem starts when user's
 code tries to retrieve something from the cache.

 In that situation for example set() acquires a lock, calls pickle.dumps()
 which calls user's code, which calls get(), which tries to acquire a lock
 - causing a deadlock. Very rare situation but it does happen.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.456b97f2d04d8f83c88f56c6570122e8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14945: ContentType.objects.get_for_model doesn't allow using multiple databases

[Django]

#14945: ContentType.objects.get_for_model doesn't allow using multiple databases
-+-
 Reporter:  donato.gr@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  ContentType, multi-  |  Unreviewed
  database, get_for_model|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Abhilash Joseph C ):

 * cc: abhi.jo89@… (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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/077.24a8e4cd97a77db6aa3681aafe674942%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14945: ContentType.objects.get_for_model doesn't allow using multiple databases

[Django]

#14945: ContentType.objects.get_for_model doesn't allow using multiple databases
-+-
 Reporter:  donato.gr@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  ContentType, multi-  |  Unreviewed
  database, get_for_model|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Abhilash Joseph C):

 Sir i need to override the function "render_change_form" and pass the
 "content_type_id" , because my django_content_type table is saved in other
 database .

 My auth_db data base has the following applications

 auth
 session
 ContentType

 and all my project related models use default db

 When i override the "change_view" and pass two object ids to
 "extra_context" i get an error "(1146, "Table 'movie.django_content_type'
 doesn't exist")

 This is because in options.py tries to load  the  "content_type_id" from
 the default db but"content_type_id" won't be available.So i tried to
 override  "render_change_form" function in admin.py and passing
 "content_type_id =
 ContentType.objects.using("auth_db").get_for_model(self.model).id" .It
 gives me an error "'QuerySet' object has no attribute 'get_for_model'"
 Therefore It would be apreciable if you would permit developers the
 accession to content_type_id though
 "ContentType.objects.using("auth_db").get_for_model(self.model).id"

 Thank you

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/077.d32a9e366d9fd32204feebd840a1f1b8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.