date:20131023

Re: [Django] #21315: Possible Error in Tutorial pt. 3

2013-10-23 Thread Django

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

Comment:

The tutorial is correct as written. You've using the wrong version of the
tutorial.

The documentation currently defaults to Django 1.5; you've logged the fact
that you are using Django 1.4.

Django 1.5 marked the point at which a subtle change in URL tag syntax was
interpreted; that syntax change was introduced slowly over a series of
releases. However, it does mean that it's important that you use the
version of the tutorial that matches your Django install.

You can address the problem by either following the tutorial that matches
your installed version:

https://docs.djangoproject.com/en/1.4/intro/tutorial03/

or updating your Django install to Django 1.5.

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

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

[Django] #21315: Possible Error in Tutorial pt. 3

2013-10-23 Thread Django

#21315: Possible Error in Tutorial pt. 3
---+
Reporter: andy@… | Owner: nobody
Type: Bug| Status: new
Component: Documentation |Version: 1.4
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
Hello, I just lost about 30 minutes chasing down an error while walking
through the tutorial. It's on the very last part of pt. 3 involving
namespacing. (See pt 3 here:
https://docs.djangoproject.com/en/1.5/intro/tutorial03/)

It says to change the line to this:

However, I was getting an error message: u"'polls" is not a registered
namespace

After some googling, it looks like others are having the same trouble, and
I was able to fix it by instead changing the line in question to this:

I'm only a beginner and am not familiar enough to have any clue why this
makes a difference.

If there's any other information I can provide, feel free to let me know.

Thanks
Andy

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

[django/django] 8688f0: Fixed #20945 -- Allowed cache tag to use a specifi...

2013-10-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8688f03eef9cf5fd763ba35481ddcff933a60c30
  
https://github.com/django/django/commit/8688f03eef9cf5fd763ba35481ddcff933a60c30
  Author: Curtis Maloney 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M django/templatetags/cache.py
M docs/releases/1.7.txt
M docs/topics/cache.txt
M tests/template_tests/tests.py

  Log Message:
  ---
  Fixed #20945 -- Allowed cache tag to use a specific cache.



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

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

2013-10-23 Thread Django

#20945: Allow cache tag to use specified cache config.
-+
 Reporter:  FunkyBob |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Template system  |  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 Tim Graham ):

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


Comment:

 In [changeset:"8688f03eef9cf5fd763ba35481ddcff933a60c30"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8688f03eef9cf5fd763ba35481ddcff933a60c30"
 Fixed #20945 -- Allowed cache tag to use a specific cache.
 }}}

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

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

Re: [Django] #9523: Restart runserver after translation MO files change

2013-10-23 Thread Django

#9523: Restart runserver after translation MO files change
--+
 Reporter:  wim@… |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  1.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * needs_tests:  0 => 1


Comment:

 I've left some comments on the [https://github.com/django/django/pull/1799
 rebased PR]. I'd like to see this tested in some way -- based on the
 coverage report, none of django/utils/autoreload.py is tested.

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

Re: [Django] #21314: Feature request: allow renaming of fields in dicts returned by ValuesQuerySet via kwargs

2013-10-23 Thread Django

#21314: Feature request: allow renaming of fields in dicts returned by
ValuesQuerySet via kwargs
-+-
 Reporter:  chris@…  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  duplicate
 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
-+-
Changes (by timo):

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


Comment:

 Duplicate of #16735

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

[django/django] 3a46f6: [1.4.x] Bumped release date for 1.5.5 & 1.4.9.

2013-10-23 Thread GitHub

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 3a46f621fe376c9fac59fd980b9c58100bcdf47c
  
https://github.com/django/django/commit/3a46f621fe376c9fac59fd980b9c58100bcdf47c
  Author: Tim Graham 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M docs/releases/1.4.9.txt

  Log Message:
  ---
  [1.4.x] Bumped release date for 1.5.5 & 1.4.9.

Backport of 4ce5c119b5 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/52684e0c46b27_32691321d50209556%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 4ce5c1: Bumped release date for 1.5.5 & 1.4.9.

2013-10-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4ce5c119b5a6109058500e207333cc6889d78abe
  
https://github.com/django/django/commit/4ce5c119b5a6109058500e207333cc6889d78abe
  Author: Tim Graham 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M docs/releases/1.4.9.txt
M docs/releases/1.5.5.txt

  Log Message:
  ---
  Bumped release date for 1.5.5 & 1.4.9.



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

[django/django] bc62a2: [1.6.x] Bumped release date for 1.5.5 & 1.4.9.

2013-10-23 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: bc62a20a3eff77435ad51eabc29dc231063b4c36
  
https://github.com/django/django/commit/bc62a20a3eff77435ad51eabc29dc231063b4c36
  Author: Tim Graham 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M docs/releases/1.4.9.txt
M docs/releases/1.5.5.txt

  Log Message:
  ---
  [1.6.x] Bumped release date for 1.5.5 & 1.4.9.

Backport of 4ce5c119b5 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/52684dfc29fbe_3c82a5dd54122674%40hookshot-fe5-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] f57134: [1.5.x] Bumped release date for 1.5.5 & 1.4.9.

2013-10-23 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: f571345ef795d28fbe8aa7e6291a77fe372f3cf8
  
https://github.com/django/django/commit/f571345ef795d28fbe8aa7e6291a77fe372f3cf8
  Author: Tim Graham 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M docs/releases/1.4.9.txt
M docs/releases/1.5.5.txt

  Log Message:
  ---
  [1.5.x] Bumped release date for 1.5.5 & 1.4.9.

Backport of 4ce5c119b5 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/52684df82852a_38211417d5416512f%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19941: Make running django's test suite easier

2013-10-23 Thread Django

#19941: Make running django's test suite easier
--+
 Reporter:  akaariai  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Testing framework |  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 Tim Graham ):

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


Comment:

 In [changeset:"c573d6de173c0e6743473081cde786e749641a48"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c573d6de173c0e6743473081cde786e749641a48"
 Fixed #19941 -- Removed sys.path hack when running the test suite.

 Thanks jezdez for the suggestion.
 }}}

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

[django/django] c573d6: Fixed #19941 -- Removed sys.path hack when running...

2013-10-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c573d6de173c0e6743473081cde786e749641a48
  
https://github.com/django/django/commit/c573d6de173c0e6743473081cde786e749641a48
  Author: Tim Graham 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M docs/internals/contributing/writing-code/unit-tests.txt
M tests/runtests.py

  Log Message:
  ---
  Fixed #19941 -- Removed sys.path hack when running the test suite.

Thanks jezdez for the suggestion.



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

[Django] #21314: Feature request: allow renaming of fields in dicts returned by ValuesQuerySet via kwargs

2013-10-23 Thread Django

#21314: Feature request: allow renaming of fields in dicts returned by
ValuesQuerySet via kwargs
--+
 Reporter:  chris@…   |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 It would be convenient to be able to rename the fields returned by
 ValuesQuerySet by passing keyword arguments to QuerySet.values(), e.g.
 {{{
 >>> Foo.objects.all().values('id', 'bar__name')
 [{'id': 1, 'bar__name': 'Bar'}]

 >>> Foo.objects.all().values('id', bar__name='name')
 [{'id': 1, 'name': 'Bar'}]
 }}}
 I think using extra(select=...) and values() can achieve this but with
 significant verbosity.

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

[django/django] 5ab8b5: Fix migration planner to fully understand squashed...

2013-10-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5ab8b5d72c5277833908bc57b0765682e5aadc0b
  
https://github.com/django/django/commit/5ab8b5d72c5277833908bc57b0765682e5aadc0b
  Author: Andrew Godwin 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M django/db/migrations/executor.py
M django/db/migrations/loader.py
M django/db/migrations/migration.py
M tests/migrations/test_executor.py
M tests/migrations/test_loader.py
A tests/migrations/test_migrations_squashed/0001_initial.py
A tests/migrations/test_migrations_squashed/0001_squashed_0002.py
A tests/migrations/test_migrations_squashed/0002_second.py
A tests/migrations/test_migrations_squashed/__init__.py

  Log Message:
  ---
  Fix migration planner to fully understand squashed migrations. And test.



-- 
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/52684659dc223_32691321d502050a9%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-10-23 Thread Django

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

 * cc: schacki (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/073.86c2a637e0102f52665e126faf3c564c%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-10-23 Thread Django

Comment (by schacki):

I have changed the code as follows:
1. Refactored the got_request_exception handling into
handle_uncaught_exception. This makes to code much cleaner and the process
more transparent
2. The inital exception, that triggered the handle_uncaught_exception is
the main focus. I.e. this exception is logged first, this exception is
raised if settings.DEBUG_PROPAGATE_EXCEPTIONS is True. This makes
debugging and analyzing the root cause of all the trouble much easier
(which was one of the reasons, why this ticket was raised), nevertheless
all follow-up errors are still logged.
3. Implemented proposal from ptone, to make the resolve500 more robust.
4. Commented the code in handle_uncaugh_exception to make the process and
ideas behind it more transparent.

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

Re: [Django] #21274: django-admin's --template option fails to download from https via proxy

2013-10-23 Thread Django

Comment (by blueyed):

I have not investigated much into fixing this - I stopped when I arrived
at the Python2/3-compatibility layer (django.utils.six).

I have fixed some proxy issue in an urllib based Python program before
(IIRC), but cannot provide a fix here.

I agree that downloading the file via wget and/or disabling the https
proxy is a good enough workaround. But I also believe that there should be
a more descriptive error, instead of just a traceback and "File is not a
zip file".
"

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

Re: [Django] #21170: Clearing DatabseCache doesn't work with Oracle backend.

2013-10-23 Thread Django

#21170: Clearing DatabseCache doesn't work with Oracle backend.
-+-
 Reporter:  mmmnow@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:   |   Resolution:  needsinfo
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  1|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by shai):

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


Comment:

 So we're not fixing for pre-1.6; and there seems to be no problem for 1.6
 and up.

 If anyone sees a problem, or even wants to add a test for 1.6, feel free
 to reopen.

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

Re: [Django] #21313: load tag before extends

2013-10-23 Thread Django

#21313: load tag before extends
---+--
 Reporter:  ztorstri@… |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by ztorstri@…):

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


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

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

[Django] #21313: load tag before extends

2013-10-23 Thread Django

#21313: load tag before extends
---+
Reporter: ztorstri@… | Owner: nobody
Type: New feature| Status: new
Component: Uncategorized |Version: 1.5
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
I'd like to be able to load a template tag before extends. I don't want to
use a context processor because I don't want every view that uses
RequestContext to get the variable. Here's the detailed situation:

I'm designing an app, and I want the "base.html" template to be a
configurable in the settings file. So a user downloads my application,
goes to the settings file, adds the setting
"BASE_TEMPLATE_NAME=somestring", and then all of my templates
automatically inherit this base template.

If I use a context processor, then every other page on their site that
uses RequestContext will get this variable as well. I tried to use a
template tag to return the base template setting, but I can't put anything
before extends.

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

Re: [Django] #16436: `annotate()` + `select_related()` + `only()` = `ValueError: invalid literal for int() with base 10`

2013-10-23 Thread Django

#16436: `annotate()` + `select_related()` + `only()` = `ValueError: invalid 
literal
for int() with base 10`
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  annotate |  Needs documentation:  0
  select_related only defer  |  Patch needs improvement:  1
  ValueError empty list  |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by shai):

 For anyone else who might be confused at first: [comment:15 Anssi]
 backported the fix to the problem, [comment:16 Tim] backported the fix to
 the test on Oracle.

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

Re: [Django] #21182: Extra Column in Group By When Using date_trunc

2013-10-23 Thread Django

#21182: Extra Column in Group By When Using date_trunc
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  needsinfo
 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 shai):

 For anyone who looks at this later:

 The query produced includes `ORDER BY "finance_transaction"."date" DESC`,
 which hints that the user's Transaction model has a meta
 `ordering=["-date"]`; if this is the case, the date field is
 '''correctly''' added to the group-by, to allow this ordering. Ordering by
 month instead should solve 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/067.6ade563ff731db9a023c02672a5de663%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21312: models.DateTimeField with default=now: South migration fails

2013-10-23 Thread Django

#21312: models.DateTimeField with default=now: South migration fails
-+-
 Reporter:  magopian |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-beta-1
 Severity:  Normal   |   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):

 * component:  Uncategorized => Database layer (models, ORM)
 * severity:  Release blocker => Normal


Comment:

 Based on Anssi's analysis, this is not a blocker for Django. Not sure it
 is even a bug in Django.

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

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

Re: [Django] #15760: Feature: JS Hooks for Dynamic Inlines

2013-10-23 Thread Django

#15760: Feature: JS Hooks for Dynamic Inlines
-+-
 Reporter:  mlavin   |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  inlines jquery   | Triage Stage:  Accepted
  callback   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by gstrat):

 * cc: gstrat (added)


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

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

[django/django] 4cfbde: Fixed #12027 -- Fixed EmailValidator to reject a t...

2013-10-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4cfbde71a33973cb8c8da406b2523dfc742358e7
  
https://github.com/django/django/commit/4cfbde71a33973cb8c8da406b2523dfc742358e7
  Author: Tim Graham 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M django/core/validators.py
M tests/validators/tests.py

  Log Message:
  ---
  Fixed #12027 -- Fixed EmailValidator to reject a trailing dot.

Thanks Klas H for the report and claudep for the patch.



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

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

2013-10-23 Thread Django

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

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


Comment:

 In [changeset:"4cfbde71a33973cb8c8da406b2523dfc742358e7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4cfbde71a33973cb8c8da406b2523dfc742358e7"
 Fixed #12027 -- Fixed EmailValidator to reject a trailing dot.

 Thanks Klas H for the report and claudep for the patch.
 }}}

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

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

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

2013-10-23 Thread Django

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

 * stage:  Accepted => Ready for checkin


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

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

2013-10-23 Thread Django

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

Comment (by timo):

 And now a version that modifies the regex. Thanks @claudep

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

Re: [Django] #21311: Issues using mySQL on OS X in the tutorial

2013-10-23 Thread Django

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

Comment:

Looks like you had a pretty good experience with the tutorial. I've read
your blog post and I'll leave some more specific comments there about some
of the little issues you had.

We try to keep our tutorial as a tutorial for Django, rather than a
tutorial for python. Things like `pip` and `PYTHONPATH` aren't really the
domain of our tutorial, so we try to just give enough information to make
things work and keep it moving so people actually see a website. People do
the tutorial from a huge range of backgrounds - if you were an experienced
rails developer you'd very quickly go "ok, pip is gem for python" and move
on - similarly npm in node and so on.

One comment you made in your blog with was very salient was about the
"done any work" - I think that comment could be improved to "you haven't
actually built a site yet".

|n any case, I'm going to close this ticket - if you feel strongly about
the "done any work" comment feel free to open a new one specifically about
that (and provide a 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/074.d58a7fcb31442e088b956ec0c562e418%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21311: Issues using mySQL on OS X in the tutorial

2013-10-23 Thread Django

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

Comment:

Thanks for your feedback, it's helpful to get feedback from people who are
new to Django. I think most of the issues you've raised are either
Operating System specific (environment variables) or concepts that should
be taught in a Python tutorial (PYTHONPATH). Django assumes some basic
knowledge of Python and related concepts -- we can't reasonably expect to
teach everything. Knowing that, if you can propose some specific text, we
could consider it. Also, if you report a ticket in the future, please try
to report one issue per ticket. Thank-you!

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

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

Re: [Django] #21312: models.DateTimeField with default=now: South migration fails

2013-10-23 Thread Django

#21312: models.DateTimeField with default=now: South migration fails
-+--
 Reporter:  magopian |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:  1.6-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by akaariai):

 I've taken a quick look at this. This was introduced by
 ddff6522fa72aacc7475ba5cd4bf8683ff12b8c7. The problem is that South
 doesn't assign the field to any model. In Django self.model should always
 exists (or at least always after app-loading).

 I am not sure if this should be fixed in Django or in South. We can
 definitely say that South relies on non-public usage of fields (after all
 the only public way to use fields is to assign them to models in model
 definition, and that means they will have self.model set). OTOH it seems
 pretty simple to fix this in Django... I have generally favoured "private
 API is private" -approach, so I am slightly in favour of that
 interpretation.

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

Re: [Django] #21312: models.DateTimeField with default=now: South migration fails

2013-10-23 Thread Django

#21312: models.DateTimeField with default=now: South migration fails
-+--
 Reporter:  magopian |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:  1.6-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by mjtamlyn):

 * needs_better_patch:   => 0
 * version:  1.4 => 1.6-beta-1
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 I haven't checked this but marking as a release block as assuming it is
 repeatable it certainly is a problem.

 Do you perhaps have a minimal project set up to reproduce this? If not,
 could you perhaps try to use `git bisect` to identify where between the
 tags it broke? This would help us identify a fix faster.

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

[django/django] d72059: typo on 1.7 release notes

2013-10-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d72059c2ae2753ee7d7e0ba8e684ed3d04909e53
  
https://github.com/django/django/commit/d72059c2ae2753ee7d7e0ba8e684ed3d04909e53
  Author: Collin Anderson 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  typo on 1.7 release notes


  Commit: efb05978b36ef6eeb02f47b7c58b138d089d581a
  
https://github.com/django/django/commit/efb05978b36ef6eeb02f47b7c58b138d089d581a
  Author: Alex Gaynor 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  Merge pull request #1801 from collinanderson/patch-10

typo in 1.7 release notes


Compare: https://github.com/django/django/compare/c3aa2948c6c1...efb05978b36e

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

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

2013-10-23 Thread Django

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

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


Comment:

 Here's a simple patch that avoids messing with the regex. Perhaps it's
 good enough.

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

Re: [Django] #21142: Cannot run migrations that reference django.contrib.auth.models.User

2013-10-23 Thread Django

#21142: Cannot run migrations that reference django.contrib.auth.models.User
-+
 Reporter:  mario.pfeifer@…  |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  Migration, Auth  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by timo):

 From Andrew on IRC: "My plan was that contrib apps would ship with
 migrations. Specifically, I'd like to ship auth with some straight in 1.7.
 Initial fake migrations will be handled by the new framework directly."

 So this bug should be fixed in due time before the 1.7 release. Thanks for
 your patience.

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

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

[Django] #21312: models.DateTimeField with default=now: South migration fails

2013-10-23 Thread Django

#21312: models.DateTimeField with default=now: South migration fails
---+
 Reporter:  magopian   |  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
---+
 This is a problem that didn't happen on django1.6b4, but does on
 django1.6c1:

 Here's a snippet of the model:


 {{{
 from django.utils.timezone import now


 @python_2_unicode_compatible
 class User(AbstractBaseUser, PermissionsMixin):
 """TopChretien User, identified by its email."""
 ...
 last_modified = models.DateTimeField(
 _('last modification'), default=now, editable=False)
 ...
 }}}

 Here's the auto migration created by South when adding this new field to
 the model:

 {{{
 import datetime
 ...

 class Migration(SchemaMigration):

 def forwards(self, orm):
 # Adding field 'User.last_modified'
 db.add_column(u'user_user', 'last_modified',
 
self.gf('django.db.models.fields.DateTimeField')(default=datetime.datetime.now),
   keep_default=False)
 }}}

 And here's the result of running "manage.py migrate user" on django1.6b4:

 {{{
 $ ./manage.py migrate user
 Running migrations for user:
  - Migrating forwards to
 0007_auto__add_field_user_last_modified__add_field_user_moderation_date__ad.
  >
 
user:0007_auto__add_field_user_last_modified__add_field_user_moderation_date__ad
 /home/mathieu/.virtualenvs/top/lib/python2.7/site-
 packages/django/db/models/fields/__init__.py:901: RuntimeWarning:
 DateTimeField received a naive datetime (2013-10-23 15:50:11.448018) while
 time zone support is active.
   RuntimeWarning)

  - Loading initial data for user.
 Installed 0 object(s) from 0 fixture(s)
 }}}

 And now on django1.6c1 (only the end of stacktrace, for readability,
 please let me know if you need more):

 {{{
   File
 
"/home/mathieu/Dropbox/dev/topchretien/web/topchretien/user/migrations/0007_auto__add_field_user_moderation_date__add_field_user_moderator__add_fi.py",
 line 14, in forwards
 keep_default=False)
   File "/home/mathieu/.virtualenvs/top/lib/python2.7/site-
 packages/south/db/generic.py", line 47, in _cache_clear
 return func(self, table, *args, **opts)
   File "/home/mathieu/.virtualenvs/top/lib/python2.7/site-
 packages/south/db/generic.py", line 411, in add_column
 sql = self.column_sql(table_name, name, field)
   File "/home/mathieu/.virtualenvs/top/lib/python2.7/site-
 packages/south/db/generic.py", line 706, in column_sql
 default = field.get_db_prep_save(default,
 connection=self._get_connection())
   File "/home/mathieu/.virtualenvs/top/lib/python2.7/site-
 packages/django/db/models/fields/__init__.py", line 350, in
 get_db_prep_save
 prepared=False)
   File "/home/mathieu/.virtualenvs/top/lib/python2.7/site-
 packages/django/db/models/fields/__init__.py", line 911, in
 get_db_prep_value
 value = self.get_prep_value(value)
   File "/home/mathieu/.virtualenvs/top/lib/python2.7/site-
 packages/django/db/models/fields/__init__.py", line 902, in get_prep_value
 (self.model.__name__, self.name, value),
 AttributeError: 'DateTimeField' object has no attribute 'model'
 }}}


 The solution I used was to modify the South migration to get rid of the
 warning (in Django1.6b4) and make it work correctly (in django1.6c1):

 {{{
 import django.utils.timezone
 ...

 class Migration(SchemaMigration):

 def forwards(self, orm):
 # Adding field 'User.last_modified'
 db.add_column(u'user_user', 'last_modified',
 
self.gf('django.db.models.fields.DateTimeField')(default=django.utils.timezone.now),
   keep_default=False)
 }}}

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

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

Re: [Django] #21299: verbose_name inconsistently capitalized in admin inlines

2013-10-23 Thread Django

#21299: verbose_name inconsistently capitalized in admin inlines
+
 Reporter:  renatooliveira  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  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:  0   |UI/UX:  0
+

Comment (by renatooliveira):

 I sent a pull request, but I don't know how to test this.

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

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

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

Re: [Django] #21310: Admin recent actions section doesn't show content with settings.AUTH_USER_MODEL

2013-10-23 Thread Django

#21310: Admin recent actions section doesn't show content with
settings.AUTH_USER_MODEL
+--
Reporter: franklin.steve02@… |Owner: nobody
Type: Bug | Status: closed
Component: contrib.admin | Version: 1.4
Severity: Normal | Resolution: worksforme
Keywords: admin event log | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 |UI/UX: 0
+--
Changes (by timo):

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

Comment:

I'm unable to reproduce using this example custom user package here:
https://github.com/jonathanchu/django-custom-user-example

I added a Group in the admin and then was able to see that listed under
"Recent Actions" on /admin/.

The code looks correct as it is -- you specify the name of a foreign key
to follow when using `select_related`. The FK attribute on `LogEntry` is
named `user`.

Please reopen if you can provide more details with steps to 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 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.42565a43ebb6065f917d294cdd6bfcd1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

2013-10-23 Thread Django

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

Comment (by olau):

 We just had an SMTP exception from Exim because a user managed to enter
 his email address with a trailing dot. Probably he copied it from
 somewhere with a period at the end. This echoes what Josh C said, but I
 just want to confirm that Django's behaviour in this case caused us a real
 problem, so yeah, this is a genuine bug.

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

Re: [Django] #21271: Django's usage of smtplib.SMTP should have a timeout

2013-10-23 Thread Django

#21271: Django's usage of smtplib.SMTP should have a timeout
--+
 Reporter:  edevil|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Mail)   |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  smtp timeout  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 The patch needs improvement per the comments on the pull request.

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

Re: [Django] #21271: Django's usage of smtplib.SMTP should have a timeout

2013-10-23 Thread Django

#21271: Django's usage of smtplib.SMTP should have a timeout
--+
 Reporter:  edevil|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Mail)   |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  smtp timeout  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by edevil):

 Any news on this? There is a patch available with 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 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.92b358131c69f6c34bd5be986a8b8ae8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] c3aa29: Fixed #21298 -- Fixed E301 pep8 warnings

2013-10-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c3aa2948c6c14862407501290571f858ccf45b07
  
https://github.com/django/django/commit/c3aa2948c6c14862407501290571f858ccf45b07
  Author: Alasdair Nicol 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M django/contrib/auth/tests/test_hashers.py
M django/contrib/auth/tests/test_tokens.py
M django/contrib/formtools/tests/wizard/wizardtests/tests.py
M django/contrib/gis/admin/widgets.py
M django/contrib/gis/db/backends/oracle/models.py
M django/contrib/gis/db/backends/postgis/operations.py
M django/contrib/gis/db/backends/spatialite/operations.py
M django/contrib/gis/db/models/sql/conversion.py
M django/contrib/gis/forms/widgets.py
M django/contrib/gis/gdal/prototypes/generation.py
M django/contrib/gis/geos/mutable_list.py
M django/contrib/gis/geos/tests/test_geos.py
M django/contrib/gis/geos/tests/test_mutable_list.py
M django/contrib/gis/tests/inspectapp/tests.py
M django/contrib/gis/tests/test_geoforms.py
M django/contrib/messages/storage/cookie.py
M django/contrib/sitemaps/tests/test_http.py
M django/core/files/move.py
M django/db/migrations/graph.py
M django/db/migrations/recorder.py
M django/forms/formsets.py
M django/forms/models.py
M django/forms/widgets.py
M django/template/defaultfilters.py
M django/test/utils.py
M django/utils/decorators.py
M django/utils/feedgenerator.py
M django/utils/html.py
M django/utils/six.py
M django/utils/text.py
M setup.cfg
M tests/admin_scripts/complex_app/models/bar.py
M tests/admin_scripts/complex_app/models/foo.py
M tests/admin_scripts/tests.py
M tests/admin_validation/tests.py
M tests/admin_views/models.py
M tests/basic/tests.py
M tests/cache/tests.py
M tests/custom_pk/models.py
M tests/decorators/tests.py
M tests/defaultfilters/tests.py
M tests/delete/tests.py
M tests/delete_regress/tests.py
M tests/deprecation/tests.py
M tests/expressions/tests.py
M tests/file_storage/tests.py
M tests/fixtures/models.py
M tests/forms_tests/tests/test_extra.py
M tests/forms_tests/tests/test_fields.py
M tests/forms_tests/tests/test_forms.py
M tests/forms_tests/tests/test_media.py
M tests/forms_tests/tests/test_widgets.py
M tests/generic_relations_regress/tests.py
M tests/generic_views/views.py
M tests/inspectdb/tests.py
M tests/lookup/models.py
M tests/middleware/tests.py
M tests/migrations/test_operations.py
M tests/migrations/test_state.py
M tests/model_forms/models.py
M tests/model_forms/tests.py
M tests/model_forms_regress/tests.py
M tests/model_formsets/tests.py
M tests/model_inheritance_regress/models.py
M tests/modeladmin/tests.py
M tests/one_to_one/tests.py
M tests/ordering/models.py
M tests/queries/tests.py
M tests/requests/tests.py
M tests/select_for_update/tests.py
M tests/select_related/models.py
M tests/serializers_regress/models.py
M tests/tablespaces/models.py
M tests/template_tests/test_callables.py
M tests/template_tests/test_parser.py
M tests/template_tests/test_response.py
M tests/template_tests/tests.py
M tests/test_client_regress/tests.py
M tests/transactions_regress/tests.py
M tests/update_only_fields/tests.py
M tests/utils_tests/test_functional.py
M tests/validators/tests.py
M tests/wsgi/tests.py

  Log Message:
  ---
  Fixed #21298 -- Fixed E301 pep8 warnings



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

Re: [Django] #21298: pep8 cleanup: expected 1 blank line, found 0

2013-10-23 Thread Django

#21298: pep8 cleanup: expected 1 blank line, found 0
--+
 Reporter:  timo  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  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:  1 |UI/UX:  0
--+
Changes (by Alasdair Nicol ):

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


Comment:

 In [changeset:"c3aa2948c6c14862407501290571f858ccf45b07"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c3aa2948c6c14862407501290571f858ccf45b07"
 Fixed #21298 -- Fixed E301 pep8 warnings
 }}}

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

Re: [Django] #21298: pep8 cleanup: expected 1 blank line, found 0

2013-10-23 Thread Django

#21298: pep8 cleanup: expected 1 blank line, found 0
--+
 Reporter:  timo  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 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 alasdair):

 Pull request https://github.com/django/django/pull/1798

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

[Django] #21311: Issues using mySQL on OS X in the tutorial

2013-10-23 Thread Django

At first a big thank you for the great tutorial. I started a point zero
and now I got some nice app working (only in local lightweight webserver
deployment). When I started the tutorial I wanted to use it with mySQL
which was already installed on my machine. But for some reason it did not
work (i keep trying to fix this issue but still have no clue until now).

I have extensively documented my experience with the tutorial (as newbie
to both, python & django) here:
http://www.thetawelle.de/?p=3047

One part which always really gets into the way of making things work
smoothly is that the importance of UNIX environment vars is completely
left in the dark. That is not any different on this tutorial. I have no
clue which env vars do exist, get used, and how they influence the whole
django/python cosmos.

e.g. what exactly is the "pythonpath"? I mean I know the search paths
which I handle in my bash_profile. It would be so much easier to
understand whats going on, if you could give a little clue about the task
of env vars here. I also think that these env vars are a thing that is not
very well understood by most people.

I mean I am coming from Xcode and Objective-C where I do not have to do a
lot of stuff on the shell. But for python and django the shell is the
natual environment where it lives. A short quickstart on the most
important things of the env vars would be a huge improvment on the
tutorial.

Another helpful improvement would be to explain upfront, what these
installers (like pip) are actually doing. I do not want to know every
single step, but it would be so helpful to know if they are special
binaries, if they are scripts, if in which language, and what kind of
operations they will carry out for me. If I call this stuff via "sudo" I
basically should know about this. I just trusted the installer this time,
but I should have been more careful I think.

Best & thanks already for the nice tutorial,
Helge

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

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

[django/django] 7f5555: [1.6.x] Workaround admin scripts test failures on ...

2013-10-23 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 7fdb2b2c711a2ba66ee586d145d70e1a7609
  
https://github.com/django/django/commit/7fdb2b2c711a2ba66ee586d145d70e1a7609
  Author: Ramiro Morales 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M tests/admin_scripts/tests.py

  Log Message:
  ---
  [1.6.x] Workaround admin scripts test failures on Windows+Python 3.

Change strategy used to examine instrumented output to acommodate the
fact that on Windows, where the path separator is '\', repr() of Python
modules has changed in Python 3 to use escaped backslashes in the FS
path section (e.g.
'C:\\python3x\\Lib\\site-packages\\django\\contrib\\auth\\models.py')
without having to special-case based on platform.

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

Re: [Django] #13245: Document Oracle behavior regarding quoting of database table names

2013-10-23 Thread Django

#13245: Document Oracle behavior regarding quoting of database table names
-+-
 Reporter:  skoom|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  oracle   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by shai):

 Hmm, cherry-picking this was too easy... I forgot to add branch prefixes
 to the header line.

 6de3726423b8df4fb8ab05caa109a8c6308e6060 is for 1.4.x
 cc0dcfc64405419d95e87c8dcc612bd441a8d6de is for 1.5.x
 27f3f341369c8e18ea4a360a1f7c01531836b68b is for 1.6.x
 317040a73b77be8f8210801793b2ce6d1a69301e is for 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/063.feb063f18b53cac366f94cf93de2a976%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13245: Document Oracle behavior regarding quoting of database table names

2013-10-23 Thread Django

#13245: Document Oracle behavior regarding quoting of database table names
-+-
 Reporter:  skoom|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  oracle   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Shai Berger ):

 In [changeset:"317040a73b77be8f8210801793b2ce6d1a69301e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="317040a73b77be8f8210801793b2ce6d1a69301e"
 Fixed #13245: Explained Oracle's behavior w.r.t db_table
 and how to prevent table-name truncation

 Thanks russellm & timo for discussion, and timo for 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/063.9fa792914a4da6124981d29caca8247f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13245: Document Oracle behavior regarding quoting of database table names

2013-10-23 Thread Django

#13245: Document Oracle behavior regarding quoting of database table names
-+-
 Reporter:  skoom|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  oracle   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Shai Berger ):

 In [changeset:"27f3f341369c8e18ea4a360a1f7c01531836b68b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="27f3f341369c8e18ea4a360a1f7c01531836b68b"
 Fixed #13245: Explained Oracle's behavior w.r.t db_table
 and how to prevent table-name truncation

 Thanks russellm & timo for discussion, and timo for review.

 Backported from master 317040a73b77be8f8210801793b2ce6d1a69301e
 }}}

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

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

Re: [Django] #13245: Document Oracle behavior regarding quoting of database table names

2013-10-23 Thread Django

#13245: Document Oracle behavior regarding quoting of database table names
-+-
 Reporter:  skoom|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  oracle   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Shai Berger ):

 In [changeset:"cc0dcfc64405419d95e87c8dcc612bd441a8d6de"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cc0dcfc64405419d95e87c8dcc612bd441a8d6de"
 Fixed #13245: Explained Oracle's behavior w.r.t db_table
 and how to prevent table-name truncation

 Thanks russellm & timo for discussion, and timo for review.

 Backported from master 317040a73b77be8f8210801793b2ce6d1a69301e
 }}}

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

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

[django/django] 27f3f3: Fixed #13245: Explained Oracle's behavior w.r.t db...

2013-10-23 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 27f3f341369c8e18ea4a360a1f7c01531836b68b
  
https://github.com/django/django/commit/27f3f341369c8e18ea4a360a1f7c01531836b68b
  Author: Shai Berger 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M docs/ref/databases.txt
M docs/ref/models/options.txt

  Log Message:
  ---
  Fixed #13245: Explained Oracle's behavior w.r.t db_table
and how to prevent table-name truncation

Thanks russellm & timo for discussion, and timo for review.

Backported from master 317040a73b77be8f8210801793b2ce6d1a69301e



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

Re: [Django] #13245: Document Oracle behavior regarding quoting of database table names

2013-10-23 Thread Django

#13245: Document Oracle behavior regarding quoting of database table names
-+-
 Reporter:  skoom|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  oracle   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Shai Berger ):

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


Comment:

 In [changeset:"6de3726423b8df4fb8ab05caa109a8c6308e6060"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6de3726423b8df4fb8ab05caa109a8c6308e6060"
 Fixed #13245: Explained Oracle's behavior w.r.t db_table
 and how to prevent table-name truncation

 Thanks russellm & timo for discussion, and timo for review.

 Backported from master 317040a73b77be8f8210801793b2ce6d1a69301e
 }}}

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

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

[django/django] 6de372: Fixed #13245: Explained Oracle's behavior w.r.t db...

2013-10-23 Thread GitHub

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 6de3726423b8df4fb8ab05caa109a8c6308e6060
  
https://github.com/django/django/commit/6de3726423b8df4fb8ab05caa109a8c6308e6060
  Author: Shai Berger 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M docs/ref/databases.txt
M docs/ref/models/options.txt

  Log Message:
  ---
  Fixed #13245: Explained Oracle's behavior w.r.t db_table
and how to prevent table-name truncation

Thanks russellm & timo for discussion, and timo for review.

Backported from master 317040a73b77be8f8210801793b2ce6d1a69301e



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

[django/django] 317040: Fixed #13245: Explained Oracle's behavior w.r.t db...

2013-10-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 317040a73b77be8f8210801793b2ce6d1a69301e
  
https://github.com/django/django/commit/317040a73b77be8f8210801793b2ce6d1a69301e
  Author: Shai Berger 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M docs/ref/databases.txt
M docs/ref/models/options.txt

  Log Message:
  ---
  Fixed #13245: Explained Oracle's behavior w.r.t db_table
and how to prevent table-name truncation

Thanks russellm & timo for discussion, and timo for review.



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

[django/django] cc0dcf: Fixed #13245: Explained Oracle's behavior w.r.t db...

2013-10-23 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: cc0dcfc64405419d95e87c8dcc612bd441a8d6de
  
https://github.com/django/django/commit/cc0dcfc64405419d95e87c8dcc612bd441a8d6de
  Author: Shai Berger 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M docs/ref/databases.txt
M docs/ref/models/options.txt

  Log Message:
  ---
  Fixed #13245: Explained Oracle's behavior w.r.t db_table
and how to prevent table-name truncation

Thanks russellm & timo for discussion, and timo for review.

Backported from master 317040a73b77be8f8210801793b2ce6d1a69301e



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

Re: [Django] #21306: Fix (or document) lower-casing behavior of title filter

2013-10-23 Thread Django

#21306: Fix (or document) lower-casing behavior of title filter
--+
 Reporter:  timo  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

 * type:  Uncategorized => Cleanup/optimization
 * version:  1.4 => master
 * component:  Template system => Documentation


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

Re: [Django] #21306: Fix (or document) lower-casing behavior of title filter

2013-10-23 Thread Django

#21306: Fix (or document) lower-casing behavior of title filter
-+
 Reporter:  timo |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Template system  |  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 bmispelon):

 * cc: bmispelon@… (added)
 * component:  Uncategorized => Template system
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 That behavior is consistent with python's `str.title` method [1].

 Django's `title` function has two features on top of `str.title`:
 * `title("isn't it") == "Isn't It"` (whereas `"isn't it".title() == "Isn'T
 It`)
 * `title("8foo") == "8foo"` (whereas `"8foo".title() == "8Foo"`)

 I don't think we can fix this particular issue without breaking backwards-
 compatibility so I think documenting it is the best course of action.

 [1]
 http://docs.python.org/2/library/stdtypes.html?highlight=str.title#str.title

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

[django/django] aefc1d: Workaround admin scripts test failures on Windows+...

2013-10-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: aefc1d4e65c04f3fc6863a2e0563957c3b1e726b
  
https://github.com/django/django/commit/aefc1d4e65c04f3fc6863a2e0563957c3b1e726b
  Author: Ramiro Morales 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M tests/admin_scripts/tests.py

  Log Message:
  ---
  Workaround admin scripts test failures on Windows+Python 3.

Change strategy used to examine instrumented output to acommodate the
fact that on Windows, where the path separator is '\', repr() of Python
modules has changed in Python 3 to use escaped backslashes in the FS
path section (e.g.
'C:\\python3x\\Lib\\site-packages\\django\\contrib\\auth\\models.py')
without having to special-case based on platform.



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

[django/django] ae48d7: Fixed E225 pep8 warnings.

2013-10-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ae48d77ef8e14dae76fddcd5a677b897c7c7c4ae
  
https://github.com/django/django/commit/ae48d77ef8e14dae76fddcd5a677b897c7c7c4ae
  Author: Tim Graham 
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
M django/contrib/gis/db/backends/postgis/operations.py
M django/contrib/gis/db/models/proxy.py
M django/contrib/gis/gdal/geomtype.py
M django/contrib/gis/gdal/prototypes/srs.py
M django/contrib/gis/geos/linestring.py
M django/contrib/gis/geos/prototypes/prepared.py
M django/contrib/gis/maps/google/gmap.py
M django/contrib/gis/maps/google/overlays.py
M django/contrib/gis/maps/google/zoom.py
M django/contrib/gis/tests/test_geoforms.py
M django/contrib/gis/tests/test_measure.py
M django/contrib/messages/tests/base.py
M django/contrib/redirects/models.py
M django/contrib/sites/managers.py
M django/core/management/commands/makemessages.py
M django/dispatch/saferef.py
M django/forms/widgets.py
M django/utils/datastructures.py
M django/utils/dateformat.py
M django/utils/datetime_safe.py
M docs/conf.py
M setup.cfg
M tests/admin_inlines/admin.py
M tests/admin_validation/tests.py
M tests/admin_views/admin.py
M tests/admin_widgets/tests.py
M tests/backends/tests.py
M tests/cache/tests.py
M tests/defer/models.py
M tests/dispatch/tests/test_saferef.py
M tests/distinct_on_fields/tests.py
M tests/expressions_regress/tests.py
M tests/forms_tests/tests/test_widgets.py
M tests/i18n/commands/compilation.py
M tests/i18n/commands/extraction.py
M tests/m2m_and_m2o/tests.py
M tests/m2m_through_regress/tests.py
M tests/model_forms/tests.py
M tests/model_inheritance_regress/tests.py
M tests/multiple_database/tests.py
M tests/queries/tests.py
M tests/select_related_regress/tests.py
M tests/validation/tests.py

  Log Message:
  ---
  Fixed E225 pep8 warnings.



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

Re: [Django] #21303: Allow custom link text for urlize filter

2013-10-23 Thread Django

#21303: Allow custom link text for urlize filter
-+-
 Reporter:  dbrgn|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  urlize,  | Triage Stage:
  defaultfilters |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by dbrgn):

 OK, valid point by bmispelon.

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

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

[Django] #21310: Admin recent actions section doesn't show content with settings.AUTH_USER_MODEL

2013-10-23 Thread Django

#21310: Admin recent actions section doesn't show content with
settings.AUTH_USER_MODEL
+-
 Reporter:  franklin.steve02@…  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  contrib.admin   |Version:  1.4
 Severity:  Normal  |   Keywords:  admin event log
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  1   |  UI/UX:  0
+-
 If a custom model is specified in settings (AUTH_USER_MODEL), then the
 query for recent activity always returns no events.

 On some digging I have found the problem to be with the select related in
 the AdminLogNode like;

 context[self.varname] =
 LogEntry.objects.filter(user__id__exact=user_id).select_related('content_type',
 'user')[:self.limit]

 Changing this to settings.AUTH_USER_MODEL as

 context[self.varname] =
 LogEntry.objects.filter(user__id__exact=user_id).select_related('content_type',
 settings.AUTH_USER_MODEL)[:self.limit]

 Actually I believe from the documentation this should be get_user_model()
 but I haven't tested that.

 thanks

 Steve

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

Re: [Django] #21309: Minimum Python version for 1.6?

2013-10-23 Thread Django

#21309: Minimum Python version for 1.6?
---+--
 Reporter:  bouke  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6-beta-1
 Severity:  Normal |   Resolution:  fixed
 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 aaugustin):

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


Comment:

 I've edited the blog post. Thank you.

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

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

62 matches

Mail list logo