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|
-+-
Changes (by bmispelon):

 * cc: bmispelon@… (added)
 * owner:  nobody => bmispelon
 * status:  new => assigned
 * needs_better_patch:  1 => 0


Comment:

 I've brought  Matt McClanahan's old patch up to date and added some
 documentation [1]

 The tests pass without modification so this change should be completely
 backwards-compatible (I was actually surprised at how well it worked).

 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.

 In my branch, the commit for this ticket depends on two other ones: #4117
 and #19874 which are somewhat related.

 [1] https://github.com/bmispelon/django/compare/ticket-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.

Re: [Django] #20247: qualify folders for .py files on tutorial

[Django]

#20247: qualify folders for .py files on tutorial
---+
 Reporter:  gsavix |  Owner:  nobody
 Type:  Cleanup/optimization   | Status:  closed
Component:  Documentation  |Version:  master
 Severity:  Normal | Resolution:  fixed
 Keywords:  docs tutorial 1 and 2  |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+

Comment (by Tim Graham ):

 In [changeset:"6e3b80239e9a066ac2e9d10212196acbc2e6d35c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6e3b80239e9a066ac2e9d10212196acbc2e6d35c"
 [1.5.x] Fixed #20247 - Added some missing paths in the tutorial.

 Thanks gsavix for the suggestion and patch.

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

[django/django] 6e3b80: [1.5.x] Fixed #20247 - Added some missing paths in...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 6e3b80239e9a066ac2e9d10212196acbc2e6d35c
  
https://github.com/django/django/commit/6e3b80239e9a066ac2e9d10212196acbc2e6d35c
  Author: Tim Graham 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
M docs/intro/tutorial01.txt
M docs/intro/tutorial02.txt

  Log Message:
  ---
  [1.5.x] Fixed #20247 - Added some missing paths in the tutorial.

Thanks gsavix for the suggestion and patch.

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

Re: [Django] #20247: qualify folders for .py files on tutorial

[Django]

#20247: qualify folders for .py files on tutorial
---+
 Reporter:  gsavix |  Owner:  nobody
 Type:  Cleanup/optimization   | Status:  closed
Component:  Documentation  |Version:  master
 Severity:  Normal | Resolution:  fixed
 Keywords:  docs tutorial 1 and 2  |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"aad5661c6c44ac58c4218fcac8d433ae2293dfce"]:
 {{{
 #!CommitTicketReference repository=""
 revision="aad5661c6c44ac58c4218fcac8d433ae2293dfce"
 Fixed #20247 - Added some missing paths in the tutorial.

 Thanks gsavix for the suggestion and 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] aad566: Fixed #20247 - Added some missing paths in the tut...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: aad5661c6c44ac58c4218fcac8d433ae2293dfce
  
https://github.com/django/django/commit/aad5661c6c44ac58c4218fcac8d433ae2293dfce
  Author: Tim Graham 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
M docs/intro/tutorial01.txt
M docs/intro/tutorial02.txt

  Log Message:
  ---
  Fixed #20247 - Added some missing paths in the tutorial.

Thanks gsavix for the suggestion and patch.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
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
---+--
Changes (by anonymous):

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


-- 
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:  new
Component:  Forms  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by anonymous):

 Looks like it's something with the my options in settings.py
 Clear django-project work's fine. I will test this in detail.

-- 
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] e8446b: Modified validation to work with unittest2 discove...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e8446be5600a8f5022e82541df432268ae5f737d
  
https://github.com/django/django/commit/e8446be5600a8f5022e82541df432268ae5f737d
  Author: Preston Timmons 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
A tests/validation/test_validators.py
M tests/validation/tests.py
R tests/validation/validators.py

  Log Message:
  ---
  Modified validation to work with unittest2 discovery.


  Commit: 56e777eba3687bd56b954de4b3dfa44775481b14
  
https://github.com/django/django/commit/56e777eba3687bd56b954de4b3dfa44775481b14
  Author: Preston Timmons 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
M tests/view_tests/tests/__init__.py
R tests/view_tests/tests/debug.py
R tests/view_tests/tests/defaults.py
R tests/view_tests/tests/i18n.py
R tests/view_tests/tests/shortcuts.py
R tests/view_tests/tests/specials.py
R tests/view_tests/tests/static.py
A tests/view_tests/tests/test_debug.py
A tests/view_tests/tests/test_defaults.py
A tests/view_tests/tests/test_i18n.py
A tests/view_tests/tests/test_shortcuts.py
A tests/view_tests/tests/test_specials.py
A tests/view_tests/tests/test_static.py

  Log Message:
  ---
  Modified view_tests for unittest2 discovery.


  Commit: 6d968317698b99115be2652a9e2e41adc3a28e79
  
https://github.com/django/django/commit/6d968317698b99115be2652a9e2e41adc3a28e79
  Author: Preston Timmons 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
A tests/template_tests/loaders.py
R tests/template_tests/test_loaders.py
M tests/template_tests/tests.py

  Log Message:
  ---
  Fixed template_tests so discovery doesn't directly find tests that require 
setuptools.


Compare: https://github.com/django/django/compare/612ef3e5c9ba...6d968317698b

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 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 bmispelon):

 * cc: bmispelon@… (added)


Comment:

 For some reason, trac decided i was spamming and it logged me out.

 Sorry about the noise.

-- 
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] #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:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 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 anonymous):

 * needs_better_patch:  1 => 0


Comment:

 I've created a pull request based on Alex's last patch.

 Half of the work was already done in #19874.

-- 
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] cdf520: Modified forms_tests to work with unittest2 discov...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cdf520ee86e7613f29421fb2c99646ce00899b3d
  
https://github.com/django/django/commit/cdf520ee86e7613f29421fb2c99646ce00899b3d
  Author: Preston Timmons 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
M tests/forms_tests/tests/__init__.py
R tests/forms_tests/tests/error_messages.py
R tests/forms_tests/tests/extra.py
R tests/forms_tests/tests/fields.py
R tests/forms_tests/tests/forms.py
R tests/forms_tests/tests/formsets.py
R tests/forms_tests/tests/input_formats.py
R tests/forms_tests/tests/media.py
R tests/forms_tests/tests/models.py
R tests/forms_tests/tests/regressions.py
A tests/forms_tests/tests/test_error_messages.py
A tests/forms_tests/tests/test_extra.py
A tests/forms_tests/tests/test_fields.py
A tests/forms_tests/tests/test_forms.py
A tests/forms_tests/tests/test_formsets.py
A tests/forms_tests/tests/test_input_formats.py
A tests/forms_tests/tests/test_media.py
A tests/forms_tests/tests/test_regressions.py
A tests/forms_tests/tests/test_util.py
A tests/forms_tests/tests/test_validators.py
A tests/forms_tests/tests/test_widgets.py
R tests/forms_tests/tests/util.py
R tests/forms_tests/tests/validators.py
R tests/forms_tests/tests/widgets.py

  Log Message:
  ---
  Modified forms_tests to work with unittest2 discovery.


  Commit: 751b007c9840de9cb4e5fc622e8ea9f44e5554ca
  
https://github.com/django/django/commit/751b007c9840de9cb4e5fc622e8ea9f44e5554ca
  Author: Preston Timmons 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
M django/test/simple.py
A tests/test_utils/doctest_output.py
M tests/test_utils/tests.py

  Log Message:
  ---
  Modified test_utils to work with unittest2 discovery.


  Commit: 6f3e1397394da838db9e9aee6ba0eb102ac6f49b
  
https://github.com/django/django/commit/6f3e1397394da838db9e9aee6ba0eb102ac6f49b
  Author: Preston Timmons 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
R tests/test_client_override/__init__.py
R tests/test_client_override/models.py
R tests/test_client_override/tests.py
A tests/test_suite_override/__init__.py
A tests/test_suite_override/models.py
A tests/test_suite_override/tests.py

  Log Message:
  ---
  Modified test_client_override to work with unittest2 discovery.


  Commit: 5e84abec14fe43cc08198411cbd2b67804ab7e47
  
https://github.com/django/django/commit/5e84abec14fe43cc08198411cbd2b67804ab7e47
  Author: Preston Timmons 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
M tests/comment_tests/tests/__init__.py
R tests/comment_tests/tests/app_api_tests.py
R tests/comment_tests/tests/comment_form_tests.py
R tests/comment_tests/tests/comment_utils_moderators_tests.py
R tests/comment_tests/tests/comment_view_tests.py
R tests/comment_tests/tests/feed_tests.py
R tests/comment_tests/tests/model_tests.py
R tests/comment_tests/tests/moderation_view_tests.py
R tests/comment_tests/tests/templatetag_tests.py
A tests/comment_tests/tests/test_app_api.py
A tests/comment_tests/tests/test_comment_form.py
A tests/comment_tests/tests/test_comment_utils_moderators.py
A tests/comment_tests/tests/test_comment_view.py
A tests/comment_tests/tests/test_feeds.py
A tests/comment_tests/tests/test_models.py
A tests/comment_tests/tests/test_moderation_views.py
A tests/comment_tests/tests/test_templatetags.py

  Log Message:
  ---
  Modified comment_tests for unittest2 discovery.


  Commit: 3ca3d2206c31ed251474d66b6775fa0903c09eae
  
https://github.com/django/django/commit/3ca3d2206c31ed251474d66b6775fa0903c09eae
  Author: Preston Timmons 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
R tests/generic_views/base.py
R tests/generic_views/dates.py
R tests/generic_views/detail.py
R tests/generic_views/edit.py
R tests/generic_views/forms.py
R tests/generic_views/list.py
A tests/generic_views/test_base.py
A tests/generic_views/test_dates.py
A tests/generic_views/test_detail.py
A tests/generic_views/test_edit.py
A tests/generic_views/test_forms.py
A tests/generic_views/test_list.py
M tests/generic_views/tests.py
M tests/generic_views/views.py

  Log Message:
  ---
  Modified generic_views for unittest2 discovery.


  Commit: 44293c5c053d616326d5dfe82252e5e8431d81ea
  
https://github.com/django/django/commit/44293c5c053d616326d5dfe82252e5e8431d81ea
  Author: Preston Timmons 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
R tests/model_fields/imagefield.py
A tests/model_fields/test_imagefield.py
M tests/model_fields/tests.py

  Log Message:
  ---
  Modified 

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 anonymous):

 I dont understand, I have updated Django to 1.5.1 and still got an error.
 Is this function implement with Spatialite 4.0? Thats the version im
 using.

-- 
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] #20255: What Just how to Cope with It? and Causes Pain behind Knee Operating

[Django]

#20255: What Just how to Cope with It? and Causes Pain behind Knee Operating
---+
 Reporter:  checking   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Anyone can be affected by pain behind knee running, regardless of just how
 long he/ she's become a sportsman. Everybody has exactly the same
 opportunity to encounter disturbing feeling while appreciate their day
 running, despite the fact that a few of the triggers might seem to just
 occur in a specific group. Therapy differs with respect to the signs and
 how serious the condition is but throughout the medicine interval, you
 will possibly not be permitted to operate by your physician. This short
 article may protect all you need to understand about pain behind knee
 operating. What causes Pain behind Knee Operating Much like all muscles
 within our human anatomy, the muscle which facilitates the architectural
 basis of our knee also offers its restriction. Ergo, if you operate and
 are actually therefore inspired that you choose to drive it only a little
 off the restriction, you might start to feel anxious feeling around your
 knee. Youre likely to feel like your knee has dropped its versatility and
 turn into a ton firmer. This type of sensation probably exists from
 pressured cartilages because of constant stress on the knee. The health-
 related phrase for the scenario is Chondromalacia. It is really because
 the cartilages, which work not just as a connection between leg and femur
 but additionally surprise absorber, are broken and become sensitive. The
 outcome is the set of bones may provide pain to the surface and stroke
 each the others surface. This isn't to be used gently as regularly
 continuing the operating is only going to worsen the harm. Pain behind
 knee operating may also be brought on by leg muscle that has grown fragile
 and aged. In since studies have said that flat feet have instead
 substandard stress ingesting capacity addition, flat feet may also donate
 to the improvement of tenderness round the knee. Just how to Cope with
 Pain behind Knee Operating You nevertheless have to tend to the therapy
 significantly to be able to recuperate quick, despite the fact that
 Chondromalacia never exhibits it self in ugly great and bruise. Sufferer
 can be helped by most of the time, taking a break from your athletic
 routine combined with special massage to achieve his exercise rapidly. Do
 examine it together with your doctor, when you yourself have heard of RICE
 (Rest, Ice, Compression, and Elevation) treatment. This type of therapy is
 well-liked as you of the very effective exterior medicine for pain behind
 knee operating. Third therapy mindfully could get your powerful knee back
 inside a couple of days. Nevertheless, if the harm on the cartilages is
 extremely serious, you might need treatment from surgery device to obtain
 cured. Stopping Operating Knee Pain Establishing a greater goal for your
 operating is definitely very important to enhance the power and stamina of
 one's muscle. Nevertheless, it's also essential to complete it mindfully.
 Making your thighs to protect a length of 30 miles while generally you
 simply operate for around 10 miles is merely silly. Your muscle need
 certainly to adjust to the elevated part of your instruction.
 Additionally, don't be inexpensive as it pertains to athletic shoes.
 Choose types that provide the very best defense against effect you create
 each time you stump on the difficult tangible street. This will aid your
 knee cartilages digest the stress and in the course of time may stop you
 from [http://painbehindkneecure.com pain behind knee] operating.

-- 
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] #18872: Add prefix attribute to FormMixin

[Django]

#18872: Add prefix attribute to FormMixin
--+
 Reporter:  dragonsnaker@…|Owner:  zsiciarz
 Type:  New feature   |   Status:  assigned
Component:  Generic views |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  FormMixin prefix  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by druidjaidan):

 Have to agree.  There are lots of reasons you might need to use a prefix
 that don't involve processing more than one form.  I ran into this because
 we had a form on the page that acted as a context switcher, changing it's
 value caused the form to be processed, changed a session value, and
 reloaded the page given the new context.  This caused an id collision
 anytime the user was on a page that happened to have a form that had the
 same field name (really common considering the context was a FK).

-- 
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] #20254: startproject command - need better error message

[Django]

#20254: startproject command - need better error message
---+
 Reporter:  dhivya23   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 can startproject command throw a more useful error message ?
 When I already have started a project called 'companyweb' and have set env
 variable, DJANGO_SETTINGS_MODULE to its settings file, and I do,
 > django-admin.py startproject mysite
 Unknown command: 'startproject'
 Type 'django-admin.py help' for usage

 Can this message say something like,
 "Unknown command: 'startproject'. Project 'companyweb' is the current
 project. "

-- 
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] #20253: GeoDjango - made GeoQuerySet.extent() available with Spatialite

[Django]

#20253: GeoDjango - made GeoQuerySet.extent() available with Spatialite
-+-
 Reporter:  burton449geo@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  GeoDjango,   | Triage Stage:  Accepted
  Spatialite |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * needs_better_patch:   => 0
 * version:  1.4 => master
 * needs_tests:   => 0
 * needs_docs:   => 0
 * 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] #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|
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"991ce52bc872f827de8e7b5b441e2dfa2185bfd2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="991ce52bc872f827de8e7b5b441e2dfa2185bfd2"
 [1.5.x] Fixed #20252 -- Mentionned geojson Spatialite support from 1.5

 Thanks burton449geo at gmail.com for the report.
 Backport of d58e985aa 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 991ce5: [1.5.x] Fixed #20252 -- Mentionned geojson Spatial...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 991ce52bc872f827de8e7b5b441e2dfa2185bfd2
  
https://github.com/django/django/commit/991ce52bc872f827de8e7b5b441e2dfa2185bfd2
  Author: Claude Paroz 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
M docs/ref/contrib/gis/geoquerysets.txt

  Log Message:
  ---
  [1.5.x] Fixed #20252 -- Mentionned geojson Spatialite support from 1.5

Thanks burton449geo at gmail.com for the report.
Backport of d58e985aa 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] d58e98: Fixed #20252 -- Mentionned geojson Spatialite supp...

[GitHub]

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

  Changed paths:
M docs/ref/contrib/gis/geoquerysets.txt

  Log Message:
  ---
  Fixed #20252 -- Mentionned geojson Spatialite support from 1.5

Thanks burton449geo at gmail.com 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.
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:  new
  Cleanup/optimization   |  Version:  1.4
Component:  GIS  |   Resolution:
 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 claudep):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 geojson support for Spatialite has been added in Django 1.5. I'll add the
 missing notice to the docs.

-- 
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] #20253: GeoDjango - made GeoQuerySet.extent() available with Spatialite

[Django]

#20253: GeoDjango - made GeoQuerySet.extent() available with Spatialite
+---
 Reporter:  burton449geo@…  |  Owner:  nobody
 Type:  New feature | Status:  new
Component:  GIS |Version:  1.4
 Severity:  Normal  |   Keywords:  GeoDjango, Spatialite
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+---
 It could be a good idea to implement a GeoQuerySet.extent() for spatialite
 using this sql query:

 SELECT Min(MbrMinX(geometry)), Min(MbrMinY(geometry)),
 Max(MbrMaxX(geometry)), Max(MbrMaxY(geometry))FROM MyTable;

-- 
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:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Forms|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * has_patch:  0 => 1
 * stage:  Accepted => Ready for checkin


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

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

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

[Django]

#20252: GeoDjango - GeoQuerySet.geojson NotImplementedError with Spatialite
+---
 Reporter:  burton449geo@…  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  GIS |Version:  1.4
 Severity:  Normal  |   Keywords:  GeoDjango, Spatialite
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+---
 As the documentation mentions
 
(https://docs.djangoproject.com/en/dev/ref/contrib/gis/geoquerysets/#django.contrib.gis.db.models.GeoQuerySet.geojson)
 GeoQuerySet.geojson should be available with Spatialite but it is not.

 Traceback:
 File "C:\Python27\lib\site-packages\django\core\handlers\base.py" in
 get_response
   111. response = callback(request,
 *callback_args, **callback_kwargs)
 File "C:\Python27\lib\site-packages\django\contrib\auth\decorators.py" in
 _wrapped_view
   20. return view_func(request, *args, **kwargs)
 File "c:\mygeosite\geodjango\ezmapping\views.py" in editShapefile
   55. feature_geoJson = features.geojson()
 File "C:\Python27\lib\site-packages\django\contrib\gis\db\models\query.py"
 in geojson
   145. raise NotImplementedError('Only PostGIS 1.3.4+ supports
 GeoJSON serialization.')

 Exception Type: NotImplementedError at /ezmapping/layer/edit/1
 Exception Value: Only PostGIS 1.3.4+ supports 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] #20237: Unable to test pure binary with assertContains

[Django]

#20237: Unable to test pure binary with assertContains
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  regression   | 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 Claude Paroz ):

 In [changeset:"abdcf818431525ec1c1165b9351cc16c5c5fa1c6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="abdcf818431525ec1c1165b9351cc16c5c5fa1c6"
 [1.5.x] Fixed #20237 (again) Allowed binary parameter to assertContains

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

[django/django] abdcf8: [1.5.x] Fixed #20237 (again) Allowed binary parame...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: abdcf818431525ec1c1165b9351cc16c5c5fa1c6
  
https://github.com/django/django/commit/abdcf818431525ec1c1165b9351cc16c5c5fa1c6
  Author: Claude Paroz 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
M django/test/testcases.py
M tests/regressiontests/test_client_regress/tests.py

  Log Message:
  ---
  [1.5.x] Fixed #20237 (again) Allowed binary parameter to assertContains

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

Re: [Django] #20237: Unable to test pure binary with assertContains

[Django]

#20237: Unable to test pure binary with assertContains
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  regression   | 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:"b04fd579d58332632c85ecd1ab3c7062e90086a8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b04fd579d58332632c85ecd1ab3c7062e90086a8"
 Fixed #20237 (again) Allowed binary parameter to assertContains
 }}}

-- 
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] b04fd5: Fixed #20237 (again) Allowed binary parameter to a...

[GitHub]

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

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

  Log Message:
  ---
  Fixed #20237 (again) Allowed binary parameter to assertContains



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #18416: Query fails when SimpleLazyObject evaluates to None

[Django]

#18416: Query fails when SimpleLazyObject evaluates to None
-+-
 Reporter:  bouke|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   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
-+-

Comment (by jonash):

 Same thing happened to me just now. I believe a common case is
 `request.user` in unit tests. Maybe `request.user` shouldn't be a
 `SimpleLazyObject` after all.

-- 
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:  new
Component:  Forms  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by bmispelon):

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


Comment:

 Interesting.

 Does `Decimal(u"1 грн")` also trigger a `UnicodeEncodeError` in a plain
 python shell?

 I'm reopening because I don't have access to a windows installation to
 test 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.
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:  invalid
 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):

 {{{
 #!/usr/bin/python
 # -*- coding: utf-8 -*-
 import sys
 import os

 os.environ['DJANGO_SETTINGS_MODULE'] = 'agu.settings'

 from agu import settings
 from django import forms

 class TestForm(forms.Form):
 field = forms.DecimalField()

 data = {'field': u"1 грн"}
 form = TestForm(data)
 if form.is_valid():
 print(form.cleaned_data)
 else:
 print('Invalid form')

 }}}

 Runing on Windows7 64bit, python 2.7, Django 1.5

 {{{
 Traceback (most recent call last):
   File "temp.py", line 19, in 
 if form.is_valid():
   File "C:\Python\lib\site-packages\django\forms\forms.py", line 126, in
 is_valid
 return self.is_bound and not bool(self.errors)
   File "C:\Python\lib\site-packages\django\forms\forms.py", line 117, in
 _get_errors
 self.full_clean()
   File "C:\Python\lib\site-packages\django\forms\forms.py", line 272, in
 full_clean
 self._clean_fields()
   File "C:\Python\lib\site-packages\django\forms\forms.py", line 287, in
 _clean_fields
 value = field.clean(value)
   File "C:\Python\lib\site-packages\django\forms\fields.py", line 154, in
 clean
 value = self.to_python(value)
   File "C:\Python\lib\site-packages\django\forms\fields.py", line 293, in
 to_python
 value = Decimal(value)
 UnicodeEncodeError: 'decimal' codec can't encode characters in position
 2-4: invalid decimal Unicode string
 }}}

-- 
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:  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 bmispelon):

 * status:  new => closed
 * cc: bmispelon@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => invalid


Comment:

 Hi,

 Could you provide more details on how to reproduce the issue?

 I tried the following (with python 2.7 and 3.2) but could not trigger the
 `UnicodeEncodeError`:
 {{{
 #!python
 class TestForm(forms.Form):
 field = forms.DecimalField()

 data = {'field': u"1 грн"}
 form = TestForm(data)
 if form.is_valid():
 print(form.cleaned_data)
 else:
 print('Invalid form')
 }}}

 This prints out "Invalid form", without triggering any other error.

 I also simply tried `Decimal("1 грн")` but this raise a
 `DecimalException`, not a `UnicodeEncodeError`.

-- 
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] #17365: Extend test discovery to include unittest2 test suite runner

[Django]

#17365: Extend test discovery to include unittest2 test suite runner
---+
 Reporter:  jezdez |Owner:  myusuf3
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by guettli):

 * cc: hv@… (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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20251: UnicodeEncodeError with DecimalField

[Django]

#20251: UnicodeEncodeError with DecimalField
+
 Reporter:  anonymous   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  1.5
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 My form:
 {{{
 class TestForm(forms.Form):
 value = forms.DecimalField()

 }}}
 When enteing "1 грн"


 {{{
 'decimal' codec can't encode characters in position 4-6: invalid decimal
 Unicode string
 }}}


 Method '''to_python''' catch only 'DecimalException' but not
 'UnicodeEncodeError'.
 {{{


 C:\Python\lib\site-packages\django\forms\fields.py in to_python
 """
 if value in validators.EMPTY_VALUES:
 return None
 if self.localize:
 value = formats.sanitize_separators(value)
 value = smart_text(value).strip()
 try:
 value = Decimal(value)
 ...
 except DecimalException:
 raise ValidationError(self.error_messages['invalid'])

 return value

 def validate(self, value):

 super(DecimalField, self).validate(value)


 }}}

-- 
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] #20187: Django 1.5 using a cached HttpResponse with WSGI has an empty body

[Django]

#20187: Django 1.5 using a cached HttpResponse with WSGI has an empty body
---+--
 Reporter:  smbrooks1@…|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  HttpResponse   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 Discussion here : https://groups.google.com/d/msg/django-developers/cGw-
 VitKWIw/hp860m27KggJ

-- 
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] #2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in mysql)

[Django]

#2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in
mysql)
-+-
 Reporter:  scanner@…|Owner:
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by slafs):

 This is awesome! I can provide some Oracle testing if it's still needed.
 Though, I probably would need some guidance about performing those tests.

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

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

Re: [Django] #20196: Better support for folder uploads

[Django]

#20196: Better support for folder uploads
-+-
 Reporter:  jonash   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Someday/Maybe
 * component:  Uncategorized => Forms
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 It looks like this could live outside of core at first. I'd prefer to wait
 until this feature is standardized by W3C to implement it in Django.

 The testing part may be tricky, but can probably be solved by subclassing
 the test client.

-- 
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] #20147: Provide an alternative to request.META for accessing HTTP headers (was: Replace and deprecate request.META for HTTP headers)

[Django]

#20147: Provide an alternative to request.META for accessing HTTP headers
---+
 Reporter:  lukeplant  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 The mailing list discussion converged towards keeping META, but
 recommending a dict-like `request.headers`.

 I'm updating the summary to reflect 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20248: Clarifying Documentation

[Django]

#20248: Clarifying Documentation
-+--
 Reporter:  anonymous|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  django-admin.py  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--

Comment (by Tim Graham ):

 In [changeset:"8ab5db7a3348b7890eae5db20e48f820bf09c81c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8ab5db7a3348b7890eae5db20e48f820bf09c81c"
 [1.5.x] Fixed #20248 - Clarified manage.py vs. django-admin.py

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

[django/django] 8ab5db: [1.5.x] Fixed #20248 - Clarified manage.py vs. dja...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 8ab5db7a3348b7890eae5db20e48f820bf09c81c
  
https://github.com/django/django/commit/8ab5db7a3348b7890eae5db20e48f820bf09c81c
  Author: Tim Graham 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
M docs/ref/django-admin.txt

  Log Message:
  ---
  [1.5.x] Fixed #20248 - Clarified manage.py vs. django-admin.py

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

Re: [Django] #20248: Clarifying Documentation

[Django]

#20248: Clarifying Documentation
-+--
 Reporter:  anonymous|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  django-admin.py  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"8fc68af9c09f47760080327fb820fe88f02f9bf9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8fc68af9c09f47760080327fb820fe88f02f9bf9"
 Fixed #20248 - Clarified manage.py vs. django-admin.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.

[django/django] 8fc68a: Fixed #20248 - Clarified manage.py vs. django-admi...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8fc68af9c09f47760080327fb820fe88f02f9bf9
  
https://github.com/django/django/commit/8fc68af9c09f47760080327fb820fe88f02f9bf9
  Author: Tim Graham 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
M docs/ref/django-admin.txt

  Log Message:
  ---
  Fixed #20248 - Clarified manage.py vs. django-admin.py



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #20250: AttributeError when filtering annotated queryset with negated Q (via fk)

[Django]

#20250: AttributeError when filtering annotated queryset with negated Q (via fk)
-+-
 Reporter:  jan.koutny@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  annotate |  Needs documentation:  0
  AttributeError |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by akaariai):

 * status:  closed => new
 * resolution:  fixed =>
 * needs_tests:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Reverting my fixed resolution, regression test should be added even if
 this already works in 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20250: AttributeError when filtering annotated queryset with negated Q (via fk)

[Django]

#20250: AttributeError when filtering annotated queryset with negated Q (via fk)
-+-
 Reporter:  jan.koutny@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:  annotate |  Unreviewed
  AttributeError |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

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


Comment:

 This seems to work on master. The results of the print qst.query are:
 {{{
 SELECT "tester_m1"."id", "tester_m1"."rtom3_id", "tester_m1"."x",
 COUNT("tester_m2"."id") AS "m2__count"
 FROM "tester_m1" INNER JOIN "tester_m3" ON ( "tester_m1"."rtom3_id" =
 "tester_m3"."id" )
 LEFT OUTER JOIN "tester_m2" ON ( "tester_m1"."id" = "tester_m2"."rtom1_id"
 )
 WHERE NOT ("tester_m3"."x" = 0 ) GROUP BY "tester_m1"."id",
 "tester_m1"."rtom3_id", "tester_m1"."x"
 }}}
 I haven't verified that the generated query is correct, but at least no
 errors are thrown.

 Backpatching this to 1.4 will not happen as this isn't a critical bug (not
 a dataloss/security/regression/crash bug). I am marking this as 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20250: AttributeError when filtering annotated queryset with negated Q (via fk)

[Django]

#20250: AttributeError when filtering annotated queryset with negated Q (via fk)
--+
 Reporter:  jan.koutny@…  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:  annotate
 Triage Stage:  Unreviewed|  AttributeError
Easy pickings:  0 |  Has patch:  0
  |  UI/UX:  0
--+
 If these conditions are met:
 * annotated queryset
 * Q is filtering attribute related via foreign key
 * Q is negation

 Then {{{AttributeError: 'NoneType' object has no attribute 'startswith'}}}
 exception is throwed. Stack looks the same as in 12687 (fixed), see below.

 Note that *all* conditions above are necessary, code works if one omitted.
 Reproducible with Django 1.4.5, python 2.6.8.

 {{{
 Traceback (most recent call last):
   File "bug.py", line 16, in 
 print qst.query
   File "/usr/lib/python2.6/site-packages/django/db/models/sql/query.py",
 line 167, in __str__
 sql, params = self.sql_with_params()
   File "/usr/lib/python2.6/site-packages/django/db/models/sql/query.py",
 line 175, in sql_with_params
 return self.get_compiler(DEFAULT_DB_ALIAS).as_sql()
   File "/usr/lib/python2.6/site-
 packages/django/db/models/sql/compiler.py", line 82, in as_sql
 where, w_params = self.query.where.as_sql(qn=qn,
 connection=self.connection)
   File "/usr/lib/python2.6/site-packages/django/db/models/sql/where.py",
 line 91, in as_sql
 sql, params = child.as_sql(qn=qn, connection=connection)
   File "/usr/lib/python2.6/site-packages/django/db/models/sql/where.py",
 line 91, in as_sql
 sql, params = child.as_sql(qn=qn, connection=connection)
   File "/usr/lib/python2.6/site-packages/django/db/models/sql/where.py",
 line 91, in as_sql
 sql, params = child.as_sql(qn=qn, connection=connection)
   File "/usr/lib/python2.6/site-packages/django/db/models/sql/where.py",
 line 91, in as_sql
 sql, params = child.as_sql(qn=qn, connection=connection)
   File "/usr/lib/python2.6/site-packages/django/db/models/sql/where.py",
 line 91, in as_sql
 sql, params = child.as_sql(qn=qn, connection=connection)
   File "/usr/lib/python2.6/site-packages/django/db/models/sql/where.py",
 line 94, in as_sql
 sql, params = self.make_atom(child, qn, connection)
   File "/usr/lib/python2.6/site-packages/django/db/models/sql/where.py",
 line 154, in make_atom
 field_sql = self.sql_for_columns(lvalue, qn, connection)
   File "/usr/lib/python2.6/site-packages/django/db/models/sql/where.py",
 line 227, in sql_for_columns
 lhs = '%s.%s' % (qn(table_alias), qn(name))
   File "/usr/lib/python2.6/site-
 packages/django/db/models/sql/compiler.py", line 49, in
 quote_name_unless_alias
 r = self.connection.ops.quote_name(name)
   File "/usr/lib/python2.6/site-
 packages/django/db/backends/sqlite3/base.py", line 145, in quote_name
 if name.startswith('"') and name.endswith('"'):
 AttributeError: 'NoneType' object has no attribute 'startswith'
 }}}


 Code snippet to reproduce the issue, bug.py:
 {{{
 from bug.models import *
 from django.db.models import Q,Count

 qobj=~Q(rtom3__x=0) #TOXIC
 #qobj=~Q(x=0) #OK
 #qobj=Q(rtom3__x=0) #OK

 qst =  M1.objects.annotate(Count('m2')) #TOXIC
 #qst =  M1.objects.all() #OK

 qst = qst.filter(qobj)

 #Gracefully returns [], no attempt to hit the database
 #print qst

 #Throws an exception!
 print qst.query
 }}}

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

 class M1(models.Model):
 rtom3 = models.ForeignKey("M3")
 x = models.IntegerField()

 class M2(models.Model):
 rtom1 = models.ForeignKey("M1")

 class M3(models.Model):
 x = models.IntegerField()
 }}}

-- 
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] #20241: QuerySets with callable filter args have said args evaluated only once

[Django]

#20241: QuerySets with callable filter args have said args evaluated only once
-+-
 Reporter:   |Owner:  nobody
  christopher.m.pike@…   |   Status:  new
 Type:  Bug  |  Version:  1.5
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 akaariai):

 The reasons why fixing this isn't easy:
   1. The WhereNode._prepare_data() call is done at .filter() call time.
 The _prepare_data() method does some transformations based on the type of
 the value, specifically datetime.datetime values will cause some
 transformations. If the callable is timezone.now, then the lookup will not
 work correctly.
   2. The value will need to be resolved for isnull lookups (isnull=True
 lookups will need to produce LEFT OUTER JOINs and join promotion is done
 at .filter() call time).
   3. Some advanced constructs do not work correctly - returning F()
 objects for example (they don't work correctly even now).

 At least no.1 will need to be fixed if the value resolving is deferred to
 query execution time. So, _prepare_data will need to be moved to query
 execution time. The only problematic case seems to be iterators - they
 must not be consumed multiple times, and this would happen if all of
 _prepare_data is moved to query execution time.

 Fixing number 2 and 3 properly will be really hard (need to alter the join
 types at execution time, and that is problematic for multiple reasons, not
 least because the query should not be altered at execution time...). But,
 I am not sure if those need to be fixed at all, they could be documented
 as known limitations when using callable arguments. In practice the
 limitations wouldn't cause much trouble to users, and it is easy enough to
 raise errors in problematic cases.

-- 
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] #20211: BoundField.label_tag now always escapes its `contents` parameter.

[Django]

#20211: BoundField.label_tag now always escapes its `contents` parameter.
-+-
 Reporter:  bmispelon|Owner:  bmispelon
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Release blocker  |   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 Claude Paroz ):

 In [changeset:"9c49e64b66994ff25980d9d0d21ce3599b17cc4b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9c49e64b66994ff25980d9d0d21ce3599b17cc4b"
 [1.5.x] Fixed #20211: Document backwards-incompatible change in
 BoundField.label_tag

 Also cleaned up label escaping and consolidated the test suite regarding
 label_tag.
 Backport of ab686022f 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 9c49e6: [1.5.x] Fixed #20211: Document backwards-incompati...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 9c49e64b66994ff25980d9d0d21ce3599b17cc4b
  
https://github.com/django/django/commit/9c49e64b66994ff25980d9d0d21ce3599b17cc4b
  Author: Baptiste Mispelon 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
M django/forms/forms.py
M docs/releases/1.5.txt
M tests/regressiontests/forms/tests/forms.py

  Log Message:
  ---
  [1.5.x] Fixed #20211: Document backwards-incompatible change in 
BoundField.label_tag

Also cleaned up label escaping and consolidated the test suite regarding
label_tag.
Backport of ab686022f 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20241: QuerySets with callable filter args have said args evaluated only once

[Django]

#20241: QuerySets with callable filter args have said args evaluated only once
-+-
 Reporter:   |Owner:  nobody
  christopher.m.pike@…   |   Status:  new
 Type:  Bug  |  Version:  1.5
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 bmispelon):

 Replying to [comment:2 michael.c.urbanski@…]:
 > I was under the impression that callables in QuerySets, like callables
 in fields, were called as they were used.

 I would have thought so too, but it appears it's not the case.

 I've opened #20249 to fix the tutorial while this ticket remains open
 (fixing this ticket is likely more complicated than amending 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.
For more options, visit https://groups.google.com/groups/opt_out.

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

[Django]

#20249: Tutorial part 5 uses broken undocumented feature
---+
 Reporter:  bmispelon  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 As reported in #20241, passing callable arguments to a queryset's `filter`
 method doesn't actually work the way it's described in the tutorial [1].

 It's also an undocumented feature (#11629).


 [1]
 
https://github.com/django/django/blob/master/docs/intro/tutorial05.txt#L408-L411

-- 
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] #20211: BoundField.label_tag now always escapes its `contents` parameter.

[Django]

#20211: BoundField.label_tag now always escapes its `contents` parameter.
-+-
 Reporter:  bmispelon|Owner:  bmispelon
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Release blocker  |   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:"ab686022f8619b57e7f851fb2ce8617583d70d8d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ab686022f8619b57e7f851fb2ce8617583d70d8d"
 Fixed #20211: Document backwards-incompatible change in
 BoundField.label_tag

 Also cleaned up label escaping and consolidated the test suite regarding
 label_tag.
 }}}

-- 
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] ab6860: Fixed #20211: Document backwards-incompatible chan...

[GitHub]

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

  Changed paths:
M django/forms/forms.py
M docs/releases/1.5.txt
M tests/forms_tests/tests/forms.py

  Log Message:
  ---
  Fixed #20211: Document backwards-incompatible change in BoundField.label_tag

Also cleaned up label escaping and consolidated the test suite regarding
label_tag.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] 991432: [1.5.x] Documented BoundField.label_tag

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 991432ee8ab49eca76113f0b6c23e885ea316507
  
https://github.com/django/django/commit/991432ee8ab49eca76113f0b6c23e885ea316507
  Author: Claude Paroz 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
M docs/ref/forms/api.txt

  Log Message:
  ---
  [1.5.x] Documented BoundField.label_tag

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

[django/django] 0f9924: Documented BoundField.label_tag

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0f99246b6f4e7d08600c19fbbeb8feb1a335f985
  
https://github.com/django/django/commit/0f99246b6f4e7d08600c19fbbeb8feb1a335f985
  Author: Claude Paroz 
  Date:   2013-04-12 (Fri, 12 Apr 2013)

  Changed paths:
M docs/ref/forms/api.txt

  Log Message:
  ---
  Documented BoundField.label_tag



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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] #11629: Callable QuerySet filter arguments not mentioned in documentation

[Django]

#11629: Callable QuerySet filter arguments not mentioned in documentation
--+
 Reporter:  harrym|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by bmispelon):

 It looks like the feature is "broken" since callable arguments are
 evaluated when the queryset is built, not when it's evaluated.

 This means (if I understand it right), that doing
 `queryset.filter(foo=some_callable)` is basically the same as doing
 `queryset.filter(foo=some_callable())`, which makes this feature less
 useful.

 This was discovered in ticket #20241.

 I think the feature would be useful but after discussing it on IRC, it
 seems it might be quite tricky to get it to work.

-- 
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] #20248: Clarifying Documentation

[Django]

#20248: Clarifying Documentation
-+--
 Reporter:  anonymous|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  django-admin.py  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by anonymous):

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


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

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

[Django] #20248: Clarifying Documentation

[Django]

#20248: Clarifying Documentation
---+-
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:  django-admin.py
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+-
 These suggestions relate to the tutorial on "django-admin.py and
 manage.py"

 In there you will find:
 "Generally, when working on a single Django project, it’s easier to use
 manage.py. Use django-admin.py with DJANGO_SETTINGS_MODULE, or the
 --settings command line option, if you need to switch between multiple
 Django settings files."

 Easier than what?

 I suggest rewording this to:
 "Generally, when working on a single Django project, it’s easier to use
 manage.py than to use django-admin.py.  If you need to switch between
 multiple Django settings files then you will have to use django-admin.py
 with DJANGO_SETTINGS_MODULE, or the --settings command line option."

-- 
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.