[Django] #23526: modelform fields="__all__" equivalence in admin

[Django]

#23526: modelform fields="__all__" equivalence in admin
---+
 Reporter:  hadisunyoto|  Owner:  nobody
 Type:  New feature| Status:  new
Component:  contrib.admin  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Since modelform has fields="__all__" for shortcut, why not add it to admin

--
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/054.52340a5c138086a6d5d9d3618684c9c7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23525: admin/docs/filters|tags __file__ attribute errors for egg extensions

[Django]

#23525: admin/docs/filters|tags __file__ attribute errors for egg extensions
-+-
 Reporter:  welbornprod  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admindocs|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  __file__ | Triage Stage:
  AttributeError filters tags|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Description changed by welbornprod:

Old description:

> Accessing `hostname.com/admin/doc/filters` and
> `hostname.com/admin/doc/tags` causes an Internal Server Error on Django
> 1.7.
>
> In `django/contrib/admindocs/views.py`, the function
> `load_all_installed_template_libraries()` already gracefully fails on
> `OSError` when finding python files. However, when the module being
> checked has no `__file__` attribute the error bubbles up and causes an
> Internal Server Error.
>
> Someone on django-users suggested that it may be because some extensions
> are installed as eggs. I've attached a naive patch that simply adds
> `AttributeError` to the caught exceptions, causing the function to fail
> gracefully instead of letting it bubble up.
>
> The code that triggers the error:
> {{{#!python
> try:
> libraries = [
> os.path.splitext(p)[0]
> for p in os.listdir(os.path.dirname(upath(mod.__file__)))
> if p.endswith('.py') and p[0].isalpha()
> ]
> except OSError:
> libraries = []
> }}}
>
> I've simply added another error to that block:
>
> {{{#!python
> try:
># ...same code from above.
> except (OSError, AttributeError):
> libraries = []
> }}}
>

> I thought about refactoring this and maybe expanding the for-loop so
> `AttributeError` is only caught where needed, but chose instead to make
> the least invasive change possible.

New description:

 Accessing `hostname.com/admin/doc/filters` and
 `hostname.com/admin/doc/tags` causes an Internal Server Error on Django
 1.7. The cause is modules that have no `__file__` attribute.

 In `django/contrib/admindocs/views.py`, the function
 `load_all_installed_template_libraries()` already gracefully fails on
 `OSError` when finding python files. However, when the module being
 checked has no `__file__` attribute the error bubbles up and causes an
 Internal Server Error.

 Someone on django-users suggested that it may be because some extensions
 are installed as eggs. I've attached a naive patch that simply adds
 `AttributeError` to the caught exceptions, causing the function to fail
 gracefully instead of letting it bubble up.

 The code that triggers the error:
 {{{#!python
 try:
 libraries = [
 os.path.splitext(p)[0]
 for p in os.listdir(os.path.dirname(upath(mod.__file__)))
 if p.endswith('.py') and p[0].isalpha()
 ]
 except OSError:
 libraries = []
 }}}

 I've simply added another error to that block:

 {{{#!python
 try:
# ...same code from above.
 except (OSError, AttributeError):
 libraries = []
 }}}


 I thought about refactoring this and maybe expanding the for-loop so
 `AttributeError` is only caught where needed, but chose instead to make
 the least invasive change possible.

--

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

Re: [Django] #23525: admin/docs/filters|tags __file__ attribute errors for egg extensions

[Django]

#23525: admin/docs/filters|tags __file__ attribute errors for egg extensions
-+-
 Reporter:  welbornprod  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admindocs|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  __file__ | Triage Stage:
  AttributeError filters tags|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by welbornprod):

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


Old description:

> Accessing `hostname.com/admin/doc/filters` and
> `hostname.com/admin/doc/tags` causes an Internal Server Error on Django
> 1.7.
>
> In `django/contrib/admindocs/views.py`, the function
> `load_all_installed_template_libraries()` already gracefully fails on
> `OSError` when finding python files. However, when the module being
> checked has no `__file__` attribute the error bubbles up and causes an
> Internal Server Error.
>
> Someone on django-users suggested that it may be because some extensions
> are installed as eggs. I've attached a naive patch that simply adds
> `AttributeError` to the caught exceptions, causing the function to fail
> gracefully instead of letting it bubble up.
>
> The code that triggers the error:
> {{{#!python
> try:
> libraries = [
> os.path.splitext(p)[0]
> for p in os.listdir(os.path.dirname(upath(mod.__file__)))
> if p.endswith('.py') and p[0].isalpha()
> ]
> except OSError:
> libraries = []
> }}}
>
> I've simply added another error to that block:
>
> {{{#!python
> try:
># ...same code from above.
> except OSError, AttributeError:
> libraries = []
> }}}

New description:

 Accessing `hostname.com/admin/doc/filters` and
 `hostname.com/admin/doc/tags` causes an Internal Server Error on Django
 1.7.

 In `django/contrib/admindocs/views.py`, the function
 `load_all_installed_template_libraries()` already gracefully fails on
 `OSError` when finding python files. However, when the module being
 checked has no `__file__` attribute the error bubbles up and causes an
 Internal Server Error.

 Someone on django-users suggested that it may be because some extensions
 are installed as eggs. I've attached a naive patch that simply adds
 `AttributeError` to the caught exceptions, causing the function to fail
 gracefully instead of letting it bubble up.

 The code that triggers the error:
 {{{#!python
 try:
 libraries = [
 os.path.splitext(p)[0]
 for p in os.listdir(os.path.dirname(upath(mod.__file__)))
 if p.endswith('.py') and p[0].isalpha()
 ]
 except OSError:
 libraries = []
 }}}

 I've simply added another error to that block:

 {{{#!python
 try:
# ...same code from above.
 except (OSError, AttributeError):
 libraries = []
 }}}


 I thought about refactoring this and maybe expanding the for-loop so
 `AttributeError` is only caught where needed, but chose instead to make
 the least invasive change possible.

--

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

[django/django] b28767: [1.7.x] Made a GIS test work on Oracle.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: b287676739849aae397969aef4e0e09e88cf8bdb
  
https://github.com/django/django/commit/b287676739849aae397969aef4e0e09e88cf8bdb
  Author: Tim Graham 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/geoapp/tests.py

  Log Message:
  ---
  [1.7.x] Made a GIS test work on Oracle.

Thanks Josh Smeaton and Claude Paroz for advice.

Backport of 7add30df01 from master


  Commit: 17a4038cf3aad025c653342eb18882c38dbdb1a9
  
https://github.com/django/django/commit/17a4038cf3aad025c653342eb18882c38dbdb1a9
  Author: Tim Graham 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/relatedapp/tests.py

  Log Message:
  ---
  [1.7.x] Skipped a broken GIS test on Oracle; refs #23504.

Backport of 828edc5ba9 from master


Compare: https://github.com/django/django/compare/0f52bf7c96e0...17a4038cf3aa

-- 
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/541c7f9dc402c_36973f9ea1dd72bc92531%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23504: Oracle GIS test failures

[Django]

#23504: Oracle GIS test failures
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Tim Graham ):

 In [changeset:"17a4038cf3aad025c653342eb18882c38dbdb1a9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="17a4038cf3aad025c653342eb18882c38dbdb1a9"
 [1.7.x] Skipped a broken GIS test on Oracle; refs #23504.

 Backport of 828edc5ba9 from master
 }}}

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

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

[django/django] 828edc: Skipped a broken GIS test on Oracle; refs #23504.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 828edc5ba91e124392417c5a87c17647dbb1cf67
  
https://github.com/django/django/commit/828edc5ba91e124392417c5a87c17647dbb1cf67
  Author: Tim Graham 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/relatedapp/tests.py

  Log Message:
  ---
  Skipped a broken GIS test on Oracle; refs #23504.


-- 
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/541c7e88c23cd_35d83ff2be6232c029848%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23504: Oracle GIS test failures

[Django]

#23504: Oracle GIS test failures
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Tim Graham ):

 In [changeset:"828edc5ba91e124392417c5a87c17647dbb1cf67"]:
 {{{
 #!CommitTicketReference repository=""
 revision="828edc5ba91e124392417c5a87c17647dbb1cf67"
 Skipped a broken GIS test on Oracle; refs #23504.
 }}}

--
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.504f7248b27a593588bd7872a8af3495%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 7add30: Made a GIS test work on Oracle.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7add30df01f46ec91b8da411620a0f1a117c1b73
  
https://github.com/django/django/commit/7add30df01f46ec91b8da411620a0f1a117c1b73
  Author: Tim Graham 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/geoapp/tests.py

  Log Message:
  ---
  Made a GIS test work on Oracle.

Thanks Josh Smeaton and Claude Paroz for advice.


-- 
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/541c7e17be3bf_7f3b3f8bd23b32b83956b%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[Django] #23525: admin/docs/filters|tags __file__ attribute errors for egg extensions

[Django]

#23525: admin/docs/filters|tags __file__ attribute errors for egg extensions
-+-
 Reporter:   |  Owner:  nobody
  welbornprod| Status:  new
 Type:  Bug  |Version:  1.7
Component:   |   Keywords:  __file__ AttributeError filters
  contrib.admindocs  |  tags
 Severity:  Normal   |  Has patch:  1
 Triage Stage:   |  UI/UX:  0
  Unreviewed |
Easy pickings:  1|
-+-
 Accessing `hostname.com/admin/doc/filters` and
 `hostname.com/admin/doc/tags` causes an Internal Server Error on Django
 1.7.

 In `django/contrib/admindocs/views.py`, the function
 `load_all_installed_template_libraries()` already gracefully fails on
 `OSError` when finding python files. However, when the module being
 checked has no `__file__` attribute the error bubbles up and causes an
 Internal Server Error.

 Someone on django-users suggested that it may be because some extensions
 are installed as eggs. I've attached a naive patch that simply adds
 `AttributeError` to the caught exceptions, causing the function to fail
 gracefully instead of letting it bubble up.

 The code that triggers the error:
 {{{#!python
 try:
 libraries = [
 os.path.splitext(p)[0]
 for p in os.listdir(os.path.dirname(upath(mod.__file__)))
 if p.endswith('.py') and p[0].isalpha()
 ]
 except OSError:
 libraries = []
 }}}

 I've simply added another error to that block:

 {{{#!python
 try:
# ...same code from above.
 except OSError, AttributeError:
 libraries = []
 }}}

--
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/054.181533c19d76ec6590f6c12db69a1fd3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13906: REPEATABLE READ (as used by default on MySQL) breaks atleast QuerySet.get_or_create().

[Django]

#13906: REPEATABLE READ (as used by default on MySQL) breaks atleast
QuerySet.get_or_create().
-+-
 Reporter:  sebastian_noack  |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:  mysql transaction|  Patch needs improvement:  1
  isolation  |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by streeter):

 * cc: django@… (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.c318b13eb712791aa90950a419a35403%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 0f52bf: [1.7.x] Fixed some flake8 errors.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 0f52bf7c96e0b407a381bc4596f34cd01065f90d
  
https://github.com/django/django/commit/0f52bf7c96e0b407a381bc4596f34cd01065f90d
  Author: Tim Graham 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M tests/migrations/test_executor.py
M tests/migrations/test_migrations_backwards_deps_1/0001_initial.py
M tests/migrations/test_migrations_backwards_deps_1/0002_second.py

  Log Message:
  ---
  [1.7.x] Fixed some flake8 errors.

Backport of 9d30412a5a 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/541c5b3946ef_f143fae0d9272a089259%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 9d3041: Fixed some flake8 errors.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9d30412a5ad1c72b3d319b4c2bceacb53a0ff1da
  
https://github.com/django/django/commit/9d30412a5ad1c72b3d319b4c2bceacb53a0ff1da
  Author: Tim Graham 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M setup.cfg
M tests/migrations/test_executor.py
M tests/migrations/test_migrations_backwards_deps_1/0001_initial.py
M tests/migrations/test_migrations_backwards_deps_1/0002_second.py

  Log Message:
  ---
  Fixed some flake8 errors.

Originally I added migrations to flake8 exclude because of long lines
in migration files, but there are other directories named migrations we
do want to check. We are not warning on line lengths yet anyway.


-- 
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/541c5aae68c75_36cf3ff4126a72a049330%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 988c74: [1.7.x] Skipped an unsupported test on Oracle GIS.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 988c7425ff038f0b8b1c7d5ea9e04fc70b2b01f8
  
https://github.com/django/django/commit/988c7425ff038f0b8b1c7d5ea9e04fc70b2b01f8
  Author: Tim Graham 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/test_spatialrefsys.py

  Log Message:
  ---
  [1.7.x] Skipped an unsupported test on Oracle GIS.

This is fixed more elegantly on master with a feature flag in 6c1a0581ab.


-- 
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/541c59e42471d_42cf3f89eb8a72bc25856%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] aa9c69: [1.7.x] Fixed an inspectapp test on Oracle GIS.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: aa9c69a726d1dc3035a7518c90519b2cdf5475f6
  
https://github.com/django/django/commit/aa9c69a726d1dc3035a7518c90519b2cdf5475f6
  Author: Tim Graham 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/inspectapp/tests.py

  Log Message:
  ---
  [1.7.x] Fixed an inspectapp test on Oracle GIS.

This is fixed more elegantly with a feature flag on master in 33e817a6d8.


-- 
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/541c588967905_38f63ff72ab372a08552%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23504: Oracle GIS test failures

[Django]

#23504: Oracle GIS test failures
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Tim Graham ):

 In [changeset:"e295b0f8757db9bca72c21c15e7db6003a96393d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e295b0f8757db9bca72c21c15e7db6003a96393d"
 [1.7.x] Removed unnecessary order_by() from a GIS test that crashed
 Oracle.

 Oracle cannot order_by() a TextField; refs #23504.

 Backport of 7fc13178d6 from master
 }}}

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

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

[django/django] e295b0: [1.7.x] Removed unnecessary order_by() from a GIS ...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: e295b0f8757db9bca72c21c15e7db6003a96393d
  
https://github.com/django/django/commit/e295b0f8757db9bca72c21c15e7db6003a96393d
  Author: Tim Graham 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/layermap/tests.py

  Log Message:
  ---
  [1.7.x] Removed unnecessary order_by() from a GIS test that crashed Oracle.

Oracle cannot order_by() a TextField; refs #23504.

Backport of 7fc13178d6 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/541c56f86080f_38f63ff72ab372a0851b9%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] a0a65b: [1.7.x] Skipped some broken tests on Oracle GIS; r...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: a0a65b2fd21d3f09997ff1701cb44e32d6eb0f59
  
https://github.com/django/django/commit/a0a65b2fd21d3f09997ff1701cb44e32d6eb0f59
  Author: Tim Graham 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/geoapp/test_regress.py
M django/contrib/gis/tests/relatedapp/tests.py

  Log Message:
  ---
  [1.7.x] Skipped some broken tests on Oracle GIS; refs #23504.

Backport of 7fce7f51ef 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/541c56b15f002_35cf3fd498d8d2c055380%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23504: Oracle GIS test failures

[Django]

#23504: Oracle GIS test failures
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Tim Graham ):

 In [changeset:"a0a65b2fd21d3f09997ff1701cb44e32d6eb0f59"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a0a65b2fd21d3f09997ff1701cb44e32d6eb0f59"
 [1.7.x] Skipped some broken tests on Oracle GIS; refs #23504.

 Backport of 7fce7f51ef from master
 }}}

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

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

[django/django] c61d2c: [1.7.x] Improved GIS migration test cleanup; refs ...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: c61d2c0387aeeaf5600b85c08b0d01b10655155c
  
https://github.com/django/django/commit/c61d2c0387aeeaf5600b85c08b0d01b10655155c
  Author: Tim Graham 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/gis_migrations/test_operations.py

  Log Message:
  ---
  [1.7.x] Improved GIS migration test cleanup; refs #23504.

Backport of 8facb02faf 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/541c55879482f_9cf3ff095fa72b8735c6%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23504: Oracle GIS test failures

[Django]

#23504: Oracle GIS test failures
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Tim Graham ):

 In [changeset:"c61d2c0387aeeaf5600b85c08b0d01b10655155c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c61d2c0387aeeaf5600b85c08b0d01b10655155c"
 [1.7.x] Improved GIS migration test cleanup; refs #23504.

 Backport of 8facb02faf from master
 }}}

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

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

Re: [Django] #23496: Model not detected as installed if custom model path is used

[Django]

#23496: Model not detected as installed if custom model path is used
-+-
 Reporter:  yscumc   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 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 bmispelon):

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


Comment:

 I can reproduce the described issue and confirm that it's indeed fixed in
 1.7.

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

Re: [Django] #23505: unique constraint tracking lost after DropColumn + AddColumn in postgres

[Django]

#23505: unique constraint tracking lost after DropColumn + AddColumn in postgres
-+--
 Reporter:  CloudNiner   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  unique_together  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by bmispelon):

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


Comment:

 Hi,

 Could you give us some more details on how to reproduce the issue?

 I tried using this model:
 {{{
 #!python
 class Foo(models.Model):
 foo = models.IntegerField()
 bar = models.IntegerField()

 class Meta:
 unique_together = (('foo', 'bar'),)
 }}}
 Then I ran `makemigrations` and `migrate`.
 After that, I changed the `bar` field to `bar =
 models.CharField(max_length=10)` and ran `makemigrations` and `migrate`
 again.

 But when I do that, I can see that the unique constraint is still there:
 {{{
 Table "public.bug23505_foo"
  Column | Type  | Modifiers
 
+---+---
  id | integer   | not null default
 nextval('bug23505_foo_id_seq'::regclass)
  foo| integer   | not null
  bar| character varying(10) | not null
 Indexes:
 "bug23505_foo_pkey" PRIMARY KEY, btree (id)
 "bug23505_foo_foo_30361d88471c726e_uniq" UNIQUE CONSTRAINT, btree
 (foo, bar)
 }}}

 Thanks.

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

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

Re: [Django] #23523: pyinotify yelling no space available

[Django]

#23523: pyinotify yelling no space available
---+--
 Reporter:  MattBlack85|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.7
 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
---+--

Comment (by bmispelon):

 What about `sysctl -n fs.inotify.max_user_watches`?
 (https://github.com/seb-m/pyinotify/wiki/Frequently-Asked-Questions)

--
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.9528932326b69737a7def964ca471e97%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21670: New Model.save() mechanism causes deadlocks in mysql transactions

[Django]

#21670: New Model.save() mechanism causes deadlocks in mysql transactions
-+-
 Reporter:  err  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by streeter):

 * cc: django@… (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/061.27d9ba55eba32ea7b8bf2a565b8ec643%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23515: AUTH_USER_MODEL and admin.E108

[Django]

#23515: AUTH_USER_MODEL and admin.E108
-+-
 Reporter:  fizista  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.7
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  admin| Triage Stage:
  AUTH_USER_MODEL|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Duplicate of #5863 which was closed as "won't fix". See
 [https://code.djangoproject.com/ticket/5863#comment:28 this comment] for
 the rationale.

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

[django/django] 185ab9: Fixed Oracle GIS failures introduced by e9103402c0...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 185ab9ffefcf81378d7da02dddca0a59487b9613
  
https://github.com/django/django/commit/185ab9ffefcf81378d7da02dddca0a59487b9613
  Author: Tim Graham 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M django/contrib/gis/db/backends/oracle/operations.py
M django/contrib/gis/db/models/fields.py
M django/contrib/gis/db/models/sql/compiler.py

  Log Message:
  ---
  Fixed Oracle GIS failures introduced by e9103402c0; refs #18757.

Thanks Marc Tamlyn 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/541c1ed8c4156_d8a3ff70ffb129c397c6%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18757: Examine ways to get rid of DB backend convert_values()

[Django]

#18757: Examine ways to get rid of DB backend convert_values()
-+-
 Reporter:  akaariai |Owner:  mjtamlyn
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"185ab9ffefcf81378d7da02dddca0a59487b9613"]:
 {{{
 #!CommitTicketReference repository=""
 revision="185ab9ffefcf81378d7da02dddca0a59487b9613"
 Fixed Oracle GIS failures introduced by e9103402c0; refs #18757.

 Thanks Marc Tamlyn for the patch.
 }}}

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

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

Re: [Django] #22423: Geodjango spatial functions should leverage mysql 5.6 spatial functions.

[Django]

#22423: Geodjango spatial functions should leverage mysql 5.6 spatial functions.
-+
 Reporter:  visu |Owner:  visu
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  gis, mysql,  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by timgraham):

 * needs_docs:  1 => 0
 * needs_better_patch:  0 => 1


Comment:

 I left comments for improvement on the PR. Please uncheck "Patch needs
 improvement" when you update it, thanks.

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

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

[Django] #23524: Django postgres connection's timezone is always set to UTC. Breaks date_trunc function

[Django]

#23524: Django postgres connection's timezone is always set to UTC. Breaks
date_trunc function
--+-
 Reporter:  Mactory   |  Owner:
 Type:  Bug   | Status:  new
Component:  contrib.postgres  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 When using a cursor created by  django.db.connection.cursor() to execute a
 database function on a postgresql database, the timezone of the database
 connection is always set to UTC instead of using the specified TIME_ZONE.
 This behavior brakes postgres' {{{ date_trunc }}} function, since it will
 truncate the hour to be 0 at UTC creating an offset from midnight at the
 local timestamp.

 Example:
 settings.py
 {{{
 TIME_ZONE = 'Europe/Berlin' # Offset +2
 USE_TZ = TRUE
 }}}

 using date_trunc in a djago python shell:
 {{{
 ./manage.py shell
 >>> from django.db import connection
 >>> cursor = connection.cursor()
 >>> cursor.execute("select date_trunc('month', TIMESTAMP WITH TIME ZONE
 '2014-09-14 04:10:00+02');")
 >>> unicode(cursor.fetchone()[0])
 u'2014-09-01 00:00:00+00:00'
 }}}

 using date_tunc directly in psql:
 {{{
 psql db
 db=#select date_trunc('month', TIMESTAMP WITH TIME ZONE '2014-09-14
 04:10:00+02');
date_trunc
 
  2014-09-01 00:00:00+02
 (1 row)
 }}}

 For executing custom functions for which no return value is needed, the
 following workaround does work:
 {{{
 >>> cursor.execute("SET TIMEZONE to %s;select date_trunc('month',
 TIMESTAMP WITH TIME ZONE '2014-09-14 04:10:00+02');SET TIMEZONE to
 'UTC';", (settings.TIME_ZONE,))
 }}}

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

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

[django/django] 07b4c3: [1.7.x] Fixed a formatting issue in the 1.7 releas...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 07b4c3e115ba6cbd29d1b037f9a6bb774ca449a3
  
https://github.com/django/django/commit/07b4c3e115ba6cbd29d1b037f9a6bb774ca449a3
  Author: Aymeric Augustin 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  [1.7.x] Fixed a formatting issue in the 1.7 release notes.

Backport of 47ff469 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/541c0e20d49f7_26073f9571d4d2bc6722b%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 47ff46: Fixed a formatting issue in the 1.7 release notes.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 47ff469057f168a08c4d90708c701b91a70b5fd0
  
https://github.com/django/django/commit/47ff469057f168a08c4d90708c701b91a70b5fd0
  Author: Aymeric Augustin 
  Date:   2014-09-19 (Fri, 19 Sep 2014)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  Fixed a formatting issue in the 1.7 release notes.


-- 
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/541c0e02af185_646a3fedbb6ab2b87630%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23523: pyinotify yelling no space available

[Django]

#23523: pyinotify yelling no space available
---+--
 Reporter:  MattBlack85|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.7
 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
---+--

Comment (by MattBlack85):

 {{{
 ➜  patients_database git:(big_field) df -i
 Filesystem  Inodes  IUsed  IFree IUse% Mounted on
 /dev/mapper/fedora-root3276800 3548692921931   11% /
 devtmpfs   203998851120394771% /dev
 tmpfs  2042567 1120425561% /dev/shm
 tmpfs  204256769420418731% /run
 tmpfs  2042567 1520425521% /sys/fs/cgroup
 tmpfs  2042567 3020425371% /tmp
 /dev/mapper/fedora-home   11395072 238864   111562083% /home
 /dev/sda5   128016 83 1279331% /boot
 /dev/sda4   4294967295   2886 42949644091% /boot/efi

 }}}

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

Re: [Django] #23523: pyinotify yelling no space available

[Django]

#23523: pyinotify yelling no space available
---+--
 Reporter:  MattBlack85|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.7
 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
---+--

Comment (by bmispelon):

 And what does `df -i` report (http://serverfault.com/questions/427091/no-
 space-left-on-device-but-there-is-space#427092)?

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

Re: [Django] #23523: pyinotify yelling no space available

[Django]

#23523: pyinotify yelling no space available
---+--
 Reporter:  MattBlack85|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.7
 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
---+--

Comment (by MattBlack85):

 yep, I have just 23% used


 {{{
 ➜  django git:(django-support-testing) df /usr/lib64
 Filesystem  1K-blocks Used Available Use% Mounted on
 /dev/mapper/fedora-root  51475068 10943904  37893340  23% /

 }}}

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

Re: [Django] #23523: pyinotify yelling no space available

[Django]

#23523: pyinotify yelling no space available
---+--
 Reporter:  MattBlack85|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.7
 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 bmispelon):

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


Comment:

 Sorry if that's obvious, but have you checked that you still have space
 left on your root partition (or wherever `/usr/lib64` is mounted)?

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

Re: [Django] #23501: remove/add fields programatically in modelform fails in admin

[Django]

#23501: remove/add fields programatically in modelform fails in admin
---+
 Reporter:  hadisunyoto|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.7
 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 hadisunyoto):

 A little update:

 i tried get_fields() method and still keep del intact, it turns out to be
 an error

 KeyError at /admin/thicknesses/thickness/0.55/
 'value'

 {{{

 21.def __init__(self, *args, **kwargs):
 22.super(ThicknessForm, self).__init__(*args, **kwargs)
 23.instance = getattr(self, 'instance', None)
 24.
 25.# edit
 26.if instance and instance.pk:
 27.del self.fields['value'] <--
 28.
 29.class Meta:

 }}}

 occur in line 27

 i guess i have to forget about the form and put everything in admin then.
 What worries me is there will be several models that requires the clean()
 method in form to check related fields, that means that i have two places
 (form and admin) that handles the form, and i don't think that's a good
 approach

--
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.358b696f4aec56c58b9f5787d39e2e41%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23501: remove/add fields programatically in modelform fails in admin

[Django]

#23501: remove/add fields programatically in modelform fails in admin
---+
 Reporter:  hadisunyoto|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.7
 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 hadisunyoto):

 thank you for your quick response, in the mean time, i will try your
 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/069.4994db1f4e85c66b790e0a78d73e9a62%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23522: reverse() should return a text string, not a byte string

[Django]

#23522: reverse() should return a text string, not a byte string
-+
 Reporter:  jdufresne|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by claudep):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #23520: Custom Plural-Forms is ignored in django.po

[Django]

#23520: Custom Plural-Forms is ignored in django.po
-+-
 Reporter:  aruseni  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  gettext, plural- |  Needs documentation:  0
  forms  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

 * type:  Uncategorized => Cleanup/optimization
 * version:  1.7 => master
 * component:  Internationalization => Documentation
 * stage:  Unreviewed => Accepted


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

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