date:20130821

Re: [Django] #20954: Tutorial Doco Error

2013-08-21 Thread Django

#20954: Tutorial Doco Error
---+--
 Reporter:  n2cheval@… |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.5
 Severity:  Normal |   Resolution:  fixed
 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 n2cheval@…):

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


Comment:

 Didn't read the detail that it was the same file in different folders.

 Sorry.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

[Django] #20954: Tutorial Doco Error

2013-08-21 Thread Django

#20954: Tutorial Doco Error
---+
 Reporter:  n2cheval@… |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 On the page "https://docs.djangoproject.com/en/1.5/intro/tutorial03/;
 at the section "Write your first view"

 It says to update the same file "polls/urls.py" twice, but with completely
 different code, even through it says to only add the "include".

 First
 from django.conf.urls import patterns, url

 from polls import views

 urlpatterns = patterns('',
 url(r'^$', views.index, name='index')
 )

 Second
 from django.conf.urls import patterns, include, url

 from django.contrib import admin
 admin.autodiscover()

 urlpatterns = patterns('',
 url(r'^polls/', include('polls.urls')),
 url(r'^admin/', include(admin.site.urls)),
 )

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

Re: [Django] #20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails

2013-08-21 Thread Django

#20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails
-+-
 Reporter:  diek@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  views| Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 No problem, sorry it took me so long to convey my point. If you have any
 other suggestions, don't hesitate to let us know.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails

2013-08-21 Thread Django

#20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails
-+-
 Reporter:  diek@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  views|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by diek@…):

 timo,
 Ohhh man do I feel dumb. I just checked it again. You are correct, it
 works perfectly with 34. Obviously I was doing something wrong.

 My apologies. I will reread Part 3 again, I am obviously not understanding
 it as well as I should.

 derrick

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails

2013-08-21 Thread Django

#20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails
-+-
 Reporter:  diek@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  views|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 There shouldn't be a failure because the views (up to this point) simply
 display whatever ID you pass in the URL. The code does not verify that a
 poll with the given ID actually exists. Please tell me if I'm wrong.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails

2013-08-21 Thread Django

Comment (by diek@…):

timo,
From the tutorial https://docs.djangoproject.com/en/1.5/intro/tutorial03/,
right after what you have written it states:
"Take a look in your browser, at “/polls/34/”. It’ll run the detail()
method and display whatever ID you provide in the URL. Try
“/polls/34/results/” and “/polls/34/vote/” too – these will display the
placeholder results and voting pages." '''This fails because there is no
record 34.''' There is a record 1, and as I discovered it works with
polls/1/. Here is my concern, you are an expert but someone like myself is
brand new to django. When I read a tutorial I follow it step by step. As a
beginner I have to trust a tutorial, that has been written and edited
several times; when I get an error, I do not doubt the tutorial and I
think I did something incorrect. The topic is slightly complicated as
well, so I do not understand why the tutorial would use record 34, all it
did is cause confusion. And really I cannot understand why you would not
remove 34, or explain that you need to use an existing id. Again please
try to look at this from a new learner's perspective and not an expert.

Thank you,

derrick

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

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

[django/django] 69a459: [1.6.x] Documentation -- Corrected error about Mod...

2013-08-21 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 69a4594cb7b4eab7c689866557c491c85cdf3aa2
  
https://github.com/django/django/commit/69a4594cb7b4eab7c689866557c491c85cdf3aa2
  Author: Kevin Christopher Henry 
  Date:   2013-08-21 (Wed, 21 Aug 2013)

  Changed paths:
M docs/ref/models/instances.txt

  Log Message:
  ---
  [1.6.x] Documentation -- Corrected error about Model.full_clean()

Although the ModelForm validation code was changed to call
Model.full_clean(), the documentation still said otherwise. The
offending phrase was removed.

Backport of bb011cf809 from master



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

[django/django] bb011c: Documentation -- Corrected error about Model.full_...

2013-08-21 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bb011cf809359da3f717e35b5e70fec7897dd22f
  
https://github.com/django/django/commit/bb011cf809359da3f717e35b5e70fec7897dd22f
  Author: Kevin Christopher Henry 
  Date:   2013-08-21 (Wed, 21 Aug 2013)

  Changed paths:
M docs/ref/models/instances.txt

  Log Message:
  ---
  Documentation -- Corrected error about Model.full_clean()

Although the ModelForm validation code was changed to call
Model.full_clean(), the documentation still said otherwise. The
offending phrase was removed.


  Commit: c5f768f8cc53a54686bcb1867cc4400393427ffe
  
https://github.com/django/django/commit/c5f768f8cc53a54686bcb1867cc4400393427ffe
  Author: Tim Graham 
  Date:   2013-08-21 (Wed, 21 Aug 2013)

  Changed paths:
M docs/ref/models/instances.txt

  Log Message:
  ---
  Merge pull request #1502 from marfire/doc_modelvalid

Documentation -- Corrected error about Model.full_clean()


Compare: https://github.com/django/django/compare/0073f1d94fad...c5f768f8cc53

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

Re: [Django] #20537: `request_finished` signal not being called with Django 1.5 and uWSGI < 1.2.6(?)

2013-08-21 Thread Django

#20537: `request_finished` signal not being called with Django 1.5 and uWSGI <
1.2.6(?)
-+-
 Reporter:  jaap3|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  uwsgi postgres   | Triage Stage:  Ready for
  mysql idle connections |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by aaugustin):

 Do you have evidence of that behavior?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #16286: Models virtual fields and ModelForms

2013-08-21 Thread Django

#16286: Models virtual fields and ModelForms
-+-
 Reporter:  loic84   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  invalid
 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 danols):

 * cc: ognajd@… (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20937: pytz pauses 4 sec the manage.py output

2013-08-21 Thread Django

#20937: pytz pauses 4 sec the manage.py output
---+--
 Reporter:  antonxx@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:  invalid
 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 aaugustin):

 In addition to what timo said, please check if typing "import pytz" in a
 python shell triggers the 4 second delay. If it does, it's a bug in pytz,
 not in Django.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20936: When logging out/ending a session, don't create a new, empty session

2013-08-21 Thread Django

#20936: When logging out/ending a session, don't create a new, empty session
-+-
 Reporter:  mattrobenolt |Owner:
 Type:   |  mattrobenolt
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.sessions |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  session, logout, | Triage Stage:  Accepted
  auth   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 FYI I remember (but can't locate right now) a ticket about preserving the
 language, which is stored in the session, after logout. It's related to
 this discussion.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #19949: Cached template loader doesn't cache TemplateDoesNotExist

2013-08-21 Thread Django

#19949: Cached template loader doesn't cache TemplateDoesNotExist
--+
 Reporter:  Kronuz|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  templates cache   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by susan):

 https://github.com/django/django/pull/1501 I'm still debugging, I'm
 getting an error on this line L135:

 {{{
 template_tuple = cache_loader.load_template('missing.html',
 "django/tests/missing")
 }}}


 File "/../django/template/loaders/cached.py", line 27, in loaders
 for loader in self._loaders:
 TypeError: 'type' object is not iterable

 I'll appreciate any feedback.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20537: `request_finished` signal not being called with Django 1.5 and uWSGI < 1.2.6(?)

2013-08-21 Thread Django

#20537: `request_finished` signal not being called with Django 1.5 and uWSGI <
1.2.6(?)
-+-
 Reporter:  jaap3|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  uwsgi postgres   | Triage Stage:  Ready for
  mysql idle connections |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by anonymous):

 Bug exists in Django 1.5.2 and uwsgi 1.9.12

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20953: git push -f in docs needs a stern warning

2013-08-21 Thread Django

#20953: git push -f in docs needs a stern warning
--+
 Reporter:  EvilDMP   |Owner:  nobody
 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 timo):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 See this [http://stackoverflow.com/a/948397/5112 answer from
 stackoverflow].

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20953: git push -f in docs needs a stern warning

2013-08-21 Thread Django

#20953: git push -f in docs needs a stern warning
---+--
 Reporter:  EvilDMP|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by mjtamlyn):

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


Comment:

 I believe the elegant solution is to get the most up to date version of
 git, or set the parameter (can't remember off the top of my head) that
 will make sure that push by default only pushes the current branch.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails

2013-08-21 Thread Django

#20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails
-+-
 Reporter:  diek@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  views|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 It will display a placeholder page, won't it? There isn't any fetching
 from the database in the views that have been implemented thus far:
 {{{
 def detail(request, poll_id):
 return HttpResponse("You're looking at poll %s." % poll_id)

 def results(request, poll_id):
 return HttpResponse("You're looking at the results of poll %s." %
 poll_id)

 def vote(request, poll_id):
 return HttpResponse("You're voting on poll %s." % poll_id)
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

[Django] #20953: git push -f in docs needs a stern warning

2013-08-21 Thread Django

#20953: git push -f in docs needs a stern warning
---+
Reporter: EvilDMP| 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
---+
https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
/working-with-git/#rebasing-branches:

{{{
git push -f origin ticket_x
}}}

This should be accompanied by a note saying something like:

'''Never''' use `push -f` without specifying a remote, otherwise you may
be force-pushing changes to one or more unexpected remotes without even
realising it. If you force-push to the wrong remote, you ''will'' be
sorry.

Ways of avoiding accidents with `push -f` include:

* thinking twice and three times before using `push -f`
* never using `push -f`, and instead:
* deleting the branch on GitHub and pushing again, or:
* creating a new local branch with `git checkout -b
and pushing that
* using a password (Git with HTTPS) rather than your key (Git with SSH)
for your remotes' URLs

(perhaps there are some more elegant solutions).

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20934: NoReverseMatch on ModelAdmin.changelist_view if appname_modelname_change url is removed from get_urls

2013-08-21 Thread Django

#20934: NoReverseMatch on ModelAdmin.changelist_view if appname_modelname_change
url is removed from get_urls
---+-
 Reporter:  koirikivi  |Owner:  koirikivi
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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 koirikivi):

 * has_patch:  0 => 1


Comment:

 Topic branch at https://github.com/koirikivi/django/tree/ticket_20934
 Pull request at https://github.com/django/django/pull/1499

 Tests pass under sqlite and postgresql

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails

2013-08-21 Thread Django

#20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails
-+-
 Reporter:  diek@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  views|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by diek@…):

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


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails

2013-08-21 Thread Django

Comment (by diek@…):

Good Morning,
I did not follow them out of order. If you look at tut 3, for 1.5. This is
an exact quote from Part 3, Writing more views: "Take a look in your
browser, at “/polls/34/”. It’ll run the detail() method and display
whatever ID you provide in the URL. Try “/polls/34/results/” and
“/polls/34/vote/” too – these will display the placeholder results and
voting pages."

I imagine you are volunteer, but I have to say closing my topic without
giving a chance to explain was a bit premature.

derrick

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails

2013-08-21 Thread Django

#20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails
-+-
 Reporter:  diek@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  views| Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 At that point in the tutorial, we've only stubbed out the views with
 something like `return HttpResponse("You're looking at poll %s." %
 poll_id)` -- there's no database operation yet. It sounds like you're
 following the tutorial out of order.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20937: pytz pauses 4 sec the manage.py output

2013-08-21 Thread Django

#20937: pytz pauses 4 sec the manage.py output
---+--
 Reporter:  antonxx@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:  invalid
 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 timo):

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


Comment:

 Please see this link for ways to get help; this ticket tracker isn't the
 proper channel, thanks.
 https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20937: pytz pauses 4 sec the manage.py output

2013-08-21 Thread Django

#20937: pytz pauses 4 sec the manage.py output
---+--
 Reporter:  antonxx@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by antonxx@…):

 sorry I forgot as last remark:

 I have no direct internet access by python itself
 (we are behind a company proxy, but I didn't get python
 to go through it).

 So its not possible to install packages with pip or easy_install
 from the internet:
 I have to download them first with my browser, and install from
 the local files.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20937: pytz pauses 4 sec the manage.py output

2013-08-21 Thread Django

#20937: pytz pauses 4 sec the manage.py output
---+--
 Reporter:  antonxx@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by antonxx@…):

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


Comment:

 Here another information:.

 I type {{{ manage.py }}} and after 3 sec (before the 4 sec pause ends)
 I interrupt the script by Ctrl-C and get the following traceback.
 {{{
 Traceback (most recent call last):
   File "D:\tmp\djangotest\djtest\manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "D:\Programme\python27\lib\site-
 packages\django\core\management\__init__.
 py", line 453, in execute_from_command_line
 utility.execute()
   File "D:\Programme\python27\lib\site-
 packages\django\core\management\__init__.
 py", line 376, in execute
 sys.stdout.write(self.main_help_text() + '\n')
   File "D:\Programme\python27\lib\site-
 packages\django\core\management\__init__.
 py", line 242, in main_help_text
 for name, app in six.iteritems(get_commands()):
   File "D:\Programme\python27\lib\site-
 packages\django\core\management\__init__.
 py", line 109, in get_commands
 apps = settings.INSTALLED_APPS
   File "D:\Programme\python27\lib\site-packages\django\conf\__init__.py",
 line 5
 3, in __getattr__
 self._setup(name)
   File "D:\Programme\python27\lib\site-packages\django\conf\__init__.py",
 line 4
 9, in _setup
 self._configure_logging()
   File "D:\Programme\python27\lib\site-packages\django\conf\__init__.py",
 line 7
 1, in _configure_logging
 from django.utils.log import DEFAULT_LOGGING
   File "D:\Programme\python27\lib\site-packages\django\utils\log.py", line
 6, in
  
 from django.views.debug import ExceptionReporter,
 get_exception_reporter_fil
 ter
   File "D:\Programme\python27\lib\site-packages\django\views\debug.py",
 line 11,
  in 
 from django.http import (HttpResponse, HttpResponseServerError,
   File "D:\Programme\python27\lib\site-packages\django\http\__init__.py",
 line 4
 , in 
 from django.http.response import (HttpResponse, StreamingHttpResponse,
   File "D:\Programme\python27\lib\site-packages\django\http\response.py",
 line 1
 7, in 
 from django.utils import six, timezone
   File "D:\Programme\python27\lib\site-packages\django\utils\timezone.py",
 line
 11, in 
 import pytz
   File "build\bdist.win32\egg\pytz\__init__.py", line 1103, in 
   File "build\bdist.win32\egg\pytz\__init__.py", line 107, in
 resource_exists
   File "build\bdist.win32\egg\pytz\__init__.py", line 100, in
 open_resource
   File "build\bdist.win32\egg\pkg_resources.py", line 950, in
 resource_stream
   File "build\bdist.win32\egg\pkg_resources.py", line 250, in get_provider
   File "build\bdist.win32\egg\pkg_resources.py", line 1602, in __init__
   File "build\bdist.win32\egg\pkg_resources.py", line 1583, in
 build_zipmanifest

   File "D:\Programme\python27\lib\zipfile.py", line 766, in __init__
 self._RealGetContents()
   File "D:\Programme\python27\lib\zipfile.py", line 842, in
 _RealGetContents
 x.comment = fp.read(centdir[_CD_COMMENT_LENGTH])
 KeyboardInterrupt
 }}}

 does anybody have an idea?

 Please give a short look at it, if you still
 have no idea then lets forget it.

 Thanks.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20937: pytz pauses 4 sec the manage.py output

2013-08-21 Thread Django

#20937: pytz pauses 4 sec the manage.py output
---+--
 Reporter:  antonxx@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:  worksforme
 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 anonymous):

 Hi,

 I still do not really understand what happens.
 Here are all my packages as shown by {{{ pip list }}}
 which I have on Windows 7 64 bit with python 2.7.5 (32bit):
 {{{
 babel (0.9.6)
 Django (1.5.2)
 docutils (0.11)
 genshi (0.7)
 ipython (1.0.0)
 jinja2 (2.7)
 lxml (3.2.3)
 markupsafe (0.18)
 matplotlib (1.3.0)
 mercurial (2.7)
 MySQL-python (1.2.3)
 numpy (1.7.1)
 pillow (2.1.0)
 pip (1.4.1)
 pygments (1.6)
 pyparsing (2.0.1)
 pyreadline (2.0)
 python-dateutil (2.1)
 python-ldap (2.4.13)
 pytz (2013b)
 pywin32 (218)
 scipy (0.12.0)
 setuptools (0.9.8)
 six (1.3.0)
 south (0.8.1)
 sphinx (1.1.3)
 trac (1.0.1)
 }}}


 I have made a python script for installing all that stuff.
 Now whats happens:
  - if I type {{{manage.py}}} in my test django project (created from
 scratch)
I get the 4 sec pause as mentioned above
  - if I uninstall pytz, and retry the pause is gone.
  - if I reinstall pytz:
 - with {{{ setup.py install }}} in the unpacked source dir
 - with {{{ easy_install pytz-2013b.zip }}}
the pause is here again.
  - if I reinstall pytz with {{{ pip install pytz-2013b.zip }}}, '''then I
 have no problems! ''',
the pause is gone.

 Seems like a satanic dependency :-)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

[Django] #20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails

2013-08-21 Thread Django

#20952: Django 1.5 Tutorial Part 3, Test after Update of Polls/urls.py Fails
--+
Reporter: diek@…| Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation |Version: 1.5
Severity: Normal| Keywords: views
Triage Stage: Unreviewed| Has patch: 0
Easy pickings: 0 | UI/UX: 0
--+
Good day,
I really appreciate the effort that you put forth. I hit a bit of wall
last night, and perhaps should have picked up on it myself but I did the
tutorials 1-3 back to back and maybe my brain was not %100. The test
recommended after the user changes urls: "The next step is "Take a look in
your browser, at “/polls/34/”. Unless the user has added another 33
records to polls_poll this fails, the majority of users would not have
done that. It works perfect with /polls/1/. Using '34' is very confusing,
especially for new users. I think it needs clarification which would need
maybe one sentence.

Thank you,

derrick

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20951: Add hosting to DjangoFriendlyWebHosts list

2013-08-21 Thread Django

#20951: Add hosting to DjangoFriendlyWebHosts list
-+-
 Reporter:  mamamtum |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  *.djangoproject.com  |  Version:
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  wiki page| Triage Stage:
  djangohosting  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Added.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #5929: Allow Fields to use multiple db columns (complex datatypes)

2013-08-21 Thread Django

#5929: Allow Fields to use multiple db columns (complex datatypes)
-+-
 Reporter:  poelzi   |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (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 jelko):

 * cc: j.arnds@… (added)


Comment:

 related: https://code.djangoproject.com/ticket/27

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20949: typos in code docstring

2013-08-21 Thread Django

#20949: typos in code docstring
-+-
 Reporter:  minddust |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"28b1317fd815325b5a58a7acae12ca45de5a6ac9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="28b1317fd815325b5a58a7acae12ca45de5a6ac9"
 [1.6.x] Fixed #20949 -- Typo #2 in docstring

 Backport of 0073f1d94f from master
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

[django/django] 28b131: [1.6.x] Fixed #20949 -- Typo #2 in docstring

2013-08-21 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 28b1317fd815325b5a58a7acae12ca45de5a6ac9
  
https://github.com/django/django/commit/28b1317fd815325b5a58a7acae12ca45de5a6ac9
  Author: Tim Graham 
  Date:   2013-08-21 (Wed, 21 Aug 2013)

  Changed paths:
M django/template/loader_tags.py

  Log Message:
  ---
  [1.6.x] Fixed #20949 -- Typo #2 in docstring

Backport of 0073f1d94f from master



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

[django/django] 0073f1: Fixed #20949 -- Typo #2 in docstring

2013-08-21 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0073f1d94fad3f04ed77e63984cfd7827f78e580
  
https://github.com/django/django/commit/0073f1d94fad3f04ed77e63984cfd7827f78e580
  Author: Tim Graham 
  Date:   2013-08-21 (Wed, 21 Aug 2013)

  Changed paths:
M django/template/loader_tags.py

  Log Message:
  ---
  Fixed #20949 -- Typo #2 in docstring



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

Re: [Django] #20949: typos in code docstring

2013-08-21 Thread Django

#20949: typos in code docstring
-+-
 Reporter:  minddust |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"0073f1d94fad3f04ed77e63984cfd7827f78e580"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0073f1d94fad3f04ed77e63984cfd7827f78e580"
 Fixed #20949 -- Typo #2 in docstring
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #27: Single form field for multiple database fields

2013-08-21 Thread Django

#27: Single form field for multiple database fields
-+-
 Reporter:  adrian   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jelko):

 * cc: j.arnds@… (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20949: typos in code docstring

2013-08-21 Thread Django

#20949: typos in code docstring
-+-
 Reporter:  minddust |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by minddust):

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


Comment:

 missed the **L** in temp**l**ate

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

[django/django] 082b06: Added myself to the committers list.

2013-08-21 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 082b0638ef05391fa3004463bd7f49721cde3c1d
  
https://github.com/django/django/commit/082b0638ef05391fa3004463bd7f49721cde3c1d
  Author: evildmp 
  Date:   2013-08-21 (Wed, 21 Aug 2013)

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

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


  Commit: 17fb5768e0d5442ddef1ad0b0eefb2f5c6be1319
  
https://github.com/django/django/commit/17fb5768e0d5442ddef1ad0b0eefb2f5c6be1319
  Author: Daniele Procida 
  Date:   2013-08-21 (Wed, 21 Aug 2013)

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

  Log Message:
  ---
  Merge pull request #1498 from evildmp/add-myself

Added Daniele Procida to the committers list.


Compare: https://github.com/django/django/compare/d3ed15b79d8b...17fb5768e0d5

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

Re: [Django] #20951: Add hosting to DjangoFriendlyWebHosts list

2013-08-21 Thread Django

#20951: Add hosting to DjangoFriendlyWebHosts list
-+-
 Reporter:  mamamtum |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  *.djangoproject.com  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  wiki page| Triage Stage:
  djangohosting  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 The page is locked for non-admins due to spam issues.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20951: Add hosting to DjangoFriendlyWebHosts list

2013-08-21 Thread Django

#20951: Add hosting to DjangoFriendlyWebHosts list
-+-
 Reporter:  mamamtum |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  *.djangoproject.com  |  Version:
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  wiki page| Triage Stage:
  djangohosting  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mjtamlyn):

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


Comment:

 It's a wiki, feel free to add it yourself.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

[Django] #20951: Add hosting to DjangoFriendlyWebHosts list

2013-08-21 Thread Django

Please add hosting to the wiki "DjangoFriendly" page.

Section: "Django-friendly VPS/dedicated hosts"

Host: e24cloud (please link directly to
http://www.e24cloud.com/en/Solutions/Ready-made-solutions/e24webdev)
Type: Scalable cloud
Notes: Scalable cloud hosting company, offering a ready-made solution
'e24webdev', which gives the ability to easy setup Django's development
environment as well as Pyramid's or Ruby on Rails'. It also offers a great
support, low prices and full root access to your machine.
It is not a cluster - it is a cloud, providing its services in accordance
to the IaaS (Infrastructure as a Service) model. You can adjust the
efficiency of your servers yourself, according to your needs. Prices
starting from 14,88 USD/month.

Thank you,

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20945: Allow cache tag to use specified cache config.

2013-08-21 Thread Django

#20945: Allow cache tag to use specified cache config.
-+
 Reporter:  FunkyBob |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by timo):

 From IRC, mjtamlyn and I favor carljm's approach of a custom wrapper to
 the cache tag rather than always defaulting to a "template_fragments"
 cache.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20949: typos in code docstring

2013-08-21 Thread Django

#20949: typos in code docstring
-+-
 Reporter:  minddust |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by mjtamlyn):

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


Comment:

 Fixed in d3ed15b79d8b9288c4f6af07d5161f0727dd7669 and
 b0821e6d3a5dcb8b040ce2323f49b46dabbc9e37

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

[django/django] b0821e: [1.6.x] Fixed docstring typo, thanks minddust.

2013-08-21 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: b0821e6d3a5dcb8b040ce2323f49b46dabbc9e37
  
https://github.com/django/django/commit/b0821e6d3a5dcb8b040ce2323f49b46dabbc9e37
  Author: Tim Graham 
  Date:   2013-08-21 (Wed, 21 Aug 2013)

  Changed paths:
M django/template/loader_tags.py

  Log Message:
  ---
  [1.6.x] Fixed docstring typo, thanks minddust.

Backport of d3ed15b79d from master



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

[django/django] d3ed15: Fixed docstring typo, thanks minddust.

2013-08-21 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d3ed15b79d8b9288c4f6af07d5161f0727dd7669
  
https://github.com/django/django/commit/d3ed15b79d8b9288c4f6af07d5161f0727dd7669
  Author: Tim Graham 
  Date:   2013-08-21 (Wed, 21 Aug 2013)

  Changed paths:
M django/template/loader_tags.py

  Log Message:
  ---
  Fixed docstring typo, thanks minddust.



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

[Django] #20950: Use OrderedDicts in ORM only when needed

2013-08-21 Thread Django

#20950: Use OrderedDicts in ORM only when needed
-+-
Reporter: akaariai | Owner: nobody
Type: | Status: new
Cleanup/optimization |Version: master
Component: Database | Keywords:
layer (models, ORM)| Has patch: 1
Severity: Normal |Needs tests: 0
Triage Stage: Accepted | Easy pickings: 0
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-+-
Initializing OrderedDicts seem to be really slow, at least on Python 2.7.
By instantiating OrderedDicts in Query only when needed one can save
considerable time. For example model_save_existing benchmark is 1.3x
faster, qs_filter_chaining 1.35x faster. Nearly all of the query_
benchmarks have at least 10% speedup.

Patch at https://github.com/akaariai/django/tree/ordered_dict_on_need.
Together with splitted_clone branch this gives over 1.5x speedup to
model_save_existing.

There might be some cleaner way to implement the "initiate only on need"
for Query._aggregates and Query._extra. Ideas welcome.

Ill accept this directly as this seems like a good idea to do. This trades
code-cleanness for performance, but in this particular case I think it is
worth it.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20429: Add QuerySet.update_or_create method

2013-08-21 Thread Django

#20429: Add QuerySet.update_or_create method
-+-
 Reporter:  tunixman |Owner:
 Type:  New feature  |  elektrrrus
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"f7290581fe2106c08d97215ab93e27cf6b27e100"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f7290581fe2106c08d97215ab93e27cf6b27e100"
 Fixed a regression with get_or_create and virtual fields.

 refs #20429

 Thanks Simon Charette for the report and review.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

[django/django] f72905: Fixed a regression with get_or_create and virtual ...

2013-08-21 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f7290581fe2106c08d97215ab93e27cf6b27e100
  
https://github.com/django/django/commit/f7290581fe2106c08d97215ab93e27cf6b27e100
  Author: Tim Graham 
  Date:   2013-08-21 (Wed, 21 Aug 2013)

  Changed paths:
M django/db/models/query.py
M tests/generic_relations/tests.py

  Log Message:
  ---
  Fixed a regression with get_or_create and virtual fields.

refs #20429

Thanks Simon Charette for the report and review.



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

Re: [Django] #20947: Broken link

2013-08-21 Thread Django

#20947: Broken link
-+-
 Reporter:  thundera |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  duplicate
 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 timo):

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


Comment:

 Duplicate of #20469

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #13694: SafeMIMEText argument names incompatible with those from MIMEText

2013-08-21 Thread Django

#13694: SafeMIMEText argument names incompatible with those from MIMEText
-+
 Reporter:  davenaff |Owner:  ramiro
 Type:  Bug  |   Status:  assigned
Component:  Core (Mail)  |  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 ramiro):

 * owner:  nobody => ramiro
 * status:  new => assigned


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

[django/django] a5cf5d: Switched mail tests to SimpleTestCase.

2013-08-21 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a5cf5da50d93ccb75de2af6ee3b65d942076d0f8
  
https://github.com/django/django/commit/a5cf5da50d93ccb75de2af6ee3b65d942076d0f8
  Author: Ramiro Morales 
  Date:   2013-08-21 (Wed, 21 Aug 2013)

  Changed paths:
M tests/mail/tests.py

  Log Message:
  ---
  Switched mail tests to SimpleTestCase.



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

[django/django] ececbe: Fixed #12422 -- Don't override global email charse...

2013-08-21 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ececbe77ff573707d8f25084018e66ee07f820fd
  
https://github.com/django/django/commit/ececbe77ff573707d8f25084018e66ee07f820fd
  Author: Ramiro Morales 
  Date:   2013-08-21 (Wed, 21 Aug 2013)

  Changed paths:
M django/core/mail/message.py
M tests/mail/tests.py

  Log Message:
  ---
  Fixed #12422 -- Don't override global email charset behavior for utf-8.

Thanks simonb for the report, Claude Paroz and Susan Tan for their work
on a fix.



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

Re: [Django] #12422: Django overrides the default email charset behaviour for utf-8

2013-08-21 Thread Django

#12422: Django overrides the default email charset behaviour for utf-8
---+
 Reporter:  simonb |Owner:  ramiro
 Type:  Bug|   Status:  closed
Component:  Core (Mail)|  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  charset utf-8  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Ramiro Morales ):

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


Comment:

 In [changeset:"ececbe77ff573707d8f25084018e66ee07f820fd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ececbe77ff573707d8f25084018e66ee07f820fd"
 Fixed #12422 -- Don't override global email charset behavior for utf-8.

 Thanks simonb for the report, Claude Paroz and Susan Tan for their work
 on a fix.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20949: typos in code docstring

2013-08-21 Thread Django

#20949: typos in code docstring
-+-
 Reporter:  minddust |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by minddust):

 * needs_better_patch:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * needs_docs:   => 0


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20880: Split clone() to clone() and pre_next_op()

2013-08-21 Thread Django

#20880: Split clone() to clone() and pre_next_op()
-+-
 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 updated (force-pushed) to
 https://github.com/akaariai/django/tree/splitted_clone. The patch is
 pretty good (cleanup needed), and shows promising results for model saving
 and some other queryset operations:
 {{{
 Running 'model_save_existing' benchmark ...
 Min: 0.014001 -> 0.010278: 1.3622x faster
 Avg: 0.014304 -> 0.010394: 1.3763x faster
 Significant (t=37.226713)


 Running 'model_save_new' benchmark ...
 Min: 0.013848 -> 0.010196: 1.3582x faster
 Avg: 0.014079 -> 0.010408: 1.3527x faster
 Significant (t=20.503974)


 Running 'query_get' benchmark ...
 Min: 0.027801 -> 0.023326: 1.1918x faster
 Avg: 0.028116 -> 0.023599: 1.1914x faster
 Significant (t=31.307197)
 }}}

 For qs_filter_chaining (~5 .filter() calls) using inplace results in
 speedup of:
 {{{
 Running 'qs_filter_chaining_inplace' benchmark ...
 Min: 0.000892 -> 0.000553: 1.6132x faster
 Avg: 0.000937 -> 0.000571: 1.6424x faster
 Significant (t=16.654697)
 }}}

 This is by no means complex query, yet it shows promising results.

 So, it is worth considering if .inplace() should be public API. If so,
 then it would make sense to guard against using stale versions of the
 queryset. This is doable by cloning the outer QuerySet. Skipping cloning
 of the internal Query, should give most of the speedup.

 Another consideration is that if the ._clone() should be renamed to
 ._copy() or something. The patched version ._clone() does subtly different
 thing than the old version, so this might cause some grey hairs for those
 who use that internal API.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

[Django] #20949: typos in code docstring

2013-08-21 Thread Django

#20949: typos in code docstring
---+
 Reporter:  minddust   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 == original: ==

 the parent tempate itelf

 == should be: ==

 the parent temp**l**ate it**s**elf

 == place in code: ==

 
https://github.com/django/django/blob/master/django/template/loader_tags.py#L207

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20867: Allow Form.clean() to target specific fields when raising ValidationError.

2013-08-21 Thread Django

#20867: Allow Form.clean() to target specific fields when raising 
ValidationError.
-+
 Reporter:  loic84   |Owner:  loic84
 Type:  New feature  |   Status:  assigned
Component:  Forms|  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 mjtamlyn):

 Any resolution to this will not also include the `add_errors()`
 functionality, which fixes #5335. I've closed that ticket as its topic has
 been subsumed into this 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.85bdfc8c4e599aaab3ffc34f6a336259%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #5335: Add an append method to ErrorDict

2013-08-21 Thread Django

#5335: Add an append method to ErrorDict
-+-
 Reporter:  Thomas Güttler   |Owner:
   |  jkocherhans
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  append errodict  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mjtamlyn):

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


Comment:

 I agree that this is not the best way forwards. The ticket #20867 is now
 covering the `Form.add_errors()` approach. I'm going to close this ticket
 as a "duplicate" cos I think that's closest to what's happening.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20934: NoReverseMatch on ModelAdmin.changelist_view if appname_modelname_change url is removed from get_urls

2013-08-21 Thread Django

#20934: NoReverseMatch on ModelAdmin.changelist_view if appname_modelname_change
url is removed from get_urls
---+-
 Reporter:  koirikivi  |Owner:  koirikivi
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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 koirikivi):

 * status:  new => assigned
 * owner:  nobody => koirikivi


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20945: Allow cache tag to use specified cache config.

2013-08-21 Thread Django

#20945: Allow cache tag to use specified cache config.
-+
 Reporter:  FunkyBob |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by FunkyBob):

 Timo,

 I missed your comment there...  yes, I have considered if it should be a
 hard error or not to specify a cache that doesn't exist.

 I can see a case either way, to be honest.  But I guess since there's now
 a fallback approach for "template_fragments" -> "default", when you define
 one explicitly we probably should go splodey if it's not 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.439f8c049a5476bb04d90f569862b51a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20948: Form ImageField, MemoryFileUploadHandler and reading content of the InMemoryUploadedFile

2013-08-21 Thread Django

#20948: Form ImageField, MemoryFileUploadHandler and reading content of the
InMemoryUploadedFile
-+-
Reporter: p_hrechyshkin@… | Owner: nobody
Type: Uncategorized| Status: new
Component: Python 2 |Version: 1.4
Severity: Normal | Keywords: file upload
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0| UI/UX: 0
-+-
There is a form with ImageField, which returns validation error

"Upload a valid image. The file you uploaded was either not an image
or a corrupted image."

In my view I am trying to read image file content:

image = self.request.FILES.get('image')
if image:
content = "".join(image.chunks())
Validation error doesn't occur if I comment line with image.chunks(), also
it isn't showed if I remove
"django.core.files.uploadhandler.MemoryFileUploadHandler" from
FILE_UPLOAD_HANDLERS setting.

So the reason could be in file object created by MemoryFileUploadHandler
(InMemoryUploadedFile).

My guess was it could be that after read there is no call file.seek(0)
which set file reader pointer to the begging of the file.

It could be ImageFile.to_python assumes that pointer set to the beginning.
In ImageField.to_python I have added

data.file.seek(0)
before

file = StringIO(data.read())
and I haven't got image validation error after that.

Is it proper behavior? Or ImageField shouldn't assume that file haven't
been read? Or InMemoryUploadedFile should call file.seek(0) after chunks
iterator ended its 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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.4d160765d43f1bc1e8bdca36b1900a13%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20947: Broken link

2013-08-21 Thread Django

#20947: Broken link
-+-
 Reporter:  thundera |Owner:  nobody
 Type:  Bug  |   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|
-+-

Comment (by mjtamlyn):

 Also worth noting that the rtfd builds of the docs do not have this
 problem. I think it's an issue with our deployment procedures rather than
 the docs files themselves.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #20947: Broken link

2013-08-21 Thread Django

#20947: Broken link
-+-
 Reporter:  thundera |Owner:  nobody
 Type:  Bug  |   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 mjtamlyn):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * component:  Uncategorized => Database layer (models, ORM)
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Also applies to all other versions from 1.0 to 1.4, but not to 1.5 or 1.6.

 The py-modindex is autogenerated. The reference in question does not
 exist. It seems that somehow we're getting the wrong version of the `py-
 modindex` between different builds of the 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.4a67a19182707f25014ae7935e529c7d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #5335: Add an append method to ErrorDict

2013-08-21 Thread Django

#5335: Add an append method to ErrorDict
-+-
 Reporter:  Thomas Güttler   |Owner:
   |  jkocherhans
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  append errodict  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by alasdair):

 * cc: alasdair (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

[Django] #20947: Broken link

2013-08-21 Thread Django

#20947: Broken link
---+
 Reporter:  thundera   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 On pagehttps://docs.djangoproject.com/en/1.4/py-modindex/ link to
 django.views is broken.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

63 matches

Mail list logo