Re: [Django] #18687: Randomly failing test: test_performance_scalability

[Django]

#18687: Randomly failing test: test_performance_scalability
-+
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Aymeric Augustin ):

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


Comment:

 In [5262a288df07daa050a0e17669c3f103f47a8640]:
 {{{
 #!CommitTicketReference repository=""
 revision="5262a288df07daa050a0e17669c3f103f47a8640"
 Fixed #18687: Removed test_performance_scalability

 Even after repeated adjustment of the constants, this test still fails
 randomly. It has educated us to ignore messages from Jenkins, to a
 point where we missed some actual failures. In addition, it accounts
 for a non-negligible percentage of the run time of the test suite
 just by itself. Since no one has proposed a convincing patch in months,
 I'm going to remove the patch. We can't keep a randomly failing test
 forever.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 5262a2: Fixed #18687: Removed test_performance_scalability

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5262a288df07daa050a0e17669c3f103f47a8640
  
https://github.com/django/django/commit/5262a288df07daa050a0e17669c3f103f47a8640
  Author: Aymeric Augustin 
  Date:   2012-09-05 (Wed, 05 Sep 2012)

  Changed paths:
M tests/regressiontests/utils/crypto.py

  Log Message:
  ---
  Fixed #18687: Removed test_performance_scalability

Even after repeated adjustment of the constants, this test still fails
randomly. It has educated us to ignore messages from Jenkins, to a
point where we missed some actual failures. In addition, it accounts
for a non-negligible percentage of the run time of the test suite
just by itself. Since no one has proposed a convincing patch in months,
I'm going to remove the patch. We can't keep a randomly failing test
forever.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 813241: Clarifies day and month in example queryset

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 813241f65562bc0e7f20264238424d82bee2febc
  
https://github.com/django/django/commit/813241f65562bc0e7f20264238424d82bee2febc
  Author: Matt Stevens 
  Date:   2012-09-03 (Mon, 03 Sep 2012)

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

  Log Message:
  ---
  Clarifies day and month in example queryset


  Commit: a7d831a3056449b2aca88492031be8cedef58f87
  
https://github.com/django/django/commit/a7d831a3056449b2aca88492031be8cedef58f87
  Author: Matt Stevens 
  Date:   2012-09-03 (Mon, 03 Sep 2012)

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

  Log Message:
  ---
  Changes day to from 2 to 30


  Commit: 3f53cac520d6a4f87b7b8e45eeb06921a58c515f
  
https://github.com/django/django/commit/3f53cac520d6a4f87b7b8e45eeb06921a58c515f
  Author: Adrian Holovaty 
  Date:   2012-09-05 (Wed, 05 Sep 2012)

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

  Log Message:
  ---
  Merge pull request #318 from Matt-Stevens/master

Small doc change: clarify day and month


Compare: https://github.com/django/django/compare/e5983af7c16c...3f53cac520d6

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18904: Django documentations faulty link

[Django]

#18904: Django documentations faulty link
--+
 Reporter:  johie_anderson@…  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [53f533f8648eb869978020c11f0c9c8f4dae4679]:
 {{{
 #!CommitTicketReference repository=""
 revision="53f533f8648eb869978020c11f0c9c8f4dae4679"
 [1.4.X] Fixed #18904 - Typo in MySQL link; thanks Johie Anderson for the
 report.

 Backport of e5983af7c1 from master
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 53f533: [1.4.X] Fixed #18904 - Typo in MySQL link; thanks ...

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 53f533f8648eb869978020c11f0c9c8f4dae4679
  
https://github.com/django/django/commit/53f533f8648eb869978020c11f0c9c8f4dae4679
  Author: Tim Graham 
  Date:   2012-09-05 (Wed, 05 Sep 2012)

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

  Log Message:
  ---
  [1.4.X] Fixed #18904 - Typo in MySQL link; thanks Johie Anderson for the 
report.

Backport of e5983af7c1 from master



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18904: Django documentations faulty link

[Django]

#18904: Django documentations faulty link
--+
 Reporter:  johie_anderson@…  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [e5983af7c16cc889cf7d52fdae67270717a1a846]:
 {{{
 #!CommitTicketReference repository=""
 revision="e5983af7c16cc889cf7d52fdae67270717a1a846"
 Fixed #18904 - Typo in MySQL link; thanks Johie Anderson 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] e5983a: Fixed #18904 - Typo in MySQL link; thanks Johie An...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e5983af7c16cc889cf7d52fdae67270717a1a846
  
https://github.com/django/django/commit/e5983af7c16cc889cf7d52fdae67270717a1a846
  Author: Tim Graham 
  Date:   2012-09-05 (Wed, 05 Sep 2012)

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

  Log Message:
  ---
  Fixed #18904 - Typo in MySQL link; thanks Johie Anderson for the report.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #10808: Multiple inheritance (model-based) broken for __init__ of common fields in diamond inheritance

[Django]

#10808: Multiple inheritance (model-based) broken for __init__ of common fields 
in
diamond inheritance
-+-
 Reporter:  mikemintz|Owner:
 Type:  Bug  |  mtredinnick
Component:  Database layer   |   Status:  new
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by lsaffre):

 The following workaround uses the class_prepared signal to removes any
 duplicate fields from `_meta._field_cache`:


 {{{
 def on_class_prepared(signal,sender=None,**kw):
 cache = []
 field_names = set()
 for f,m in model._meta._field_cache:
 if f.attname not in field_names:
 field_names.add(f.attname)
 cache.append( (f,m) )
 model._meta._field_cache = tuple(cache)
 model._meta._field_name_cache = [x for x, _ in cache]

 models.signals.class_prepared.connect(on_class_prepared)
 }}}

 Works for me and has the advantage of not needing to patch 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16649: Models.save() refactoring: check updated rows to determine action

[Django]

#16649: Models.save() refactoring: check updated rows to determine action
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 A bit more information about what the approach suggested is about. Assume
 you load a model from DB, change some fields and save it. We currently do:
 {{{
 SELECT - load from DB
 [change fields]; save()
 In save:
 SELECT - assert that the PK exists in the DB
 if yes:
 UPDATE
 else:
 INSERT
 }}}

 The second select above is usually redundant. If we know the object is
 loaded from DB (self._state.adding == False), and we are saving it to the
 same DB it was loaded from (self._state.db == the db we are saving to),
 then it is very likely the object exists in the DB. So, instead we should
 do:
 {{{
 In save:
 if same db, not adding:
 exists = UPDATE
 else:
 exists = SELECT
 if exists:
 UPDATE
 if not exists:
 INSERT
 }}}
 So, in the case the model is already in the DB, we do just a single update
 instead of select + update. If it so happens it doesn't exist (which
 should be very unlikely), we do update with zero rows modified and still
 know to do an insert.

 This does lead to behaviour change on MySQL when there is a concurrent
 insert to the same table. Currently the SELECT sees nothing, and the
 insert will lead to integrity error. After this, the update will block
 until the inserting transaction is committed, and then update the matching
 row. However, on PostgreSQL the update sees nothing, so there is no
 behaviour change there. For MySQL users this will be better than what we
 have now. For PostgreSQL users there is no change from behaviour
 standpoint.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9532: min_num on formsets

[Django]

#9532: min_num on formsets
-+-
 Reporter:  gsf  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by kitsunde):

 * cc: kitsunde@… (added)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #901: [patch] Reload method for models

[Django]

#901: [patch] Reload method for models
-+-
 Reporter:  andreas@…|Owner:  adrian
 Type:  enhancement  |   Status:  closed
Component:  Core (Other) |  Version:
 Severity:  normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by anonymous):

 I had more luck with:
 {{{
 def refresh_from_db(self):
 """Refreshes this instance from db
 https://code.djangoproject.com/ticket/901
 """
 from_db = self.__class__.objects.get(pk=self.pk)
 for field in self.__class__._meta.fields:
 setattr(self, field.name, getattr(from_db, field.name))
 }}}
 But I don't know enough to know if it's correct, only that it seems to
 work.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18416: Query fails when SimpleLazyObject evaluates to None

[Django]

#18416: Query fails when SimpleLazyObject evaluates to None
-+-
 Reporter:  bouke|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by fabiosantosart@…):

 And yet, when you accidentally pass None, django gives you that really
 tall call stack with an unrelated error message at the bottom. Couldn't a
 better message be issued?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18909: QueryString with non-ascii characters under Windows (Python 2.7) may be decoded inproperly

[Django]

#18909: QueryString with non-ascii characters under Windows (Python 2.7) may be
decoded inproperly
-+
 Reporter:  public@… |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (URLs)  |Version:  1.4
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Under Python 2.7, using cgi.parse_qsl would vary on return type according
 to the input arguments. Take the following query string as example:


 {{{
 >>> cgi.parse_qsl('q=%E4%BD%A0%E5%A5%BD')
 [('q', '\xe4\xbd\xa0\xe5\xa5\xbd')]
 >>> cgi.parse_qsl(u'q=%E4%BD%A0%E5%A5%BD')
 [(u'q', u'\xe4\xbd\xa0\xe5\xa5\xbd')]
 }}}


 The url-encoded string, "%E4%BD%A0%E5%A5%BD", carries two Chinese
 characters. There's not much trouble for the time being though, but when
 it is used together with django.http.QueryDict, something bad happens.

 {{{
 def __init__(self, query_string, mutable=False, encoding=None):
 super(QueryDict, self).__init__()
 if not encoding:
 encoding = settings.DEFAULT_CHARSET
 self.encoding = encoding
 #if (isinstance(query_string, unicode)): # These two lines
 were added by me.
 #query_string = query_string.encode('utf-8')
 if six.PY3:
 for key, value in parse_qsl(query_string or '',
 keep_blank_values=True,
 encoding=encoding):
 self.appendlist(key, value)
 else:
 for key, value in parse_qsl(query_string or '',
 keep_blank_values=True):
 self.appendlist(force_text(key, encoding,
 errors='replace'),
 force_text(value, encoding,
 errors='replace'))
 self._mutable = mutable
 }}}

 Although key and values are intended to be translated to Unicode, they
 have no chance to make the effort. The value remains
 u'\xe4\xbd\xa0\xe5\xa5\xbd', which is certainly not a valid UTF-16 string.
 I can't say whether this bug would be fixed silently later in other place
 of Django. What's more, I just couldn't see the bug under Linux (UTF-8).
 But under Windows, it really exists.

 Here I will upload my Django application along with this ticket. It is a
 really small application, and just displays everything client requested to
 server. You can start the application by manage.py runserver, and hit
 "http://localhost:8000/?q=%E4%BD%A0%E5%A5%BD; to see whether the bug
 occurs or not.

 Note: I discovered this under Windows XP SP3 (Simplified Chinese) with
 system encoding = gbk (Though the django is set to utf-8).

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18908: Can't set multiple cookies with the same name but different domains/paths

[Django]

#18908: Can't set multiple cookies with the same name but different 
domains/paths
---+
 Reporter:  ludwig.haehne  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  HTTP handling  |Version:  master
 Severity:  Normal |   Keywords:  cookie
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 There is no way to set cookies with the same name for multiple domains or
 paths in the same response.

 The following code only sets the second cookie:

 {{{
 response.set_cookie("alice", "123", domain='sub.example.com')
 response.set_cookie("alice", "456", domain='example.com')
 }}}

 It makes sense because Django uses a dictionary for storing cookies:

 {{{
 self.cookies[key] = value
 }}}

 Therefore, Django cannot set multiple cookies with the same name but
 different domains or paths in the same response.
 [http://tools.ietf.org/html/rfc2965 RFC2965] is not completely clear if
 this should be possible but this article
 [http://www.nczonline.net/blog/2009/05/05/http-cookies-explained/]
 suggests that it should be:

   This cookie has four identifying characteristics: the cookie '''name''',
 the '''domain''', the '''path''', and the '''secure''' flag. In order to
 change the value of this cookie in the future, another Set-Cookie header
 must be sent using the same cookie name, domain, and path.

 This issue was brought up on [http://stackoverflow.com/q/12281038/63392
 Stackoverflow].

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18907: Documentation regarding population of backrefs is incorrect

[Django]

#18907: Documentation regarding population of backrefs is incorrect
+
 Reporter:  simonpercivall  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Documentation   |Version:  1.4
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 It is stated at https://docs.djangoproject.com/en/1.4/topics/db/queries
 /#how-are-the-backward-relationships-possible in the third paragraph that
 "the first time any model is loaded" Django iterates `INSTALLED_APPS` and
 populates backrefs. Either this is plain wrong, or the text needs
 clarification.

 1. I create a minimal two-app project where app2.Model2 has a reference to
 app1.Model1 and both `app1` and `app2` are in `INSTALLED_APPS`
 2. I create a Model1: `Model1.objects.create()`
 3. I write and run a script:
 {{{#!python
 from app1.models import Model1

 m = Model1.objects.get().model2s.all()
 }}}
 4. and get
 {{{#!python
 Traceback (most recent call last):
   File "f.py", line 8, in 
 Model1.objects.get().model2s.all()
 AttributeError: 'Model1' object has no attribute 'model2s'
 }}}

 If I add `import app2.models`, it'll work.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18906: BaseModelFormSet.validate_unique should ignore forms marked for deletion

[Django]

#18906: BaseModelFormSet.validate_unique should ignore forms marked for deletion
-+
 Reporter:  c.pollock@…  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Forms|Version:  1.4
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 is_valid() returns false for a formset where uniquness is violated even if
 one of the forms where the violation occurs has DELETE set to true in
 cleaned data

 so maybe line 521 in django/forms/models.py which is currently

 if not hasattr(form, "cleaned_data"):
 continue

 should read something like, so it will ignore forms that are getting
 deleted anyway

  if not hasattr(form, "cleaned_data") or form.cleaned_data.get('DELETE',
 True):
 continue

 unless of course I have completely missed the point

 Cheers
 Charlie

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18905: New location of DjangoPeople.net

[Django]

#18905: New location of DjangoPeople.net
---+
 Reporter:  shabda@…   |Owner:  nobody
 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:  1  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [cff911f4ba3b3e6393c58da5131ce8b188a68f0c]:
 {{{
 #!CommitTicketReference repository=""
 revision="cff911f4ba3b3e6393c58da5131ce8b188a68f0c"
 Merge pull request #325 from shabda/ticket_18905

 Fixed #18905 - Updated URL for Django People
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18905: New location of DjangoPeople.net

[Django]

#18905: New location of DjangoPeople.net
---+
 Reporter:  shabda@…   |Owner:  nobody
 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:  1  |UI/UX:  0
---+
Changes (by Shabda Raaj ):

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


Comment:

 In [b791fda0dfd689a1514a1a2a55d60e0baa57a107]:
 {{{
 #!CommitTicketReference repository=""
 revision="b791fda0dfd689a1514a1a2a55d60e0baa57a107"
 Fixed #18905 - Changed to new url for Djangopeople
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b791fd: Fixed #18905 - Changed to new url for Djangopeople

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b791fda0dfd689a1514a1a2a55d60e0baa57a107
  
https://github.com/django/django/commit/b791fda0dfd689a1514a1a2a55d60e0baa57a107
  Author: Shabda Raaj 
  Date:   2012-09-05 (Wed, 05 Sep 2012)

  Changed paths:
M docs/faq/general.txt

  Log Message:
  ---
  Fixed #18905 - Changed to new url for Djangopeople


  Commit: cff911f4ba3b3e6393c58da5131ce8b188a68f0c
  
https://github.com/django/django/commit/cff911f4ba3b3e6393c58da5131ce8b188a68f0c
  Author: Tim Graham 
  Date:   2012-09-05 (Wed, 05 Sep 2012)

  Changed paths:
M docs/faq/general.txt

  Log Message:
  ---
  Merge pull request #325 from shabda/ticket_18905

Fixed #18905 - Updated URL for Django People


Compare: https://github.com/django/django/compare/4193a0f3d581...cff911f4ba3b

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18905: New location of DjangoPeople.net

[Django]

#18905: New location of DjangoPeople.net
---+
 Reporter:  shabda@…   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by anonymous):

 * has_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18905: New location of DjangoPeople.net

[Django]

#18905: New location of DjangoPeople.net
---+
 Reporter:  shabda@…   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by anonymous):

 Here is the pull request. https://github.com/django/django/pull/325

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18905: New location of DjangoPeople.net

[Django]

#18905: New location of DjangoPeople.net
---+
 Reporter:  shabda@…   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 https://docs.djangoproject.com/en/dev/faq/general/#where-can-i-find-
 django-developers-for-hire mentions DjangoPeople.net. Change this to the
 new url

 https://people.djangoproject.com/

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18904: Django documentations faulty link

[Django]

#18904: Django documentations faulty link
--+
 Reporter:  johie_anderson@…  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by akaariai):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Documentation
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 This is exactly the right place. Thanks for the report!

 The same problem is also in the dev docs.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18904: Django documentations faulty link

[Django]

#18904: Django documentations faulty link
--+
 Reporter:  johie_anderson@…  |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Uncategorized |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 While I was reading through the documentation I found a corrupt link

 at
 https://docs.djangoproject.com/en/1.4/ref/models/querysets/#search

 The link to "MySQL Documentation" has an extra > at the end.
 This is probably the wrong place for this but I don't know where else to
 tell you.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18903: Add forms validation for GB telephone numbers.

[Django]

#18903: Add forms validation for GB telephone numbers.
-+-
 Reporter:  g1smd|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  Telephone Number | Triage Stage:
  Forms GB   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by anonymous):

 https://github.com/django/django/pull/316 is b0rked.

 See https://github.com/django/django/pull/324 for replacement.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16455: Postgis 2.0 Compatibility

[Django]

#16455: Postgis 2.0 Compatibility
-+
 Reporter:  ckarrie  |Owner:  jbronn
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgis 2.0  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by aurelio):

 * cc: aurelio@… (added)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.