[Django] #20257: QuerySet that prefetches related object with a ManyToMany field cannot be pickled.

[Django]

#20257: QuerySet that prefetches related object with a ManyToMany field cannot 
be
pickled.
-+
 Reporter:  bryced   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (Cache system)  |Version:  1.5
 Severity:  Release blocker  |   Keywords:  ORM, pickle, cache
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 After upgrading from 1.4 to 1.5, exceptions were thrown when trying to
 pickle certain querysets. This means that the caching framework doesn't
 work for these querysets.

 In 1.4 the following code runs fine. In 1.5 this error occurs:
 {{{
 PicklingError: Can't pickle :
 it's not found as people.models.SocialProfile_friends
 }}}


 models.py
 {{{
 from django.db import models


 class Person(models.Model):
 name = models.CharField(max_length=200)


 class SocialProfile(models.Model):
 person = models.ForeignKey(Person)
 friends = models.ManyToManyField('self')

 }}}

 tests.py
 {{{
 from django.test import TestCase
 from people.models import Person
 import pickle


 class SimpleTest(TestCase):

 def test_pickle_failure(self):
 bob = Person(name="Bob")
 bob.save()

 people =
 Person.objects.all().prefetch_related('socialprofile_set')
 pickle.dumps(people)
 }}}

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

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

Re: [Django] #20256: Incorrect text in startproject command line help

[Django]

#20256: Incorrect text in startproject command line help
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   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:  1|
-+-
Changes (by bmispelon):

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


Comment:

 Hi,

 Thanks for the report, it does appear that the help text is incorrect.

 For reference, here's the method where the project/app template handling
 happens:
 
https://github.com/django/django/blob/master/django/core/management/templates.py#L187

 As for your proposed correction, it looks good to me, though I would write
 "URL" instead of "url".

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

Re: [Django] #17048: Add Docs for Guidelines for Upgrading an Existing Project's Django

[Django]

#17048: Add Docs for Guidelines for Upgrading an Existing Project's Django
---+
 Reporter:  dstufft|Owner:  susan
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  upgrading  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by anonymous):

 I've attempted to resolve this ticket in my PR:
 https://github.com/django/django/pull/1012 Feel free to code 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20256: Incorrect text in startproject command line help

[Django]

#20256: Incorrect text in startproject command line help
+
 Reporter:  anonymous   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Core (Management commands)  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  1   |  UI/UX:  0
+
 The command line help for startproject `django-admin.py startproject
 --help` is

 {{{
   --template=TEMPLATE   The dotted import path to load the template from.
 }}}

 The directory need not to be ''importable'' and should not be ''dotted''
 but a path with "/".

 {{{
 --- a/django/core/management/templates.py
 +++ b/django/core/management/templates.py
 @@ -43,7 +43,7 @@ class TemplateCommand(BaseCommand):
  option_list = BaseCommand.option_list + (
  make_option('--template',
  action='store', dest='template',
 -help='The dotted import path to load the template
 from.'),
 +help='The path or url to load the template from.'),
  make_option('--extension', '-e', dest='extensions',
  action='append', default=['py'],
  help='The file extension(s) to render (default:
 "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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite

[Django]

#20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite
-+-
 Reporter:  burton449geo@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5-rc-1
Component:  GIS  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  GeoDjango,   |  Needs documentation:  0
  Spatialite |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by burton449geo@…):

 I do not have the error anymore with the patch installed. Good job and
 thank you!

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

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

Re: [Django] #20251: UnicodeEncodeError with DecimalField

[Django]

#20251: UnicodeEncodeError with DecimalField
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  1.5
 Severity:  Normal |   Resolution:  needsinfo
 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 anonymous):

 I use cdecimal for speedup operations, it problem

 {{{
 import cdecimal # speedup decimal
 sys.modules["decimal"] = cdecimal
 }}}

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

Re: [Django] #20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite

[Django]

#20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite
-+-
 Reporter:  burton449geo@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5-rc-1
Component:  GIS  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  GeoDjango,   |  Needs documentation:  0
  Spatialite |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by claudep):

 OK, now I see the bug, which has been fixed in master by commit
 [eb9430fc4be1]. It was unfortunately a bit late to enter the 1.5 branch. I
 will try to make a more limited patch for the stable branch. Could you
 test the following patch to see if it resolves your issue?

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

Re: [Django] #20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite

[Django]

#20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite
-+-
 Reporter:  burton449geo@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5-rc-1
Component:  GIS  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  GeoDjango,   |  Needs documentation:  0
  Spatialite |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by burton449geo@…):

 In the django project shell: print(connection.ops.spatial_version())
 returns 3.0.1 and connection.ops.spatialite_version_tuple() returns
 (u'3.0.1', 3,0,1)

 In spatialite prompt: SELECT spatialite_version(); returns 4.0.0

 There is no error on those results, it was done on the same spatilatie db
 defined in settings.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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17840: Overriding form field error messages without argument causes string formatting error.

[Django]

#17840: Overriding form field error messages without argument causes string
formatting error.
+
 Reporter:  klein4  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Forms   |  Version:  1.3
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"be9ae693c46021fd3a70c0ec21dd566960b29ffb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="be9ae693c46021fd3a70c0ec21dd566960b29ffb"
 Fixed #17840 -- Generalized named placeholders in form error messages

 Also fixed plural messages for DecimalField.
 }}}

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

[django/django] be9ae6: Fixed #17840 -- Generalized named placeholders in ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: be9ae693c46021fd3a70c0ec21dd566960b29ffb
  
https://github.com/django/django/commit/be9ae693c46021fd3a70c0ec21dd566960b29ffb
  Author: Claude Paroz 
  Date:   2013-04-13 (Sat, 13 Apr 2013)

  Changed paths:
M django/forms/fields.py
M django/forms/models.py
M tests/forms_tests/tests/test_error_messages.py

  Log Message:
  ---
  Fixed #17840 -- Generalized named placeholders in form error messages

Also fixed plural messages for DecimalField.



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

Re: [Django] #20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite

[Django]

#20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite
-+-
 Reporter:  burton449geo@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5-rc-1
Component:  GIS  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  GeoDjango,   |  Needs documentation:  0
  Spatialite |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by claudep):

 Oh, sorry, `spatial_version` is a cached property in master, but it is a
 method in 1.5. So the last snippet line should read
 {{{print(connection.ops.spatial_version())}}}. Here is the code:
 
https://github.com/django/django/blob/stable/1.5.x/django/contrib/gis/db/backends/spatialite/operations.py#L246

 Basically, this executes the SQL query `SELECT spatialite_version();` (you
 can also try it at the spatialite prompt).
 It would also be interesting to get the result of
 `connection.ops.spatialite_version_tuple()`.

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

Re: [Django] #15819: Admin searches should use distinct, if query involves joins

[Django]

#15819: Admin searches should use distinct, if query involves joins
-+-
 Reporter:  Adam Kochanowski |Owner:  ryankask
  |   Status:  new
 Type:  Bug  |  Version:  master
Component:  contrib.admin|   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 ikelly):

 The DISTINCT also causes an Oracle error if the model contains a
 TextField.  This was reported on django-users:

 https://groups.google.com/forum/?fromgroups=#!topic/django-
 users/eYTdpy4eWLQ

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

Re: [Django] #20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite

[Django]

#20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite
-+-
 Reporter:  burton449geo@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5-rc-1
Component:  GIS  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  GeoDjango,   |  Needs documentation:  0
  Spatialite |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by burton449geo@…):

 The return is None. I have made a test and re-creating a new spatialite db
 from spatialite_gui v.4.0, but it still returned None. When I use a
 PostGIS settings it returns 2.0.3. Do you know what could be the meaning?

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

Re: [Django] #4592: Make CheckboxSelectMultiple more like RadioSelect

[Django]

#4592: Make CheckboxSelectMultiple more like RadioSelect
-+-
 Reporter:  Scott Sinclair   |Owner:  bmispelon
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Forms|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  feature  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"9ac4dbd7b53d187ca54f28e247d3a120660938ca"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9ac4dbd7b53d187ca54f28e247d3a120660938ca"
 Fixed #4592: Made CheckboxSelectMultiple more like RadioSelect

 I refactored RadioSelect and CheckboxSelectMultiple to
 make them inherit from a base class, allowing them to share
 the behavior of being able to iterate over their subwidgets.

 Thanks to Matt McClanahan for the initial patch and to
 Claude Paroz 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 9ac4db: Fixed #4592: Made CheckboxSelectMultiple more like...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9ac4dbd7b53d187ca54f28e247d3a120660938ca
  
https://github.com/django/django/commit/9ac4dbd7b53d187ca54f28e247d3a120660938ca
  Author: Baptiste Mispelon 
  Date:   2013-04-13 (Sat, 13 Apr 2013)

  Changed paths:
M django/forms/widgets.py
M docs/internals/deprecation.txt
M docs/ref/forms/widgets.txt
M tests/forms_tests/tests/test_widgets.py

  Log Message:
  ---
  Fixed #4592: Made CheckboxSelectMultiple more like RadioSelect

I refactored RadioSelect and CheckboxSelectMultiple to
make them inherit from a base class, allowing them to share
the behavior of being able to iterate over their subwidgets.

Thanks to Matt McClanahan for the initial patch and to
Claude Paroz 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite

[Django]

#20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite
-+-
 Reporter:  burton449geo@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5-rc-1
Component:  GIS  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  GeoDjango,   |  Needs documentation:  0
  Spatialite |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by claudep):

 Could you try this snippet inside your project:
 {{{
 $ python manage.py shell
 >>> from django.db import connection
 >>> print(connection.ops.spatial_version)
 }}}
 It may be that your Django instance does not use the expected Spatialite
 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite

[Django]

#20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite
-+-
 Reporter:  burton449geo@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5-rc-1
Component:  GIS  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  GeoDjango,   |  Needs documentation:  0
  Spatialite |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by burton449geo@…):

 * version:  1.4 => 1.5-rc-1


Comment:

 This error using Django 1.5.1 ans Spatialite 4.0 when calling function
 GeoQuerySet.geojson()

 Traceback:
 File "C:\python27\lib\site-packages\django\core\handlers\base.py" in
 get_response
   115. response = callback(request,
 *callback_args, **callback_kwargs)
 File "C:\python27\lib\site-packages\django\contrib\auth\decorators.py" in
 _wrapped_view
   25. return view_func(request, *args, **kwargs)
 File "c:\mygeosite\geodjango\ezmapping\views.py" in editShapefile
   59. bounds = features.geojson()
 File "C:\python27\lib\site-packages\django\contrib\gis\db\models\query.py"
 in geojson
   149. raise NotImplementedError('Only PostGIS 1.3.4+ and
 SpatiaLite 3.0+ '

 Exception Type: NotImplementedError at /ezmapping/layer/edit/1
 Exception Value: Only PostGIS 1.3.4+ and SpatiaLite 3.0+ support GeoJSON
 serialization.

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

Re: [Django] #4592: Make CheckboxSelectMultiple more like RadioSelect

[Django]

#4592: Make CheckboxSelectMultiple more like RadioSelect
-+-
 Reporter:  Scott Sinclair   |Owner:  bmispelon
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Forms|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  feature  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 Replying to [comment:16 bmispelon]:
 > One thing to note is the disappearance of
 `django.forms.widgets.RadioInput` which was not part of the public API
 (it's not in `__all__` and was not documented anywhere).
 > If needed, it would be possible to re-introduce it as an alias of the
 new `RadioChoiceInput` with a deprecationwarning.

 Yes, I think that adding a deprecation shim for `RadioInput` would be a
 good thing, as it does not cost us much. See
 http://djangosnippets.org/snippets/2159/ for an example of a `RadioInput`
 usage. Apart from that, the patch is RFC.

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

Re: [Django] #4592: Make CheckboxSelectMultiple more like RadioSelect

[Django]

#4592: Make CheckboxSelectMultiple more like RadioSelect
-+-
 Reporter:  Scott Sinclair   |Owner:  bmispelon
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Forms|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  feature  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by bmispelon):

 Here's the link to the pull request:
 https://github.com/django/django/pull/1011/files

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

Re: [Django] #9230: Iterating over checkboxes in CheckboxSelectMultiple should be possible

[Django]

#9230: Iterating over checkboxes in CheckboxSelectMultiple should be possible
-+---
 Reporter:  mtredinnick  |Owner:  mtredinnick
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.0
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---
Changes (by bmispelon):

 * status:  new => closed
 * cc: bmispelon@… (added)
 * resolution:   => duplicate


Comment:

 Unless I'm mistaken, this is a duplicate of #4592.

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

[django/django] c4186c: Fixed #4117: Apply id attribute to the outer ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c4186c2fec6f5418c81366a911792bf5295db494
  
https://github.com/django/django/commit/c4186c2fec6f5418c81366a911792bf5295db494
  Author: Baptiste Mispelon 
  Date:   2013-04-13 (Sat, 13 Apr 2013)

  Changed paths:
M django/forms/widgets.py
M docs/ref/forms/widgets.txt
M tests/forms_tests/tests/test_forms.py
M tests/forms_tests/tests/test_regressions.py
M tests/forms_tests/tests/test_widgets.py

  Log Message:
  ---
  Fixed #4117: Apply id attribute to the outer  of RadioSelect



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

Re: [Django] #4117: Attributes for Widgets composed of more than one HTML element

[Django]

#4117: Attributes for Widgets composed of more than one HTML element
-+-
 Reporter:  Iwan Vosloo  |Owner:  Alex
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  attrs, RadioSelect,  | Triage Stage:  Accepted
  MultiWidget|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"c4186c2fec6f5418c81366a911792bf5295db494"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c4186c2fec6f5418c81366a911792bf5295db494"
 Fixed #4117: Apply id attribute to the outer  of RadioSelect
 }}}

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

Re: [Django] #20234: SingleObjectMixin does not add 'object' key to context

[Django]

#20234: SingleObjectMixin does not add 'object' key to context
---+
 Reporter:  dracos |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Generic views  |  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 tinodb):

 * cc: tinodb (added)
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 Hmm, all "object" stuff does not seem to be very consistent (like you
 mention in your other tickets).

 It also strikes me as strange, that these mixins rely on `self.object`
 being set, while it is only set in it's derived classes (that is probably
 why object was passed as a kwarg earlier).

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

[django/django] f56b70: Used a Python 3 compatible StringIO in test_utils

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f56b703b2748c958468344d894902ac18ec36d78
  
https://github.com/django/django/commit/f56b703b2748c958468344d894902ac18ec36d78
  Author: Claude Paroz 
  Date:   2013-04-13 (Sat, 13 Apr 2013)

  Changed paths:
M tests/test_utils/tests.py

  Log Message:
  ---
  Used a Python 3 compatible StringIO in test_utils



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

Re: [Django] #20249: Tutorial part 5 uses broken undocumented feature

[Django]

#20249: Tutorial part 5 uses broken undocumented feature
---+
 Reporter:  bmispelon  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by tinodb):

 * cc: tinodb (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20235: MultipleObjectMixin requires object_list to be passed in rather than using self.object_list

[Django]

#20235: MultipleObjectMixin requires object_list to be passed in rather than 
using
self.object_list
--+
 Reporter:  dracos|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Generic views |  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 tinodb):

 * cc: tinodb (added)
 * type:  Uncategorized => Cleanup/optimization
 * component:  Uncategorized => Generic views


Comment:

 A question about the tests. Why are you testing that
 `get_context_object_name` works, and not that the correct queryset is
 used? The first two assertions would also pass without your changes,
 right? Or do I miss something?

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

Re: [Django] #19874: Add id to element in CheckboxSelectMultiple

[Django]

#19874: Add id to  element in CheckboxSelectMultiple
-+-
 Reporter:  l3on |Owner:  bmispelon
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Forms|   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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"844fbc85c1d419ed7ecbb7208bd392c1770ea72d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="844fbc85c1d419ed7ecbb7208bd392c1770ea72d"
 Fixed #19874: Apply id attribute to the outer  of
 CheckboxSelectMultiple
 }}}

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

[django/django] 844fbc: Fixed #19874: Apply id attribute to the outer ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 844fbc85c1d419ed7ecbb7208bd392c1770ea72d
  
https://github.com/django/django/commit/844fbc85c1d419ed7ecbb7208bd392c1770ea72d
  Author: Baptiste Mispelon 
  Date:   2013-04-13 (Sat, 13 Apr 2013)

  Changed paths:
M django/forms/widgets.py
M docs/ref/forms/widgets.txt
M tests/forms_tests/tests/test_forms.py
M tests/forms_tests/tests/test_widgets.py

  Log Message:
  ---
  Fixed #19874: Apply id attribute to the outer  of CheckboxSelectMultiple



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

[django/django] 3f05c7: Updated a renamed test file

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3f05c70be065fd915d2cddc1e7f74d1d4cb1e54e
  
https://github.com/django/django/commit/3f05c70be065fd915d2cddc1e7f74d1d4cb1e54e
  Author: Claude Paroz 
  Date:   2013-04-13 (Sat, 13 Apr 2013)

  Changed paths:
M tests/view_tests/tests/__init__.py

  Log Message:
  ---
  Updated a renamed test file



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

Re: [Django] #20254: startproject command - need better error message

[Django]

#20254: startproject command - need better error message
-+-
 Reporter:  dhivya23 |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bmispelon):

 * status:  new => closed
 * cc: bmispelon@… (added)
 * needs_better_patch:   => 0
 * component:  Uncategorized => Core (Management commands)
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => needsinfo


Comment:

 Hi,

 Could you provide some mode details on how to reproduce this?

 The `starproject` command should normally always be available regardless
 of which settings you're using.

 I've tried both with `django-admin.py` and `manage.py` to create a new
 project inside an existing one (with the `DJANGO_SETTINGS_MODULE` env var
 set), but it succeeded each time.

 I'm closing this as `needsinfo`. Please reopen if you have more
 information on how to reproduce this issue.

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

Re: [Django] #20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite

[Django]

#20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite
-+-
 Reporter:  burton449geo@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  GIS  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  GeoDjango,   |  Needs documentation:  0
  Spatialite |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by claudep):

 For the record, this was added in #19028 - [95f7ea3af185]

 If you get an error with 1.5.1, we'll need the traceback, please.

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