Re: [Django] #19043: Mutable Password Hash Strength

[Django]

#19043: Mutable Password Hash Strength
-+-
 Reporter:  jbuckner |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  auth, bcrypt,| Triage Stage:
  pbkdf2 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by ptone):

 The bar is pretty high for introducing new settings - I'm not sure this
 passes that bar.

 The subclassing of the hashers is very straightforward and even well
 documented:

 https://docs.djangoproject.com/en/dev/topics/auth/#increasing-the-work-
 factor

 You don't have to actually write your own hasher when subclassing in this
 case, just change a few attributes.

 I do think an argument could be made for changing the {{{must_update}}}
 flag to check if the same hasher is being used, not just the same
 algorithm. That would address the second part of your changes.

 Another reason not to introduce these settings - is it makes our sane
 security defaults a little too easy to muck with.  The project has to
 tread a line between defaults that are robust and not easily circumvented
 by genuine accident, while still allowing those who know what they are
 doing to make the changes they need to.  Subclassing seems to strike that
 balance better than a pair of settings.

-- 
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] #19043: Mutable Password Hash Strength

[Django]

#19043: Mutable Password Hash Strength
-+-
 Reporter:  jbuckner |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  auth, bcrypt,| Triage Stage:
  pbkdf2 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jbuckner):

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


Comment:

 I have also opened a [https://github.com/django/django/pull/406 pull
 request] for this ticket.

-- 
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] ab2a17: Added a missing comma

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ab2a1773fdef2ff240b124268f5ae1118d8e27b5
  
https://github.com/django/django/commit/ab2a1773fdef2ff240b124268f5ae1118d8e27b5
  Author: Preston Holmes 
  Date:   2012-09-29 (Sat, 29 Sep 2012)

  Changed paths:
M docs/howto/deployment/wsgi/modwsgi.txt

  Log Message:
  ---
  Added a missing comma



-- 
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] #19043: Mutable Password Hash Strength

[Django]

#19043: Mutable Password Hash Strength
--+--
 Reporter:  jbuckner  |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  contrib.auth  |Version:  master
 Severity:  Normal|   Keywords:  auth, bcrypt, pbkdf2
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+--
 Django 1.4 introduced automatic conversion of passwords from one hashing
 algorithm to another. Some algorithms, notably Bcrypt and PBKDF2 can have
 different work factors and iterations. Currently there's no way to change
 the difficulty of the particular algorithm without subclassing it and
 writing your own hasher. Even then, it won't re-hash the password with the
 new difficulty.

 This patch adds two Django settings, {{{BCRYPT_ROUNDS}}} (as used in
 django-bcrypt) and {{{PBKDF2_ITERATIONS}}}, depending on your preferred
 algorithm. If you change these values, the next time
 {{{check_password()}}} is called when a user logs in, it will re-hash
 their password with the new difficulty.

 We did this by introducing an {{{is_current()}}} method in the
 {{{django.contrib.auth.hashers.BasePasswordHasher}}} that returns whether
 or not the hash matches the desired difficulty. For instance, in the
 {{{BCryptPasswordHasher}}}, we compare the {{{safe_summary['work
 factor']}}} against the {{{BCRYPT_ROUNDS}}} setting and if they differ,
 re-hash the password.

 There are also tests included.

-- 
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] #19042: mod_wsgi docs for virtualenv uses WSGIPythonPath incorrectly

[Django]

#19042: mod_wsgi docs for virtualenv uses WSGIPythonPath incorrectly
---+
 Reporter:  ptone  |  Owner:  nobody
 Type:  Bug| Status:  closed
Component:  Documentation  |Version:  master
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+
Changes (by Preston Holmes ):

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


Comment:

 In [changeset:"3abf6105b6c953c6feb28708b9903f583cb28438"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3abf6105b6c953c6feb28708b9903f583cb28438"
 Fixed a couple errors and inconsistencies in mod_wsgi docs

 Fixes #19042
 }}}

-- 
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] 3abf61: Fixed a couple errors and inconsistencies in mod_w...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3abf6105b6c953c6feb28708b9903f583cb28438
  
https://github.com/django/django/commit/3abf6105b6c953c6feb28708b9903f583cb28438
  Author: Preston Holmes 
  Date:   2012-09-29 (Sat, 29 Sep 2012)

  Changed paths:
M docs/howto/deployment/wsgi/apache-auth.txt
M docs/howto/deployment/wsgi/modwsgi.txt

  Log Message:
  ---
  Fixed a couple errors and inconsistencies in mod_wsgi docs

Fixes #19042



-- 
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] #16391: New URL tag for reversing urls with placeholder args/kwargs

[Django]

#16391: New URL tag for reversing urls with placeholder args/kwargs
+-
 Reporter:  h.a.clifford@…  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Core (Other)|  Version:  1.3
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Someday/Maybe
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-

Comment (by mitar):

 I add this code (with some improvements) [http://django-
 
missing.readthedocs.org/en/latest/templatetags.html#missing.templatetags.url_tags.urltemplate
 to my library].

-- 
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] #18306: Deferred models should automatically issue update_fields when saving

[Django]

#18306: Deferred models should automatically issue update_fields when saving
-+-
 Reporter:  akaariai |Owner:  akaariai
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

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

 In [changeset:"dad7eec6e1c1770f5d81d5c5ed2de296c1eca969"]:
 {{{
 #!CommitTicketReference repository=""
 revision="dad7eec6e1c1770f5d81d5c5ed2de296c1eca969"
 Corrected links to only()/defer() in Model documentation

 Refs #18306
 }}}

-- 
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] dad7ee: Corrected links to only()/defer() in Model documen...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: dad7eec6e1c1770f5d81d5c5ed2de296c1eca969
  
https://github.com/django/django/commit/dad7eec6e1c1770f5d81d5c5ed2de296c1eca969
  Author: Anssi Kääriäinen 
  Date:   2012-09-29 (Sat, 29 Sep 2012)

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

  Log Message:
  ---
  Corrected links to only()/defer() in Model documentation

Refs #18306



-- 
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] #9279: loaddata should have an option to ignore data for fields that no longer exist

[Django]

#9279: loaddata should have an option to ignore data for fields that no longer
exist
-+-
 Reporter:  erichs@… |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core |  Version:  1.0
  (Serialization)|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by d1ffuz0r):

 * cc: d1fffuz0r@… (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] #7936: Add Last-Modified header to feeds

[Django]

#7936: Add Last-Modified header to feeds
-+-
 Reporter:  julianb  |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  syndication last-| Triage Stage:  Accepted
  modified   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by d1ffuz0r):

 * cc: d1fffuz0r@… (added)
 * has_patch:  1 => 0
 * version:  1.2-alpha => master
 * needs_tests:  1 => 0


Comment:

 https://github.com/django/django/pull/409

-- 
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] #18891: Add django-wkhtmltopdf to further resources

[Django]

#18891: Add django-wkhtmltopdf to further resources
---+
 Reporter:  kerry@…|Owner:  nobody
 Type:  New feature|   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 timo):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => New feature
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Adding to further resources is ok with me.

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

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

[django/django] 10e505: Moved filter at handler level

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 10e505b1b37f29c9ac6567134c48677b042c2a87
  
https://github.com/django/django/commit/10e505b1b37f29c9ac6567134c48677b042c2a87
  Author: Claude Paroz 
  Date:   2012-09-29 (Sat, 29 Sep 2012)

  Changed paths:
M django/utils/log.py

  Log Message:
  ---
  Moved filter at handler level

Filters at logger level are only processed for messages directly
logged to the specific logger, not for loggers in the parent chain.
As the 'django' logger is almost always processed as an inherited
logger, it makes more sense to filter messages at the 'console'
handler level.



-- 
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] #16087: Add ResolverMatch object to test client responses.

[Django]

#16087: Add ResolverMatch object to test client responses.
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Testing framework|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  test client view | Triage Stage:  Accepted
  url resolve reverse|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mrmachine):

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


Comment:

 Sorry, it must be too early in the morning. Got my requests and responses
 mixed up!

-- 
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] #16087: Add ResolverMatch object to test client responses.

[Django]

#16087: Add ResolverMatch object to test client responses.
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.3
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  test client view | Triage Stage:  Accepted
  url resolve reverse|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mrmachine):

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


Comment:

 Closing this as fixed. Since #15695 was fixed, the resolver match object
 is added to all requests (not only test client requests).

-- 
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] #18993: Default django logging to StreamHandler (when DEBUG=True)

[Django]

#18993: Default django logging to StreamHandler (when DEBUG=True)
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"f0f327bbfe1caae6d11fbe20a3b5b96eed1704cf"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f0f327bbfe1caae6d11fbe20a3b5b96eed1704cf"
 Fixed #18993 -- 'django' logger logs to console when DEBUG=True

 Thanks Preston Holmes for the 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 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] #18993: Default django logging to StreamHandler (when DEBUG=True)

[Django]

#18993: Default django logging to StreamHandler (when DEBUG=True)
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"a014ddfef2f606471f25c756d97b3b50fcbd9e91"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a014ddfef2f606471f25c756d97b3b50fcbd9e91"
 Combined Django DEFAULT_LOGGING with user LOGGING config

 Refs #18993.
 }}}

-- 
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] a014dd: Combined Django DEFAULT_LOGGING with user LOGGING ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a014ddfef2f606471f25c756d97b3b50fcbd9e91
  
https://github.com/django/django/commit/a014ddfef2f606471f25c756d97b3b50fcbd9e91
  Author: Claude Paroz 
  Date:   2012-09-29 (Sat, 29 Sep 2012)

  Changed paths:
M django/conf/__init__.py
M django/conf/global_settings.py
M django/utils/log.py
M docs/topics/logging.txt

  Log Message:
  ---
  Combined Django DEFAULT_LOGGING with user LOGGING config

Refs #18993.


  Commit: f0f327bbfe1caae6d11fbe20a3b5b96eed1704cf
  
https://github.com/django/django/commit/f0f327bbfe1caae6d11fbe20a3b5b96eed1704cf
  Author: Claude Paroz 
  Date:   2012-09-29 (Sat, 29 Sep 2012)

  Changed paths:
M django/utils/log.py
M docs/releases/1.5.txt
M docs/topics/logging.txt
M tests/regressiontests/logging_tests/tests.py

  Log Message:
  ---
  Fixed #18993 -- 'django' logger logs to console when DEBUG=True

Thanks Preston Holmes for the review.


Compare: https://github.com/django/django/compare/15202baace14...f0f327bbfe1c

-- 
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] #19030: primary key in model is not primary key in database

[Django]

#19030: primary key in model is not primary key in database
-+-
 Reporter:  ccruickshank |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 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 Ccruickshank):

 Interesting reply. You mentioned syncdb and then I realised that I use
 South to create and manage tables . I wonder if this has introduced the
 problem, if fact I'm use the  trunk version which may not be fully
 developed.

 I'll try your suggestion and just use a raw model . it is probably worthy
 checking without and without South.

-- 
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] #17058: Docs refer to extras/csrf_migration_helper.py which is not packaged

[Django]

#17058: Docs refer to extras/csrf_migration_helper.py  which is not packaged
---+
 Reporter:  slinkp |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"15202baace1453e7576806f13d137ae930de6dcb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="15202baace1453e7576806f13d137ae930de6dcb"
 Fixed #17058 - Clarified where extras/csrf_migration_helper.py is located
 }}}

-- 
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] 15202b: Fixed #17058 - Clarified where extras/csrf_migrati...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 15202baace1453e7576806f13d137ae930de6dcb
  
https://github.com/django/django/commit/15202baace1453e7576806f13d137ae930de6dcb
  Author: Tim Graham 
  Date:   2012-09-29 (Sat, 29 Sep 2012)

  Changed paths:
M docs/ref/contrib/csrf.txt

  Log Message:
  ---
  Fixed #17058 - Clarified where extras/csrf_migration_helper.py is located



-- 
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] #15695: Save ResolverMatch in HttpRequest

[Django]

#15695: Save ResolverMatch in HttpRequest
-+-
 Reporter:  nischu7  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  1.3
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  1|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Florian Apolloner ):

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


Comment:

 In [changeset:"b946db5241b924c72c1079ce30d9b368e2b82f07"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b946db5241b924c72c1079ce30d9b368e2b82f07"
 Fixed #15695 -- Added `ResolverMatch` to the request object.
 }}}

-- 
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] b946db: Fixed #15695 -- Added `ResolverMatch` to the reque...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b946db5241b924c72c1079ce30d9b368e2b82f07
  
https://github.com/django/django/commit/b946db5241b924c72c1079ce30d9b368e2b82f07
  Author: Florian Apolloner 
  Date:   2012-09-27 (Thu, 27 Sep 2012)

  Changed paths:
M django/core/handlers/base.py
M docs/ref/request-response.txt
M docs/releases/1.5.txt
M tests/regressiontests/urlpatterns_reverse/namespace_urls.py
M tests/regressiontests/urlpatterns_reverse/tests.py
M tests/regressiontests/urlpatterns_reverse/views.py

  Log Message:
  ---
  Fixed #15695 -- Added `ResolverMatch` to the request object.


  Commit: 6a6f589bfe4d03c3de04753330c307832cd2dcbe
  
https://github.com/django/django/commit/6a6f589bfe4d03c3de04753330c307832cd2dcbe
  Author: Florian Apolloner 
  Date:   2012-09-29 (Sat, 29 Sep 2012)

  Changed paths:
M django/core/handlers/base.py
M docs/ref/request-response.txt
M docs/releases/1.5.txt
M tests/regressiontests/urlpatterns_reverse/namespace_urls.py
M tests/regressiontests/urlpatterns_reverse/tests.py
M tests/regressiontests/urlpatterns_reverse/views.py

  Log Message:
  ---
  Merge branch 'ticket15695'


Compare: https://github.com/django/django/compare/8867c2761358...6a6f589bfe4d

-- 
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] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
---+
 Reporter:  pixelcort  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+

Comment (by anonymous):

 +1 just looking for this function

-- 
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] 8867c2: Added link to PostGIS matrix on OSGeo Wiki

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8867c276135887458c21536f53c8b4045baefefc
  
https://github.com/django/django/commit/8867c276135887458c21536f53c8b4045baefefc
  Author: Claude Paroz 
  Date:   2012-09-29 (Sat, 29 Sep 2012)

  Changed paths:
M docs/ref/contrib/gis/install.txt

  Log Message:
  ---
  Added link to PostGIS matrix on OSGeo Wiki



-- 
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:  Ready for checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 While preparing the commit, I'm still getting a failing test
 (`geoapp.GeoLookupTest.test_left_right_lookups`). When I short-circuit the
 index creation process, the test succeeds, so I guess this has something
 to do with indexes. I have PostGIS 2.0.1 on Ubuntu 12.04. Can someone
 reproduce the problem?

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

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

Re: [Django] #15338: django.utils.decorators isn't documented

[Django]

#15338: django.utils.decorators isn't documented
---+-
 Reporter:  gabrielhurley  |Owner:  gabrielhurley
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by timo):

 Thanks for the feedback.  I can't take credit for "dynamically" or most of
 this patch as it's mostly copied from docstrings.

-- 
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] #19042: mod_wsgi docs for virtualenv uses WSGIPythonPath incorrectly

[Django]

#19042: mod_wsgi docs for virtualenv uses WSGIPythonPath incorrectly
---+
 Reporter:  ptone  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 as near as I can tell this section of the docs is incorrect:

 
https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/modwsgi/#using-a-virtualenv

 The docs suggest adding a line to the conf

 however

 http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIPythonPath

 stipulates that multiple locations be separated with a ':'

 In my tests, using two lines will result in only the last line modifying
 the Python path, while using ':' works

 I don't really use mod_wsgi much, so wouldn't mind someone validating this
 on another setup.

-- 
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] #19030: primary key in model is not primary key in database

[Django]

#19030: primary key in model is not primary key in database
-+-
 Reporter:  ccruickshank |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 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 ptone):

 Using the same backend and pgadmin I can not reproduce this.  I'm nearly
 positive the platform Win32 vs OSX is not making any difference.

 I'm pretty sure this should/will be closed as invalid.

 As a final check towards reproducibility  - is there a chance you added
 the primary_key=True to your Django models after running syncdb?

 Django does not alter tables once created.

 Please try to reproduce your issue from scratch - without reusing your
 project and see if you can reproduce.

-- 
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] #7857: manage.py shell, dbshell funtionality

[Django]

#7857: manage.py shell, dbshell funtionality
-+-
 Reporter:  Sanha|Owner:  marclurr
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  manage.py,   |  Needs documentation:  0
  testserver, shell, dbshell |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by aaugustin):

 You can use pdb in tests.

-- 
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:  Accepted
  Forms GB   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  1|
-+-

Comment (by aaugustin):

 While I appreciate the effort that went into this patch, I'm surprised by
 how deep it goes into the territory of specialized validation and
 formatting tools such as [https://github.com/daviddrysdale/python-
 phonenumbers phonenumbers]. I don't know any local phone number field with
 such minute validation in Django.

 I'm not against this patch — especially given the BDFL's plan to split
 localflavor and rely on national communities for maintenance. I'm just
 pointing out a possible mismatch with user expectations regarding
 localflavor.

-- 
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] #12728: loadata/flush issues given GenericRelation, model inheritance and postgres

[Django]

#12728: loadata/flush issues given GenericRelation, model inheritance and 
postgres
-+-
 Reporter:  pragmar  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  master
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
  psycopg2.ProgrammingError, |  Patch needs improvement:  0
  GenericRelation|UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by lorinh):

 My original pull request was against the wrong branch in the django
 repository. This new pull request is against the master branch:
 https://github.com/django/django/pull/408

-- 
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] #18998: Removing an authentication backend that's cached in a user's session causes exception

[Django]

#18998: Removing an authentication backend that's cached in a user's session 
causes
exception
-+-
 Reporter:  Bradley Ayers|Owner:
 |  mhaligowski
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  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
-+-
Changes (by mhaligowski):

 * owner:  nobody => mhaligowski


-- 
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] #7857: manage.py shell, dbshell funtionality

[Django]

#7857: manage.py shell, dbshell funtionality
-+-
 Reporter:  Sanha|Owner:  marclurr
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  manage.py,   |  Needs documentation:  0
  testserver, shell, dbshell |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by sjl@…):

 It is useful to explore fixtures in the interactive shell, otherwise you
 are reduced to printf-style debugging in the test case.

-- 
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] #16594: Missing altitude (z) on Point on admin interface for geodjango

[Django]

#16594: Missing altitude (z) on Point on admin interface for geodjango
+
 Reporter:  info@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  1.3
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 I'd be interested to hear from tests with the attached patch. GEOS 3.3 is
 still required to have 3D WKTs.

-- 
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] #18919: GEOSGeometry transform method is dropping Z attribute on 3D geometries

[Django]

#18919: GEOSGeometry transform method is dropping Z attribute on 3D geometries
---+
 Reporter:  luizvital  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  GIS|  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"ffdd6595ea2220f8e8a6fb3aacd3213b751d982f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ffdd6595ea2220f8e8a6fb3aacd3213b751d982f"
 Fixed #18919 -- Stopped dropping Z attribute when transforming geometries

 Previously, the wkb of geometries was dropping the Z attribute.
 Thanks luizvital for the report and tests and georger.si...@gmail.com
 for the tests.
 }}}

-- 
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] ffdd65: Fixed #18919 -- Stopped dropping Z attribute when ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ffdd6595ea2220f8e8a6fb3aacd3213b751d982f
  
https://github.com/django/django/commit/ffdd6595ea2220f8e8a6fb3aacd3213b751d982f
  Author: Claude Paroz 
  Date:   2012-09-29 (Sat, 29 Sep 2012)

  Changed paths:
M django/contrib/gis/geos/geometry.py
M django/contrib/gis/geos/prototypes/io.py
M django/contrib/gis/geos/tests/test_geos.py
M django/contrib/gis/tests/geo3d/tests.py
M docs/ref/contrib/gis/geos.txt
M docs/releases/1.5.txt

  Log Message:
  ---
  Fixed #18919 -- Stopped dropping Z attribute when transforming geometries

Previously, the wkb of geometries was dropping the Z attribute.
Thanks luizvital for the report and tests and georger.si...@gmail.com
for the tests.



-- 
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] 82a74d: Used TransactionTestCase in ModWsgiHandlerTestCase

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 82a74dce243935688f4f9cd447521d4d141c563b
  
https://github.com/django/django/commit/82a74dce243935688f4f9cd447521d4d141c563b
  Author: Claude Paroz 
  Date:   2012-09-29 (Sat, 29 Sep 2012)

  Changed paths:
M django/contrib/auth/tests/handlers.py

  Log Message:
  ---
  Used TransactionTestCase in ModWsgiHandlerTestCase

Now the data created in setUp() is not discarded when the connection
is closed in the handler's methods.



-- 
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:  Accepted
  Forms GB   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  1|
-+-

Comment (by g1smd):

 The only constraint I placed was "make it look something like a UK phone
 number". Most people are aware that UK numbers are entered as 2+8, 3+7,
 4+6 or 5+5 for 10 digit numbers or 3+6, 4+5 or 5+4 for 9 digit numbers,
 but not many people are aware of which format goes with which area code.
 The RegEx here allows any of those formats with any number and various
 punctuation options. Numbers can, of course, be entered with no spaces or
 punctuation at all.

 Merely checking the number of digits in the NSN part would allow people to
 enter

 (011)-(44)-(0)-(((2 -(- 0)-((---)))()()()--5-   --3  (---4() --0--
 )))((2)(()- )3)))3--   7

 and that number still be accepted. Do you really want that? There's a
 point at which the user input should be rejected as garbage.

-- 
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:  Accepted
  Forms GB   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  1|
-+-

Comment (by g1smd):

 There's a good chance that someone entering that number in that format is
 entering a number from Belguim, not the UK. Spacing only matters when it's
 something that doesn't even look like a UK number.

-- 
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] #11948: Linear referencing for Django

[Django]

#11948: Linear referencing for Django
-+
 Reporter:  novalis  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"2f6e00a840176f95c836f25a41cc1a7d31941ba5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2f6e00a840176f95c836f25a41cc1a7d31941ba5"
 Fixed #11948 -- Added interpolate and project linear referencing methods

 Thanks novalis for the report and the initial patch, and Anssi
 Kääriäinen and Justin Bronn for the 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 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] 2f6e00: Fixed #11948 -- Added interpolate and project line...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2f6e00a840176f95c836f25a41cc1a7d31941ba5
  
https://github.com/django/django/commit/2f6e00a840176f95c836f25a41cc1a7d31941ba5
  Author: Claude Paroz 
  Date:   2012-09-29 (Sat, 29 Sep 2012)

  Changed paths:
M django/contrib/gis/geos/geometry.py
M django/contrib/gis/geos/prototypes/topology.py
M django/contrib/gis/geos/tests/test_geos.py
M docs/ref/contrib/gis/geos.txt
M docs/releases/1.5.txt

  Log Message:
  ---
  Fixed #11948 -- Added interpolate and project linear referencing methods

Thanks novalis for the report and the initial patch, and Anssi
Kääriäinen and Justin Bronn for the review.



-- 
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:  Accepted
  Forms GB   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  1|
-+-

Comment (by andrewgodwin):

 Alright, spacing does matter - while my london example works due to the
 other area code rules, this does not: '014 153 455 67'.

 Over-validation is as bad as no validation - I'm happy to accept a patch
 that checks the number ranges but having the format hard-enforced like
 this is just going to annoy 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.