date:20130528

Re: [Django] #20342: Replace CBV lookup arguments with single `lookup_field` argument.

2013-05-28 Thread Django

#20342: Replace CBV lookup arguments with single `lookup_field` argument.
-+-
 Reporter:  tomchristie  |Owner:
 Type:   |  tomchristie
  Cleanup/optimization   |   Status:  new
Component:  Generic views|  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 anonymous):

 I like simplifying this, but I don't think it's appropriate to force that
 the urlpattern name matches the model field name. We need two parameters
 here -- one is the urlconf name, the other is the model field.
 ``lookup_url_field`` and ``lookup_model_field``, maybe. Assuming that the
 urlconf matches the model is inappropriate coupling.

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

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

Re: [Django] #20393: django.db.models.query.QuerySet.repr should not have side-effects

2013-05-28 Thread Django

#20393: django.db.models.query.QuerySet.__repr__ should not have side-effects
-+-
 Reporter:  justin@… |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  QuerySet, repr,  |  Unreviewed
  side-effect|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 That sounds like  a great change 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 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/079.ef45e9276925b5719360d6013001f323%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20525: clearsessions documentation should indicate version added

2013-05-28 Thread Django

#20525: clearsessions documentation should indicate version added
---+
 Reporter:  wiml@… |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  1.5
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  1
UI/UX:  0  |
---+

Comment (by Tim Graham ):

 In [changeset:"1ce5672753c004da1cbe3347e2c7f652b48251b2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1ce5672753c004da1cbe3347e2c7f652b48251b2"
 [1.5.x] Fixed #20525 -- Added versionadded for clearsessions.

 Thanks wiml@.

 Backport of 8a6e040bfa 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/076.66b17c8d27760b93ec7eb26045fcd4c3%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 1ce567: [1.5.x] Fixed #20525 -- Added versionadded for cle...

2013-05-28 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 1ce5672753c004da1cbe3347e2c7f652b48251b2
  
https://github.com/django/django/commit/1ce5672753c004da1cbe3347e2c7f652b48251b2
  Author: Tim Graham 
  Date:   2013-05-28 (Tue, 28 May 2013)

  Changed paths:
M docs/ref/django-admin.txt

  Log Message:
  ---
  [1.5.x] Fixed #20525 -- Added versionadded for clearsessions.

Thanks wiml@.

Backport of 8a6e040bfa 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/51a5489f8f26b_4089c7bdd41057da%40hookshot-fe1-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 8a6e04: Fixed #20525 -- Added versionadded for clearsessio...

2013-05-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8a6e040bfa58c69ba9760a67d7d2e714bffccfc1
  
https://github.com/django/django/commit/8a6e040bfa58c69ba9760a67d7d2e714bffccfc1
  Author: Tim Graham 
  Date:   2013-05-28 (Tue, 28 May 2013)

  Changed paths:
M docs/ref/django-admin.txt

  Log Message:
  ---
  Fixed #20525 -- Added versionadded for clearsessions.

Thanks wiml@.



-- 
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/51a5487eb2658_3f90123fdd8103411%40hookshot-fe1-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20525: clearsessions documentation should indicate version added

2013-05-28 Thread Django

#20525: clearsessions documentation should indicate version added
---+
 Reporter:  wiml@… |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  1.5
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  1
UI/UX:  0  |
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"8a6e040bfa58c69ba9760a67d7d2e714bffccfc1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8a6e040bfa58c69ba9760a67d7d2e714bffccfc1"
 Fixed #20525 -- Added versionadded for clearsessions.

 Thanks wiml@.
 }}}

-- 
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/076.7fdecc747137ba9070ecc813c2d6a48c%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20521: {% local_url %} to extend {% url %} with instrospection of the rendering app

2013-05-28 Thread Django

#20521: {% local_url %} to extend {% url %} with instrospection of the rendering
app
-+--
Reporter: littlepig|Owner: nobody
Type: New feature | Status: closed
Component: Template system | Version: 1.5
Severity: Normal | Resolution: wontfix
Keywords: tag, url | 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:

I'm going to mark this wontfix, for two reasons:

1) I don't accept that a new template tag for name resolving is a good
idea. There should be one, and only one, obvious way to do it. I don't see
how a second url tag will improve matters here.

2) Your whole argument is based on the premise that the current URL
reversal scheme is "limited due to either url name collisions or app's
name collision". I don't accept that this is true in practice. If you name
your URLs things like "update", then collisions are probable, but every
best practice I've seen either incorporates the app name into the url name
(e.g., django-registration uses 'registration_activation_complete' and
'registration_activate') or actively encourages the use of namespaces --
which are in the control of the end user. By way of proof -- Django has
been in public use for almost 8 years, and namespacing has been available
for almost 4, and this is the first time I've seen anyone make a public
complaint that name collisions are a significant problem that needs a
solution.

I'm not claiming you don't (or shouldn't) have a problem in your own code.
I'm just questioning whether the problem is so widespread that it warrants
the introduction of a second parallel URL reversal scheme.

There might be some merit to your idea of using current_app inside the
existing url reversal tools; however, the implementation and consequences
of that change would need to be elaborated some more.

If this is an idea you're passionate about, I suggest taking it to django-
developers for further discussion. We don't discuss new features on
tickets because of the lack of visibility of the discussion. In that
discussion, I suggest you spend a lot more time explaining the set of
conditions that have led to you getting regular URL name collisions.

--
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.a7fe6b840a2e9c7c0b7b22e6ee76904b%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20525: clearsessions documentation should indicate version added

2013-05-28 Thread Django

#20525: clearsessions documentation should indicate version added
---+
 Reporter:  wiml@… |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  0
---+
 Attached patch adds that information.

-- 
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/061.a001a2b060d2ba388fe6aeb8795d0649%40djangoproject.com?hl=en.
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

2013-05-28 Thread Django

#19263: DatabaseError on using empty Page .object_list in __in clause in a query
-+-
 Reporter:  chkwok@… |Owner:  biern
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * cc: timograham@… (added)
 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 Patch no longer applies cleanly after
 97774429aeb54df4c09895c07cd1b09e70201f7d

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

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

Re: [Django] #12027: EmailField validation is incorrect, trailing dots fail

2013-05-28 Thread Django

#12027: EmailField validation is incorrect, trailing dots fail
-+-
 Reporter:  Klas H   |Owner:  shaz
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  email, regular   | Triage Stage:  Accepted
  expression, validation |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * cc: timograham@… (added)
 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 Please don't mark your own patch as RFC. It looks like this needs to be
 discussed as to whether we want to continue to allow email addresses that
 end with periods or not. If so, the test in the latest patch is a bit
 awkward (using both unittest.expectedFailure and assertFailsValidation).

-- 
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.e943e5904e2a2c9f8541439099a29336%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20484: GenericIPAddressField must not allow blank for NOT NULL fields

2013-05-28 Thread Django

#20484: GenericIPAddressField must not allow blank for NOT NULL fields
-+-
 Reporter:  erikr|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ded95ccdce0ba983c405ddde9eb071e454245a94"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ded95ccdce0ba983c405ddde9eb071e454245a94"
 Fixed #20484 -- Added model validation for GenericIPAddressField

 GenericIPAddressField must not allow blank for NOT NULL fields

 Thanks Erik Romijn.
 }}}

-- 
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.ed9796f80bd61cd069556173b9e7e7c8%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ded95c: Fixed #20484 -- Added model validation for Generic...

2013-05-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ded95ccdce0ba983c405ddde9eb071e454245a94
  
https://github.com/django/django/commit/ded95ccdce0ba983c405ddde9eb071e454245a94
  Author: Tim Graham 
  Date:   2013-05-28 (Tue, 28 May 2013)

  Changed paths:
M django/core/management/validation.py
M docs/releases/1.6.txt
M tests/invalid_models/invalid_models/models.py
M tests/validation/models.py
M tests/validation/tests.py

  Log Message:
  ---
  Fixed #20484 -- Added model validation for GenericIPAddressField

GenericIPAddressField must not allow blank for NOT NULL fields

Thanks Erik Romijn.



-- 
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/51a501d8ebf96_1034b83ddc34675%40hookshot-fe4-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19988: django.contrib.humanize : ordinal returns escaped HTML code in some languages

2013-05-28 Thread Django

#19988: django.contrib.humanize : ordinal returns escaped HTML code in some
languages
-+-
Reporter: maxime.lorant@… |Owner: EvilDMP
Type: Bug | Status: assigned
Component: contrib.humanize | Version: 1.5
Severity: Normal | Resolution:
Keywords: humanize ordinal | Triage Stage: Accepted
html escaped | Needs documentation: 0
Has patch: 1| Patch needs improvement: 0
Needs tests: 0|UI/UX: 0
Easy pickings: 1|
-+-
Changes (by EvilDMP):

* owner: matiasb => EvilDMP

Comment:

I have marked this ticket as suitable for a first-time committer attending
a [https://dont-be-afraid-to-commit.readthedocs.org/ Don't be afraid to
commit workshop].

The next planned session will be hosted by
[http://www.cardiffdevworkshop.com Cardiff Dev Workshop] on Saturday 8th
June.

If you want to tackle this ticket before then, or at any time in fact,
please '''don't''' let the fact that it's assigned to me stop you. Feel
free to re-assign it to yourself and do whatever you like to 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/081.612af00a0cefbc19db0c262b40dfe957%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20520: Bug when using nginx+apache not listening on 80 port.

2013-05-28 Thread Django

#20520: Bug when using nginx+apache not listening on 80 port.
---+--
 Reporter:  himikhimik@…   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 Keywords:  nginx apache   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by himikhimik@…):

 Resolved by removing wrong nginx.conf properties with proxy_set_header
 directive.

-- 
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.ca22d8ad748c6c945593632f02120089%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20520: Bug when using nginx+apache not listening on 80 port.

2013-05-28 Thread Django

#20520: Bug when using nginx+apache not listening on 80 port.
---+--
 Reporter:  himikhimik@…   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 Keywords:  nginx apache   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by himikhimik@…):

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


-- 
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.9080a80edd6a18e86be8622d6f1d%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19496: truncatechars_html

2013-05-28 Thread Django

Comment (by EvilDMP):

I have marked this ticket as suitable for a first-time committer attending
a [https://dont-be-afraid-to-commit.readthedocs.org/ Don't be afraid to
commit workshop].

The next planned session will be hosted by
[http://www.cardiffdevworkshop.com Cardiff Dev Workshop] on Saturday 8th
June.

--
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.47f062e2995e4740adde98d2c77d5b72%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19496: truncatechars_html

2013-05-28 Thread Django

#19496: truncatechars_html
-+
 Reporter:  esevece  |Owner:  EvilDMP
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  truncatchars | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+
Changes (by EvilDMP):

 * owner:  martmatwarne => EvilDMP


-- 
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.c715ebdc523c275bd5ab316d24d3e839%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20524: Triaging tickets docs should explain how keywords work

2013-05-28 Thread Django

#20524: Triaging tickets docs should explain how keywords work
--+
 Reporter:  EvilDMP   |Owner:  EvilDMP
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

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


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

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

Re: [Django] #20524: Triaging tickets docs should explain how keywords work

2013-05-28 Thread Django

#20524: Triaging tickets docs should explain how keywords work
---+--
 Reporter:  EvilDMP|Owner:  EvilDMP
 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:  1  |UI/UX:  0
---+--

Comment (by EvilDMP):

 It seems that a keyword search finds that string anywhere in the keywords,
 for example "to" in "refactor".

-- 
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.3a9ca1774cb60dfef0036fc8394006c1%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13462: GoogleMaps object should default to version 2 of google maps

2013-05-28 Thread Django

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

Comment:

I have tentatively reserved this ticket for first-time committers who take
part in the [https://dont-be-afraid-to-commit.readthedocs.org/ Don't be
afraid to commit workshop] at the [http://2013.djangocon.eu/ DjangoCon
Europe 2013] sprints on 18th and 19th May.

If you want to tackle this ticket before then, please '''don't''' let the
fact that it's assigned to me stop you. Feel free to re-assign it to
yourself and do whatever you like to 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/062.b2f34cb39b90288d7caee0c02e32a4d0%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20511: Dead link about isolation levels in databases docs

2013-05-28 Thread Django

#20511: Dead link about isolation levels in databases docs
---+-
 Reporter:  tinodb |Owner:  aaugustin
 Type:  Bug|   Status:  assigned
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):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #16357: Navigation buttons in Docs footer would be helpful

2013-05-28 Thread Django

#16357: Navigation buttons in Docs footer would be helpful
-+-
 Reporter:  ncoghlan@…   |Owner:
 Type:   |  giuliettamasina
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.3
 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:  1
-+-

Comment (by giuliettamasina):

 Looks good :) I think "Next" should stay though, for clarity. "Previous"
 is not as important, as you probably just were on that page. But if
 someone finds it too asymmetrical to have "Next" and not "Previous" I
 think finding a way to incorporate the word "Previous" would be better.
 Just my humble opinion.

-- 
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/076.af7ea67be2dc6e66e5be01b4e2afef58%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20524: Triaging tickets docs should explain how keywords work

2013-05-28 Thread Django

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

Comment:

If you want to tackle this ticket before then, please '''don't''' let the
fact that it's assigned to me stop you. Feel free to re-assign it to
yourself and do whatever you like to 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/065.d081533cc156631bc39e5e13cac62aeb%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20524: Triaging tickets docs should explain how keywords work

2013-05-28 Thread Django

#20524: Triaging tickets docs should explain how keywords work
---+-
 Reporter:  EvilDMP|  Owner:  EvilDMP
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+-
 https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/#keywords

 Are keywords comma-separated? Space separated? What are good/bad examples?

-- 
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.a27bd2ecaec599ece6a3a51061144022%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] a2967d: Fixed #20242 - Added a regression test for prefetc...

2013-05-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a2967d5204729771e3716c431ea98f8ee8562d3e
  
https://github.com/django/django/commit/a2967d5204729771e3716c431ea98f8ee8562d3e
  Author: Tim Graham 
  Date:   2013-05-28 (Tue, 28 May 2013)

  Changed paths:
M AUTHORS
M tests/prefetch_related/tests.py

  Log Message:
  ---
  Fixed #20242 - Added a regression test for prefetch_related.

Issue was fixed by removal of chunked reads from
QuerySet iteration in 70679243d1786e03557c28929f9762a119e3ac14.

Thanks Simeon Visser for the patch.



-- 
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/51a4eb9180fe8_3f11d43dd4648d2%40hookshot-fe3-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20242: Django queryset 'in' operator fails on first call

2013-05-28 Thread Django

#20242: Django queryset 'in' operator fails on first call
-+-
 Reporter:  anonymous|Owner:  svisser
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"a2967d5204729771e3716c431ea98f8ee8562d3e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a2967d5204729771e3716c431ea98f8ee8562d3e"
 Fixed #20242 - Added a regression test for prefetch_related.

 Issue was fixed by removal of chunked reads from
 QuerySet iteration in 70679243d1786e03557c28929f9762a119e3ac14.

 Thanks Simeon Visser for the patch.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.8c23d4cc2404c08a9b802715ae2a4b28%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20242: Django queryset 'in' operator fails on first call

2013-05-28 Thread Django

#20242: Django queryset 'in' operator fails on first call
-+-
 Reporter:  anonymous|Owner:  svisser
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by timo):

 It looks like this has been fixed with the removal of chunked reads from
 QuerySet iteration (the `__contains__` method no longer exists)
 [70679243d1786e03557c28929f9762a119e3ac14]. I'll commit the regression
 test 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 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.6b8c9f745d36165dea4ae764ea06ab6a%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20500: Flatpages catchall URLconf example that works with APPEND_SLASH

2013-05-28 Thread Django

#20500: Flatpages catchall URLconf example that works with APPEND_SLASH
--+
Reporter: josh.23.french@… |Owner: EvilDMP
Type: Cleanup/optimization | Status: assigned
Component: Documentation | Version: master
Severity: Normal| Resolution:
Keywords: flatpages | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 |UI/UX: 0
--+
Changes (by EvilDMP):

* owner: ByteMonk => EvilDMP

Comment:

I have marked this ticket as suitable for a first-time committer attending
a [https://dont-be-afraid-to-commit.readthedocs.org/ Don't be afraid to
commit workshop].

The next planned session will be hosted by
[http://www.cardiffdevworkshop.com Cardiff Dev Workshop] on Saturday 8th
June.

--
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/082.7563527560ea3dc351331b447da3a02b%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20517: Jython support is not as complete as indicated

2013-05-28 Thread Django

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

Comment:

I have marked this ticket as suitable for a first-time committer attending
a [https://dont-be-afraid-to-commit.readthedocs.org/ Don't be afraid to
commit workshop].

The next planned session will be hosted by
[http://www.cardiffdevworkshop.com Cardiff Dev Workshop] on Saturday 8th
June.

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

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

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

2013-05-28 Thread Django

#7028: Better raw_id_fields feedback in newform-admins branch
-+-
 Reporter:  Marcob   |Owner:  nobody
|   Status:  new
 Type:  New feature  |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  raw-id-fields nfa-   |  Needs documentation:  0
  someday design_ux  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  1
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by Stanislas):

 Fixed `Clear' button malfunction in admin raw_id fields.

 Github branch : https://github.com/Starou/django/tree/ticket_7028_1_4

-- 
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/086.c3241373f045854e7326cad1a6e28653%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 227d7f: [1.4.x] Fixed #20523 - Incorrect form field for Fi...

2013-05-28 Thread GitHub

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 227d7f63e4c1797acc3552fdfe994181636fd033
  
https://github.com/django/django/commit/227d7f63e4c1797acc3552fdfe994181636fd033
  Author: Tim Graham 
  Date:   2013-05-28 (Tue, 28 May 2013)

  Changed paths:
M docs/topics/forms/modelforms.txt

  Log Message:
  ---
  [1.4.x] Fixed #20523 - Incorrect form field for FilePathField.

Thanks sane4ka.sh@ for the report.

Backport of 1fdc3d256d 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/51a4d4d63a0b2_6dd89a9de038480%40hookshot-fe6-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20523: Wrong form filed for model FilePathField in Field types table (Creating forms from models)

2013-05-28 Thread Django

#20523: Wrong form filed for model FilePathField in Field types table (Creating
forms from models)
--+
 Reporter:  sane4ka.sh@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.5
 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 Tim Graham ):

 In [changeset:"227d7f63e4c1797acc3552fdfe994181636fd033"]:
 {{{
 #!CommitTicketReference repository=""
 revision="227d7f63e4c1797acc3552fdfe994181636fd033"
 [1.4.x] Fixed #20523 - Incorrect form field for FilePathField.

 Thanks sane4ka.sh@ for the report.

 Backport of 1fdc3d256d 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/078.d4fee7e117d934f2127df1bdf06aa0f5%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 17d604: [1.5.X] Fixed #20523 - Incorrect form field for Fi...

2013-05-28 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 17d60438e9c5dff35e8abe311b1ea1ed06f8f98a
  
https://github.com/django/django/commit/17d60438e9c5dff35e8abe311b1ea1ed06f8f98a
  Author: Tim Graham 
  Date:   2013-05-28 (Tue, 28 May 2013)

  Changed paths:
M docs/topics/forms/modelforms.txt

  Log Message:
  ---
  [1.5.X] Fixed #20523 - Incorrect form field for FilePathField.

Thanks sane4ka.sh@ for the report.

Backport of 1fdc3d256d 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/51a4d47c4d26a_5c7e114fdd8855d2%40hookshot-fe2-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20523: Wrong form filed for model FilePathField in Field types table (Creating forms from models)

2013-05-28 Thread Django

#20523: Wrong form filed for model FilePathField in Field types table (Creating
forms from models)
--+
 Reporter:  sane4ka.sh@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.5
 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 Tim Graham ):

 In [changeset:"17d60438e9c5dff35e8abe311b1ea1ed06f8f98a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="17d60438e9c5dff35e8abe311b1ea1ed06f8f98a"
 [1.5.X] Fixed #20523 - Incorrect form field for FilePathField.

 Thanks sane4ka.sh@ for the report.

 Backport of 1fdc3d256d 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/078.c0599c42323c65aa148ef6bc3742f11c%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20523: Wrong form filed for model FilePathField in Field types table (Creating forms from models)

2013-05-28 Thread Django

#20523: Wrong form filed for model FilePathField in Field types table (Creating
forms from models)
--+
 Reporter:  sane4ka.sh@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.5
 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 Tim Graham ):

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


Comment:

 In [changeset:"1fdc3d256d5d515bd0b4646ad57f231a2359e0cd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1fdc3d256d5d515bd0b4646ad57f231a2359e0cd"
 Fixed #20523 - Incorrect form field for FilePathField.

 Thanks sane4ka.sh@ for the report.
 }}}

-- 
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.8ac54341ef0c46449a11eaad26d58679%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 1fdc3d: Fixed #20523 - Incorrect form field for FilePathFi...

2013-05-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1fdc3d256d5d515bd0b4646ad57f231a2359e0cd
  
https://github.com/django/django/commit/1fdc3d256d5d515bd0b4646ad57f231a2359e0cd
  Author: Tim Graham 
  Date:   2013-05-28 (Tue, 28 May 2013)

  Changed paths:
M docs/topics/forms/modelforms.txt

  Log Message:
  ---
  Fixed #20523 - Incorrect form field for FilePathField.

Thanks sane4ka.sh@ for the report.



-- 
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/51a4d45d96e4d_2de1801de487654%40hookshot-fe3-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16357: Navigation buttons in Docs footer would be helpful

2013-05-28 Thread Django

#16357: Navigation buttons in Docs footer would be helpful
-+-
 Reporter:  ncoghlan@…   |Owner:
 Type:   |  giuliettamasina
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.3
 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:  1
-+-

Comment (by timo):

 I like it and have tweaked it slightly, see attached image.  (Modified
 background color & removed "Previous" in favor of guillemets, could also
 possibly removed "Next" although it seems less awkward since it appears to
 the right of the next chapter name). Will try to get at least one more
 opinion and then commit this.

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

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

Re: [Django] #20520: Bug when using nginx+apache not listening on 80 port.

2013-05-28 Thread Django

#20520: Bug when using nginx+apache not listening on 80 port.
---+--
 Reporter:  himikhimik@…   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  nginx apache   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by anonymous):

 * needs_better_patch:   => 0
 * version:  1.5 => 1.4
 * 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/078.369c619e480cf7113ed35a616a885ed2%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20523: Wrong form filed for model FilePathField in Field types table (Creating forms from models)

2013-05-28 Thread Django

#20523: Wrong form filed for model FilePathField in Field types table (Creating
forms from models)
--+
 Reporter:  sane4ka.sh@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by bmispelon):

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


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

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

[django/django] d321d1: Fixed #20228 - Documented unique_for_date and excl...

2013-05-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d321d1acf0fdf00247e78b9686be84c18b35b9d8
  
https://github.com/django/django/commit/d321d1acf0fdf00247e78b9686be84c18b35b9d8
  Author: Tim Graham 
  Date:   2013-05-28 (Tue, 28 May 2013)

  Changed paths:
M docs/ref/models/fields.txt
M tests/model_forms/models.py
M tests/model_forms/tests.py

  Log Message:
  ---
  Fixed #20228 - Documented unique_for_date and exclude behavior.

Thanks Deepak Thukral for the patch.



-- 
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/51a4b96b4aa35_4c34bb9dd8820a8%40hookshot-fe5-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20228: Admin interface doesn't prevent duplicates with unique_for_date

2013-05-28 Thread Django

#20228: Admin interface doesn't prevent duplicates with unique_for_date
---+
 Reporter:  monuszko   |Owner:  iapain
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 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
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"d321d1acf0fdf00247e78b9686be84c18b35b9d8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d321d1acf0fdf00247e78b9686be84c18b35b9d8"
 Fixed #20228 - Documented unique_for_date and exclude behavior.

 Thanks Deepak Thukral for the patch.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.3b4ec5065f03d21110a1b5f1ecb2e019%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20521: {% local_url %} to extend {% url %} with instrospection of the rendering app

2013-05-28 Thread Django

#20521: {% local_url %} to extend {% url %} with instrospection of the rendering
app
-+--
 Reporter:  littlepig|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  tag, url | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by littlepig):

 * cc: littlepig (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.75dd3de6947cfbc4aec4739f83a2200e%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20517: Jython support is not as complete as indicated

2013-05-28 Thread Django

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

Comment:

This could be done as a wiki page, but we couldn't reasonably maintain a
correct list of compatible/incompatible apps within Django docs itself,
because out-of-date/incorrect information is just as unhelpful as no
information at all. I'm going to accept the idea of having a warning and a
link to such a wiki page within the docs though.

Care will still need to be taken with the wiki page - like putting
sufficient dates and version numbers on the information.

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

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

[Django] #20523: Wrong form filed for model FilePathField in Field types table (Creating forms from models)

2013-05-28 Thread Django

#20523: Wrong form filed for model FilePathField in Field types table (Creating
forms from models)
--+
 Reporter:  sane4ka.sh@…  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+
 According to logic and my tests with ModelForm, default form field for
 FilePathField model field should be FilePathField, not CharField as
 mentioned in the table.

-- 
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.a0c33d5dd64ad176df65cc76551102fb%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14087: django.core.management.get_commands only sees commands in the last package of a namespace package

2013-05-28 Thread Django

#14087: django.core.management.get_commands only sees commands in the last 
package
of a namespace package
--+
 Reporter:  KyleMac   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  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 alexkoshelev):

 * cc: daevaorn@… (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/065.cc131b9f3215507e6e3d0a0277e2d310%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20522: Admin formset validation cannot take submitted model instance into account when form not valid.

2013-05-28 Thread Django

#20522: Admin formset validation cannot take submitted model instance into
account
when form not valid.
---+--
Reporter: meshy | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized |Version: 1.5
Severity: Normal | Keywords: admin formset validation
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
---+--
In the admin, if the validation on an inline formset depends upon the data
from the main form it cannot be correctly validated when the main form is
not valid. This is because the instance from the incomplete form is not
passed into the formset unless it is completely valid. Instead, on add

(https://github.com/django/django/blob/1.5.1/django/contrib/admin/options.py#L988-L994),
we get a completely blank new instance, or on change

(https://github.com/django/django/blob/1.5.1/django/contrib/admin/options.py#L1085-L1091),
we are passed the original instance.

I understand that the current way of doing things may stop invalid data
being sent to the formsets but I believe, as this is the data that has
been submitted, and the majority of it will likely be correct, that this
would be better than the nothing we currently get.

I propose that lines 994 and 1091 both change to `new_object =
form.instance`. This would mean that in a fair number of cases the errors
on the main form would not need to be fixed before the errors on the
inline form become visible.

I hope that my concerns/intention are clear, but if not, please ask and I
will produce a working example and patch for examination.

--
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/048.9dc7a7d7dc8e70a5ea52f81d872c2f36%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 2e0267: [1.5.X] Fixed #20513 - Expanded docs on QuerySet c...

2013-05-28 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 2e026739dcab545703160456503a1183c6c0702d
  
https://github.com/django/django/commit/2e026739dcab545703160456503a1183c6c0702d
  Author: Tim Graham 
  Date:   2013-05-28 (Tue, 28 May 2013)

  Changed paths:
M docs/topics/db/queries.txt

  Log Message:
  ---
  [1.5.X] Fixed #20513 - Expanded docs on QuerySet caching.

Thanks seddonym.

Backport of 8365d76da0 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/51a4a665ec2a4_87e1475ddc14283e%40hookshot-fe3-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20513: Queryset caching behaviour needs more documentation

2013-05-28 Thread Django

#20513: Queryset caching behaviour needs more documentation
-+-
 Reporter:  seddonym |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  queryset |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"2e026739dcab545703160456503a1183c6c0702d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2e026739dcab545703160456503a1183c6c0702d"
 [1.5.X] Fixed #20513 - Expanded docs on QuerySet caching.

 Thanks seddonym.

 Backport of 8365d76da0 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.33c2cdd1566a920728d12a67bf2e8419%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20513: Queryset caching behaviour needs more documentation

2013-05-28 Thread Django

#20513: Queryset caching behaviour needs more documentation
-+-
 Reporter:  seddonym |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  queryset |  checkin
Has patch:  1|  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:"8365d76da01af1d4391cba32d62178791d074b06"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8365d76da01af1d4391cba32d62178791d074b06"
 Fixed #20513 - Expanded docs on QuerySet caching.

 Thanks seddonym.
 }}}

-- 
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.c561c6ba29148d737e4c0672dc364fe4%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20513: Queryset caching behaviour needs more documentation

2013-05-28 Thread Django

#20513: Queryset caching behaviour needs more documentation
-+-
 Reporter:  seddonym |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  queryset |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timo):

 * stage:  Accepted => Ready for checkin


Comment:

 This looks good to me as well. I've wrapped the lines and made some minor
 edits.

-- 
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.e78afde4886f650f0261aa7e80d21eeb%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 8365d7: Fixed #20513 - Expanded docs on QuerySet caching.

2013-05-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8365d76da01af1d4391cba32d62178791d074b06
  
https://github.com/django/django/commit/8365d76da01af1d4391cba32d62178791d074b06
  Author: Tim Graham 
  Date:   2013-05-28 (Tue, 28 May 2013)

  Changed paths:
M docs/topics/db/queries.txt

  Log Message:
  ---
  Fixed #20513 - Expanded docs on QuerySet caching.

Thanks seddonym.



-- 
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/51a4a6478bbc6_4c37753dd444119%40hookshot-fe5-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20521: {% local_url %} to extend {% url %} with instrospection of the rendering app

2013-05-28 Thread Django

#20521: {% local_url %} to extend {% url %} with instrospection of the rendering
app
-+--
Reporter: littlepig| Owner: nobody
Type: New feature | Status: new
Component: Template system |Version: 1.5
Severity: Normal | Keywords: tag, url
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0| UI/UX: 0
-+--
==Summary==

New feature: use app's directory tree to resolve urls on templates.

==Motivation==
Currently the {% url %} tag requires the full path of the view or a url
name to reverse the correct url of the view. This is limited due to either
url name collisions or app's name collision.
To avoid url collisions, django implements a URL namespace, which has to
be applied on each app coded to be reusable. One of the biggest problems
of the current implementation is the difficultly in using the URL
namespace for practical proposes: it is mainly used and (limited to) the
case where the same app is being deployed on the same site more than one
time.

==Proposal==

I here propose a new templatetag, {% local_url %} and a shortcut to a
render, "local_render", that solves the url resolving issue, and does not
collide with the current django state.

It works as follows: the local_render passes the argument 'current_app' to
the django's render (shortcuts.render) with the full path of the app
(package.package.(...)). The {% local_url %} then resolves the url
according to the current_app. It is basically a copy of the tag {% url %},
where the "render" of the node is slightly different:

# if the context does not have current_app (case where current_app is not
used), render normally
# if the context has current_app (e.g. here 'main.main1.main2'):
try to render with view_name as main.main1.main2.view_name
if NoReverseMatch, try to render with
self.view_name=main.main1.main2.view_name
if NoReverseMatch, try to render with
self.view_name=main.main1.view_name
if NoReverseMatch, try to render with self.view_name=main.view_name
if NoReverseMatch, try to render with self.view_name=view_name
if NoReverseMatch, raise NoReverseMatch

where view_name is the argument passed in __init__ to self.view_name.

I.e. this basically implements a resolver that works over the app's path.

==Discussion==

* Neither the render nor the tag collide with current implementation (as
far as I understood, the current_app is never passed as argument to the
url resolver in the {% url %} tag).

* This deprecate the need of URL namespaces for working with templates:
the strategy to resolve URL in templates is with this approach according
to the directory structure, and apps must have different names inside a
directory.

* This agrees with django's spirit of using app's as reusable and modules
that complement other app's.

* This allows for views "overload": Consider a child app that is installed
on top of a parent which has a view (e.g. views.rules) and a template with
{% local_url views.rules %}. The child decides to extend the template (for
instance for using the same footers or headers. The child can define a
view with the same name (rules) which overloads the parent's view: if the
render is called from the child, it uses the view, if it is called from
the parent, it is the parent's view. This is the same behavior one would
obtain for python classes: the child can always overload a parent's
method.

* This idea can be extended to URL resolvers in general, but that requires
a major design decision that I don't want to enter for now.

I already have a code which reproduces the behavior I'm suggesting, which
I use for a project of mine. I will wait for approach/criticisms to see if
it deserves be written in django's standards.

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

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

Re: [Django] #20500: Flatpages catchall URLconf example that works with APPEND_SLASH

2013-05-28 Thread Django

#20500: Flatpages catchall URLconf example that works with APPEND_SLASH
--+
 Reporter:  josh.23.french@…  |Owner:  ByteMonk
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  flatpages | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by claudep):

 * version:  1.4 => master
 * stage:  Unreviewed => Accepted


Comment:

 Replying to [comment:5 josh.23.french@…]:
 > If we skip right to the redirect, we'd end up redirecting pages to 404s,
 which seems like something we want to keep.
 
([https://github.com/django/django/commit/196ac8f8b31302d026af6d79f764c8f146a8c78e
 196ac8f8b3])
 > (If it's not, ignore everything that follows.)

 Good point, you are right.

 Maybe you were also right from the start, telling people to add the final
 slash in the catch-all pattern when APPEND_SLASH is True might be the
 better solution.

-- 
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/082.1cc476c6ad48918d8aab8fd668a00c39%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20519: Request DJango to support IP2Location Lite with Zip Code

2013-05-28 Thread Django

#20519: Request DJango to support IP2Location Lite with Zip Code
---+--
 Reporter:  Clarence   |Owner:  nobody
 Type:  New feature|   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 bmispelon):

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


Comment:

 Hi,

 This ticket tracker is for reporting bugs against django.

 For support questions, you should try the django-users mailing list, or
 the #django IRC channel on Freenode.

 See https://docs.djangoproject.com/en/1.5/faq/help/

 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/066.eb958c5756bc172fcda11f4ae54bdc8d%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20520: Bug when using nginx+apache not listening on 80 port.

2013-05-28 Thread Django

#20520: Bug when using nginx+apache not listening on 80 port.
---+--
 Reporter:  himikhimik@…   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  HTTP handling  |Version:  1.5
 Severity:  Normal |   Keywords:  nginx apache
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 I made nginx and apache servers working together.
 Nginx is listening on 81 port, serving all media files and passing all
 other requests to apache.
 Apache is listening on 88 port and serving all other requests by means of
 wsgi.py.

 When one makes GET request all work ok. But when one makes POST with
 redirect to another
 page the redirect leads to 80 port instead of 81 port (when just saving
 any object on django admin site).

 The problem is incorrect forming POST headers.
 django/http/utils.py -> fix_location_header function.
 If do comment the string
 {{{
 #!div style="font-size: 80%"
   {{{#!python
 response["Location"] =
 request.build_absolute_uri(response["Location"])
   }}}
 }}}
 the POST requests work ok.

 There are my config files.
 nginx.conf:
 {{{
 #!div style="font-size: 80%"
   {{{#!python
 server {

 listen 81;

 access_log /var/log/nginx/vertex.access.log;
 error_log /var/log/nginx/vertex.error.log;

 location /static/ {
 alias /srv/vertex/media/admin_static/;
 expires 30d;
 }

 location /site-media/ {
 alias /srv/vertex/media/;
 expires 30d;
 }

 location / {
 proxy_pass http://127.0.0.1:88/;
 proxy_set_header Host $host;
 proxy_set_header X-Real-IP $remote_addr;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 }

 }
   }}}
 }}}

 apache2.conf:
 {{{
 #!div style="font-size: 80%"
   {{{#!python
 Listen 88

 

 WSGIDaemonProcess localhost python-
 path=/srv/vertex/src:/srv/vertex/env/lib/python2.7/site-packages
 WSGIProcessGroup localhost

 WSGIScriptAlias / /srv/vertex/src/wsgi.py

 
 
 Order deny,allow
 Allow from all
 
 

 
   }}}
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.3ddca696648088480e017c61200eb095%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20513: Queryset caching behaviour needs more documentation

2013-05-28 Thread Django

#20513: Queryset caching behaviour needs more documentation
--+
 Reporter:  seddonym  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  queryset  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by bmispelon):

 * cc: bmispelon@… (added)
 * stage:  Unreviewed => Accepted


Comment:

 This looks useful and the proposed patch looks pretty good (`git apply`
 complains about trailing whitespace on line 25 though).

 I'm marking this as accepted.

 I would mark it as ready for checkin too, but I feel this should get
 reviewed by a native speaker (which I'm not).

 Thanks for your contribution.

-- 
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.007e62cbea19a2bb900f1ce31f4eb0c5%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20519: Request DJango to support IP2Location Lite with Zip Code

2013-05-28 Thread Django

#20519: Request DJango to support IP2Location Lite with Zip Code
---+
 Reporter:  Clarence   |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Hi, I am new here.

 Just being assigned with a new project that requires me to filter and
 redirect users by Zip Code from an IP Address. I saw sample data from
 IP2Location Lite. How can I do this for 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/051.ba45d2c90c9e632eabe28ef36601ee59%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17974: .distint('FIELDNAME') FAILS for MySQL

2013-05-28 Thread Django

#17974: .distint('FIELDNAME') FAILS for MySQL
-+-
 Reporter:  mschettler@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  distinct on  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 If you can make .distinct('somefield') work on MySQL it would be very
 welcome addition. I believe it is somewhat hard to write that patch
 correctly (particularly, how to make .order_by() + .distinct() work
 correctly). MySQL doesn't have DISTINCT ON (fields), so you need something
 like this: http://stackoverflow.com/questions/5804529/distinct-on-
 multiple-columns.

 Of course, if you want just distinct somefield values, instead of the full
 DISTINCT ON semantics, then qs.values_list('somefield').distinct() should
 work.

 Why is there DISTINCT ON implementation that works only on PostgreSQL? The
 choice was to not support this at all, or support this only on PostgreSQL.
 The distinct(*fields) is very useful in certain cases, so I think having
 it on PostgreSQL only is better than not having it at all.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.77f08408d333e244d4477b8c2156cb70%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17974: .distint('FIELDNAME') FAILS for MySQL

2013-05-28 Thread Django

#17974: .distint('FIELDNAME') FAILS for MySQL
-+-
 Reporter:  mschettler@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  distinct on  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Paul von Hoesslin):

 "If you are getting exactly the error noted in the original description,
 then the problem is you are trying to use a feature supported by only
 PostgreSQL on some other database. "

  Mysql supports distinct. I practically use it daily. So your statement is
 invalid. This error != true

-- 
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.68b56ba93c00b2eca230c63467c32ce2%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17974: .distint('FIELDNAME') FAILS for MySQL

2013-05-28 Thread Django

Comment (by Paul von Hoesslin):

ok but then what is the point of an ORM? The purpose of having an ORM is
to create database independence (and don't kid yourself, I use distinct in
mysql all the time). Please cater for this functionality or don't bother
giving us the choice. This is as useless as
Model.objects.all().delete()... Why not just truncate the table, or give
some sort of functionality to do so, such as Model.objects.truncate().
Django's awesome but without these "little" functionalities you really
shoot yourself in the foot.https://code.djangoproject.com/ticket/17974#no3

--
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.2c72d7579d900b50c245c4a71ccd6f17%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20518: Add obvious note to the development docs about being work in progress

2013-05-28 Thread Django

#20518: Add obvious note to the development docs about being work in progress
+
   Reporter:  jezdez|  Owner:  jezdez
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  1.5
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 As discussed in IRC this should be a fixed position box in the header of
 the page stating that it's the in-development documentation, not the
 stable documentation, maybe with stripped background so it has visual
 importance (yuck, I know) or something similar. Alternatively this could
 be put into the sidebar.

-- 
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/049.459876af28bc61e1acabce9edd01a6f1%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #5849: Strip indentation and leading/trailing spaces/linebreaks from contents of blocktrans block.

2013-05-28 Thread Django

#5849: Strip indentation and leading/trailing spaces/linebreaks from contents of
blocktrans block.
-+-
 Reporter:  Dmitri Fedortchenko  |Owner:  mpessas
  |   Status:  assigned
 Type:  New feature  |  Version:  master
Component:   |   Resolution:
  Internationalization   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  blocktrans strip |  Patch needs improvement:  0
  indentation|UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by mpessas):

 Pull request updated: https://github.com/django/django/pull/803

-- 
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/097.55e8892f5262975931deb92977eaf23d%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20514: django.contrib.gis.tests.test_measure.{AreaTest, DistanceTest} fail in py3

2013-05-28 Thread Django

#20514: django.contrib.gis.tests.test_measure.{AreaTest,DistanceTest} fail in 
py3
-+--
 Reporter:  idella4  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  1.5
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  tests| Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Ian Delaney ):

 right.  well my python installs are recent and current, sp I'd go for
 something re-instating it.  I'll see if some other python devs have some
 idea. thx

-- 
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.2009f51d125225e86751950bdd5b7fe1%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20500: Flatpages catchall URLconf example that works with APPEND_SLASH

2013-05-28 Thread Django

#20500: Flatpages catchall URLconf example that works with APPEND_SLASH
-+-
 Reporter:  josh.23.french@… |Owner:  ByteMonk
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  flatpages|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by josh.23.french):

 The whole try/except around `found_url = urlresolvers.resolve(url)` is
 excessive. Apparently, `Resolver404` is a subclass of `Http404`. (I
 couldn't edit it-I assume because I didn't have an account, so I got 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/082.87e5f2575727052f1ae7928253e39bca%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20500: Flatpages catchall URLconf example that works with APPEND_SLASH

2013-05-28 Thread Django

#20500: Flatpages catchall URLconf example that works with APPEND_SLASH
-+-
 Reporter:  josh.23.french@… |Owner:  ByteMonk
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  flatpages|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by josh.23.french@…):

 If we skip right to the redirect, we'd end up redirecting pages to 404s,
 which seems like something we want to keep.
 
([https://github.com/django/django/commit/196ac8f8b31302d026af6d79f764c8f146a8c78e
 196ac8f8b3])
 (If it's not, ignore everything that follows.)
 [[BR]]
 [[BR]]
 ''Keep in mind I'm completely new to Django's codebase(4 months), so the
 following code might be inappropriate.''

 This logic might be too heavy, but if we want to keep the no-redirect in
 cases where it'll end up a 404, it's something to think about:

 {{{
 #!python
 from django.core import urlresolvers

 if not url.endswith('/') and settings.APPEND_SLASH:
 url += '/'

 # Check if new url will resolve, and get the view info if it does.
 try:
 found_url = urlresolvers.resolve(url)
 except urlresolvers.Resolver404:
 raise

 # Check if the new url is a flatpage. If it is, skip the second half
 of the OR and redirect.
 if (FlatPage.objects.filter(url__exact=url,
 sites__id__exact=site_id).exists()

# Check if the new url_name would bring us back here. (If it won't,
 redirect.
# If it will, both sides of the OR are False and we raise the 404.)
or (found_url.url_name !=
 "django.contrib.flatpages.views.flatpage")):

 # Stole this from CommonMiddleware. We want the same warning...
 and CommonMiddleware's warning will never get raise'd.
 if settings.DEBUG and request.method == 'POST':
 raise RuntimeError((""
 "You called this URL via POST, but the URL doesn't end "
 "in a slash and you have APPEND_SLASH set. Django can't "
 "redirect to the slash URL while maintaining POST data. "
 "Change your form to point to %s (note the trailing "
 "slash), or set APPEND_SLASH=False in your Django "
 "settings.") % url)
 return HttpResponsePermanentRedirect(url)
 else:
 # No flatpage exists
 raise
 else:
 raise
 }}}

 This is basically the APPEND_SLASH logic with a check for FlatPages
 specifically.

-- 
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/082.4556c2fe9947d1e118f4edb80163e0ce%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20514: django.contrib.gis.tests.test_measure.{AreaTest, DistanceTest} fail in py3

2013-05-28 Thread Django

#20514: django.contrib.gis.tests.test_measure.{AreaTest,DistanceTest} fail in
py3
-+--
Reporter: idella4 |Owner: nobody
Type: Bug | Status: closed
Component: GIS | Version: 1.5
Severity: Normal | Resolution: invalid
Keywords: tests| Triage Stage: Unreviewed
Has patch: 1| Needs documentation: 0
Needs tests: 0| Patch needs improvement: 0
Easy pickings: 0|UI/UX: 0
-+--
Changes (by claudep):

* resolution: needsinfo => invalid

Comment:

I think I found the bug: http://bugs.python.org/issue10353

Now the question is for you why you are still affected by this bug fixed
some time ago. Either some older Python installation is left somewhere on
your system, or a very recent Python commit reinstated this bug. In any
case, this is not Django's fault, as `self.assertAlmostEqual(a.sq_ft,
1076.391, places=3)` or `self.assertAlmostEqual(a.sq_ft, 1076.391, 3)`
are strictly equivalent.

--
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.717239feecc80b544b79ee9dee622bd0%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20514: django.contrib.gis.tests.test_measure.{AreaTest, DistanceTest} fail in py3

2013-05-28 Thread Django

#20514: django.contrib.gis.tests.test_measure.{AreaTest,DistanceTest} fail in 
py3
-+--
 Reporter:  idella4  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  1.5
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  tests| Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Ian Delaney ):

 I'm totally miffed by why yours passes under py3 and mine doesn't.  There
 must be something 'special on my side' logically. Any guesses? I got
 nothing.
 The adding of places= simply makes the code consistent between tests. I
 won't re-open this since that really needs pinning that special quality,
 however the patch won't break anything and will make for consistency. I've
 added the patch to the 1.5 versions in portage.

-- 
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.e46c7255f54d0d050625229effdeefab%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

67 matches

Mail list logo