[Django] #19291: Sort out deprecation of ADMIN_MEDIA_PREFIX

[Django]

#19291: Sort out deprecation of ADMIN_MEDIA_PREFIX
--+
   Reporter:  ptone   |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Documentation   |Version:  master
   Severity:  Release blocker |   Keywords:
   Triage Stage:  Design decision needed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 The deprecation of this setting went in for 1.4 straight as a
 DeprecationWarning, not PendingDeprecation.

 
https://github.com/django/django/commit/38a2444277a84eb6b74425f0e324d1dceb7d2ef1

 However an accelerated timeline wasn't mentioned in the release notes, and
 it was not added to the deprecation timeline.

 Should we pull it in 1.5 - or give it till 1.6?  Either way - it needs to
 be added to the deprecation timeline.

 Given that it was not in the timeline - I feel we should probably leave it
 in till 1.6?

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19290: 'exclude' on aggregations makes wrong SQL

[Django]

#19290: 'exclude' on aggregations makes wrong SQL
--+-
 Reporter:  letscan@… |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:  aggregation
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 I have a query like this:

 {{{
 qs.annotate(num_a=Sum(field1), num_b=Sum(field2)).exclude(num_a=0,
 num_b=0)
 }}}

 the query returns fewer objects than expected. I have checked the SQL of
 the query and found it is wrong:

 {{{
 SELECT . HAVING (NOT SUM(field1)=0 AND NOT SUM(field2)=0) ...
 }}}

 while what I want is like (just as the
 [https://docs.djangoproject.com/en/1.4/ref/models/querysets/#exclude
 documentation] says):

 {{{
 SELECT . HAVING (NOT (SUM(field1)=0 AND SUM(field2)=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 https://groups.google.com/groups/opt_out.

[Django] #19289: In https://docs.djangoproject.com/en/dev/intro/tutorial02/, a sentence refers to "code from above" that doesn't exist above that sentence.

[Django]

#19289: In https://docs.djangoproject.com/en/dev/intro/tutorial02/, a sentence
refers to "code from above" that doesn't exist above that sentence.
+
 Reporter:  colinnkeenan@…  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Documentation   |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 In https://docs.djangoproject.com/en/dev/intro/tutorial02/ it says:

  Note that our loader.get_template('polls/index.html') code from above
 maps to [template_directory]/polls/index.html” on the filesystem.

 However, `loader.get_template('polls/index.html')` does not appear
 anywhere above that sentence on that page, and the reference makes no
 sense 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19278: Return the string after a certain number of words

[Django]

#19278: Return the string after a certain number of words
-+--
 Reporter:  esevece  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  truncatewords| Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by esevece):

 I've found the solution: {{ my_text.split|slice:'4:'|join:' ' }}
 But it would be great to have a filter like 'truncatewords' for 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 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 https://groups.google.com/groups/opt_out.

[Django] #19288: incorrect default verbose_name_plural in 1.5

[Django]

#19288: incorrect default verbose_name_plural in 1.5
--+-
 Reporter:  cdestigter|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.5-alpha-1
 Severity:  Release blocker   |   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 Sometime since 1.5a1, `MyModel._meta.verbose_name_plural` seems to be set
 to a weird default:

 {{{
 from django.db.models.loading import get_models
 for cls in get_models():
 print cls._meta.verbose_name_plural

 
 
 ...
 }}}

 Overriding it via adding a `Meta` class on the model it works as expected.
 But the default is a little puzzling.

 Marking as release blocker since this appears to be a regression in 1.5.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #9962: Add a tutorial for the testing framework

[Django]

#9962: Add a tutorial for the testing framework
---+
 Reporter:  russellm   |Owner:
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timo):

 1. Hmm, I'm not sure. It may be easiest to port these changes over to my
 updated patch manually, if that's not too much work.  You could try using
 something like Meld to view changes between my updated version and your
 local copy.

 2. Feel free to download the patch I uploaded, make any changes, and re-
 upload it. If you have some changes you're not sure about, feel free to
 leave a comment here and we can discuss. Or if you want to just leave
 comments here for typos, etc. as well, I'll be happy to update it.

 3. Are you perhaps using a version of Django older than
 8bd7b598b6de1be1e3f72f3a1ee62803b1c02010 as that commit made the 404
 template optional. Even before this commit, tutorial 3 instructed to
 create a 404.html template:
 https://docs.djangoproject.com/en/1.4/intro/tutorial03/#write-a-404-page-
 not-found-view

 4. I sympathize with that argument. On the other hand, a new paragraph is
 typically used to indicate a change of subject matter and I had some
 trouble following sections since the breaks suggested to me that the two
 sections weren't closely related -- thus, I collapsed a few sections a
 bit. Let me know if you think anything I did was too extreme.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18726: Combination of F() expression with query seems to confuse sql compiler's table aliases

[Django]

#18726: Combination of F() expression with query seems to confuse sql compiler's
table aliases
-+-
 Reporter:  bugs@…   |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 I rewrote the test case into expressions regress. I know at least of two
 different bugs happening here:
   1. The joins are "reverse trimmed" in a way that causes the query error
 in split_exclude() -> set_start().
   2. The F() expr is added to the query, then split_exclude() need is
 seen, and the F() expr is again added to the subquery.

 Even after bypassing the two above issues there is still something else
 going on.

 I am not sure if the test case is correct - at least it shows the U4
 reference error, see
 https://github.com/akaariai/django/compare/ticket_18726

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #9962: Add a tutorial for the testing framework

[Django]

#9962: Add a tutorial for the testing framework
---+
 Reporter:  russellm   |Owner:
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by EvilDMP):

 Thanks.

 I have made a couple of changes and corrections locally based on comments
 from Mark Jones, but I also made a mess rebasing my local copy, and now I
 am not sure how (or whether) I can push them to my branch on GitHub, all
 at
 
.

 If I want to comment on your version, or note typos etc, what is the best
 way to do that?

 For example:

 was_published_recently() returns True, though we wanted it to return
 False`

 If I *don't* override_settings, DEBUG = False causes a
 TemplateDoesNotExist: 404.html:


 {{{
 Traceback (most recent call last):
   File "/home/daniele/django-testing-tutorial/mysite/polls/tests.py", line
 116, in test_detail_view_with_a_future_poll
 response = self.client.get(reverse('polls:detail',
 args=(self.stones_poll.id,)))
   File "/home/daniele/django-testing-tutorial/local/lib/python2.7/site-
 packages/django/test/client.py", line 439, in get
 response = super(Client, self).get(path, data=data, **extra)
   File "/home/daniele/django-testing-tutorial/local/lib/python2.7/site-
 packages/django/test/client.py", line 244, in get
 return self.request(**r)
   File "/home/daniele/django-testing-tutorial/local/lib/python2.7/site-
 packages/django/core/handlers/base.py", line 150, in get_response
 response = callback(request, **param_dict)
   File "/home/daniele/django-testing-tutorial/local/lib/python2.7/site-
 packages/django/utils/decorators.py", line 91, in _wrapped_view
 response = view_func(request, *args, **kwargs)
   File "/home/daniele/django-testing-tutorial/local/lib/python2.7/site-
 packages/django/views/defaults.py", line 20, in page_not_found
 t = loader.get_template(template_name) # You need to create a 404.html
 template.
   File "/home/daniele/django-testing-tutorial/local/lib/python2.7/site-
 packages/django/template/loader.py", line 145, in get_template
 template, origin = find_template(template_name)
   File "/home/daniele/django-testing-tutorial/local/lib/python2.7/site-
 packages/django/template/loader.py", line 138, in find_template
 raise TemplateDoesNotExist(name)
 TemplateDoesNotExist: 404.html

 }}}

 Finally, my preference when writing documents like this (on the web,
 dense, and likely to be read by non-native English speakers) is to break
 the text up into shorter paragraphs than the Django documentation
 generally does. What's your feeling on that?

 Daniele

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19284: django.contrib.auth.forms imports User instead of using get_user_model

[Django]

#19284: django.contrib.auth.forms imports User instead of using get_user_model
-+---
 Reporter:  kunitoki@…   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  contrib.auth |  Version:  1.5-alpha-1
 Severity:  Release blocker  |   Resolution:  wontfix
 Keywords:  auth user| Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---
Changes (by russellm):

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


Comment:

 Just importing User shouldn't cause an error. You must be inadvertently
 using the User model in some way.

 The only forms using User are UserCreationForm and UserChangeForm, both of
 which are documented as needing to be over

 The patch form @akaariai won't work reliably, either -- because it assumes
 makes an assumption about the name and validation of the username field.
 This means the form will fail in interesting ways, depending on the User
 model you have in use.

 As an aside, the patch also make testing difficult, because the form is
 bound to the User model that is in use at the time the auth module is
 imported.

 It might be possible to make the Create and Change forms completely
 generic, but for my money, it just isn't worth the effort and complexity,
 given the effort required to fix in a subclass. There might be some
 opportunity for introducing a base class to make subclassing easier, but
 that's a topic for a separate ticket.

 tl;dr - that particular User import was deliberate, and shouldn't be
 causing problems. Marking wontfix on that basis.

 If someone can demonstrate the way to reproduce the described error, then
 feel free to reopen.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19276: ORM performance regression between 1.4.x and 1.5.x

[Django]

#19276: ORM performance regression between 1.4.x and 1.5.x
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Database layer   |  1.5-alpha-1
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

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


Comment:

 OK, it seems the regressions are now fixed, see:
 http://users.tkk.fi/~akaariai/djbench/query_select_related/ and
 http://users.tkk.fi/~akaariai/djbench/query_annotate/ (the last commits
 are barely visible in the right, but they are there...).

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 911d35: [1.5.x] fixed a broken link in the docs. Backport ...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 911d3581ea065410f742497cc498ae2bc58f9e91
  
https://github.com/django/django/commit/911d3581ea065410f742497cc498ae2bc58f9e91
  Author: Alex Gaynor 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M docs/topics/logging.txt

  Log Message:
  ---
  [1.5.x] fixed a broken link in the docs. Backport of 
1e34fd3c03e8f9a9e2b9be35488b8209178a4df0



-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 1e34fd: fixed a broken link in the docs

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1e34fd3c03e8f9a9e2b9be35488b8209178a4df0
  
https://github.com/django/django/commit/1e34fd3c03e8f9a9e2b9be35488b8209178a4df0
  Author: Alex Gaynor 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M docs/topics/logging.txt

  Log Message:
  ---
  fixed a broken link in the docs



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19263: DatabaseError on using empty Page .object_list in __in clause in a query

[Django]

#19263: DatabaseError on using empty Page .object_list in __in clause in a query
--+
 Reporter:  chkwok@…  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.4
 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 aaugustin):

 * type:  Uncategorized => Bug
 * component:  Uncategorized => Core (Other)
 * stage:  Unreviewed => Accepted


Old description:

> I've noticed that after upgrading to Django 1.4, __in queries really
> don't like empty sets. Simple queries still work, like
> User.objects.filter(groups__in=[]), but most failures I've seen are with
> Paginators. I think this is the minimum set to cause a DatabaseError,
> create any app, add a models.py with:
>
> {{{#!python
> from django.db import models
>
> class Author(models.Model):
> pass
>
> class Book(models.Model):
> author = models.ForeignKey(Author)
>
> def crash():
> from django.core.paginator import Paginator
>
> pages = Paginator(Author.objects.all(), 25)
> page = pages.page(1)
>
> books = Book.objects.filter(author__in=page.object_list)
> print books
> }}}
>
> calling crash() will cause this stack trace:
>
> {{{
> C:\Workspace\someproject\src\someproject\test.py in ()
>   6
>   7 books = Book.objects.filter(author__in=page.object_list)
> > 8 print books
>   9
>
> C:\Dev\Python27\lib\site-packages\django\db\models\query.pyc in
> __repr__(self)
>  70
>  71 def __repr__(self):
> ---> 72 data = list(self[:REPR_OUTPUT_SIZE + 1])
>  73 if len(data) > REPR_OUTPUT_SIZE:
>  74 data[-1] = "...(remaining elements truncated)..."
>
> C:\Dev\Python27\lib\site-packages\django\db\models\query.pyc in
> __len__(self)
>  85 self._result_cache = list(self.iterator())
>  86 elif self._iter:
> ---> 87 self._result_cache.extend(self._iter)
>  88 if self._prefetch_related_lookups and not
> self._prefetch_done:
>  89 self._prefetch_related_objects()
>
> C:\Dev\Python27\lib\site-packages\django\db\models\query.pyc in
> iterator(self)
> 289 klass_info = get_klass_info(model,
> max_depth=max_depth,
> 290 requested=requested,
> only_load=only_load)
> --> 291 for row in compiler.results_iter():
> 292 if fill_cache:
> 293 obj, _ = get_cached_row(row, index_start, db,
> klass_info,
>
> C:\Dev\Python27\lib\site-packages\django\db\models\sql\compiler.pyc in
> results_iter(self)
> 761 if self.query.select_for_update and
> transaction.is_managed(self.using):
> 762 transaction.set_dirty(self.using)
> --> 763 for rows in self.execute_sql(MULTI):
> 764 for row in rows:
> 765 if resolve_columns:
>
> C:\Dev\Python27\lib\site-packages\django\db\models\sql\compiler.pyc in
> execute_sql(self, result_type)
> 816
> 817 cursor = self.connection.cursor()
> --> 818 cursor.execute(sql, params)
> 819
> 820 if not result_type:
>
> C:\Dev\Python27\lib\site-packages\django\db\backends\util.pyc in
> execute(self, sql, params)
>  38 start = time()
>  39 try:
> ---> 40 return self.cursor.execute(sql, params)
>  41 finally:
>  42 stop = time()
>
> C:\Dev\Python27\lib\site-
> packages\django\db\backends\postgresql_psycopg2\base.pyc in execute(self,
> query, args)
>  50 def execute(self, query, args=None):
>  51 try:
> ---> 52 return self.cursor.execute(query, args)
>  53 except Database.IntegrityError, e:
>  54 raise utils.IntegrityError,
> utils.IntegrityError(*tuple(e)), sys.exc_info()[2]
>
> DatabaseError: syntax error at or near ")"
> LINE 1: ...ugtest_book" WHERE "bugtest_book"."author_id" IN () LIMIT 21
> }}}
>
> The SQL statement created is:
>
> {{{
> SELECT "bugtest_book"."id", "bugtest_book"."author_id" FROM
> "bugtest_book" WHERE "bugtest_book"."author_id" IN () LIMIT 21
> }}}

New description:

 I've noticed that after upgrading to Django 1.4, `__in` queries really
 don't like empty sets. Simple queries still work, like
 `User.objects.filter(groups__in=[])`, but most failures I've seen are with
 Paginators. I think this is the minimum set to cause a DatabaseError,
 create any app, add a models.py with:

 {{{#!python
 from django.db import models

 class Author(models.Model):
 pass

Re: [Django] #18922: Proliferation of dev docs on search engines confuses newbies

[Django]

#18922: Proliferation of dev docs on search engines confuses newbies
-+-
 Reporter:  dloewenherz  |Owner:
 Type:  Bug  |  dloewenherz
Component:  Djangoproject.com|   Status:  reopened
  Web site   |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * status:  closed => reopened
 * resolution:  wontfix =>
 * stage:  Unreviewed => Accepted


Old description:

> I brought this issue up earlier today at DjangoCon, but the basic issue
> can be summarized hence:
>
> 1. User searches to find info on a specific feature, gets directed to dev
> documentation.
> 2. Said feature (on the development version) is backwards incompatible
> with previous versions of Django.
> 3. User does not know better, assumes Django has a bug.
> 4. Invalid bug is filed in trac.
>
> Hopefully, removing the dev documentation pages from search engines will
> help solve
> this issue, since those who want to read the dev docs can just click
> through to
> them by using the version navigation at the bottom of the docs pages.
>
> I think there is a small subset of actual Django users who run their
> applications
> on trunk. I don't have data to back that up but I can't imagine it's a
> lot.
>
> I talked with Alex earlier today about how to deal with this issue--he
> also suggested
> redirecting users from dev -> 1.4 (or whatever the latest version is). I
> initially
> thought it was a good idea, but I thought about it and realized you would
> have to at
> least add some sort of referrer check. I then thought whether it would be
> ok to do
> something like
>
> {{{
> def conditional_documentation_redirect(request):
> if not
> request.META['REFERER'].startswith("http://docs.djangoproject.com;):
> return HttpResponseRedirect #... and so on
> }}}
>
> This felt wrong to me because if that sort of check were in place, users
> would
> no longer be able to permalink to dev docs.
>
> PR @ https://github.com/django/djangoproject.com/pull/43

New description:

 I brought this issue up earlier today at DjangoCon, but the basic issue
 can be summarized hence:

 1. User searches to find info on a specific feature, gets directed to dev
 documentation.
 2. Said feature (on the development version) is backwards incompatible
 with previous versions of Django.
 3. User does not know better, assumes Django has a bug.
 4. Invalid bug is filed in trac.

 EDIT: rejected proposal removed, see comment 4.

--

Comment:

 Yes, we can keep this ticket to track other ideas to resolve this problem.

 For the record, the original proposal was:

 > Hopefully, removing the dev documentation pages from search engines will
 help solve
 > this issue, since those who want to read the dev docs can just click
 through to
 > them by using the version navigation at the bottom of the docs pages.

 > I think there is a small subset of actual Django users who run their
 applications
 > on trunk. I don't have data to back that up but I can't imagine it's a
 lot.

 > I talked with Alex earlier today about how to deal with this issue--he
 also suggested
 > redirecting users from dev -> 1.4 (or whatever the latest version is). I
 initially
 > thought it was a good idea, but I thought about it and realized you
 would have to at
 > least add some sort of referrer check. I then thought whether it would
 be ok to do
 > something like

 {{{
 def conditional_documentation_redirect(request):
 if not
 request.META['REFERER'].startswith("http://docs.djangoproject.com;):
 return HttpResponseRedirect #... and so on
 }}}

 > This felt wrong to me because if that sort of check were in place, users
 would
 > no longer be able to permalink to dev docs.

 > PR @ https://github.com/django/djangoproject.com/pull/43

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19168: GeoIP does not work properly under os X

[Django]

#19168: GeoIP does not work properly under os X
--+
 Reporter:  tejinderss@…  |Owner:  nobody
 Type:  Bug   |   Status:  reopened
Component:  GIS   |  Version:  1.4
 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 aaugustin):

 * stage:  Unreviewed => Accepted


Old description:

> django.contrib.gis.geoip.GeoIP does not read the city/country databases
> when called without any parameters. But when passing the city/country
> database files path explicitly to the init method, it works fine.
>
> Here is example:
> # Settings
> GEOIP_PATH = os.path.join(PROJECT_DIR, 'bin',
> 'GeoIP')
> GEOIP_COUNTRY  = 'GeoIP.dat'
> GEOIP_CITY  = 'GeoLiteCity.dat'
>
> In [1]: from django.contrib.gis.geoip import GeoIP
> In [2]: geo = GeoIP()
> In [3]: geo.info
> Out[3]: 'GeoIP Library:\n\t1.4.8\nCountry:\n\t\nCity:\n\t'
> In [4]: geo._city_file
> Out[4]:
> Path(u'/Users/tejindersingh/Projects/kyb/bin/GeoIP/GeoLiteCity.dat')
> In [5]: geo._country_file
> Out[5]: Path(u'/Users/tejindersingh/Projects/kyb/bin/GeoIP/GeoIP.dat')
> In [6]: geo.city('8.8.8.8')
> Invalid database type GeoIP Country Edition, expected GeoIP City Edition,
> Rev 1
>
> Doing same thing passing the path as parameters:
>
> In [7]: geo =
> GeoIP(city='/Users/tejindersingh/Projects/kyb/bin/GeoIP/GeoLiteCity.dat',
> country='/Users/tejindersingh/Projects/kyb/bin/GeoIP/GeoIP.dat')
> In [8]: geo.info
> Out[8]: 'GeoIP Library:\n\t1.4.8\nCountry:\n\tGEO-106FREE 20120207 Build
> 1 Copyright (c) 2011 MaxMind Inc All Rights Reserved\nCity:\n\tGEO-
> 533LITE 20121002 Build 1 Copyright (c) 2012 MaxMind Inc All Rights
> Reserved'
> In [9]: geo._city_file
> Out[9]: '/Users/tejindersingh/Projects/kyb/bin/GeoIP/GeoLiteCity.dat'
> In [10]: geo._country_file
> Out[10]: '/Users/tejindersingh/Projects/kyb/bin/GeoIP/GeoIP.dat'
> In [11]: geo.city('8.8.8.8')
> Out[11]:
> {'area_code': 650,
>  'charset': 0,
>  'city': u'Mountain View',
>  'continent_code': u'NA',
>  'country_code': u'US',
>  'country_code3': u'USA',
>  'country_name': u'United States',
>  'dma_code': 807,
>  'latitude': 37.4192008972168,
>  'longitude': -122.05740356445312,
>  'postal_code': u'94043',
>  'region': u'CA'}
>
> This happens under ox X mountain lion and with kyngchaos gis/gdal binary
> packages as well as self compile brews.

New description:

 django.contrib.gis.geoip.GeoIP does not read the city/country databases
 when called without any parameters. But when passing the city/country
 database files path explicitly to the init method, it works fine.

 Here is example:
 {{{
 # Settings
 GEOIP_PATH = os.path.join(PROJECT_DIR, 'bin',
 'GeoIP')
 GEOIP_COUNTRY  = 'GeoIP.dat'
 GEOIP_CITY  = 'GeoLiteCity.dat'
 }}}

 {{{
 In [1]: from django.contrib.gis.geoip import GeoIP
 In [2]: geo = GeoIP()
 In [3]: geo.info
 Out[3]: 'GeoIP Library:\n\t1.4.8\nCountry:\n\t\nCity:\n\t'
 In [4]: geo._city_file
 Out[4]:
 Path(u'/Users/tejindersingh/Projects/kyb/bin/GeoIP/GeoLiteCity.dat')
 In [5]: geo._country_file
 Out[5]: Path(u'/Users/tejindersingh/Projects/kyb/bin/GeoIP/GeoIP.dat')
 In [6]: geo.city('8.8.8.8')
 Invalid database type GeoIP Country Edition, expected GeoIP City Edition,
 Rev 1
 }}}

 Doing same thing passing the path as parameters:

 {{{
 In [7]: geo =
 GeoIP(city='/Users/tejindersingh/Projects/kyb/bin/GeoIP/GeoLiteCity.dat',
 country='/Users/tejindersingh/Projects/kyb/bin/GeoIP/GeoIP.dat')
 In [8]: geo.info
 Out[8]: 'GeoIP Library:\n\t1.4.8\nCountry:\n\tGEO-106FREE 20120207 Build 1
 Copyright (c) 2011 MaxMind Inc All Rights Reserved\nCity:\n\tGEO-533LITE
 20121002 Build 1 Copyright (c) 2012 MaxMind Inc All Rights Reserved'
 In [9]: geo._city_file
 Out[9]: '/Users/tejindersingh/Projects/kyb/bin/GeoIP/GeoLiteCity.dat'
 In [10]: geo._country_file
 Out[10]: '/Users/tejindersingh/Projects/kyb/bin/GeoIP/GeoIP.dat'
 In [11]: geo.city('8.8.8.8')
 Out[11]:
 {'area_code': 650,
  'charset': 0,
  'city': u'Mountain View',
  'continent_code': u'NA',
  'country_code': u'US',
  'country_code3': u'USA',
  'country_name': u'United States',
  'dma_code': 807,
  'latitude': 37.4192008972168,
  'longitude': -122.05740356445312,
  'postal_code': u'94043',
  'region': u'CA'}
 }}}

 This happens under ox X mountain lion and with kyngchaos gis/gdal binary
 packages as well as self compile brews.

--

Comment:

 Fixed formatting -- please use preview.

 If I understand correctly, the problem only occurs when `GEOIP_PATH` is a

Re: [Django] #19267: 1.4.1 PDF Table of Contents links broken

[Django]

#19267: 1.4.1 PDF Table of Contents links broken
-+-
 Reporter:  michael.amie@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  PDF, Documentation,  | Triage Stage:  Accepted
  Links  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 Indeed.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19284: django.contrib.auth.forms imports User instead of using get_user_model

[Django]

#19284: django.contrib.auth.forms imports User instead of using get_user_model
-+---
 Reporter:  kunitoki@…   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.auth |  Version:  1.5-alpha-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  auth user| 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):

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


Comment:

 This was discussed in [https://groups.google.com/d/topic/django-developers
 /EI-ihJ4CLqw/discussion this thread].

 There's a
 
[https://github.com/akaariai/django/commit/04ae5183df8613fd0d91b43834a4582fdf6b0d04
 proposed patch] but it isn't entirely satisfying.

 I'm pretty sure that the current implementation is a design decision and
 not on oversight; I'll ask its author to confirm.

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] d33f8d: [1.5.x] Correct link to Sentry

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: d33f8d0f54fc57fddfad3c01d3f487c55d06d267
  
https://github.com/django/django/commit/d33f8d0f54fc57fddfad3c01d3f487c55d06d267
  Author: David Cramer 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M docs/topics/logging.txt

  Log Message:
  ---
  [1.5.x] Correct link to Sentry

django-sentry is no longer maintained, and sentry is the replacement.

Backport of 54fbe6c and c91a127 from master, as requested by Mr Gaynor.



-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19287: Change from "e-mail" to "email" not reflected in translation files for contrib.auth

[Django]

#19287: Change from "e-mail" to "email" not reflected in translation files for
contrib.auth
--+-
 Reporter:  bmispelon |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.auth  |Version:  1.5-alpha-1
 Severity:  Normal|   Keywords:  e-mail i18n
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 The changeset 2c8267bf3db608b99c04ae903c424b60cafaaf93 renamed all
 instances of "e-mail" to "email", both in the code and in the
 documentation.

 It did not, however, touch the translation files in
 django/contrib/auth/locale/, causing missing translations.

 As far as I can tell, this affects all locales except for "en".

 I'm not sure what the release process for translations is, but this could
 probably be fixed with a simple sed incantation (every instance of
 "e-mail" is all lowercase).

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 54fbe6: Correct link to Sentry

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 54fbe6ce5f758d63213ef571f175978823881834
  
https://github.com/django/django/commit/54fbe6ce5f758d63213ef571f175978823881834
  Author: David Cramer 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M docs/topics/logging.txt

  Log Message:
  ---
  Correct link to Sentry

django-sentry is no longer maintained, and sentry is the replacement.


  Commit: c91a12716ddf820d5248b4b09ec078d00ea4aa37
  
https://github.com/django/django/commit/c91a12716ddf820d5248b4b09ec078d00ea4aa37
  Author: Alex Gaynor 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M docs/topics/logging.txt

  Log Message:
  ---
  Merge pull request #516 from dcramer/master

Correct link to Sentry


Compare: https://github.com/django/django/compare/ebcf6b36ffa7...c91a12716ddf

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19279: docs.djangoproject.com/en/dev/topics/install/ "you'll need to ensure that Django has permission to create and alter tables in the database you're using" makes it seem like there's

[Django]

#19279: docs.djangoproject.com/en/dev/topics/install/ "you'll need to ensure 
that
Django has permission to create and alter tables in the database you're
using" makes it seem like there's more to do with the database before
installing Django framework
+
 Reporter:  colinnkeenan@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Documentation   |  Version:  1.4
 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 aaugustin):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * 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 https://groups.google.com/groups/opt_out.

Re: [Django] #18726: Combination of F() expression with query seems to confuse sql compiler's table aliases

[Django]

#18726: Combination of F() expression with query seems to confuse sql compiler's
table aliases
-+-
 Reporter:  bugs@…   |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * stage:  Unreviewed => Accepted


Comment:

 The error is confirmed on master. It is not caused by what I suspected in
 comment: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 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19126: runserver versus model validation

[Django]

#19126: runserver versus model validation
-+-
 Reporter:  direvus  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.3
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Design decision needed


Comment:

 One might try to work around this by inheriting `runserver.Command` and
 disabling validation, but that requires copying `inner_run`, a 50-lines
 method, just to remove the call to `validate`.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18922: Proliferation of dev docs on search engines confuses newbies

[Django]

#18922: Proliferation of dev docs on search engines confuses newbies
-+-
 Reporter:  dloewenherz  |Owner:
 Type:  Bug  |  dloewenherz
Component:  Djangoproject.com|   Status:  closed
  Web site   |  Version:  1.4
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by dloewenherz):

 This issue wasn't opened with a specific solution in mind--it's just
 illuminating that this is a problem. I get if the solution I presented is
 a bit too drastic, but I think closing this ticket ignores the real issue.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18922: Proliferation of dev docs on search engines confuses newbies

[Django]

#18922: Proliferation of dev docs on search engines confuses newbies
-+-
 Reporter:  dloewenherz  |Owner:
 Type:  Bug  |  dloewenherz
Component:  Djangoproject.com|   Status:  closed
  Web site   |  Version:  1.4
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Thanks for the suggestion.

 I understand the idea, but I'm not ready to wipe the dev docs from
 Google's index. People should be able to find information about an
 upcoming feature by googling its name.

 Besides, we take care to mention in which version new feature are added.
 And closing invalid tickets is cheap. The most troublesome change was the
 new `{% url %]`, and the flow of tickets eventually stopped.

 '''tl;dr''' The cost of the solution seems too high to me compared to the
 magnitude of the problem.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18668: Make related_query_name more configurable

[Django]

#18668: Make related_query_name more configurable
-+-
 Reporter:  zmsmith  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 It took me quite some time to understand the problem described here, but I
 think it's valid.

 I'll rephrase it to ensure we're talking about the same thing, and for the
 benefit of other contributors.

 The OP's description translates to the following models:

 {{{
 from django.db import models

 class Bar(models.Model):
 pass

 class Foo(models.Model):
 name = models.CharField(max_length=100)
 bar = models.ForeignKey(Bar)
 }}}

 With these definitions, you can do:

 {{{
 bar.foo_set.all()
 Bar.objects.filter(foo__name__contains='xxx')
 }}}

 Now, if you add `related_name='fizz_set'` to the `ForeignKey` declaration,
 you can do:

 {{{
 bar.fizz_set.all()
 Bar.objects.filter(fizz_set__name__contains='xxx')
 #  -- ugly!
 }}}

 And if you add `related_name='fizz'` it doesn't improve the situation:
 {{{
 bar.fizz.all()
 #   -- ugly!
 Bar.objects.filter(fizz__name__contains='xxx')
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 538d6c: Some changes to SortedDict to make it faster under...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 538d6c0fcd7e0a5505aa4d0424edc823ce2f511f
  
https://github.com/django/django/commit/538d6c0fcd7e0a5505aa4d0424edc823ce2f511f
  Author: Anssi Kääriäinen 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M django/utils/datastructures.py

  Log Message:
  ---
  Some changes to SortedDict to make it faster under py2

Refs #19276


  Commit: fe21c233d44a5cafff0766eb17ed3df20e08b70f
  
https://github.com/django/django/commit/fe21c233d44a5cafff0766eb17ed3df20e08b70f
  Author: Anssi Kääriäinen 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M django/db/models/sql/query.py

  Log Message:
  ---
  Removed use of SortedDict for query.alias_refcount

This will have a smallish impact on performance. Refs #19276.


  Commit: af044d86b87d23eb504687ab66027d8c124dff81
  
https://github.com/django/django/commit/af044d86b87d23eb504687ab66027d8c124dff81
  Author: Anssi Kääriäinen 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M django/db/models/options.py
M django/db/models/query.py

  Log Message:
  ---
  Fixed select_related performance regressions

The regression was caused by select_related fix for Oracle, commit
c159d9cec0baab7bbd04d5d51a92a51e354a722a.


Compare: https://github.com/django/django/compare/5e9af1600d74...af044d86b87d

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19276: ORM performance regression between 1.4.x and 1.5.x

[Django]

#19276: ORM performance regression between 1.4.x and 1.5.x
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Database layer   |  1.5-alpha-1
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Anssi Kääriäinen ):

 In [changeset:"538d6c0fcd7e0a5505aa4d0424edc823ce2f511f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="538d6c0fcd7e0a5505aa4d0424edc823ce2f511f"
 Some changes to SortedDict to make it faster under py2

 Refs #19276
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19276: ORM performance regression between 1.4.x and 1.5.x

[Django]

#19276: ORM performance regression between 1.4.x and 1.5.x
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Database layer   |  1.5-alpha-1
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Anssi Kääriäinen ):

 In [changeset:"fe21c233d44a5cafff0766eb17ed3df20e08b70f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fe21c233d44a5cafff0766eb17ed3df20e08b70f"
 Removed use of SortedDict for query.alias_refcount

 This will have a smallish impact on performance. Refs #19276.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18508: Bug in handling out-of-date POST data with inlineformset_factory

[Django]

#18508: Bug in handling out-of-date POST data with inlineformset_factory
+
 Reporter:  olau|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.4
 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 aaugustin):

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


Comment:

 Accepting because there's a patch with a test case. I'm not very familiar
 with formsets, though.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19276: ORM performance regression between 1.4.x and 1.5.x

[Django]

#19276: ORM performance regression between 1.4.x and 1.5.x
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Database layer   |  1.5-alpha-1
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Anssi Kääriäinen ):

 In [changeset:"ce1af8d7023f02e4521cce3bcdbc9fd13d76c5f8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ce1af8d7023f02e4521cce3bcdbc9fd13d76c5f8"
 Removed use of SortedDict for query.alias_refcount

 This will have a smallish impact on performance. Refs #19276.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19276: ORM performance regression between 1.4.x and 1.5.x

[Django]

#19276: ORM performance regression between 1.4.x and 1.5.x
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Database layer   |  1.5-alpha-1
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Anssi Kääriäinen ):

 In [changeset:"fa18b0ac89723f4ed6e46e744039bf375c8945a5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fa18b0ac89723f4ed6e46e744039bf375c8945a5"
 Some changes to SortedDict to make it faster under py2

 Refs #19276
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] fa18b0: Some changes to SortedDict to make it faster under...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fa18b0ac89723f4ed6e46e744039bf375c8945a5
  
https://github.com/django/django/commit/fa18b0ac89723f4ed6e46e744039bf375c8945a5
  Author: Anssi Kääriäinen 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M django/utils/datastructures.py

  Log Message:
  ---
  Some changes to SortedDict to make it faster under py2

Refs #19276


  Commit: ce1af8d7023f02e4521cce3bcdbc9fd13d76c5f8
  
https://github.com/django/django/commit/ce1af8d7023f02e4521cce3bcdbc9fd13d76c5f8
  Author: Anssi Kääriäinen 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M django/db/models/sql/query.py

  Log Message:
  ---
  Removed use of SortedDict for query.alias_refcount

This will have a smallish impact on performance. Refs #19276.


  Commit: ebcf6b36ffa7ee20b7219d34200b093186befcb4
  
https://github.com/django/django/commit/ebcf6b36ffa7ee20b7219d34200b093186befcb4
  Author: Anssi Kääriäinen 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M django/db/models/options.py
M django/db/models/query.py

  Log Message:
  ---
  Fixed select_related performance regressions

The regression was caused by select_related fix for Oracle, commit
c159d9cec0baab7bbd04d5d51a92a51e354a722a.


Compare: https://github.com/django/django/compare/00ff69a827b3...ebcf6b36ffa7

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18501: Custom fields as foreign keys fix

[Django]

#18501: Custom fields as foreign keys fix
-+-
 Reporter:  msopacua |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  RelatedField |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 Indeed, I could easily reproduce the problem with the example provided.

 A quick scan of the models definition doesn't reveal anything suspicious.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18431: TypedChoiceField doesn't use self.coerce in its clean() and prepare_value() methods

[Django]

#18431: TypedChoiceField doesn't use self.coerce in its clean() and 
prepare_value()
methods
+--
 Reporter:  ambv|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Forms   |  Version:  1.4
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by aaugustin):

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


Comment:

 You're describing a very high level issue with the design of Django's
 form. This doesn't lead to any clear, actionnable items. As a consequence
 the ticket has languished here for five months without feedback.

 I suggest taking this topic to the django-developers mailing list. You'll
 reach a wider audience and it'll be a better medium for the discussion.
 You should give more details; try to frame the problem and explain your
 proposal.

 If the discussion determines that Django's behavior should be changed —
 taking into account backward-compatibility requirements — then you're
 welcome to add details to this ticket and reopen it, or to open a new one.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19286: Development version is up to (1, 6, 0, 'alpha', 0) and 1.6 is intended to support python 3, so the tutorial should mention differences when using python 3

[Django]

#19286: Development version is up to (1, 6, 0, 'alpha', 0) and 1.6 is intended 
to
support python 3, so the tutorial should mention differences when using
python 3
+--
 Reporter:  colinnkeenan@…  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  Documentation   |  Version:  master
 Severity:  Normal  |   Resolution:  duplicate
 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 charettes):

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


Comment:

 Duplicate of #19211

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18391: Inline forms fail to delete objects when PK is a custom field

[Django]

#18391: Inline forms fail to delete objects when PK is a custom field
-+-
 Reporter:  max@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  inline form custom   | Triage Stage:
  field  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * status:  new => closed
 * resolution:   => needsinfo
 * component:  Forms => contrib.admin


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19276: ORM performance regression between 1.4.x and 1.5.x

[Django]

#19276: ORM performance regression between 1.4.x and 1.5.x
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Database layer   |  1.5-alpha-1
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

 * stage:  Accepted => Ready for checkin


Comment:

 I did a little more work, and now I have RFC stuff in
 https://github.com/akaariai/django/compare/ticket_19276

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #15987: Add auto focus field select to admin class on add and change forms

[Django]

#15987: Add auto focus field select to admin class on add and change forms
---+--
 Reporter:  dom@…  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+--
Changes (by aaugustin):

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


Comment:

 Per our [https://docs.djangoproject.com/en/dev/internals/contributing
 /bugs-and-features/#requesting-features contributing guidelines], the
 preferred way to make a feature request is to write to the
 [https://groups.google.com/group/django-developers django-developers]
 mailing list.

 If your idea receives some support, then please open a new ticket
 (possibly with a link to this one).

 To keep Trac manageable, we ask that you don't reopen tickets closed as
 wontfix by a core developer. Thanks for your understanding!

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19286: Development version is up to (1, 6, 0, 'alpha', 0) and 1.6 is intended to support python 3, so the tutorial should mention differences when using python 3

[Django]

#19286: Development version is up to (1, 6, 0, 'alpha', 0) and 1.6 is intended 
to
support python 3, so the tutorial should mention differences when using
python 3
+
 Reporter:  colinnkeenan@…  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Documentation   |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 My installation of Django shows django.VERSION as (1, 6, 0, 'alpha', 0).
 I'm doing everything with the python3 command in Ubuntu 12.10 instead of
 python, so in other words, I'm using python-3.2

 In going through the polls tutorial, the `__unicode__()` method wasn't
 working. I eventually realized (by asking on stackoverflow.com) that when
 using python 3, there isn't any `__unicode__` method since the `__str__`
 method now supports unicode by default.

 The development version of the tutorial should be updated to mention that
 with python 3, you would just use `__str__` as usual and that
 `__unicode__` is not necessary and in fact won't even 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18347: Unit tests contain raw inserts to an identity column

[Django]

#18347: Unit tests contain raw inserts to an identity column
-+-
 Reporter:  manfre   |Owner:  akaariai
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  identity |  checkin
  insert,mssql   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by aaugustin):

 The patch looks good to me too.

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19285: Allow to redirect user back in Form wizard

[Django]

#19285: Allow to redirect user back in Form wizard
---+
 Reporter:  azurit |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  contrib.formtools  |Version:  1.4
 Severity:  Normal |   Keywords:  form wizard formwizard
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I was fighting with problem in allowing to redirect user back when using
 Form wizard. Here is the use case:

  - user1 will choose a login and password in first step, login
 availability is checked
  - user1 is redirected to second step where he needs to fill up other
 important data for creating his account
  - meanwhile, user2 registers and takes login of user1
  - finally, we got an error when creating the account for user1. here we
 need to redirect him to first step and ask him for another login

 I wasn't able to find any way how to do this. Finally i was trying to
 simulate usage of 'Go back' button, which is defined in
 contrib/formtools/wizard/views.py in WizardView.post() method:
 {{{#!python
 # Look for a wizard_goto_step element in the posted data which
 # contains a valid step name. If one was found, render the
 requested
 # form. (This makes stepping back a lot easier).
 wizard_goto_step = self.request.POST.get('wizard_goto_step', None)
 if wizard_goto_step and wizard_goto_step in self.get_form_list():
 self.storage.current_step = wizard_goto_step
 form = self.get_form(
 data=self.storage.get_step_data(self.steps.current),
 files=self.storage.get_step_files(self.steps.current))
 return self.render(form)
 }}}
 Unfortunately this won't work in final step, becase of resetting the form
 wizard in the same file at the end of WizardView.render_done() method:
 {{{#!python
 done_response = self.done(final_form_list, * *kwargs)
 self.storage.reset()
 return done_response
 }}}
 I altered this method to make it work also in final step like this:
 {{{#!python
 done_response = self.done(final_form_list, **kwargs)
 if self.steps.current == self.steps.last:
 self.storage.reset()
 return done_response
 }}}
 Do you consider this as a usefull patch which can be included in Django?
 Or can you suggest another correct way how to do 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 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 https://groups.google.com/groups/opt_out.

Re: [Django] #3591: add support for custom app_label and verbose_name

[Django]

#3591: add support for custom app_label and verbose_name
-+-
 Reporter:  jkocherhans  |Owner:  adrian
 Type:  New feature  |   Status:  reopened
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Fixed on
Has patch:  1|  a branch
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  1
-+-
Changes (by fcurella):

 * cc: flavio.curella@… (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 https://groups.google.com/groups/opt_out.

Re: [Django] #19212: app_cache_ready signal

[Django]

#19212: app_cache_ready signal
-+-
 Reporter:  cdestigter   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.5-alpha-1
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by fcurella):

 * cc: flavio.curella@… (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 https://groups.google.com/groups/opt_out.

[Django] #19284: django.contrib.auth.forms imports User instead of using get_user_model

[Django]

#19284: django.contrib.auth.forms imports User instead of using get_user_model
-+-
 Reporter:  kunitoki@…   |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  contrib.auth |Version:  1.5-alpha-1
 Severity:  Release blocker  |   Keywords:  auth user
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 When adding a user in admin (for which i've subclassed the form), i'm
 getting this:

   '''Manager isn't available; User has been swapped for 'base.MyUser

 As in forms.py there is the line:

   ''from django.contrib.auth.models import User''

 Shouldn't this use get_user_model instead ?

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19283: Django CBV examples have broken import.

[Django]

#19283: Django CBV examples have broken import.
---+
 Reporter:  pydanny|Owner:  pydanny
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 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 Aymeric Augustin ):

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


Comment:

 In [changeset:"00ff69a827b38054afe557fc7d0a589b270ed871"]:
 {{{
 #!CommitTicketReference repository=""
 revision="00ff69a827b38054afe557fc7d0a589b270ed871"
 Fixed #19283 -- Fixed typo in imports in CBV docs.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19283: Django CBV examples have broken import.

[Django]

#19283: Django CBV examples have broken import.
---+
 Reporter:  pydanny|Owner:  pydanny
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Aymeric Augustin ):

 In [changeset:"5e9af1600d74cbbfef5ad13fdf377dad73e0dd86"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5e9af1600d74cbbfef5ad13fdf377dad73e0dd86"
 [1.5.x] Fixed #19283 -- Fixed typo in imports in CBV docs.

 Backport of 00ff69a 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 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 https://groups.google.com/groups/opt_out.

[django/django] 00ff69: Fixed #19283 -- Fixed typo in imports in CBV docs.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 00ff69a827b38054afe557fc7d0a589b270ed871
  
https://github.com/django/django/commit/00ff69a827b38054afe557fc7d0a589b270ed871
  Author: Aymeric Augustin 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M docs/ref/class-based-views/generic-editing.txt
M docs/topics/class-based-views/generic-editing.txt

  Log Message:
  ---
  Fixed #19283 -- Fixed typo in imports in CBV docs.



-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 5e9af1: [1.5.x] Fixed #19283 -- Fixed typo in imports in C...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 5e9af1600d74cbbfef5ad13fdf377dad73e0dd86
  
https://github.com/django/django/commit/5e9af1600d74cbbfef5ad13fdf377dad73e0dd86
  Author: Aymeric Augustin 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M docs/ref/class-based-views/generic-editing.txt
M docs/topics/class-based-views/generic-editing.txt

  Log Message:
  ---
  [1.5.x] Fixed #19283 -- Fixed typo in imports in CBV docs.

Backport of 00ff69a from master.



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19283: Django CBV examples have broken import.

[Django]

#19283: Django CBV examples have broken import.
---+
 Reporter:  pydanny|Owner:  pydanny
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 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
---+
Description changed by aaugustin:

Old description:

> In several places it is `from djangoimport models`.
>
> It is supposed to be `from django.db import models`.

New description:

 In several places it is `from django import models`.

 It is supposed to be `from django.db import models`.

--

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19283: Django CBV examples have broken import.

[Django]

#19283: Django CBV examples have broken import.
---+
 Reporter:  pydanny|Owner:  pydanny
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 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
---+

Comment (by pydanny):

 Replying to [comment:4 ssidorenko]:
 > Oh ok, i was grepping for "djangoimport" actually. Can the description
 of the bug be updated ?

 I lack the ability to edit the ticket now that it's been accepted. Perhaps
 a core developer has those rights?

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #2169: "Please correct the error below." With No Shown Errors

[Django]

#2169: "Please correct the error below." With No Shown Errors
-+-
 Reporter:  tyson@…  |Owner:  anonymous
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.databrowse   |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Design
 Keywords:  clear all errors |  decision needed
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  1
-+-
Changes (by anonymous):

 * keywords:  errors => clear all errors


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #2169: "Please correct the error below." With No Shown Errors

[Django]

#2169: "Please correct the error below." With No Shown Errors
-+-
 Reporter:  tyson@…  |Owner:  anonymous
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.databrowse   |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Design
 Keywords:  errors   |  decision needed
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  1
-+-
Changes (by anonymous):

 * severity:  normal => Release blocker
 * needs_better_patch:  0 => 1
 * component:  contrib.admin => contrib.databrowse
 * needs_tests:  0 => 1
 * easy:  0 => 1
 * keywords:   => errors
 * needs_docs:  0 => 1
 * has_patch:  0 => 1
 * ui_ux:  0 => 1
 * type:  defect => Cleanup/optimization
 * stage:  Unreviewed => Design decision needed


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #14094: Cannot define CharField with unlimited length

[Django]

#14094: Cannot define CharField with unlimited length
--+
 Reporter:  millerdev |Owner:  nobody
 Type:  New feature   |   Status:  reopened
Component:  Core (Other)  |  Version:  1.2
 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
--+

Comment (by akaariai):

 Oracle for example uses nvarchar2 for CharField, NCLOB for TextField,
 MySQL has varchar and longtext... And these "unlimited" size text fields
 really are different than limited size text field without the limit.

 How about just having a "large" default value, like 1024 chars?

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #14094: Cannot define CharField with unlimited length

[Django]

#14094: Cannot define CharField with unlimited length
--+
 Reporter:  millerdev |Owner:  nobody
 Type:  New feature   |   Status:  reopened
Component:  Core (Other)  |  Version:  1.2
 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
--+

Comment (by aaugustin):

 I can't comment on performance, but I've always found choosing the length
 of `CharField`s incredibly annoying.

 "How long can this be? 100 chars? Fields are always too short, et's make
 it 200. Oh why not 255, everyone does that..."

 I'm in favor of removing the requirement to define `max_length` on
 `CharField`s, and making them unlimited by default — assuming this isn't a
 ''Gun Aimed At Feet''.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #14094: Cannot define CharField with unlimited length

[Django]

#14094: Cannot define CharField with unlimited length
--+
 Reporter:  millerdev |Owner:  nobody
 Type:  New feature   |   Status:  reopened
Component:  Core (Other)  |  Version:  1.2
 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 jacob):

 * stage:  Design decision needed => Accepted


Comment:

 We should do this. Postgres, at least, has no performance or storage space
 penalty for using `varchar` over `varchar(n)` -- the length requirement is
 basically a constraint, that's all. I imagine other modern DBs are
 similar, but even if not it's still a good idea to let users make the
 call, not do it unilaterally.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19283: Django CBV examples have broken import.

[Django]

#19283: Django CBV examples have broken import.
---+
 Reporter:  pydanny|Owner:  pydanny
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 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
---+

Comment (by ssidorenko):

 Oh ok, i was grepping for "djangoimport" actually. Can the description of
 the bug be 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 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19239: Provide examples in the ref docs for Generic date views

[Django]

#19239: Provide examples in the ref docs for Generic date views
--+
 Reporter:  pydanny   |Owner:  pydanny
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 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 ptone):

 * type:  Uncategorized => Cleanup/optimization
 * version:  1.4 => master
 * component:  Uncategorized => Documentation
 * 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 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19283: Django CBV examples have broken import.

[Django]

#19283: Django CBV examples have broken import.
---+
 Reporter:  pydanny|Owner:  pydanny
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 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 ptone):

 * version:  1.4 => master
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 For sure they're there

 {{{
 element:docs (master)$ ack -a 'from django import models'
 ./ref/class-based-views/generic-editing.txt
 19:from django import models

 ./topics/class-based-views/generic-editing.txt
 93:from django import models
 163:from django import models
 element:docs (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 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19283: Django CBV examples have broken import.

[Django]

#19283: Django CBV examples have broken import.
---+--
 Reporter:  pydanny|Owner:  pydanny
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by ssidorenko):

 I cannot find the problem you are describing, can you post a link or a
 path where it can be found ?

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19283: Django CBV examples have broken import. (was: Django CBV editing examples have broken import.)

[Django]

#19283: Django CBV examples have broken import.
---+--
 Reporter:  pydanny|Owner:  pydanny
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by pydanny):

 * 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 https://groups.google.com/groups/opt_out.

[Django] #19283: Django CBV editing examples have broken import.

[Django]

#19283: Django CBV editing examples have broken import.
---+-
 Reporter:  pydanny|  Owner:  pydanny
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+-
 In several places it is `from djangoimport models`.

 It is supposed to be `from django.db import models`.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #9962: Add a tutorial for the testing framework

[Django]

#9962: Add a tutorial for the testing framework
---+
 Reporter:  russellm   |Owner:
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

 * needs_better_patch:  1 => 0


Comment:

 This looks quite good to me, bravo! I've made some edits, mostly cosmetic.
 One material change I did make was to remove override_settings in the
 tests. As far as I can see, it shouldn't be necessary. What exception was
 raised when you executed that test?

 I'll reply to your thread on django-developers and hopefully we can get a
 couple more people to run through this.

 Here's an HTML version for easy review:
 http://techytim.com/django/9962/intro/tutorial05.html

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19244: Provide the missing examples from the "Built-in template tags and filters" page

[Django]

#19244: Provide the missing examples from the "Built-in template tags and 
filters"
page
---+
 Reporter:  pydanny|Owner:  pydanny
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 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 Aymeric Augustin ):

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


Comment:

 In [changeset:"e27a43cc54f120c49cac33b36568b128bcfaef5a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e27a43cc54f120c49cac33b36568b128bcfaef5a"
 Merge pull request #509 from pydanny/ticket_19244

 Fixed #19244 -- Provided examples for some built-in templatetags and
 filters
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 1db5d8: Added examples for comment, templatetag, escape, f...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1db5d8827351acd2d039c218723d5100dc7e7f95
  
https://github.com/django/django/commit/1db5d8827351acd2d039c218723d5100dc7e7f95
  Author: Daniel Greenfeld 
  Date:   2012-11-08 (Thu, 08 Nov 2012)

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

  Log Message:
  ---
  Added examples for comment, templatetag, escape, force_escape, timesince, and 
timeuntil


  Commit: 3f65f751a0082b83ff24849a1445aa0838b27d93
  
https://github.com/django/django/commit/3f65f751a0082b83ff24849a1445aa0838b27d93
  Author: Daniel Greenfeld 
  Date:   2012-11-12 (Mon, 12 Nov 2012)

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

  Log Message:
  ---
  Converted  to  per #aaugustin's request


  Commit: e27a43cc54f120c49cac33b36568b128bcfaef5a
  
https://github.com/django/django/commit/e27a43cc54f120c49cac33b36568b128bcfaef5a
  Author: Aymeric Augustin 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

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

  Log Message:
  ---
  Merge pull request #509 from pydanny/ticket_19244

Fixed #19244 -- Provided examples for some built-in templatetags and filters 


Compare: https://github.com/django/django/compare/a72b8a224721...e27a43cc54f1

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19260: Tutorial some bits a (little) unclear

[Django]

#19260: Tutorial some bits a (little) unclear
---+--
 Reporter:  terwey@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"897d8adb1c1938261472de39ccd8066b3aacf8df"]:
 {{{
 #!CommitTicketReference repository=""
 revision="897d8adb1c1938261472de39ccd8066b3aacf8df"
 [1.5.X] Fixed #19260 - Added a comment to tutorial 1.

 Thanks terwey for the suggestion.

 Backport of a72b8a2247 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 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 https://groups.google.com/groups/opt_out.

[django/django] 897d8a: [1.5.X] Fixed #19260 - Added a comment to tutorial...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 897d8adb1c1938261472de39ccd8066b3aacf8df
  
https://github.com/django/django/commit/897d8adb1c1938261472de39ccd8066b3aacf8df
  Author: Tim Graham 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M docs/intro/tutorial01.txt

  Log Message:
  ---
  [1.5.X] Fixed #19260 - Added a comment to tutorial 1.

Thanks terwey for the suggestion.

Backport of a72b8a2247 from master



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19260: Tutorial some bits a (little) unclear

[Django]

#19260: Tutorial some bits a (little) unclear
---+--
 Reporter:  terwey@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"a72b8a224721775b31e2075c99165f1e3ca28092"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a72b8a224721775b31e2075c99165f1e3ca28092"
 Fixed #19260 - Added a comment to tutorial 1.

 Thanks terwey for the suggestion.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] a72b8a: Fixed #19260 - Added a comment to tutorial 1.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a72b8a224721775b31e2075c99165f1e3ca28092
  
https://github.com/django/django/commit/a72b8a224721775b31e2075c99165f1e3ca28092
  Author: Tim Graham 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M docs/intro/tutorial01.txt

  Log Message:
  ---
  Fixed #19260 - Added a comment to tutorial 1.

Thanks terwey for the suggestion.



-- 
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 https://groups.google.com/groups/opt_out.

[django/django] fdb855: [1.4.X] Typo in comments doc

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: fdb855e7b23d9080f87ed13560bbe383271796cb
  
https://github.com/django/django/commit/fdb855e7b23d9080f87ed13560bbe383271796cb
  Author: Nicolas Ippolito 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M docs/ref/contrib/comments/index.txt

  Log Message:
  ---
  [1.4.X] Typo in comments doc

Backport of 17b14d4819 from master



-- 
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 https://groups.google.com/groups/opt_out.

[django/django] b3ea37: [1.5.X] Typo in comments doc

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: b3ea37e304554b511789a7429319484a7436d2e3
  
https://github.com/django/django/commit/b3ea37e304554b511789a7429319484a7436d2e3
  Author: Nicolas Ippolito 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M docs/ref/contrib/comments/index.txt

  Log Message:
  ---
  [1.5.X] Typo in comments doc

Backport of 17b14d4819 from master



-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 17b14d: Typo in comments doc

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 17b14d481984f3a466a02993b35940430e5dbe91
  
https://github.com/django/django/commit/17b14d481984f3a466a02993b35940430e5dbe91
  Author: Nicolas Ippolito 
  Date:   2012-11-12 (Mon, 12 Nov 2012)

  Changed paths:
M docs/ref/contrib/comments/index.txt

  Log Message:
  ---
  Typo in comments doc


  Commit: 7733f1463141f2f0fd00cc18730582cfb365dc5d
  
https://github.com/django/django/commit/7733f1463141f2f0fd00cc18730582cfb365dc5d
  Author: Tim Graham 
  Date:   2012-11-13 (Tue, 13 Nov 2012)

  Changed paths:
M docs/ref/contrib/comments/index.txt

  Log Message:
  ---
  Merge pull request #514 from nippo/master

Typo in comments doc


Compare: https://github.com/django/django/compare/09a39ca08246...7733f1463141

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19274: Separate DB connection creation and session state initialization

[Django]

#19274: Separate DB connection creation and session state initialization
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by akaariai):

 I have now a working implementation in:
 https://github.com/akaariai/django/compare/ticket_19274

 The work divides into three parts:
   - Backend conversion as mentioned in the ticket description
   - Removing the assumption that connection's self.settings_dict changes
 will be reflected in the global settings
   - Random test fixed (one Oracle specific fix, some fixes into how to
 create additional connections for testing and some fixes to accessing the
 connection.connection variable)

 After the fixes the work in https://github.com/akaariai/django_pooled/
 passes on all core backends. The pooling implementation in django_pooled
 is somewhere between ugly and hideous. What is interesting is that
 django_pooled shows that one can have generic pooling implementation
 outside core, and that it actually works.

 The separation of self.settings_dict from global settings is needed for
 the above pooling implementation (and I believe any pooling implementation
 wants that). The basic problem is that you need to tell Django to use the
 pool in ENGINE, and then you need to have the real engine somewhere
 (OPTIONS -> WRAPS in django_pooled). You need to alter the settings before
 passing to the real backend, but you can't do that to the global settings,
 otherwise the information is lost for next connection creation.

 Gis backends aren't converted yet.

-- 
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 https://groups.google.com/groups/opt_out.