date:20140326

Re: [Django] #22346: ModelForm modifies the Model instance before save is called

2014-03-26 Thread Django

#22346: ModelForm modifies the Model instance before save is called
---+--
 Reporter:  lehins@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Forms  |  Version:  1.6
 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 lehins@…):

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


Comment:

 Never mind, I just found a Warning in Documentation, and it actually makes
 sense, since model fields need to be validate as well.

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

[Django] #22346: ModelForm modifies the Model instance before save is called

2014-03-26 Thread Django

#22346: ModelForm modifies the Model instance before save is called
---+
 Reporter:  lehins@…   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Forms  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 So here is a use case that is relevant to me:
 I need a model instance's primary key(pk) before I save the model, but
 only after the model form is validated. In particular I needed it to use
 in a pre_save method on a file field. So my logical solution was:

 {{{
 try:
instance = CustomModel.objects.get(pk=pk)
 except CustomModel.DoesNotExist:
instance = CustomModel()
 form = CustomModelForm(instance=instance, data=request.POST,
 files=request.FILES))
 if form.is_valid():
if not instance.pk:
instance.save() # saves the model while generating a pk
instance = form.save()
 }}}

 To my disappointment, after a few wasted hours, I figured out that binding
 data to a model instance modifies that instance, so when I am calling
 instance.save() it already contains data from the form, before even
 calling form.save() method.
 After finding this ticket: #14885 I also noticed that it may be a partial
 update of the model instance. Despite closed ticket I couldn't find it in
 current documentation.
 In my opinion it is completely illogical. Model instance should only be
 modified only upon form.save() call, this would also give a real use case
 for the existence of commit=False argument: "apply cleaned form data to
 model instance, but do not commit to database."
 Even [https://docs.djangoproject.com/en/1.6/topics/forms/modelforms/#the-
 save-method documentation] follows the logic I am proposing: "A subclass
 of ModelForm can accept an existing model instance as the keyword argument
 instance; if this is supplied, save() will update that instance"

 Overall it sounds to me like a side effect or a bug. If it truly is an
 unavoidable side-effect, I believe, we should get at least a really good
 explanation of it in the documentation.

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

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

Re: [Django] #9025: Nested Inline Support in Admin

2014-03-26 Thread Django

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

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

Re: [Django] #6707: Another implementation for ReverseManyRelatedObjectsDescriptor.set method

2014-03-26 Thread Django

#6707: Another implementation for ReverseManyRelatedObjectsDescriptor.__set__
method
-+-
 Reporter:  favo |Owner:  loic84
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by loic84):

 * owner:  sfllaw => loic84


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

[django/django] b077ba: Add a useful stacklevel to some RemovedInDjango19W...

2014-03-26 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b077ba7ac1af3fb6557d9d32dc08cf6da07cc73d
  
https://github.com/django/django/commit/b077ba7ac1af3fb6557d9d32dc08cf6da07cc73d
  Author: Chris Beaven 
  Date:   2014-03-27 (Thu, 27 Mar 2014)

  Changed paths:
M django/contrib/gis/db/backends/util.py
M django/db/backends/util.py
M django/forms/util.py
M django/utils/tzinfo.py

  Log Message:
  ---
  Add a useful stacklevel to some RemovedInDjango19Warnings


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

[Django] #22345: API documentation should show package name

2014-03-26 Thread Django

#22345: API documentation should show package name
---+
 Reporter:  poswald|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Throughout the API, it can be very difficult to know which package you
 need to import to get access to a class or function. Often this is encoded
 into the permalink but not visible on the page. For example the anchor is:

 https://docs.djangoproject.com/en/dev/ref/forms/fields/#django.forms.Field

 but the class is described as:

 class Field(**kwargs)

 I think it would be best to list it as:

 class django.forms.Field(**kwargs)

 Or at least put the package name as a section header. I imagine there's a
 way to make the documentation do this site-wide or at least for the API
 section?

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

Re: [Django] #21694: Default filter cannot be used with undefined variables

2014-03-26 Thread Django

#21694: Default filter cannot be used with undefined variables
-+--
 Reporter:  mitar|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by mitar):

 The issue is that there is no error or warning when user does this. Even
 in debug mode. There should be at least an exception when this happens.
 Otherwise it is really hard to capture that this is happening.

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

Re: [Django] #22338: test_dict_translation seems to fails with Django 1.6.1, python 3.4 on Fedora

2014-03-26 Thread Django

#22338: test_dict_translation seems to fails with Django 1.6.1, python 3.4 on
Fedora
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Python 3   |  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:  0
---+--
Changes (by timo):

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


Comment:

 I don't think 1.6 is going to support 3.4. Do you get the same error on
 master and/or 1.7? I can't reproduce it with Python 3.4.0 on any of those
 branches, but I imagine it probably has to do with undefined ordering of
 dictionary key iteration and could be fixed by changing `list` to `sorted`
 in the assertion.

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

Re: [Django] #22325: Defining a custom user model in an app and having relations between it and other models in the app causes circular dependencies

2014-03-26 Thread Django

#22325: Defining a custom user model in an app and having relations between it 
and
other models in the app causes circular dependencies
+--
 Reporter:  melinath|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by nliberg):

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

Re: [Django] #6707: Another implementation for ReverseManyRelatedObjectsDescriptor.set method

2014-03-26 Thread Django

#6707: Another implementation for ReverseManyRelatedObjectsDescriptor.__set__
method
-+-
 Reporter:  favo |Owner:  sfllaw
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 Shouldn't at least the documentation for previous versions including
 version 1.6 be updated to not include the pre_remove and post_remove
 actions in the m2m-changed signal?

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

Re: [Django] #22337: makemigrations not working when Field takes FileSystemStorage parameter

2014-03-26 Thread Django

#22337: makemigrations not working when Field takes FileSystemStorage parameter
-+-
 Reporter:  nliberg  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-1
 Keywords:  FileSystemStorage,   |   Resolution:
  migrations | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by nliberg):

 I modified the original patch slightly. The `decode` method now avoids
 adding items to kwargs where the value is the default value. Furthermore I
 added some test code to `tests/file_storage/tests.py` in the second patch.

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

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

[django/django] bf2b0a: Forgotten slash removal in d320863878

2014-03-26 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bf2b0affe42c9c7334188129e39fcdcbca126351
  
https://github.com/django/django/commit/bf2b0affe42c9c7334188129e39fcdcbca126351
  Author: Claude Paroz 
  Date:   2014-03-26 (Wed, 26 Mar 2014)

  Changed paths:
M tests/model_forms/tests.py

  Log Message:
  ---
  Forgotten slash removal in d320863878


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

[Django] #22344: Migration from ForeignKey to FileField fails: AttributeError: 'NoneType' object has no attribute 'to'

2014-03-26 Thread Django

#22344: Migration from ForeignKey to FileField fails: AttributeError: 'NoneType'
object has no attribute 'to'
+
 Reporter:  blueyed |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 The following migration fails to change the ForeignKey field into a
 FileField:
 {{{
 migrations.AlterField(
 model_name='mainfile',
 name='file',
 field=models.FileField(upload_to='...'),
 ),
 }}}
 {{{
   Applying app.0017_auto_20140326_1849...Traceback (most recent call
 last):
   File "…/manage.py", line 62, in 
 execute_from_command_line(sys.argv)
   File "…/django-master/django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File "…/django-master/django/core/management/__init__.py", line 419, in
 execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "…/django-master/django/core/management/base.py", line 288, in
 run_from_argv
 self.execute(*args, **options.__dict__)
   File "…/django-master/django/core/management/base.py", line 337, in
 execute
 output = self.handle(*args, **options)
   File "…/django-master/django/core/management/commands/migrate.py", line
 145, in handle
 executor.migrate(targets, plan, fake=options.get("fake", False))
   File "…/django-master/django/db/migrations/executor.py", line 60, in
 migrate
 self.apply_migration(migration, fake=fake)
   File "…/django-master/django/db/migrations/executor.py", line 94, in
 apply_migration
 migration.apply(project_state, schema_editor)
   File "…/django-master/django/db/migrations/migration.py", line 97, in
 apply
 operation.database_forwards(self.app_label, schema_editor,
 project_state, new_state)
   File "…/django-master/django/db/migrations/operations/fields.py", line
 127, in database_forwards
 from_field.rel.to = to_field.rel.to
 AttributeError: 'NoneType' object has no attribute 'to'

 ipdb> from_model, from_field, from_field.rel, to_field, to_field.rel

 ,
 
 
 
 None)
 }}}

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

[Django] #22343: Two Oracle test failures since the removal of legacy transaction management

2014-03-26 Thread Django

#22343: Two Oracle test failures since the removal of legacy transaction 
management
-+-
   Reporter:  timo   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  master
  layer (models, ORM)|   Keywords:
   Severity:  Release|  Has patch:  0
  blocker|Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 Seeing these test failures after 0f9560855e5ed203b8c911c23237826e28a62a38:
 {{{
 $ ./runtests.py --settings=test_oracle select_for_update
 Testing against Django installed in '/home/tim/code/django/django'
 Creating test database for alias 'default'...
 Creating test user...
 Creating test database for alias 'other'...
 Creating test user...
 .EE...s
 ==
 ERROR: test_for_update_sql_generated
 (select_for_update.tests.SelectForUpdateTests)
 --
 Traceback (most recent call last):
   File "/home/tim/code/django/django/test/testcases.py", line 916, in
 skip_wrapper
 return test_func(*args, **kwargs)
   File "/home/tim/code/django/tests/select_for_update/tests.py", line 80,
 in test_for_update_sql_generated
 list(Person.objects.all().select_for_update())
   File "/home/tim/code/django/django/db/models/query.py", line 141, in
 __iter__
 self._fetch_all()
   File "/home/tim/code/django/django/db/models/query.py", line 961, in
 _fetch_all
 self._result_cache = list(self.iterator())
   File "/home/tim/code/django/django/db/models/query.py", line 265, in
 iterator
 for row in compiler.results_iter():
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line 694,
 in results_iter
 for rows in self.execute_sql(MULTI):
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line
 1150, in cursor_iter
 sentinel):
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line
 1149, in 
 for rows in iter((lambda: cursor.fetchmany(GET_ITERATOR_CHUNK_SIZE)),
   File "/home/tim/code/django/django/db/utils.py", line 101, in inner
 return func(*args, **kwargs)
   File "/home/tim/code/django/django/db/utils.py", line 94, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/home/tim/code/django/django/db/utils.py", line 101, in inner
 return func(*args, **kwargs)
   File "/home/tim/code/django/django/db/backends/oracle/base.py", line
 905, in fetchmany
 return tuple(_rowfactory(r, self.cursor) for r in
 self.cursor.fetchmany(size))
 DatabaseError: ORA-01002: fetch out of sequence


 ==
 ERROR: test_for_update_sql_generated_nowait
 (select_for_update.tests.SelectForUpdateTests)
 --
 Traceback (most recent call last):
   File "/home/tim/code/django/django/test/testcases.py", line 916, in
 skip_wrapper
 return test_func(*args, **kwargs)
   File "/home/tim/code/django/tests/select_for_update/tests.py", line 89,
 in test_for_update_sql_generated_nowait
 list(Person.objects.all().select_for_update(nowait=True))
   File "/home/tim/code/django/django/db/models/query.py", line 141, in
 __iter__
 self._fetch_all()
   File "/home/tim/code/django/django/db/models/query.py", line 961, in
 _fetch_all
 self._result_cache = list(self.iterator())
   File "/home/tim/code/django/django/db/models/query.py", line 265, in
 iterator
 for row in compiler.results_iter():
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line 694,
 in results_iter
 for rows in self.execute_sql(MULTI):
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line
 1150, in cursor_iter
 sentinel):
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line
 1149, in 
 for rows in iter((lambda: cursor.fetchmany(GET_ITERATOR_CHUNK_SIZE)),
   File "/home/tim/code/django/django/db/utils.py", line 101, in inner
 return func(*args, **kwargs)
   File "/home/tim/code/django/django/db/utils.py", line 94, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/home/tim/code/django/django/db/utils.py", line 101, in inner
 return func(*args, **kwargs)
   File "/home/tim/code/django/django/db/backends/oracle/base.py", line
 905, in fetchmany
 return tuple(_rowfactory(r, self.cursor) for r in
 self.cursor.fetchmany(size))
 DatabaseError: ORA-01002: fetch out of sequence


 --
 Ran 7 tests in 3.987s

Re: [Django] #12030: PositiveIntegerField in model form does not validate max value

2014-03-26 Thread Django

#12030: PositiveIntegerField in model form does not validate max value
-+-
 Reporter:  paul@…   |Owner:  Simon
 Type:  Bug  |  Charette 
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  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 Simon Charette ):

 In [changeset:"4678efd3f1e2f764583a59b9c1f4302d955acebb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4678efd3f1e2f764583a59b9c1f4302d955acebb"
 [1.7.x] Fixed the PostGIS circular imports caused by 1506c71a95.

 Thanks to @loic for the help and @timgraham for the review.

 refs #12030.

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

[django/django] 4678ef: [1.7.x] Fixed the PostGIS circular imports caused ...

2014-03-26 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 4678efd3f1e2f764583a59b9c1f4302d955acebb
  
https://github.com/django/django/commit/4678efd3f1e2f764583a59b9c1f4302d955acebb
  Author: Simon Charette 
  Date:   2014-03-26 (Wed, 26 Mar 2014)

  Changed paths:
M django/db/models/fields/__init__.py

  Log Message:
  ---
  [1.7.x] Fixed the PostGIS circular imports caused by 1506c71a95.

Thanks to @loic for the help and @timgraham for the review.

refs #12030.

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

[django/django] d32086: Fixed #22114 -- Stopped adding trailing slashes in...

2014-03-26 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d320863878f097b5cbf33ace12e3adb5e02f27e0
  
https://github.com/django/django/commit/d320863878f097b5cbf33ace12e3adb5e02f27e0
  Author: Claude Paroz 
  Date:   2014-03-26 (Wed, 26 Mar 2014)

  Changed paths:
M django/forms/fields.py
M docs/releases/1.8.txt
M tests/forms_tests/tests/test_fields.py

  Log Message:
  ---
  Fixed #22114 -- Stopped adding trailing slashes in URLField.to_python

Thanks coredumperror at gmail.com for the report 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/53330b0b6c90e_4318e39d386717e%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21758: Document South->built-in migrations transition

2014-03-26 Thread Django

Comment (by andrewgodwin):

This is meant to be the purpose of South 2 - it will support the same
migration format as 1.7, but run on versions 1.4 - 1.6, so you can follow
the same process for reusable apps as long as you tell your users to also
use South 2 (which cannot be used alongside South 1, but that's a separate
issue unfortunately).

`./manage.py migrate` already detects and ignores directories full of
South migrations, we could make it list the ones it ignores on the list it
outputs, however. If South is installed it'll immediately crash as it
doesn't work with 1.7; I'll release a final 0.x update that has a few
other bugfixes and a nice error message saying "this won't work with 1.7"
before I release 2.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/066.4d04c32a4be14b3bbf51ba8fd5faf37d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22114: URLField form adds trailing slash to pathless URLs

2014-03-26 Thread Django

#22114: URLField form adds trailing slash to pathless URLs
-+-
 Reporter:  coredumperror@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"d320863878f097b5cbf33ace12e3adb5e02f27e0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d320863878f097b5cbf33ace12e3adb5e02f27e0"
 Fixed #22114 -- Stopped adding trailing slashes in URLField.to_python

 Thanks coredumperror at gmail.com for the report 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/081.b2bae0ccb73b885c56c98eb17a1aafe9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12030: PositiveIntegerField in model form does not validate max value

2014-03-26 Thread Django

#12030: PositiveIntegerField in model form does not validate max value
-+-
 Reporter:  paul@…   |Owner:  Simon
 Type:  Bug  |  Charette 
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  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 Simon Charette ):

 In [changeset:"b9e50e47742f67dcf3c37aad989b350e8255154e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b9e50e47742f67dcf3c37aad989b350e8255154e"
 Fixed the PostGIS circular imports caused by 1506c71a95.

 Thanks to @loic for the help and @timgraham for the review.

 refs #12030.
 }}}

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

[django/django] b9e50e: Fixed the PostGIS circular imports caused by 1506c...

2014-03-26 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b9e50e47742f67dcf3c37aad989b350e8255154e
  
https://github.com/django/django/commit/b9e50e47742f67dcf3c37aad989b350e8255154e
  Author: Simon Charette 
  Date:   2014-03-26 (Wed, 26 Mar 2014)

  Changed paths:
M django/db/models/fields/__init__.py

  Log Message:
  ---
  Fixed the PostGIS circular imports caused by 1506c71a95.

Thanks to @loic for the help and @timgraham for the review.

refs #12030.


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

Re: [Django] #22325: Defining a custom user model in an app and having relations between it and other models in the app causes circular dependencies

2014-03-26 Thread Django

#22325: Defining a custom user model in an app and having relations between it 
and
other models in the app causes circular dependencies
+--
 Reporter:  melinath|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by ondrowan):

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

[Django] #22342: Changing a model to an abstract model caused "ValueError: Related model 'app.Model' cannot be resolved"

2014-03-26 Thread Django

#22342: Changing a model to an abstract model caused "ValueError: Related model
'app.Model' cannot be resolved"
+
 Reporter:  blueyed |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I have just run into an error with `migrate`.

 I had turned an existing model (which had a database table already) into a
 abstract base for others.

 The generated migration was, and removing it from the migration worked
 around the problem:

 {{{
 migrations.DeleteModel(
 name='Model',
 ),
 }}}


 {{{
   Applying app.0016_auto_20140326_1723...Traceback (most recent call
 last):
   File "…/manage.py", line 62, in 
 execute_from_command_line(sys.argv)
   File "…/django-master/django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File "…/django-master/django/core/management/__init__.py", line 419, in
 execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "…/django-master/django/core/management/base.py", line 288, in
 run_from_argv
 self.execute(*args, **options.__dict__)
   File "…/django-master/django/core/management/base.py", line 337, in
 execute
 output = self.handle(*args, **options)
   File "…/django-master/django/core/management/commands/migrate.py", line
 145, in handle
 executor.migrate(targets, plan, fake=options.get("fake", False))
   File "…/django-master/django/db/migrations/executor.py", line 60, in
 migrate
 self.apply_migration(migration, fake=fake)
   File "…/django-master/django/db/migrations/executor.py", line 94, in
 apply_migration
 migration.apply(project_state, schema_editor)
   File "…/django-master/django/db/migrations/migration.py", line 97, in
 apply
 operation.database_forwards(self.app_label, schema_editor,
 project_state, new_state)
   File "…/django-master/django/db/migrations/operations/fields.py", line
 83, in database_forwards
 schema_editor.remove_field(from_model,
 from_model._meta.get_field_by_name(self.name)[0])
   File "…/django-master/django/db/backends/schema.py", line 443, in
 remove_field
 if field.db_parameters(connection=self.connection)['type'] is None:
   File "…/django-master/django/db/models/fields/related.py", line 1758, in
 db_parameters
 return {"type": self.db_type(connection), "check": []}
   File "…/django-master/django/db/models/fields/related.py", line 1749, in
 db_type
 rel_field = self.related_field
   File "…/django-master/django/db/models/fields/related.py", line 1655, in
 related_field
 return self.foreign_related_fields[0]
   File "…/django-master/django/db/models/fields/related.py", line 1414, in
 foreign_related_fields
 return tuple(rhs_field for lhs_field, rhs_field in
 self.related_fields)
   File "…/django-master/django/db/models/fields/related.py", line 1401, in
 related_fields
 self._related_fields = self.resolve_related_fields()
   File "…/django-master/django/db/models/fields/related.py", line 1386, in
 resolve_related_fields
 raise ValueError('Related model %r cannot be resolved' % self.rel.to)
 ValueError: Related model 'app.Model' cannot be resolved
 }}}

 It might be somewhat related to bug #22319.

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

Re: [Django] #22339: accessing m2m relation where database is not 'default' throws error

2014-03-26 Thread Django

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

Comment:

I've done some testing on clean install and the problem seems to be
elsewhere. I can confirm the relation m2m lookups work as expected. I
going to close this ticket and file another one if im able to pinpoint the
bug mode precisely. Simple reinstall from ver. 1.6.2 to 1.7 causes the
code to fall but at the moment it's not clear to me where the problem 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/076.e583eac913a5e25cfcce12156e04615c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22341: Split django.db.models.fields.related into multiple modules.

2014-03-26 Thread Django

#22341: Split django.db.models.fields.related into multiple modules.
-+-
 Reporter:  loic84   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (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 loic84):

 @timo, very good point, clearly this needs to wait for the 1.7 release.

 The latest effort regarding this ticket is tracked at
 https://github.com/django/django/pull/2411.

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

Re: [Django] #22341: Split django.db.models.fields.related into multiple modules.

2014-03-26 Thread Django

#22341: Split django.db.models.fields.related into multiple modules.
-+-
 Reporter:  loic84   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (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|
-+-
Changes (by timo):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I suggest we do it after 1.7 is released so backporting any bug fixes in
 this area in the meantime is not so painful.

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

[Django] #22341: Split django.db.models.fields.related into multiple modules.

2014-03-26 Thread Django

#22341: Split django.db.models.fields.related into multiple modules.
--+
 Reporter:  loic84|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The `django.db.models.fields.related` module is very large and pretty hard
 to work with.

 It contains a lot of similar concepts with only slight differences, and
 one thing can easily be mistaken for its exact opposite, which makes
 navigating the file very error-prone. This is made worse by the fact that
 some class name are borderline wrong, (e.g.
 `ReverseSingleRelatedObjectDescriptor` which actually is the forward FK
 descriptor).

 Quoting akaariai: "fields/related.py is a brain melting machine".

 This ticket proposes that we turn `related.py` into a package with the
 following modules: `related_field.py`, `many_to_one.py`, `one_to_one.py`
 and `many_to_many.py`.

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

Re: [Django] #21758: Document South->built-in migrations transition

2014-03-26 Thread Django

Comment (by lukeplant):

These instructions work OK for projects, but for resuable apps it is
harder. Most re-usable apps will need to support several Django versions,
and 1.7 adoption is going to be **severely** hindered if it isn't possible
for an app to support both 1.7 and earlier versions.

It seems that it should be possible to support this by use of
`MIGRATION_MODULES`. e.g. you can put `MIGRATION_MODULES = {'foo':
'foo.migrations_17'}` (or `django_migrations` or something) if you are
running `foo` on Django 1.7 (because the old South migrations will be in
`foo.migrations`, and they will need to stay there AFAICS).

It would really help with the upgrade to 1.7 if this was documented, and
all apps adopted the same conventions and strategy.

Actually, I was hoping for much better support for this use case. What
will happen if someone upgrades to Django 1.7 and runs `./manage.py
migrate` with South installed and various South migrations still in place
(from their main project and all the 3rd party stuff)? This is going to be
so common that I think that graceful detection of this situation should be
a release blocker.

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

Re: [Django] #22029: documentation: new best place to put the signal handler registration

2014-03-26 Thread Django

#22029: documentation: new best place to put the signal handler registration
--+
 Reporter:  un33k |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"5233b366935dcc81e47546921ab4eb5007c83719"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5233b366935dcc81e47546921ab4eb5007c83719"
 Fixed #22029 -- Removed obsolete advice on registering migrate/syncdb
 signal handlers.

 All signals should now be registered in AppConfig.ready().

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

[django/django] 5233b3: Fixed #22029 -- Removed obsolete advice on registe...

2014-03-26 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5233b366935dcc81e47546921ab4eb5007c83719
  
https://github.com/django/django/commit/5233b366935dcc81e47546921ab4eb5007c83719
  Author: Tim Graham 
  Date:   2014-03-26 (Wed, 26 Mar 2014)

  Changed paths:
M docs/ref/signals.txt

  Log Message:
  ---
  Fixed #22029 -- Removed obsolete advice on registering migrate/syncdb signal 
handlers.

All signals should now be registered in AppConfig.ready().

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

Re: [Django] #22340: Legacy Table Creation Methods Not Properly Deprecated

2014-03-26 Thread Django

#22340: Legacy Table Creation Methods Not Properly Deprecated
-+-
 Reporter:  mlavin   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-1
 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 manfre):

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

Re: [Django] #22029: documentation: new best place to put the signal handler registration

2014-03-26 Thread Django

#22029: documentation: new best place to put the signal handler registration
--+
 Reporter:  un33k |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  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
--+

Comment (by Tim Graham ):

 In [changeset:"994274ea8315282484bc24aa403b2fd12b5bdeec"]:
 {{{
 #!CommitTicketReference repository=""
 revision="994274ea8315282484bc24aa403b2fd12b5bdeec"
 [1.7.x] Fixed #22029 -- Removed obsolete advice on registering
 migrate/syncdb signal handlers.

 All signals should now be registered in AppConfig.ready().

 Thanks un33k for the report.

 Backport of 5233b36693 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/063.75ecc050a2c3cd127b31ce8df1ef69f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 994274: [1.7.x] Fixed #22029 -- Removed obsolete advice on...

2014-03-26 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 994274ea8315282484bc24aa403b2fd12b5bdeec
  
https://github.com/django/django/commit/994274ea8315282484bc24aa403b2fd12b5bdeec
  Author: Tim Graham 
  Date:   2014-03-26 (Wed, 26 Mar 2014)

  Changed paths:
M docs/ref/signals.txt

  Log Message:
  ---
  [1.7.x] Fixed #22029 -- Removed obsolete advice on registering migrate/syncdb 
signal handlers.

All signals should now be registered in AppConfig.ready().

Thanks un33k for the report.

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

Re: [Django] #22340: Legacy Table Creation Methods Not Properly Deprecated

2014-03-26 Thread Django

#22340: Legacy Table Creation Methods Not Properly Deprecated
-+-
 Reporter:  mlavin   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-1
 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 manfre):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * 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/064.c72ad242637abf3c82d17517c73d01af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16256: More class based views: formsets derived generic views

2014-03-26 Thread Django

#16256: More class based views: formsets derived generic views
---+
 Reporter:  rasca  |Owner:  rasca
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by ville@…):

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

Re: [Django] #22337: makemigrations not working when Field takes FileSystemStorage parameter

2014-03-26 Thread Django

#22337: makemigrations not working when Field takes FileSystemStorage parameter
-+-
 Reporter:  nliberg  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-1
 Keywords:  FileSystemStorage,   |   Resolution:
  migrations | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by bmispelon):

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


Comment:

 The patch looks sensible and it does seem to fix the issue but it needs
 some tests too.

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

[django/django] 4bd741: [1.7.x] Fixed Python 3.4 test failure.

2014-03-26 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 4bd7411edf21f235a0a2b67f170a2bad8c37518c
  
https://github.com/django/django/commit/4bd7411edf21f235a0a2b67f170a2bad8c37518c
  Author: Tim Graham 
  Date:   2014-03-26 (Wed, 26 Mar 2014)

  Changed paths:
M django/utils/html_parser.py

  Log Message:
  ---
  [1.7.x] Fixed Python 3.4 test failure.

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

Re: [Django] #22337: makemigrations not working when Field takes FileSystemStorage parameter

2014-03-26 Thread Django

#22337: makemigrations not working when Field takes FileSystemStorage parameter
-+-
 Reporter:  nliberg  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-1
 Keywords:  FileSystemStorage,   |   Resolution:
  migrations | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by bmispelon):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * severity:  Normal => Release blocker
 * 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/065.d74d26827f6f13543456f25f813d29f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 45ef4b: Fixed Python 3.4 test failure.

2014-03-26 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 45ef4baf5cb018acba16c269e3d470ee1de146e0
  
https://github.com/django/django/commit/45ef4baf5cb018acba16c269e3d470ee1de146e0
  Author: Tim Graham 
  Date:   2014-03-26 (Wed, 26 Mar 2014)

  Changed paths:
M django/utils/html_parser.py

  Log Message:
  ---
  Fixed Python 3.4 test failure.


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

Re: [Django] #22029: documentation: new best place to put the signal handler registration

2014-03-26 Thread Django

#22029: documentation: new best place to put the signal handler registration
--+
 Reporter:  un33k |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
--+

Comment (by un33k):

 The current docs says that you "'''need to'''" register these signals in
 the management module or else.

 This is not the case anymore ... AppConfig.ready() is a better place,
 right Aymeric?

 Also, circular dependencies are no longer the issue if these signals are
 registering in AppConfig.ready() and yes, no need to register in urls.py
 are more.

 In short: "need to" is no longer true.

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

[Django] #22340: Legacy Table Creation Methods Not Properly Deprecated

2014-03-26 Thread Django

#22340: Legacy Table Creation Methods Not Properly Deprecated
--+
 Reporter:  mlavin|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.7-beta-1
 Severity:  Release blocker   |   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 As noted in
 
https://github.com/django/django/commit/1cb6729f58ef14c2042373d8bd61fa264a955705
 and https://groups.google.com/d/msg/django-
 developers/PWPj3etj3-U/vH4DjnVttIUJ the DB backend {{{DatabaseCreation}}}
 class and the legacy path for table creating in the {{{migrate}}} command
 are being removed. {{{DatabaseCreation}}} is a documented part of the API
 in https://docs.djangoproject.com/en/1.6/topics/testing/advanced/#django-
 db-connection-creation and is still actively used in Django's code and
 test suite. For this to be deprecated per Django's published policy these
 should raise a deprecation warning when used prior to removal and
 currently neither do.

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

Re: [Django] #22339: accessing m2m relation where database is not 'default' throws error

2014-03-26 Thread Django

#22339: accessing m2m relation where database is not 'default' throws error
-+-
 Reporter:  zzart999@…   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by akaariai):

 * severity:  Normal => Release blocker


Comment:

 I don't have time to check this just now, but I'll mark this as a release
 blocker so that this will not be missed.

 If possible, a small sample project or code for models + would help a lot
 in debugging this, from the description I am not exactly sure how to
 reproduce this.

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

Re: [Django] #22029: documentation: new best place to put the signal handler registration

2014-03-26 Thread Django

#22029: documentation: new best place to put the signal handler registration
--+
 Reporter:  un33k |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
--+

Comment (by aaugustin):

 I didn't check the commit logs, but the wording sounds like this is a
 warning against registering signals in urls.py (for instance). I don't
 think these signals are a special case any more.

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

Re: [Django] #22339: accessing m2m relation where database is not 'default' throws error

2014-03-26 Thread Django

#22339: accessing m2m relation where database is not 'default' throws error
-+-
 Reporter:  zzart999@…   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by anonymous):

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


Comment:

 I've forgotten to add that this works in django 1.6.2 and stops working in
 django 1.7beta and current git 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/076.0c9597ee3e27058e2ce5f6adde9cb730%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22029: documentation: new best place to put the signal handler registration

2014-03-26 Thread Django

#22029: documentation: new best place to put the signal handler registration
--+
 Reporter:  un33k |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 timo):

 * has_patch:  0 => 1


Comment:

 I wonder if we need to mention this as something specific to these signals
 though? Can we assume all signals will now be registered in
 `AppConfig.ready()`?

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

[Django] #22339: accessing m2m relation where database is not 'default' throws error

2014-03-26 Thread Django

#22339: accessing m2m relation where database is not 'default' throws error
--+
 Reporter:  zzart999@…|  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.7-beta-1
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Giving two models
 like here :
 https://docs.djangoproject.com/en/dev/topics/db/examples/many_to_many/
 with m2m relation located on single database which is configured with a
 different alias then 'default'

 Accessing relation  a1.publications.all() throws error:

 {{{
 Traceback (most recent call last):
   File "", line 1, in 
   File "/home/mars/dev/ve/v3/lib/python3.3/site-
 packages/django/db/models/manager.py", line 191, in all
 return self.get_queryset()
   File "/home/mars/dev/ve/v3/lib/python3.3/site-
 packages/django/db/models/fields/related.py", line 874, in get_queryset
 return qs._next_is_sticky().filter(**self.core_filters)
   File "/home/mars/dev/ve/v3/lib/python3.3/site-
 packages/django/db/models/query.py", line 686, in filter
 return self._filter_or_exclude(False, *args, **kwargs)
   File "/home/mars/dev/ve/v3/lib/python3.3/site-
 packages/django/db/models/query.py", line 704, in _filter_or_exclude
 clone.query.add_q(Q(*args, **kwargs))
   File "/home/mars/dev/ve/v3/lib/python3.3/site-
 packages/django/db/models/sql/query.py", line 1284, in add_q
 clause, require_inner = self._add_q(where_part, self.used_aliases)
   File "/home/mars/dev/ve/v3/lib/python3.3/site-
 packages/django/db/models/sql/query.py", line 1311, in _add_q
 current_negated=current_negated, connector=connector)
   File "/home/mars/dev/ve/v3/lib/python3.3/site-
 packages/django/db/models/sql/query.py", line 1138, in build_filter
 lookups, parts, reffed_aggregate = self.solve_lookup_type(arg)
   File "/home/mars/dev/ve/v3/lib/python3.3/site-
 packages/django/db/models/sql/query.py", line 1076, in solve_lookup_type
 _, field, _, lookup_parts = self.names_to_path(lookup_splitted,
 self.get_meta())
   File "/home/mars/dev/ve/v3/lib/python3.3/site-
 packages/django/db/models/sql/query.py", line 1380, in names_to_path
 self.raise_field_error(opts, name)
   File "/home/mars/dev/ve/v3/lib/python3.3/site-
 packages/django/db/models/sql/query.py", line 1386, in raise_field_error
 "Choices are: %s" % (name, ", ".join(available)))
 django.core.exceptions.FieldError: Cannot resolve keyword 'article'
 choices are 
 }}}

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

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

Re: [Django] #22336: Impossible to exclude specific subdirectories with makemessages

2014-03-26 Thread Django

#22336: Impossible to exclude specific subdirectories with makemessages
-+-
 Reporter:  infraredgirl |Owner:
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   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 anubhav9042):

 * owner:  anubhav9042 =>
 * status:  assigned => new


Comment:

 There is some problem in running of makemessages in my django
 installation. So I am deassigning myself.

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

[Django] #22338: test_dict_translation seems to fails with Django 1.6.1, python 3.4 on Fedora

2014-03-26 Thread Django

#22338: test_dict_translation seems to fails with Django 1.6.1, python 3.4 on
Fedora
+
 Reporter:  anonymous   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Python 3|Version:  1.6
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 {{{
 ==
 FAIL: test_dict_translation
 (utils_tests.test_datastructures.MultiValueDictTests)
 --
 Traceback (most recent call last):
   File "/builddir/build/BUILD/python3-python-
 django-1.6-1.fc21/tests/utils_tests/test_datastructures.py", line 283, in
 test_dict_translation
 self.assertEqual(list(six.iterkeys(d)), list(six.iterkeys(mvd)))
 AssertionError: Lists differ: ['pm', 'devs'] != ['devs', 'pm']
 First differing element 0:
 pm
 devs
 - ['pm', 'devs']
 + ['devs', 'pm']
 --
 }}}

 Full build log: http://mstuchli.fedorapeople.org/build.log

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

Re: [Django] #21941: document kwargs parameter to url()

2014-03-26 Thread Django

#21941: document kwargs parameter to url()
--+
 Reporter:  cjerdonek |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:  url,kwargs| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Left comments for improvement on the PR. Please uncheck "patch needs
 improvement" when it's updated, 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/067.f1bce9fd83c48d82a93dbbe94f590f7c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22114: URLField form adds trailing slash to pathless URLs

2014-03-26 Thread Django

#22114: URLField form adds trailing slash to pathless URLs
-+-
 Reporter:  coredumperror@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

 * stage:  Accepted => Ready for checkin


Comment:

 For the release note (besides moving it to 1.8): "URLField.to_python no
 longer adds a trailing slash to pathless URLs." Otherwise, LGTM.

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

Re: [Django] #22227: save_model in ModelAdmin with "formsets" parameter

2014-03-26 Thread Django

#7: save_model in ModelAdmin with "formsets" parameter
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.6
Component:  contrib.admin|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Could you put the logic to update the instance in `save_formset()`
 instead? That's passed `form` so you could access `form.instance`. Adding
 additional arguments to `save_model()` will be backwards incompatible for
 anyone overriding the method.

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

Re: [Django] #17638: Link up topic guides with API reference

2014-03-26 Thread Django

#17638: Link up topic guides with API reference
---+-
 Reporter:  oinopion   |Owner:  anonymous
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-

Comment (by timo):

 I don't think the table of contents should be moved into the "See Also"
 boxes, otherwise, this looks ok.

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

Re: [Django] #21858: Clarify 1.6 release notes regarding ManyToManyField help_text

2014-03-26 Thread Django

#21858: Clarify 1.6 release notes regarding ManyToManyField help_text
---+
 Reporter:  lee@…  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.6
 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 timo):

 * has_patch:  0 => 1


Comment:

 I had a chance to look at this when I did the deprecation removals for
 1.8. Could you let me know if the attached patch clarifies the situation
 for you?

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

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

Re: [Django] #6707: Another implementation for ReverseManyRelatedObjectsDescriptor.set method

2014-03-26 Thread Django

#6707: Another implementation for ReverseManyRelatedObjectsDescriptor.__set__
method
-+-
 Reporter:  favo |Owner:  sfllaw
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 This bug was opened "6 years ago" and we are still around the "patch".
 What would it take to get this fixed?

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

[Django] #22337: makemigrations not working when Field takes FileSystemStorage parameter

2014-03-26 Thread Django

#22337: makemigrations not working when Field takes FileSystemStorage parameter
+---
 Reporter:  nliberg |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.7-beta-1
 Severity:  Normal  |   Keywords:  FileSystemStorage, migrations
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  1   |  UI/UX:  0
+---
 `FileSystemStorage` is not serializable. Because of this running
 `./manage.py makemigrations` for an app that contains fields that use such
 storage results in an exception:
 {{{ValueError: Cannot serialize:
 }}}

 '''Background''':
 When `manage.py makemigrations` is run on a new app the `deconstruct`
 method is invoked for all fields. According to the django documentation
 every value in the deconstructed `kwargs` dictionary "should itself be
 serializable". However, this is not the case when one passes a
 `FileSystemStorage` object as `storage` parameter to the `FileField`
 constructor. The `deconstruct` method of the `FileFIeld` class adds the
 `FileSystemStorage` storage object to `kwargs` without it being
 serializable.

 '''Fix:'''
 I attach a patch that adds a `deconstruct` method to the
 `django.core.files.storage.FileSystemStorage` class.

 '''Reproducing'''
 The problem can be reproduced by starting a new app using the following
 models.py file and running `./manage.py makemigrations `
   {{{#!python
 from django.db import models
 from django.core.files.storage import FileSystemStorage

 class MyModel(models.Model):
 myfile = models.FileField('File', upload_to='myfiles',
 storage=FileSystemStorage(location='/tmp'))
 }}}

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

Re: [Django] #22335: tests.user_commands.UtilsTests failure on non-English Windows systems

2014-03-26 Thread Django

#22335: tests.user_commands.UtilsTests failure on non-English Windows systems
-+-
 Reporter:  zsiciarz |Owner:  zsiciarz
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Zbigniew Siciarz ):

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


Comment:

 In [changeset:"3cdb0baa453e2cc09c0a5c5c04cce66a6dc4e789"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3cdb0baa453e2cc09c0a5c5c04cce66a6dc4e789"
 Fixed #22335 -- Fixed popen_wrapper error on non-English Windows systems.
 }}}

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

Re: [Django] #22335: tests.user_commands.UtilsTests failure on non-English Windows systems

2014-03-26 Thread Django

#22335: tests.user_commands.UtilsTests failure on non-English Windows systems
-+-
 Reporter:  zsiciarz |Owner:  zsiciarz
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"ab4c96cff08b7a196807c0faaeca1b8b7ad1e8ea"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ab4c96cff08b7a196807c0faaeca1b8b7ad1e8ea"
 Merge pull request #2481 from zsiciarz/ticket-22335

 Fixed #22335 -- Fixed popen_wrapper error on non-English Windows systems.
 }}}

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

[django/django] 3cdb0b: Fixed #22335 -- Fixed popen_wrapper error on non-E...

2014-03-26 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3cdb0baa453e2cc09c0a5c5c04cce66a6dc4e789
  
https://github.com/django/django/commit/3cdb0baa453e2cc09c0a5c5c04cce66a6dc4e789
  Author: Zbigniew Siciarz 
  Date:   2014-03-26 (Wed, 26 Mar 2014)

  Changed paths:
M django/core/management/utils.py

  Log Message:
  ---
  Fixed #22335 -- Fixed popen_wrapper error on non-English Windows systems.


  Commit: ab4c96cff08b7a196807c0faaeca1b8b7ad1e8ea
  
https://github.com/django/django/commit/ab4c96cff08b7a196807c0faaeca1b8b7ad1e8ea
  Author: Claude Paroz 
  Date:   2014-03-26 (Wed, 26 Mar 2014)

  Changed paths:
M django/core/management/utils.py

  Log Message:
  ---
  Merge pull request #2481 from zsiciarz/ticket-22335

Fixed #22335 -- Fixed popen_wrapper error on non-English Windows systems.


Compare: https://github.com/django/django/compare/ff874f363ce6...ab4c96cff08b

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

58 matches

Mail list logo