date:20140522

Re: [Django] #18849: Add caching to SingleObjectMixin.get_object()

2014-05-22 Thread Django

#18849: Add caching to SingleObjectMixin.get_object()
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Generic views  |  Version:  1.4
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by ewjoachim):

 Just to add a bit of detail :

 If you want to override the get or post (or dispatch) method of a CBV, and
 you need to do a specific operation after self.object is set and before
 super() is called, then you can't use super(), which can mess up a lot of
 mixin uses.

 If get_object was cached, then you could do
 {{{
 self.object = self.get_object()
 }}}
 youself, and you'd know that when the base class does its own
 self.get_object(), it would not make a new SQL query.

 I had several cases where I had to make my own CacheObjectMixin with adds
 caching to self.object, but I think there could be a easier way.

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

Re: [Django] #22680: I/O operation on closed file

2014-05-22 Thread Django

#22680: I/O operation on closed file
-+-
 Reporter:  shelinanton@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  master
  uploads/storage|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by shelinanton@…):

 Created simple script to reproduce error:

 {{{
 from django.db import models
 from django.db.models.fields.files import FieldFile
 from django.core.files.temp import NamedTemporaryFile
 from django.core.files import File
 from django.core.files.storage import FileSystemStorage

 fs = FileSystemStorage(location='.')
 field = models.FileField(storage=fs, name="field")

 class Model(object):
 field = ""

 instance = Model()
 temp = NamedTemporaryFile(delete=True)
 field_file = FieldFile(instance,field,"field")
 field_file.save('file', File(temp),save=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/079.8f7225e39623b32418a715eb3fa78d40%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22680: I/O operation on closed file

2014-05-22 Thread Django

#22680: I/O operation on closed file
-+-
 Reporter:  shelinanton@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  master
  uploads/storage|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by shelinanton@…):

 More info could be find here [https://groups.google.com/forum/#!topic
 /django-users/SXMDKFFnoSc]
 This bug occured just after migration from dajngo 1.6 to django 1.7.
 My traceback:

 Traceback (most recent call last):
   File
 "/home/hodza/projects/pinstream/pins/management/commands/import.py", line
 85, in handle
 author.save()
   File "/home/hodza/projects/pinstream/pins/models.py", line 199, in save
 self.photo_copy.save(img_filename, File(img_temp),save=False)
   File
 
"/home/hodza/projects/pinstream/venv/src/django/django/db/models/fields/files.py",
 line 93, in save
 self._size = content.size
   File
 "/home/hodza/projects/pinstream/venv/src/django/django/core/files/base.py",
 line 46, in _get_size
 pos = self.file.tell()
 ValueError: I/O operation on closed 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/079.e84f69813599cc951e36abaab1c6edaf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] be88b0: Fixed #21357 -- Fixed test client session initiali...

2014-05-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: be88b062afaa58559bb12623e8ed8843f07b97a1
  
https://github.com/django/django/commit/be88b062afaa58559bb12623e8ed8843f07b97a1
  Author: Preston Timmons 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M django/test/client.py
M tests/test_client_regress/tests.py

  Log Message:
  ---
  Fixed #21357 -- Fixed test client session initialization.

The test client will now create a session when it is first accessed
if no session already exists.


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

Re: [Django] #21357: Test client session does not behave as stated in the django documentation.

2014-05-22 Thread Django

#21357: Test client session does not behave as stated in the django 
documentation.
---+
 Reporter:  aaronmerriam@… |Owner:  nobody
 Type:  Bug|   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:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"be88b062afaa58559bb12623e8ed8843f07b97a1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="be88b062afaa58559bb12623e8ed8843f07b97a1"
 Fixed #21357 -- Fixed test client session initialization.

 The test client will now create a session when it is first accessed
 if no session already exists.
 }}}

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

Re: [Django] #22685: SimpleTemplateResponse not suitable as TemplateView.response_class

2014-05-22 Thread Django

#22685: SimpleTemplateResponse not suitable as TemplateView.response_class
---+--
 Reporter:  mbertheau  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Generic views  |  Version:  1.6
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 I guess you should override `render_to_response` to initialize the
 `response_class` without the request. I'm not sure we should make a change
 in Django to support this. Feel free to reopen the ticket if you have a
 proposed patch and we could evaluate it.

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

Re: [Django] #22659: parent_link relationships ignored by migrations

2014-05-22 Thread Django

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

Comment:

The whole issue was related to `ModelState` using their internal `fields`
representation when building model classes and not copying of them.

Since `ModelState`s can be re-used to render models in different `Apps` it
didn't detect the `parent_company` field as a valid `parent_link` the
second time the state was rendered since it was already bound to
`apps_used_on_first_render.get_model('foo.Company')` thus adding a new
`OneToOneField` pointing to
`apps_used_on_second_render.get_model('foo.Company')`.

Created a PR with an initial test
[https://github.com/django/django/pull/2703 here]. It seems to fix the
issue encountered in the provided test project on my side, can you confirm
it's also working for you @tbartelmess? I'm working on adding an
additional test case to prevent a regression for the exact issue described
here.

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

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

Re: [Django] #21357: Test client session does not behave as stated in the django documentation.

2014-05-22 Thread Django

#21357: Test client session does not behave as stated in the django 
documentation.
---+
 Reporter:  aaronmerriam@… |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Comment:

 Test on PR does not currently pass (possibly due to upstream changes since
 the PR was submitted).

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

[django/django] 4dc4d1: Fixed #21598 -- cleaned up template loader overrid...

2014-05-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4dc4d12e27e4e0337568651136eee5b6f2171204
  
https://github.com/django/django/commit/4dc4d12e27e4e0337568651136eee5b6f2171204
  Author: Unai Zalakain 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M django/test/utils.py
M tests/template_tests/tests.py
M tests/view_tests/tests/test_debug.py
M tests/view_tests/tests/test_defaults.py

  Log Message:
  ---
  Fixed #21598 -- cleaned up template loader overrides in tests

- Template loader overriding is managed with contexts.
- The test loader is a class (function based loaders entered deprecation 
timeline
  in 1.4).
- Template loader overrider that overrides with test loader added.


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

Re: [Django] #21598: Cleanup template loader overrides in tests

2014-05-22 Thread Django

#21598: Cleanup template loader overrides in tests
-+-
 Reporter:  unaizalakain |Owner:
 Type:   |  unaizalakain
  Cleanup/optimization   |   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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"4dc4d12e27e4e0337568651136eee5b6f2171204"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4dc4d12e27e4e0337568651136eee5b6f2171204"
 Fixed #21598 -- cleaned up template loader overrides in tests

 - Template loader overriding is managed with contexts.
 - The test loader is a class (function based loaders entered deprecation
 timeline
   in 1.4).
 - Template loader overrider that overrides with test loader 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/070.b7dd237d2b2400575f3e733b86f524ab%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22659: parent_link relationships ignored by migrations

2014-05-22 Thread Django

#22659: parent_link relationships ignored by migrations
-+--
 Reporter:  tbartelmess  |Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by charettes):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => charettes
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I could reproduce with on master and 1.7.X. Looking at it.

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

Re: [Django] #22685: SimpleTemplateResponse not suitable as TemplateView.response_class

2014-05-22 Thread Django

#22685: SimpleTemplateResponse not suitable as TemplateView.response_class
---+--
 Reporter:  mbertheau  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Generic views  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by mbertheau):

 I don't know of any such hint in the documentation.

 I stumbled upon it while reading the Django code looking for how to make
 `TemplateView` not use a `RequestContext` so that I could set things like
 `user` and `messages` in the context.

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

Re: [Django] #22684: SelectDateWidget's none_value is not changeable

2014-05-22 Thread Django

#22684: SelectDateWidget's none_value is not changeable
---+
 Reporter:  danielsamuels  |Owner:  gyx1000
 Type:  New feature|   Status:  assigned
Component:  Forms  |  Version:  1.6
 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:  1
---+
Changes (by gyx1000):

 * owner:  nobody => gyx1000
 * status:  new => assigned


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

Re: [Django] #22436: migrations fail on custom upload_to on ImageField

2014-05-22 Thread Django

#22436: migrations fail on custom upload_to on ImageField
-+-
 Reporter:  David Binetti|Owner:
 |  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-2
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  1|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * version:  master => 1.7-beta-2


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

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

Re: [Django] #22510: Form fields cannot have names that are present as attributes on the form

2014-05-22 Thread Django

#22510: Form fields cannot have names that are present as attributes on the form
-+--
 Reporter:  gc@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by aaugustin):

 With reference to the list in comment 6, my order of preference is 1, 3,
 2.

 - It seems quite natural that clashes between field names and form method
 names cause errors. +0 to just documenting that.
 - Adding `ignored_fields` isn't too bad, but it's one more API that our
 users may encounter. +0 to adding this API.
 - Requiring that shadowing only works with a `None` is seriously
 idiosyncratic. -0 to that solution.

 I hope this helps!

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

Re: [Django] #22680: I/O operation on closed file

2014-05-22 Thread Django

#22680: I/O operation on closed file
-+-
 Reporter:  shelinanton@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  master
  uploads/storage|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 I don't see why this would be a release blocker.

 Can you provide the full traceback please? I suspect the exception appears
 inside `File._get_size_from_underlying_file` but I'm not sure where
 exactly.

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

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

Re: [Django] #20695: "django.contrib.humanize" Turkish Translation Error

2014-05-22 Thread Django

#20695: "django.contrib.humanize" Turkish Translation Error
-+--
 Reporter:  ruless@… |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  Translations |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by aaugustin):

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


Comment:

 I agree, this problem will resolve by itself by the 1.7 release.

 If I missed something, please reopen and explain what's needed.

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

2014-05-22 Thread Django

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by rodutSD):

 This seems like the closest topic.

 I am seeing, what I believe to be, this bug in 1.7b4.  It is not
 contenttype, logEntry, or user related.  It doesn't appear to be dangling
 lookup related either.   I have not manually tried the patch referenced
 above because I assuming that it is merged into the recent 1.7b4 release.
 (probably dumb)

 migrate is failing for a foreign key to a class of my creation.  The
 migration fails with this error:

 {{{
 File "/Users/xxx/.virtualenvs/DjangoProject/lib/python2.7/site-
 packages/django/db/migrations/state.py", line 86, in render
 model=lookup_model,
 ValueError: Lookup failed for model referenced by field
 Custom_Class.thing.transaction: Another_Custom_Class.transaction
 }}}

 makemigrations runs fine.  It creates the following dependency list which
 is where the problem is:

 {{{
 dependencies = [
 ('Another_Custom_Class', '__first__'),
 ('Custom_Class', '0005_mesh'),
 ]
 }}}

 Running migrate on this fails as above saying my reference to
 Another_Custom_Class.transaction from Custom_Class.thing because it can't
 find it.

 I changed the dependency to the following and it works:

 {{{
 dependencies = [
 ('Another_Custom_Class', '0003_transaction'),
 ('Custom_Class', '0005_mesh'),
 ]
 }}}

 I don't know how all the internals work, but it seems like it wasn't able
 to find the other migration because of what is going on when "_first_" is
 used.

 This problem has happened a bunch of separate times and changing _first_
 to the name of a valid migration seems to fix it.  I just hate having to
 dig in and fix it every time.

 Let me know if anyone needs more details.

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

Re: [Django] #22678: forms.Form silently won't bind to POST data (under certain combinations of key and label)

2014-05-22 Thread Django

#22678: forms.Form silently won't bind to POST data (under certain combinations 
of
key and label)
--+--
 Reporter:  brycenesbitt  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  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:  1 |UI/UX:  0
--+--
Changes (by brycenesbitt):

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


Comment:

 I intended to convey that above: the issue is the integer.  Strings work,
 integers don't.
 The form as build 'looked' like reasonable code, but had a murky and hard
 to track problem.
 Most code paths blow up on integers, but not this one.


 The proposed fix is to assert on string for the key.

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

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

Re: [Django] #22490: get_object within a syndication Feed has no tests

2014-05-22 Thread Django

#22490: get_object within a syndication Feed has no tests
-+-
 Reporter:  danielsamuels|Owner:  anonymous
 Type:  Bug  |   Status:  new
Component:  contrib.syndication  |  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
-+-
Changes (by timo):

 * status:  closed => new
 * has_patch:  1 => 0
 * resolution:  fixed =>
 * stage:  Ready for checkin => Accepted


Comment:

 Yes, I cannot find a test for this function. The default returns `None`,
 but there should probably be one that returns an actual object.

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

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

Re: [Django] #22685: SimpleTemplateResponse not suitable as TemplateView.response_class

2014-05-22 Thread Django

#22685: SimpleTemplateResponse not suitable as TemplateView.response_class
---+--
 Reporter:  mbertheau  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Generic views  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 No, it doesn't seem like it would be compatible. Is there something in the
 documentation that suggests it is?

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

[Django] #22685: SimpleTemplateResponse not suitable as TemplateView.response_class

2014-05-22 Thread Django

#22685: SimpleTemplateResponse not suitable as TemplateView.response_class
---+
 Reporter:  mbertheau  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Generic views  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 `SimpleTemplateResponse` not suitable as `TemplateView.response_class`
 because `TemplateView` calls the constructor with a kwarg `request` that
 `SimpleTemplateResponse` doesn't know.

 I'm not sure if that's an intended use case for `SimpleTemplateResponse`
 though.

 There's a related older commit
 
https://github.com/django/django/commit/6fe3a444dfc47c81036fb9c382f7c6647a9faca5
 but it's not in 1.6.

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

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

Re: [Django] #22684: SelectDateWidget's none_value is not changeable

2014-05-22 Thread Django

#22684: SelectDateWidget's none_value is not changeable
---+
 Reporter:  danielsamuels  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Forms  |  Version:  1.6
 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:  1
---+
Changes (by claudep):

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

Re: [Django] #20816: Document middleware ordering requirements explicitly

2014-05-22 Thread Django

#20816: Document middleware ordering requirements explicitly
-+-
 Reporter:  gthb |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"1f6b3cf145fc1057f478607c2c845e66efaaf546"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1f6b3cf145fc1057f478607c2c845e66efaaf546"
 [1.7.x] Fixed #20816 -- Added hints about Django middleware ordering

 Thanks gthb Trac user for the report, kolypto StackOverflow
 user for the initial list and Tim Graham for the review.
 Backport of 756c390fb5 from master.
 }}}

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

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

[django/django] 1f6b3c: [1.7.x] Fixed #20816 -- Added hints about Django m...

2014-05-22 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 1f6b3cf145fc1057f478607c2c845e66efaaf546
  
https://github.com/django/django/commit/1f6b3cf145fc1057f478607c2c845e66efaaf546
  Author: Claude Paroz 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M docs/ref/middleware.txt
M docs/topics/http/middleware.txt

  Log Message:
  ---
  [1.7.x] Fixed #20816 -- Added hints about Django middleware ordering

Thanks gthb Trac user for the report, kolypto StackOverflow
user for the initial list and Tim Graham for the review.
Backport of 756c390fb5 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/537e2710b1714_7359ce9d3411065%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 756c39: Fixed #20816 -- Added hints about Django middlewar...

2014-05-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 756c390fb5bce5157d2882526be0b99f45ce52c9
  
https://github.com/django/django/commit/756c390fb5bce5157d2882526be0b99f45ce52c9
  Author: Claude Paroz 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M docs/ref/middleware.txt
M docs/topics/http/middleware.txt

  Log Message:
  ---
  Fixed #20816 -- Added hints about Django middleware ordering

Thanks gthb Trac user for the report, kolypto StackOverflow
user for the initial list and Tim Graham for the 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/537e26e0b2848_72c68efd3c506a8%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20816: Document middleware ordering requirements explicitly

2014-05-22 Thread Django

#20816: Document middleware ordering requirements explicitly
-+-
 Reporter:  gthb |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"756c390fb5bce5157d2882526be0b99f45ce52c9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="756c390fb5bce5157d2882526be0b99f45ce52c9"
 Fixed #20816 -- Added hints about Django middleware ordering

 Thanks gthb Trac user for the report, kolypto StackOverflow
 user for the initial list and Tim Graham for the review.
 }}}

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

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

Re: [Django] #20856: Error with admin popups: expected a character buffer object

2014-05-22 Thread Django

Comment (by timo):

You can disable the changelist filters stuff if you want; see

[https://docs.djangoproject.com/en/dev/ref/contrib/admin/#django.contrib.admin.ModelAdmin.preserve_filters
ModelAdmin.preserve_filters].

I don't think it's broken. `escapejs` calls `force_text()` which will
invoke the proper method on an object. If you find otherwise, please open
a new ticket with a failing test case for Django's test suite.

Please don't reopen this ticket, 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/080.43b320db711cf510d9eacecf623956f6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22667: Replace occurrences of master/slave terminology with leader/follower

2014-05-22 Thread Django

#22667: Replace occurrences of master/slave terminology with leader/follower
--+
 Reporter:  fcurella  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 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:"beec05686ccc3bee8461f9a5a02c607a02352ae1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="beec05686ccc3bee8461f9a5a02c607a02352ae1"
 Fixed #22667 -- Replaced leader/follower terminology with primary/replica
 }}}

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

[django/django] beec05: Fixed #22667 -- Replaced leader/follower terminolo...

2014-05-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: beec05686ccc3bee8461f9a5a02c607a02352ae1
  
https://github.com/django/django/commit/beec05686ccc3bee8461f9a5a02c607a02352ae1
  Author: Flavio Curella 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M docs/ref/settings.txt
M docs/topics/cache.txt
M docs/topics/db/multi-db.txt
M docs/topics/testing/advanced.txt
M tests/migrations/test_operations.py
M tests/multiple_database/routers.py
M tests/multiple_database/tests.py

  Log Message:
  ---
  Fixed #22667 -- Replaced leader/follower terminology with primary/replica


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

Re: [Django] #20816: Document middleware ordering requirements explicitly

2014-05-22 Thread Django

#20816: Document middleware ordering requirements explicitly
-+-
 Reporter:  gthb |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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

Re: [Django] #22490: get_object within a syndication Feed has no tests

2014-05-22 Thread Django

#22490: get_object within a syndication Feed has no tests
-+-
 Reporter:  danielsamuels|Owner:  anonymous
 Type:  Bug  |   Status:  closed
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by danielsamuels):

 With this change, does this mean that functions such as get_object have no
 tests at all?  This isn't the outcome I was expecting from this ticket.

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

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

Re: [Django] #22684: SelectDateWidget's none_value is not changeable

2014-05-22 Thread Django

#22684: SelectDateWidget's none_value is not changeable
---+--
 Reporter:  danielsamuels  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Forms  |  Version:  1.6
 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:  1
---+--
Changes (by danielsamuels):

 * cc: danielsamuels (added)
 * 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/071.38ce32c377ba140e69b3b0ee23a8536e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22684: SelectDateWidget's none_value is not changeable

2014-05-22 Thread Django

#22684: SelectDateWidget's none_value is not changeable
---+
 Reporter:  danielsamuels  |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Forms  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  1
---+
 If you want to use a SelectDateWidget to represent your DateField, your
 output will have "---" as the default option text, this text is not
 changeable to suit the needs of each individual application in the same
 way that other fields can have their default set.  I believe this widget
 should gain a new attribute such as `empty_label` to match standard
 ChoiceFields.

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

Re: [Django] #20856: Error with admin popups: expected a character buffer object

2014-05-22 Thread Django

#20856: Error with admin popups: expected a character buffer object
-+-
 Reporter:  heppner.mark@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  admin, str,  | Triage Stage:
  character, inline, popup   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by matija):

 sorry,

 of xcourse, it is __unicode__()

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

Re: [Django] #20856: Error with admin popups: expected a character buffer object

2014-05-22 Thread Django

#20856: Error with admin popups: expected a character buffer object
-+-
 Reporter:  heppner.mark@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  admin, str,  | Triage Stage:
  character, inline, popup   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by matija@…):

 The error is django/contrib/admin/options.py
 Line 1093:
 'obj': escapejs(obj)

 escapejs does not automatically call __unicode__()

 'obj': escape(obj.__unicode__()) actually works.

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

Re: [Django] #20816: Document middleware ordering requirements explicitly

2014-05-22 Thread Django

#20816: Document middleware ordering requirements explicitly
--+
 Reporter:  gthb  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * has_patch:  0 => 1
 * version:  1.5 => master


Comment:

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

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

Re: [Django] #8162: Increase Permission.name max_length

2014-05-22 Thread Django

#8162: Increase Permission.name max_length
-+-
 Reporter:  juliae   |Owner:  wilsoniya
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  schemamigration  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anonymous):

 There is no validation right now for verbose_name less than 39 characters,
 and after migrating the app with south, it will fail 'after' creating the
 tables...so you have a database with all the tables, but no permission
 rows added.
 This is REALLY annoying and this bug is 6 years old. I understand there's
 always something more important to do, but please it's time to fix it.

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

Re: [Django] #22295: admin/base.html only shows #user-tools when user is staff

2014-05-22 Thread Django

#22295: admin/base.html only shows #user-tools when user is staff
-+-
 Reporter:  wouter@… |Owner:  maxocub
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  user-tools admin |  Needs documentation:  0
  base template  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by maxocub):

 * status:  new => assigned
 * owner:  nobody => maxocub


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

Re: [Django] #22679: makemigrations generates invalid code for default_permissions = ()

2014-05-22 Thread Django

#22679: makemigrations generates invalid code for default_permissions = ()
-+-
 Reporter:  rockallite.wulf@…|Owner:  mardini
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  makemigrations,  | Triage Stage:  Accepted
  default_permissions|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"ad994a3c5b5911a12a5e2f2a8d06c036be1b8ad8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ad994a3c5b5911a12a5e2f2a8d06c036be1b8ad8"
 Fixed #22679 -- Fixed empty tuple serialization in MigrationWriter.

 Thanks rockallite.wulf for the report.
 }}}

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

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

[django/django] 7d4a51: [1.7.x] Fixed #22679 -- Fixed empty tuple serializ...

2014-05-22 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 7d4a51e239bcde34d1614877accb3aa5f5589e0c
  
https://github.com/django/django/commit/7d4a51e239bcde34d1614877accb3aa5f5589e0c
  Author: Moayad Mardini 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M django/db/migrations/writer.py
M tests/migrations/test_writer.py

  Log Message:
  ---
  [1.7.x] Fixed #22679 -- Fixed empty tuple serialization in MigrationWriter.

Thanks rockallite.wulf for the report.

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

Re: [Django] #22679: makemigrations generates invalid code for default_permissions = ()

2014-05-22 Thread Django

#22679: makemigrations generates invalid code for default_permissions = ()
-+-
 Reporter:  rockallite.wulf@…|Owner:  mardini
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  makemigrations,  | Triage Stage:  Accepted
  default_permissions|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Baptiste Mispelon ):

 In [changeset:"7d4a51e239bcde34d1614877accb3aa5f5589e0c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7d4a51e239bcde34d1614877accb3aa5f5589e0c"
 [1.7.x] Fixed #22679 -- Fixed empty tuple serialization in
 MigrationWriter.

 Thanks rockallite.wulf for the report.

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

[django/django] ad994a: Fixed #22679 -- Fixed empty tuple serialization in...

2014-05-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ad994a3c5b5911a12a5e2f2a8d06c036be1b8ad8
  
https://github.com/django/django/commit/ad994a3c5b5911a12a5e2f2a8d06c036be1b8ad8
  Author: Moayad Mardini 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M django/db/migrations/writer.py
M tests/migrations/test_writer.py

  Log Message:
  ---
  Fixed #22679 -- Fixed empty tuple serialization in MigrationWriter.

Thanks rockallite.wulf for the report.


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

[django/django] 635acf: Fix a test dependent on json ordering.

2014-05-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 635acf42c53e77e1ab0fd61e248730d99501c5c1
  
https://github.com/django/django/commit/635acf42c53e77e1ab0fd61e248730d99501c5c1
  Author: Marc Tamlyn 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M tests/postgres_tests/test_array.py

  Log Message:
  ---
  Fix a test dependent on json ordering.


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

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

2014-05-22 Thread Django

#7028: Better raw_id_fields feedback in newform-admins branch
-+-
 Reporter:  Marcob   |Owner:  nobody
|   Status:  new
 Type:  New feature  |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  raw-id-fields nfa-   |  Needs documentation:  0
  someday design_ux  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  1
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by depaolim):

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

[Django] #22683: Schema tests and .extra queryset method

2014-05-22 Thread Django

#22683: Schema tests and .extra queryset method
---+
 Reporter:  maxi   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Migrations |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Running schema tests I caught an issue, more precisely, in
 test_add_field_default_transform.
 At the end, this test method is doing:

 self.assertEqual(Author.objects.extra(where=["thing = 1"]).count(), 2)

 The problem here is what in this where clause, the "thing" field must be
 quoted.

 In firebird :

 SELECT * FROM AUTHOR WHERE thing = 1   <-- Here thing (in lowercase)
 and THING (in uppercase) are equivalent, are the same object

 is different of:

 SELECT * FROM AUTHOR WHERE "thing" = 1   <--  field is quoted

 For a more generic test I think we need to avoid use .extra method or
 another raw sql statement.

 For a more complete discussion about it, see at
 https://groups.google.com/forum/?hl=es#!topic/django-
 developers/KRHD77KlZ28

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

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

Re: [Django] #20873: Model options assumes incorrectly that model classes resides in models-module

2014-05-22 Thread Django

#20873: Model options assumes incorrectly that model classes resides in models-
module
-+-
 Reporter:  jtiai|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  app-loading  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * keywords:   => app-loading


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

Re: [Django] #20873: Model options assumes incorrectly that model classes resides in models-module

2014-05-22 Thread Django

#20873: Model options assumes incorrectly that model classes resides in models-
module
-+-
 Reporter:  jtiai|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  fixed
 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 claudep):

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


Comment:

 Fixed by [7eea9bf30399e9a49fe164851c6132cd19a88e08]

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

Re: [Django] #20856: Error with admin popups: expected a character buffer object

2014-05-22 Thread Django

#20856: Error with admin popups: expected a character buffer object
-+-
 Reporter:  heppner.mark@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  admin, str,  | Triage Stage:
  character, inline, popup   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

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


Comment:

 Actually, there is an issue with this. Actually two

 When you open raw_id_field in a popup, you get url like:
 /admin/a/b/?_popup=1
 THEN when you want to add new object, url changes to :
 /admin/a/b/add/?_popup=1&_changelist_filters=_popup%3D1

 Well, first of all, the url is wrong, look at _changelist_filters
 Second of all, as long as you leave popup=1 parameter, you get the above
 error.

 This has nothing to do with __unicode__ methods, this is broken even with
 return 'a' ;)

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

Re: [Django] #22682: Makemigrations fails when specifying custom location for migration files

2014-05-22 Thread Django

#22682: Makemigrations fails when specifying custom location for migration files
+--
 Reporter:  ovidiuc4|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  1.7b4   | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by ovidiuc4):

 * cc: ovidiuc4 (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Update: I manually created the directories, but it ignored them and added
 the migration files in their default locations for contrib apps (i.e.
 inside django installation).

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

[Django] #22682: Makemigrations fails when specifying custom location for migration files

2014-05-22 Thread Django

#22682: Makemigrations fails when specifying custom location for migration files
+
 Reporter:  ovidiuc4|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  master
 Severity:  Normal  |   Keywords:  1.7b4
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 When running the initial:
 {{{
 python ./manage.py makemigrations appname
 }}}
 a "migrations" directory is automatically created inside the apps base
 directory.

 When specifying a custom migration file location via MIGRATION_MODULES
 setting, running initial migration fails to create the directories needed
 for the migration files. One would expect the same behavior in both
 situations.

 In my case, I want to have all the migrations inside a generic folder
 named "migrations", setup like so:


 {{{
 # in settings:
 MIGRATION_MODULES = dict([(app, 'migrations.' + app) for app in
 INSTALLED_APPS])

 # running makemigrations
 python ./manage.py makemigrations appname

 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File
 "/home/dev/.envs/atlas2/src/django/django/core/management/__init__.py",
 line 427, in execute_from_command_line
 utility.execute()
   File
 "/home/dev/.envs/atlas2/src/django/django/core/management/__init__.py",
 line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/dev/.envs/atlas2/src/django/django/core/management/base.py",
 line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/dev/.envs/atlas2/src/django/django/core/management/base.py",
 line 337, in execute
 output = self.handle(*args, **options)
   File
 
"/home/dev/.envs/atlas2/src/django/django/core/management/commands/makemigrations.py",
 line 54, in handle
 loader = MigrationLoader(None)
   File "/home/dev/.envs/atlas2/src/django/django/db/migrations/loader.py",
 line 47, in __init__
 self.build_graph()
   File "/home/dev/.envs/atlas2/src/django/django/db/migrations/loader.py",
 line 144, in build_graph
 self.load_disk()
   File "/home/dev/.envs/atlas2/src/django/django/db/migrations/loader.py",
 line 71, in load_disk
 module = import_module(module_name)
   File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
 import_module
 __import__(name)
 ImportError: No module named appname

 }}}

 I would expect the same behavior in both cases, i.e. have the modules
 automatically created.

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

[django/django] 483487: Added omitted documentation for ArrayField__len.

2014-05-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 48348782e65438829147d0d066276d1caa0d485b
  
https://github.com/django/django/commit/48348782e65438829147d0d066276d1caa0d485b
  Author: Marc Tamlyn 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M docs/ref/contrib/postgres/fields.txt

  Log Message:
  ---
  Added omitted documentation for ArrayField__len.


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

[django/django] 460823: the SECRET_KEY is not a hash

2014-05-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 46082339d2f87fdad4899e007ac529fb5d75e122
  
https://github.com/django/django/commit/46082339d2f87fdad4899e007ac529fb5d75e122
  Author: Thomas Grainger 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M django/core/management/commands/startproject.py

  Log Message:
  ---
  the SECRET_KEY is not a hash


  Commit: 3545f31bcf91065303c1adaa5154b28e8f8a5d78
  
https://github.com/django/django/commit/3545f31bcf91065303c1adaa5154b28e8f8a5d78
  Author: Marc Tamlyn 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M django/core/management/commands/startproject.py

  Log Message:
  ---
  Merge pull request #2699 from graingert/patch-3

the SECRET_KEY is not a hash


Compare: https://github.com/django/django/compare/6ab67919ac25...3545f31bcf91

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

[Django] #22681: TarArchive has_leading_dir usage bug

2014-05-22 Thread Django

#22681: TarArchive has_leading_dir usage bug
-+-
 Reporter:  phpdude  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (Management |Version:  master
  commands)  |   Keywords:  startproject, tar,
 Severity:  Normal   |  template, allversions
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  1|  UI/UX:  0
-+-
 I found small bug in django.utils.archive.TarArchive.extract function.

 https://github.com/django/django/blob/master/django/utils/archive.py#L147

 There members is a list of TarInfo objects (tarfile.TarInfo), not just a
 list of path strings.

 Because of this bug django cannot recognize leading_dir in tar archives.

 Take a look for example startproject with tar and zip archive.


 {{{
 (env)@dude /WWW# django-admin.py startproject -v 3 --template
 http://git.floraconcierge.com/flora-concierge/django-
 skeleton/repository/archive test14
 Rendering project template files with extensions: .py
 Rendering project template files with filenames:
 Downloading http://git.floraconcierge.com/flora-concierge/django-
 skeleton/repository/archive
 Extracting
 
/var/folders/7h/k___h29d15n7n5zxqk5l8ktwgn/T/django_project_template_FAMd_4_download
 /django-skeleton-f85cd58a98dd98bd22b56a82a35b3947ad7c7d79.tar.gz

 Creating /WWW/test14/django-skeleton.git/manage.py
 Creating /WWW/test14/django-skeleton.git/README
 Creating /WWW/test14/django-skeleton.git/test14/__init__.py
 Creating /WWW/test14/django-skeleton.git/test14/urls.py
 Creating /WWW/test14/django-skeleton.git/test14/wsgi.py
 ...
 }}}

 And example with zip archive

 {{{
 (env)@dude /WWW# django-admin.py startproject -v 3 --template
 https://github.com/rdegges/django-skel/zipball/master test15
 Rendering project template files with extensions: .py
 Rendering project template files with filenames:
 Downloading https://github.com/rdegges/django-skel/zipball/master
 Extracting
 
/var/folders/7h/k___h29d15n7n5zxqk5l8ktwgn/T/django_project_template_DLsbG8_download
 /rdegges-django-skel-d4631bb.zip

 Creating /WWW/test15/.gitignore
 Creating /WWW/test15/fabfile.py
 Creating /WWW/test15/gunicorn.py.ini
 Creating /WWW/test15/manage.py
 Creating /WWW/test15/Procfile
 Creating /WWW/test15/README.md
 Creating /WWW/test15/requirements.txt
 Creating /WWW/test15/runtime.txt
 Creating /WWW/test15/wsgi.py
 }}}

 I fixed this and created pull request in github. Please aply it soon.

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

 Thank you, alex

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

[django/django] 6ab679: Made nested deconstruction support both forms of d...

2014-05-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6ab67919ac25143444a57f14f6aed76ffe8a6960
  
https://github.com/django/django/commit/6ab67919ac25143444a57f14f6aed76ffe8a6960
  Author: Marc Tamlyn 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M tests/migrations/test_autodetector.py

  Log Message:
  ---
  Made nested deconstruction support both forms of deconstruct()

Nested deconstruction should (silently) handle Field.deconstruct() as
well as other arbitrary deconstructable objects. This allows having a
field in the deconstruction of another field.


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

Re: [Django] #22563: Migration of admin.LogEntry.user fails.

2014-05-22 Thread Django

#22563: Migration of admin.LogEntry.user fails.
-+
 Reporter:  efrinut@…|Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   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 rockallite.wulf@…):

 Replying to [comment:20 Andrew Godwin ]:
 > In [changeset:"4535dedc42b90b8f75576e48a12e2e63d4e93048"]:
 > {{{
 > #!CommitTicketReference repository=""
 revision="4535dedc42b90b8f75576e48a12e2e63d4e93048"
 > [1.7.x] Fixed #22563: Ignore AUTH_USER_MODEL errors in from_state
 > }}}

 Hi. I still get the error using Django 1.7b4 which contains the fix.

 I'm in the same situation with @dekkers. My custom user model
 {{{myapp.User}}} contains a foreign key to another model. When I run the
 migration, the error is raised.

 I looked into the traceback and see
 {{{django.db.migrations.operations.models.CreateModel}}} was invoking
 {{{to_state.render()}}} without the {{{ignore_swappable=True}}} argument,
 which caused the problem.

 I manually changed it to {{{to_state.render(ignore_swappable=True)}}},
 then the migration was successfully executed.

 However, {{{./manage.py test}}} fails with the same error: {{{ValueError:
 Lookup failed for model referenced by field admin.LogEntry.user:
 myapp.User}}}, and this time in {{{django.db.migrations.executor}}} in
 {{{detect_soft_applied}}}...

 Perhaps a better fix is to change the signature of
 {{{django.db.migrations.state.ProjectState.render}}} to be invoked with
 {{{ignore_swappable=True}}} by default. I've looked into the code:

 {{{
 def render(self, include_real=None, ignore_swappable=False):
 # ... Other code omitted ...
 if "%s.%s" % (lookup_model[0], lookup_model[1]) ==
 settings.AUTH_USER_MODEL and ignore_swappable:
 continue
 }}}

 This is the only occurrence of the {{{ignore_swappable}}} parameter in the
 method body. So I think it isn't so bad to change {{{ignore_swappable}}}
 parameter to {{{True}}} by default.

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

Re: [Django] #22421: Loading fixtures with one-to-one inheritance on abstract model and M2M fails since 1.7 Beta

2014-05-22 Thread Django

#22421: Loading fixtures with one-to-one inheritance on abstract model and M2M
fails since 1.7 Beta
-+-
 Reporter:  stanislas.guerra@…   |Owner:  ramiro
 Type:  Bug  |   Status:  closed
Component:  Core |  Version:  master
  (Serialization)|   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"fb45e666c204d7188c38469ca1f661a9b113b85b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb45e666c204d7188c38469ca1f661a9b113b85b"
 [1.7.x] Fixed #22421 -- Regression in fixtures loading.

 Loading fixtures were failing since the refactoring in 244e2b71f5 for
 inheritance setups where the chain contains abstract models and the
 root ancestor contains a M2M relation.

 Thanks Stanislas Guerra for the report.

 Refs #20946.

 Backport of 862e1ff234 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/084.bf910be00e5da7dddf269b7937a52f24%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20946: Clean up related field foreign value fetching implementation

2014-05-22 Thread Django

#20946: Clean up related field foreign value fetching implementation
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"fb45e666c204d7188c38469ca1f661a9b113b85b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb45e666c204d7188c38469ca1f661a9b113b85b"
 [1.7.x] Fixed #22421 -- Regression in fixtures loading.

 Loading fixtures were failing since the refactoring in 244e2b71f5 for
 inheritance setups where the chain contains abstract models and the
 root ancestor contains a M2M relation.

 Thanks Stanislas Guerra for the report.

 Refs #20946.

 Backport of 862e1ff234 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/066.3c04f7d6e2d386d128546352fd1dfa2c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] fb45e6: [1.7.x] Fixed #22421 -- Regression in fixtures loa...

2014-05-22 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: fb45e666c204d7188c38469ca1f661a9b113b85b
  
https://github.com/django/django/commit/fb45e666c204d7188c38469ca1f661a9b113b85b
  Author: Ramiro Morales 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M django/db/models/fields/related.py
A tests/fixtures_regress/fixtures/feature.json
M tests/fixtures_regress/models.py
M tests/fixtures_regress/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22421 -- Regression in fixtures loading.

Loading fixtures were failing since the refactoring in 244e2b71f5 for
inheritance setups where the chain contains abstract models and the
root ancestor contains a M2M relation.

Thanks Stanislas Guerra for the report.

Refs #20946.

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

Re: [Django] #22679: makemigrations generates invalid code for default_permissions = ()

2014-05-22 Thread Django

#22679: makemigrations generates invalid code for default_permissions = ()
-+-
 Reporter:  rockallite.wulf@…|Owner:  mardini
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  makemigrations,  | Triage Stage:  Accepted
  default_permissions|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mardini):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * version:  1.7-beta-2 => master
 * owner:  nobody => mardini
 * needs_docs:   => 0
 * has_patch:  0 => 1
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 I reproduced. The generated migration had a syntax error.
 PR with regression test: https://github.com/django/django/pull/2700

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

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

Re: [Django] #6148: Add generic support for database schemas

2014-05-22 Thread Django

#6148: Add generic support for database schemas
-+-
 Reporter:  ikelly   |Owner:  akaariai
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle postgresql|  Needs documentation:  1
  mysql schemas  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by manelclos@…):

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

Re: [Django] #22678: forms.Form silently won't bind to POST data (under certain combinations of key and label)

2014-05-22 Thread Django

#22678: forms.Form silently won't bind to POST data (under certain combinations 
of
key and label)
--+--
 Reporter:  brycenesbitt  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Forms |  Version:  1.5
 Severity:  Normal|   Resolution:  invalid
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by bmispelon):

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


Comment:

 Hi,

 I believe the problem here is that you're using integers as keys on
 `TestFormX.fields` which is not supported (only strings are allowed).

 Things should work if you use `for key in ('3', '4'):`.

 Marking this as `invalid` consequently.

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

Re: [Django] #22436: migrations fail on custom upload_to on ImageField

2014-05-22 Thread Django

#22436: migrations fail on custom upload_to on ImageField
-+-
 Reporter:  David Binetti|Owner:
 |  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Althalus):

 I'm using 1.7 now and found that migrations fail too my because upload_to
 function is generated dynamically.
 Consider the folloing example:

 {{{
 # utils/files.py
 def gen_upload_to(fieldname, path, ...):
 def upload_to(instance, filename):
 pass  # some custom logic
 return upload_to

 # app/models.py
 class MyModel(models.Model):
 file = models.FileField(upload_to=gen_upload_to('file',
 'path/to/files'))

 # app/migrations/0001_initial.py
 class Migration(migrations.Migration):
 operations = [
 migrations.CreateModel(
 name='MyModel',
 fields=[
 ('file',
 models.FileField(upload_to=utils.files.upload_to)),
 ],
 ),
 ]
 }}}

 Obviously my utils/files.py module doesn't contain `upload_to` function
 with results in errors.
 I had to create dummy `upload_to` in there to prevent import errors, but
 anyway every time I use `makemigrations` command django detect changes in
 my `file` field.

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

Re: [Django] #16508: Provide real support for virtual fields

2014-05-22 Thread Django

#16508: Provide real support for virtual fields
-+-
 Reporter:  vzima|Owner:  pirosb3
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (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 pirosb3):

 * owner:  nobody => pirosb3
 * cc: pirosb3 (added)
 * status:  new => assigned


Comment:

 Hi,

 I will be taking this ticked under consideration as we are currently
 planning a refactor of _meta.

 Dan

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

[Django] #22680: I/O operation on closed file

2014-05-22 Thread Django

#22680: I/O operation on closed file
--+
 Reporter:  shelinanton@… |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  File uploads/storage  |Version:  master
 Severity:  Release blocker   |   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Save method of file field checks contents size on closed  file.

 {{{
 class Author(models.Model):
 photo_url = models.URLField(null=True, blank=True,
 max_length=1024,verbose_name = _('Original photo url'))
 photo_copy =
 models.ImageField(upload_to='photos/%Y/%m/%d/authors',null=True,
 blank=True, verbose_name = _('Thumbnail'))

 def save(self, *args, **kwargs):
 if not self.photo_copy and self.photo_url:
 img_temp = NamedTemporaryFile(delete=True)
 img_temp.write(urllib2.urlopen(self.photo_url).read())
 img_temp.flush()
 self.photo_copy.save('filename.jpg',
 File(img_temp),save=False)
 super(Author, self).save(*args, **kwargs)
 }}}

 Results in:
 ValueError: I/O operation on closed file
 django.db.models.fileds.files.py line 93

 {{{
 self._size = content.size
 }}}

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

[Django] #22679: makemigrations generates invalid code for default_permissions = ()

2014-05-22 Thread Django

#22679: makemigrations generates invalid code for default_permissions = ()
-+-
 Reporter:   |  Owner:  nobody
  rockallite.wulf@…  | Status:  new
 Type:   |Version:  1.7-beta-2
  Uncategorized  |   Keywords:  makemigrations, default_permissions
Component:   |  Has patch:  0
  Migrations |  UI/UX:  0
 Severity:  Release  |
  blocker|
 Triage Stage:   |
  Unreviewed |
Easy pickings:  0|
-+-
 This actually happens in Django 1.7b4.

 When I define a Model with meta info like this:

 {{{
 class Foo(models.Model):
 # ...
 class Meta:
 default_permissions = ()
 }}}

 The {{{./manage.py makemigrations}}} command generates a migration file
 like this:

 {{{
 options={
 # ...
 'default_permissions': (,),
 }
 }}}

 ...which causes SynaxError on migration.

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

Re: [Django] #22676: When doing a makemigration --dry-run skip asking about default values for non-nullable fields?

2014-05-22 Thread Django

#22676: When doing a makemigration --dry-run skip asking about default values 
for
non-nullable fields?
-+--
 Reporter:  shige.abe@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+--
Changes (by mardini):

 * type:  Uncategorized => 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/076.8654a0cdcbbdc676c8c158892e001601%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22676: When doing a makemigration --dry-run skip asking about default values for non-nullable fields?

2014-05-22 Thread Django

#22676: When doing a makemigration --dry-run skip asking about default values 
for
non-nullable fields?
---+--
 Reporter:  shige.abe@…|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Migrations |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+--
Changes (by mardini):

 * has_patch:  0 => 1


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

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

Re: [Django] #22676: When doing a makemigration --dry-run skip asking about default values for non-nullable fields?

2014-05-22 Thread Django

#22676: When doing a makemigration --dry-run skip asking about default values 
for
non-nullable fields?
---+--
 Reporter:  shige.abe@…|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Migrations |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+--
Changes (by mardini):

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


Comment:

 I agree with you. No need for that step since the default value won't be
 used anyway.
 I'll leave the ticket to a core developer to accept though.
 Here's my PR: https://github.com/django/django/pull/2698
 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/076.882e518dce044a57a8053fb8b181f597%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22677: forms.Form silently won't bind to POST data (under certain combinations of key and label)

2014-05-22 Thread Django

#22677: forms.Form silently won't bind to POST data (under certain combinations 
of
key and label)
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Generic views  |  Version:  1.5
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by brycenesbitt):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => duplicate
 * 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/067.6f54a1385e34c44e3f4655a2076bb783%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22678: forms.Form silently won't bind to POST data (under certain combinations of key and label)

2014-05-22 Thread Django

#22678: forms.Form silently won't bind to POST data (under certain combinations 
of
key and label)
--+
 Reporter:  brycenesbitt  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Forms |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 In this example:


 {{{
 class TestFormX(forms.Form):
 test_one = forms.CharField(required=True)

 def __init__(self, *args, **kwargs):
 super(TestFormX, self).__init__(*args, **kwargs)

 self.fields['test_two'] = forms.IntegerField(required=False)
 for key in (3,4):
 self.fields[key]= forms.IntegerField(required=False,
 label='must have a label')

 def sandbox2(request):
 if request.method == 'POST':
 form = TestFormX(request.POST)
 if form.is_valid():
 print 'Form is valid'
 else:
 print form.errors
 else:
 form = TestFormX()
 return render(request, 'xxx_sandbox2.html', {'form' : form},
 status=200)

 }}}

 Form fields test_one and test_two act normally. Fields 3 and 4 render and
 appear to work, but
 won't bind data from the request.POST. Thus, any input by the user is
 lost.

 This was found on a dynamically built from.Form, where an integer database
 primary key was used as the field name.

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

[Django] #22677: forms.Form silently won't bind to POST data (under certain combinations of key and label)

2014-05-22 Thread Django

#22677: forms.Form silently won't bind to POST data (under certain combinations 
of
key and label)
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Generic views  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 In this example:

 {{{
 class TestFormX(forms.Form):
 test_one = forms.CharField(required=True)

 def __init__(self, *args, **kwargs):
 super(TestFormX, self).__init__(*args, **kwargs)

 self.fields['test_two'] = forms.IntegerField(required=False)
 for key in (3,4):
 self.fields[key]= forms.IntegerField(required=False,
 label='must have a label')


 def sandbox2(request):
 if request.method == 'POST':
 form = TestFormX(request.POST)
 if form.is_valid():
 print 'Form is valid'
 else:
 print form.errors
 else:
 form = TestFormX()
 return render(request, 'xxx_sandbox2.html', {'form' : form},
 status=200)
 }}}

 Form fields one and two act normally.  Fields 3 and 4 appear to work, but
 don't bind data from the request.POST.  Thus, any input by the user is
 lost.

 This was found on a dynamically built from.Form, where the database
 primary key was used as the field name.

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

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

[django/django] 604162: Added array field support for PostgreSQL.

2014-05-22 Thread GitHub

Branch: refs/heads/master
Home: https://github.com/django/django
Commit: 604162604bf816fa46b0d972621f06de64df6a66

https://github.com/django/django/commit/604162604bf816fa46b0d972621f06de64df6a66
Author: Marc Tamlyn
Date: 2014-05-22 (Thu, 22 May 2014)

Changed paths:
A django/contrib/postgres/__init__.py
A django/contrib/postgres/fields/__init__.py
A django/contrib/postgres/fields/array.py
A django/contrib/postgres/forms/__init__.py
A django/contrib/postgres/forms/array.py
A django/contrib/postgres/validators.py
M docs/index.txt
M docs/ref/contrib/index.txt
A docs/ref/contrib/postgres/fields.txt
A docs/ref/contrib/postgres/forms.txt
A docs/ref/contrib/postgres/index.txt
A tests/postgres_tests/__init__.py
A tests/postgres_tests/models.py
A tests/postgres_tests/test_array.py
M tests/runtests.py

Log Message:
---
Added array field support for PostgreSQL.

The first part of django.contrib.postgres, including model and two form
fields for arrays of other data types.

This commit is formed of the following work:

Add shell of postgres app and test handling.

First draft of array fields.

Use recursive deconstruction.

Stop creating classes at lookup time.

Add validation and size parameter.

Add contained_by lookup.

Add SimpleArrayField for forms.

Add SplitArrayField (mainly for admin).

Fix prepare_value for SimpleArrayField.

Stop using MultiValueField and MultiWidget.

They don't play nice with flexible sizes.

Add basics of admin integration.

Missing:
- Tests
- Fully working js

Add reference document for django.contrib.postgres.fields.ArrayField.

Various performance and style tweaks.

Fix internal docs link, formalise code snippets.

Remove the admin code for now.

It needs a better way of handing JS widgets in the admin as a whole
before it is easy to write. In particular there are serious issues
involving DateTimePicker when used in an array.

Add a test for nested array fields with different delimiters.

This will be a documented pattern so having a test for it is useful.

Add docs for SimpleArrayField.

Add docs for SplitArrayField.

Remove admin related code for now.

definition -> description

Fix typo.

Py3 errors.

Avoid using regexes where they're not needed.

Allow passing tuples by the programmer.

Add some more tests for multidimensional arrays.

Also fix slicing as much as it can be fixed.

Simplify SplitArrayWidget's data loading.

If we aren't including the variable size one, we don't need to search
like this.

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

[django/django] 475b37: [1.6.x] Used link label in models FAQ to ease tran...

2014-05-22 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 475b3791a348002f99f9553e9baed67b75994701
  
https://github.com/django/django/commit/475b3791a348002f99f9553e9baed67b75994701
  Author: Claude Paroz 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M docs/faq/models.txt

  Log Message:
  ---
  [1.6.x] Used link label in models FAQ to ease translation

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

[django/django] 485163: [1.7.x] Used link label in models FAQ to ease tran...

2014-05-22 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 485163f72cf916231fbef78a645a19dfa34928b2
  
https://github.com/django/django/commit/485163f72cf916231fbef78a645a19dfa34928b2
  Author: Claude Paroz 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M docs/faq/models.txt

  Log Message:
  ---
  [1.7.x] Used link label in models FAQ to ease translation

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

[django/django] d9d924: Used link label in models FAQ to ease translation

2014-05-22 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d9d9242505a59549a7519a35c0f59af13efac462
  
https://github.com/django/django/commit/d9d9242505a59549a7519a35c0f59af13efac462
  Author: Claude Paroz 
  Date:   2014-05-22 (Thu, 22 May 2014)

  Changed paths:
M docs/faq/models.txt

  Log Message:
  ---
  Used link label in models FAQ to ease translation


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

Re: [Django] #22674: migrate does not create missing intermediate table

2014-05-22 Thread Django

#22674: migrate does not create missing intermediate table
---+--
 Reporter:  shige.abe@…|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Migrations |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by davids):

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


Comment:

 the migrations framework use a table in the database to record which
 migrations have been applied (as opposed to e.g. introspection). thus, if
 you manually mess with the tables, it can't tell.

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

77 matches

Mail list logo