date:20130722

Re: [Django] #20775: Incorrect description of startswith, istartswith, contains, icontains, endswith and iendswith

2013-07-22 Thread Django

#20775: Incorrect description of startswith, istartswith, contains, icontains,
endswith and iendswith
+--
Reporter: a_nekhaychik@… |Owner: nobody
Type: Bug | Status: closed
Component: Documentation | 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 erikr):

* cc: eromijn@… (added)
* status: new => closed
* resolution: => invalid

Comment:

But the documentation speaks of an SQL //equivalent//, not of the SQL that
the ORM query would produce.

The equivalent is provided as "this is how you would do a query like this
in SQL without the Django ORM", probably so that it's easier for people
familiar with SQL to understand the ORM syntax. In other words, I see no
error in the documentation here.

--
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/084.91e1d815fe482e590a8d9b8ec47a5124%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20791: "Model %(model)s with pk %(pk)r does not exist."

2013-07-22 Thread Django

#20791: "Model %(model)s with pk %(pk)r does not exist."
-+-
 Reporter:  lsaffre  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by erikr):

 * cc: eromijn@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * easy:  0 => 1
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Agreed, the current message can be confusing.

-- 
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.39a1f12d240c231a67d5b4279d8a094f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20791: "Model %(model)s with pk %(pk)r does not exist."

2013-07-22 Thread Django

#20791: "Model %(model)s with pk %(pk)r does not exist."
--+
 Reporter:  lsaffre   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I agree that this is nit-picky, but in `db/models/fields/related.py` (line
 979 in version 1.5.1), Django issues the following message:

   "Model %(model)s with pk %(pk)r does not exist."

 This formulation is wrong. Not the model but a model *instance* is
 missing.
 So I suggest to change this message to:

   "%(model)s instance with pk %(pk)r does not exist."

 or just:

   "%(model)s with pk %(pk)r does not exist."

-- 
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.57d5adf0a0df480d5f12aac2903e14db%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20788: exclude makes bad query following two FKs and a M2M

2013-07-22 Thread Django

#20788: exclude makes bad query following two FKs and a M2M
--+
 Reporter:  david@…   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Hi,

 With models like this:

 {{{
 from django.db import models


 class Publication(models.Model):
 pass


 class Article(models.Model):
 publications = models.ManyToManyField(Publication)


 class Section(models.Model):
 article = models.ForeignKey(Article)


 class Sentence(models.Model):
 section = models.ForeignKey(Section)
 }}}

 The query to get all sentences that aren't in publication 1 looks like:

 {{{
 >>> models.Sentence.objects.exclude(section__article__publications__id=1)
 }}}

 However, this generates the following SQL:

 {{{
 SELECT "marbury_sentence"."id", "marbury_sentence"."section_id"

 FROM "marbury_sentence"
 INNER JOIN "marbury_section" ON ("marbury_sentence"."section_id" =
 "marbury_section"."id")
 INNER JOIN "marbury_article" ON ("marbury_section"."article_id" =
 "marbury_article"."id")

 WHERE NOT (

 (
 "marbury_section"."article_id" IN (
 SELECT U1."id"
 FROM "marbury_section" U1
 INNER JOIN "marbury_article" U2 ON (U1."article_id" =
 U2."id")
 INNER JOIN "marbury_article_publications" U3 ON (U2."id" =
 U3."article_id")
 WHERE (U3."publication_id" = 1  AND U1."id" IS NOT NULL)
 )
 AND "marbury_article"."id" IS NOT NULL
 )
 )
 }}}

 The WHERE clause compares "marbury_section"."article_id" to *section* IDs
 returned by the subquery.  This means that the exclusion won't be
 enforced, or worse, will be enforced incorrectly, if article IDs and
 section IDs overlap.

 Here is a simple test:

 {{{
 # Make two articles
 models.Article.objects.create()
 article = models.Article.objects.create()

 # Make a publication for the second article
 publication = article.publications.create()

 # Make a section for the article
 section = models.Section.objects.create(article=article)

 # Make a sentence for the section
 models.Sentence.objects.create(section=section)

 # Get all sentences that aren't in the publication
 sentences_not_in_pub = models.Sentence.objects.exclude(
 section__article__publications=publication)

 # There should be none
 self.assertEquals(len(sentences_not_in_pub), 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/061.0047b331220a1b3b81eb3690a65cc923%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20789: Inconsistent imports for Django Testcase

2013-07-22 Thread Django

#20789: Inconsistent imports  for Django Testcase
-+--
 Reporter:  graham.klyne@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  Testcase import  | 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
 * needs_docs:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 The two imports are different.

 django.utils.unittest.TestCase is Django's packaged copy of unittest2.
 We've included this package because historically, Python's packaging tools
 haven't been good with dependencies, and we wanted to ensure every user
 had a good out-of-the-box experience. When we drop Python 2.6 as a
 dependency, we'll be able to deprecate this packaging choice, as unittest2
 is available by default on Python 2.7+.

 django.test.TestCase is a Django's TestCase. It's a subclass of
 unittest.TestCase, and adds additional functionality specific to testing
 Django.

 So - neither import is wrong, or inconsistent - they're pointing at
 different objects.

-- 
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/083.50d7b07ec2c52040811f4ac16377e6ba%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

2013-07-22 Thread Django

#3591: add support for custom app_label and verbose_name
--+
 Reporter:  jkocherhans   |Owner:  adrian
 Type:  New feature   |   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:  1
--+
Changes (by unpig):

 * cc: unpig (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/069.6aa40deb16e28fec02c052300dddeaff%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20790: Wrong linking in tutorial part 4

2013-07-22 Thread Django

#20790: Wrong linking in tutorial part 4
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 This is in Django tutorial part 4
 ([https://docs.djangoproject.com/en/1.5/intro/tutorial04/])
 When we create a polls/results.html template, "Vote again?" link doesn't
 lead to voting.

 We should replace
 Vote again?
 with
 Vote again?

 That way it will ask us to vote again.

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

[Django] #20789: Inconsistent imports for Django Testcase

2013-07-22 Thread Django

#20789: Inconsistent imports  for Django Testcase
+-
 Reporter:  graham.klyne@…  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Documentation   |Version:  1.5
 Severity:  Normal  |   Keywords:  Testcase import
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+-
 In the documentation page at:
 https://docs.djangoproject.com/en/1.5/topics/testing/overview/

 The 'unittest2' box at the top of the page has:

 from django.utils import unittest

 But in the first example below this we have:

 from django.test import TestCase

 I note the generated test.py has the latter form of import.

 I assume one of these is wrong, probably the first?

 #g

-- 
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/068.74dc644679fbb16f286f088cbfd22524%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #2495: db.models.TextField cannot be marked unique when using mysql backend

2013-07-22 Thread Django

#2495: db.models.TextField cannot be marked unique when using mysql backend
-+-
 Reporter:  anonymous|Owner:
 Type:  Bug  |  Honza_Kral
Component:  Database layer   |   Status:  new
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  mysql TextField  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by eigenhombre):

 Just got bit by this, so here's my +1...

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

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

Re: [Django] #20787: Django template changes width of html element during append

2013-07-22 Thread Django

#20787: Django template changes width of html element during append
+--
 Reporter:  gregoryronin@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Template system |  Version:  1.5
 Severity:  Release blocker |   Resolution:
 Keywords:  template css width  | 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
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 "background_color" should be "background-color", but it does not matter,
 since it does not fix the problem.

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

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

[Django] #20787: Django template changes width of html element during append

2013-07-22 Thread Django

#20787: Django template changes width of html element during append
-+
 Reporter:  gregoryronin@…   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.5
 Severity:  Release blocker  |   Keywords:  template css width
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 I filed this issue with stackoverflow.com under the same title. This looks
 like a Django problem to me. Here is the description:

 Below you will find the HTML code. The problem is that: if you try to load
 the specified below HTML code into the browser directly, both alerts
 (before placement onto "body" and after) will give you width=498px as
 expected.

 However, if you set it up as Django template and run with Django
 development server, the second alert (after placement onto "body") will
 give you a slightly different number depending on the browser: Firefox
 gives 497.7px, IE gives 498.1px. I have not checked other browsers.

 It is important to note, that it is that combination of css attributes
 ("left", "top", "width", "height", "border-width", "background_color",
 "border-style") that shows the problem. If you remove at least one of
 them, the problem goes away.

 If you happen know what is going on and/or what the viable workaround is,
 I would really appreciate it. Thanks. Here is the code:

 
 
 

  http://code.jquery.com/jquery-1.9.1.js";>

 
 $(function() {
 var my_element = $("")
  .addClass("my_element")
  .attr("id", "my_element1")
  .css("position", "absolute")
  .css("left", "0px")
  .css("top", "0px")
  .css("width", "498px")
  .css("height", "300px")
  .css("border-width", "1px")
  .css("background_color", "#66")
  .css("border-style", "solid");

 alert("width:" + my_element.css("width"));

 $("body").append(my_element);

 alert("width:" + my_element.css("width"));

 });

 

 
 
 
 

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

Re: [Django] #20737: Request to ship feedgenerator as package separately of Django's core

2013-07-22 Thread Django

#20737: Request to ship feedgenerator as package separately of Django's core
--+--
 Reporter:  echevemaster  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Packaging |  Version:  1.5
 Severity:  Normal|   Resolution:  needsinfo
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by echevemaster):

 Actually, isn't a problem of Django or a bug from you, "bundled library"
 in fedora refer it at if a package or lib exist in the system-wide, not
 should exist in a new package, given that,  feedgenerator is part of the
 Django's core, my question refer to ship feedgenerator as a functionality
 separately from Django, question that has been answered; and it gives me
 to understand would not be possible. Anyway thanks a lot

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

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

Re: [Django] #20760: Account enumeration through timing attack in password verification in django.contrib.auth

2013-07-22 Thread Django

#20760: Account enumeration through timing attack in password verification in
django.contrib.auth
-+-
 Reporter:  jpaglier@…   |Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  security | Triage Stage:  Ready for
  authentication timing enumeration  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * owner:  anonymous => aaugustin
 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0
 * stage:  Accepted => Ready for checkin


Comment:

 Thank you Paul for the review.

 I'm going to wait a few days in case Erik has the time to re-run his
 benchmark against the latest patch, and then push it (after a little bit
 of reformatting).

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

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

Re: [Django] #20776: Multi-level Multi-table Inheritance - mismatched PKs / explicit db_columns

2013-07-22 Thread Django

#20776: Multi-level Multi-table Inheritance - mismatched PKs / explicit 
db_columns
-+-
 Reporter:  dowstreet@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  Muti-table   | Triage Stage:
  Inheritance|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

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


Comment:

 I believe the problem is having level2_id in Level2, and level2
 OneToOneField in Level3. OneToOneFields store the related instance in
 field.name (level2) and the raw database value in field.attname
 (level2_id). The level2 field's attname conflicts with level2_id field
 name in Level2.

 I am not 100% sure if this is the case. You could test this by changing
 the name of level2_id to something else in Level2. If the reason is the
 naming conflict this looks like something that could be dealt with in the
 validation GSoC project.

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

Re: [Django] #20760: Account enumeration through timing attack in password verification in django.contrib.auth

2013-07-22 Thread Django

Comment (by PaulM):

To address some things mentioned earlier:

Adding a random delay to the return is absolutely not an acceptable
solution, for both the reason that it introduces unnecessary latency, and
the fact that it does not, in fact, solve the problem in any meaningful
fashion. An attacker can always take more samples.

If you actually want to test for a timing difference, you'll want to
retain all of the processing times for both samples and use the
Kolmogorov-Smirnov test to figure out if they're different. You can't use
Student's t-test because the samples are not normally distributed. There's
more information on this in my presentation from Djangocon 2011.

The latest patch and test look reasonable 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/074.bee622b5b1577abc2b916b77a2e3e375%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20784: RegexValidator should accept a new parameter to perform reversed validation

2013-07-22 Thread Django

#20784: RegexValidator should accept a new parameter to perform reversed 
validation
+
 Reporter:  devfeng |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Core (Other)|  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  RegexValidator  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by devfeng):

 Replying to [comment:1 devfeng]:
 > https://github.com/django/django/pull/1387

 Updated, please review. :)

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

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

Re: [Django] #20752: Error signals are not reliable, especially when dealing with database errors

2013-07-22 Thread Django

Comment (by tal@…):

I was on the fence on send_robust(): I generally dislike mechanisms that
just swallow exceptions, because it makes bugs slip through the cracks. On
the other hand, some signal handlers (db rollback) are actually extremely
likely to raise an exception if something bad happened to the underlying
connection, which is what we were seeing.

You can simulate something like this by closing the underlying
connections. You can simulate it by doing something like:
{{{
from django.db import connection
connection.connection.close()
}}}

At a view or a middleware.

Some alternatives to send_robust:
1) implement something that will aggregate the exceptions and just raise a
"SignalHandlersException" container at the end. No exceptions are lost,
but I question the overall value of it in this scenario.
2) Print out exceptions to stderr, which is what django actually ends up
doing when the error signal handler go rogue.

I'm leaning towards option 2.

--
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.456f20bfa63006810bec2a4e03d7af4f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20752: Error signals are not reliable, especially when dealing with database errors

2013-07-22 Thread Django

Comment (by tal@…):

You can simulate something like this by closing the underlying
connections. You can simulate it by doing something like:
{{{
from django.db import connection
connection.connection.close()
}}}

At a view or a middleware.

I'm leaning towards option 2.

--
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.959fc132d33c3198f9febf2be0e44db3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 8e9865: Fixed small grammatical error in docstring.

2013-07-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8e9865241600a2ee0541b30902b4b0c828d2e60b
  
https://github.com/django/django/commit/8e9865241600a2ee0541b30902b4b0c828d2e60b
  Author: Tyler Garner 
  Date:   2013-07-22 (Mon, 22 Jul 2013)

  Changed paths:
M django/contrib/gis/db/models/query.py

  Log Message:
  ---
  Fixed small grammatical error in docstring.


  Commit: 29a09b3638e625458b5e07ed0956451432421acf
  
https://github.com/django/django/commit/29a09b3638e625458b5e07ed0956451432421acf
  Author: Marc Tamlyn 
  Date:   2013-07-22 (Mon, 22 Jul 2013)

  Changed paths:
M django/contrib/gis/db/models/query.py

  Log Message:
  ---
  Merge pull request #1390 from garnertb/master

Fixed small grammatical error in docstring.


Compare: https://github.com/django/django/compare/27c1a7257652...29a09b3638e6

-- 
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/51ed42f7e7db6_221a1195d4c68390%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20752: Error signals are not reliable, especially when dealing with database errors

2013-07-22 Thread Django

#20752: Error signals are not reliable, especially when dealing with database
errors
-+-
 Reporter:  tal@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  signals errors   | Triage Stage:
  databaseError  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by shai):

 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1
 * easy:  0 => 1


Comment:

 `send_robust()` implies (correctly) that errors are expected. But the
 current patch proposes to just silence them, and that seems wrong to me.

 Also, if you see a real problem, can you provide a test that exemplifies
 it (and can be used to verify that the solution is correct)?

-- 
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.9022c40c301ddd9fc22e25a8ee0d5c40%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20785: [oracle] ORA-01425: escape character must be character string of length 1

2013-07-22 Thread Django

#20785: [oracle] ORA-01425: escape character must be character string of length 
1
-+-
 Reporter:  ludo |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by shai):

 * cc: shai@… (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/062.39907d8831f90a77226378de8006b6cb%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20785: [oracle] ORA-01425: escape character must be character string of length 1

2013-07-22 Thread Django

#20785: [oracle] ORA-01425: escape character must be character string of length 
1
-+-
 Reporter:  ludo |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by shai):

 What Oracle version are you using?

 (obviously, starting connections on Oracle works for most of us --
 further, master is continuously tested against Oracle, and ATM the Oracle
 backend is essentially the same in master and 1.6b1).

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

Re: [Django] #20784: RegexValidator should accept a new parameter to perform reversed validation

2013-07-22 Thread Django

Comment (by bmispelon):

Hi,

I think `reverse` is a confusing name for this feature because it already
has a different meaning for lists (consider the `reversed` builtin or the
`reverse` argument to `sorted`). Maybe something like `invert` would work
better?

I also wonder if a separate validator wouldn't be a better approach since
the two are fundamentally different. What do you think?

Finally, as noted by claudep, your patch will need documentation too: a
new entry in the `ref/validators` page as well as a mention in the release
notes for 1.7.

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/065.9217a7ae3894932ad6368ef99ddaf087%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20786: Importing exceptions: documentation should be more explicit and clearer

2013-07-22 Thread Django

#20786: Importing exceptions: documentation should be more explicit and clearer
---+
 Reporter:  EvilDMP|Owner:  nobody
 Type:  Uncategorized  |   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
 * 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/065.92c0ae0fae9534402b8b83738aef%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20760: Account enumeration through timing attack in password verification in django.contrib.auth

2013-07-22 Thread Django

Comment (by jpaglier):

Patch written using the set_password() solution, including a test. This
solution will still have a timing difference due to the lack of a hash
comparison in the case of a failed lookup, on top of those that have
already been decided to have been acceptable. Test definitely needs a set
of fresh eyes to check it over, it's late enough that I probably made a
mistake.

Erik, if you have time could you check out what the difference looks like
with this new one?

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

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

Re: [Django] #20785: [oracle] ORA-01425: escape character must be character string of length 1

2013-07-22 Thread Django

#20785: [oracle] ORA-01425: escape character must be character string of length 
1
-+-
 Reporter:  ludo |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Marking as a release blocker since the report says it's a regression.

-- 
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.7249a329b96fa6c5affdf68717dd7db4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20786: Importing exceptions: documentation should be more explicit and clearer

2013-07-22 Thread Django

#20786: Importing exceptions: documentation should be more explicit and clearer
---+
Reporter: EvilDMP| Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation |Version: 1.5
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
---+
At https://docs.djangoproject.com/en/dev/ref/exceptions, for some of the
listed exceptions information is provided on how to import it.

For example: "The UnreadablePostError is raised when a user cancels an
upload. It is available from django.http."

For others though (e.g.
https://docs.djangoproject.com/en/dev/ref/exceptions/#noreversematch)
there isn't clear explicit information about where to get them from.

Also, when the information is provided, it's not always provided
consistently.

My suggestion is that each section (Database Exceptions, Http Exceptions
and so on) there should begin with a paragraph on its own: ''Core
exceptions are provided in django.core.exceptions'', ''Database exceptions
are provided in django.db'' and so on.

FInally, ''Django-specific Exceptions'' seems a bit of a misnomer, since
others not in that section are also Django-specific. Calling them ''Core
exceptions'' would seem to make more sense.

--
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.5baccf22b7c7d779250d7f8fa505645c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #12990: New Field Type: JSONField

2013-07-22 Thread Django

#12990: New Field Type: JSONField
-+-
 Reporter:  paltman  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.2-alpha
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by tom.gruner@…):

 If you "Don't Give Users Loaded Guns Aimed At Feet ", how do you ever
 expect them to dance ( ;

-- 
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.2107a2335317b31c51c7d44e539c4eb4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20773: contrib/gis/maps/google/gmap : script() string formating

2013-07-22 Thread Django

#20773: contrib/gis/maps/google/gmap : script() string formating
-+-
 Reporter:  martync  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"01910115329c2073e6c68b214155dd5fb87132c8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="01910115329c2073e6c68b214155dd5fb87132c8"
 [1.5.x] Fixed #20773 -- [gis] Fixed regression in GoogleMap output

 Thanks Martyn Clement for the report and the initial patch.
 Backport of 27c1a7257 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/065.1d316a3d2a83bd29553a788d9b6534c1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20785: [oracle] ORA-01425: escape character must be character string of length 1

2013-07-22 Thread Django

#20785: [oracle] ORA-01425: escape character must be character string of length 
1
--+
 Reporter:  ludo  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6-beta-1
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Upgrading from 1.5 to 1.6 beta this error, which was fixed in #14149 crops
 up again. The simple fix is to add DatabaseError to the try/except block
 that wraps the query to test for Oracle operators when creating the
 connection. I'm on Python 2.7.3 cxOracle 5.1.2.

-- 
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/047.f4f341025e221c7cea41617f5a2a599b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20774: Update the localflavor topic guide when django-localflavor is ready

2013-07-22 Thread Django

#20774: Update the localflavor topic guide when django-localflavor is ready
-+-
 Reporter:  loic84   |Owner:  jezdez
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  localflavor  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by jezdez):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * owner:  nobody => jezdez
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 This can be closed when https://github.com/django/django-
 localflavor/issues/13 is done

-- 
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.094b227c20898aadd4b55752c47f537d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20774: Update the localflavor topic guide when django-localflavor is ready

2013-07-22 Thread Django

#20774: Update the localflavor topic guide when django-localflavor is ready
--+
 Reporter:  loic84|Owner:  jezdez
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  localflavor   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by jezdez):

 * 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.fe8c10bbba97c2b57b98d54eb947e011%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20784: RegexValidator should accept a new parameter to perform reversed validation

2013-07-22 Thread Django

#20784: RegexValidator should accept a new parameter to perform reversed 
validation
+
 Reporter:  devfeng |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Core (Other)|  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  RegexValidator  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by aaugustin):

 I'm not strongly against this idea in general, however, I'm very concerned
 about the rationale.

 A blacklist implemented with a regex is a textbook example of the worst
 possible way to defending against XSS!

-- 
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.4f4fa0c1e01d79b5aec73fad6e2f2c9f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20773: contrib/gis/maps/google/gmap : script() string formating

2013-07-22 Thread Django

#20773: contrib/gis/maps/google/gmap : script() string formating
-+-
 Reporter:  martync  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"92f66a613498172e6300c8a0b57513183e998597"]:
 {{{
 #!CommitTicketReference repository=""
 revision="92f66a613498172e6300c8a0b57513183e998597"
 [1.6.x] Fixed #20773 -- [gis] Fixed regression in GoogleMap output

 Thanks Martyn Clement for the report and the initial patch.
 Backport of 27c1a7257 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/065.ce7128be829e410b8ae4d1ed0dcb3840%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 019101: [1.5.x] Fixed #20773 -- [gis] Fixed regression in ...

2013-07-22 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 01910115329c2073e6c68b214155dd5fb87132c8
  
https://github.com/django/django/commit/01910115329c2073e6c68b214155dd5fb87132c8
  Author: Claude Paroz 
  Date:   2013-07-22 (Mon, 22 Jul 2013)

  Changed paths:
M django/contrib/gis/maps/google/gmap.py
M django/contrib/gis/tests/geoadmin/tests.py

  Log Message:
  ---
  [1.5.x] Fixed #20773 -- [gis] Fixed regression in GoogleMap output

Thanks Martyn Clement for the report and the initial patch.
Backport of 27c1a7257 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/51ece90af098d_7927853d4c10292b%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 92f66a: [1.6.x] Fixed #20773 -- [gis] Fixed regression in ...

2013-07-22 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 92f66a613498172e6300c8a0b57513183e998597
  
https://github.com/django/django/commit/92f66a613498172e6300c8a0b57513183e998597
  Author: Claude Paroz 
  Date:   2013-07-22 (Mon, 22 Jul 2013)

  Changed paths:
M django/contrib/gis/maps/google/gmap.py
M django/contrib/gis/tests/geoadmin/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #20773 -- [gis] Fixed regression in GoogleMap output

Thanks Martyn Clement for the report and the initial patch.
Backport of 27c1a7257 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/51ece7a1c169b_73d9a5bd4c547e%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20773: contrib/gis/maps/google/gmap : script() string formating

2013-07-22 Thread Django

#20773: contrib/gis/maps/google/gmap : script() string formating
-+-
 Reporter:  martync  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"27c1a7257652031d3957c97271723778f27c4d7b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="27c1a7257652031d3957c97271723778f27c4d7b"
 Fixed #20773 -- [gis] Fixed regression in GoogleMap output

 Thanks Martyn Clement for the report and the initial 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/065.bb69d401acca17788a6a9acca8bbc23e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 27c1a7: Fixed #20773 -- [gis] Fixed regression in GoogleMa...

2013-07-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 27c1a7257652031d3957c97271723778f27c4d7b
  
https://github.com/django/django/commit/27c1a7257652031d3957c97271723778f27c4d7b
  Author: Claude Paroz 
  Date:   2013-07-22 (Mon, 22 Jul 2013)

  Changed paths:
M django/contrib/gis/maps/google/gmap.py
M django/contrib/gis/tests/geoadmin/tests.py

  Log Message:
  ---
  Fixed #20773 -- [gis] Fixed regression in GoogleMap output

Thanks Martyn Clement for the report and the initial 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/51ece6c1191b8_307a701d5449956%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20784: RegexValidator should accept a new parameter to perform reversed validation

2013-07-22 Thread Django

#20784: RegexValidator should accept a new parameter to perform reversed 
validation
+
 Reporter:  devfeng |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Core (Other)|  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  RegexValidator  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by claudep):

 * needs_docs:  0 => 1
 * 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.7bf878752e6af65a4598ce33e6904944%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20649: Add an easier way to override the blank option for CharFields with choices

2013-07-22 Thread Django

#20649: Add an easier way to override the blank option for CharFields with 
choices
-+--
 Reporter:  brillgen |Owner:  alexcouper
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by brillgen):

 I'm not core or reviewing the patch (just the reporter) but it looks good
 (without having tested the codebase 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/066.5d31e43ff2bd3825fe65f051b9fe53a7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20781: Regression in form field _has_changed for fields with show_hidden_initial=True

2013-07-22 Thread Django

#20781: Regression in form field _has_changed for fields with
show_hidden_initial=True
-+-
 Reporter:  timo |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:
 Severity:  Release blocker  |  1.6-beta-1
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"816bf0c6a7a13efb7ae17c9773f984f2dd16fc72"]:
 {{{
 #!CommitTicketReference repository=""
 revision="816bf0c6a7a13efb7ae17c9773f984f2dd16fc72"
 [1.6.x] Fixed #20781 -- Fixed _has_changed regression with MultiValueField

 Thanks Tim Graham for the report.
 Backport of 02b0106d 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/062.70651fbf18f067615e1602cb10498b18%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 02b010: Fixed #20781 -- Fixed _has_changed regression with...

2013-07-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 02b0106d43f6997f02cc6785359f8f7519215d3d
  
https://github.com/django/django/commit/02b0106d43f6997f02cc6785359f8f7519215d3d
  Author: Claude Paroz 
  Date:   2013-07-22 (Mon, 22 Jul 2013)

  Changed paths:
M django/forms/fields.py
M tests/forms_tests/tests/test_extra.py
M tests/forms_tests/tests/test_fields.py

  Log Message:
  ---
  Fixed #20781 -- Fixed _has_changed regression with MultiValueField

Thanks Tim Graham 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/51ecd9ebb91bc_72aa915d4897835%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 816bf0: [1.6.x] Fixed #20781 -- Fixed _has_changed regress...

2013-07-22 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 816bf0c6a7a13efb7ae17c9773f984f2dd16fc72
  
https://github.com/django/django/commit/816bf0c6a7a13efb7ae17c9773f984f2dd16fc72
  Author: Claude Paroz 
  Date:   2013-07-22 (Mon, 22 Jul 2013)

  Changed paths:
M django/forms/fields.py
M tests/forms_tests/tests/test_extra.py
M tests/forms_tests/tests/test_fields.py

  Log Message:
  ---
  [1.6.x] Fixed #20781 -- Fixed _has_changed regression with MultiValueField

Thanks Tim Graham for the report.
Backport of 02b0106d 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/51ecda3c42ae0_72e2527d58116720%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20781: Regression in form field _has_changed for fields with show_hidden_initial=True

2013-07-22 Thread Django

#20781: Regression in form field _has_changed for fields with
show_hidden_initial=True
-+-
 Reporter:  timo |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:
 Severity:  Release blocker  |  1.6-beta-1
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"02b0106d43f6997f02cc6785359f8f7519215d3d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="02b0106d43f6997f02cc6785359f8f7519215d3d"
 Fixed #20781 -- Fixed _has_changed regression with MultiValueField

 Thanks Tim Graham 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/062.4df67ce95240af7673afc3d09d85d771%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

44 matches

Mail list logo