date:20130719

Re: [Django] #20765: HTML5 number input type not working for DecimalField with big decimal_places

2013-07-19 Thread Django

#20765: HTML5 number input type not working for DecimalField with big
decimal_places
-+-
 Reporter:  aleksey.kladov@… |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"9d3f7a21a337aa82d5c9ac5ef9a6a3888bff62a8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9d3f7a21a337aa82d5c9ac5ef9a6a3888bff62a8"
 [1.6.x] Fixed #20765 -- Set small values of `step` using exponential
 notation.

 Browsers parse small factors of 10 as 0 under decimal notation.

 Thanks to Trac alias matklad for the report and Claude Paroz for the
 review.

 Backport of 415a36947c from master.
 }}}

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

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

Re: [Django] #20765: HTML5 number input type not working for DecimalField with big decimal_places

2013-07-19 Thread Django

#20765: HTML5 number input type not working for DecimalField with big
decimal_places
-+-
 Reporter:  aleksey.kladov@… |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"415a36947cb4b8b61230698e13cca2df9400e245"]:
 {{{
 #!CommitTicketReference repository=""
 revision="415a36947cb4b8b61230698e13cca2df9400e245"
 Fixed #20765 -- Set small values of `step` using exponential notation.

 Browsers parse small factors of 10 as 0 under decimal notation.

 Thanks to Trac alias matklad for the report and 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/082.322b2eaa422bc0f82af78c29b73ef2fa%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 415a36: Fixed #20765 -- Set small values of `step` using e...

2013-07-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 415a36947cb4b8b61230698e13cca2df9400e245
  
https://github.com/django/django/commit/415a36947cb4b8b61230698e13cca2df9400e245
  Author: Simon Charette 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M django/forms/fields.py
M tests/forms_tests/tests/test_fields.py
M tests/model_formsets/tests.py

  Log Message:
  ---
  Fixed #20765 -- Set small values of `step` using exponential notation.

Browsers parse small factors of 10 as 0 under decimal notation.

Thanks to Trac alias matklad for the report and 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51ea049e4dae6_1085f8dd4c8659f%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20779: document AdminSite.app_index_template

2013-07-19 Thread Django

#20779: document AdminSite.app_index_template
+
 Reporter:  CollinAnderson  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Documentation   |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  1   |  UI/UX:  0
+
 it was added back in #8498 but it's not anywhere in the docs:

 it should be added here:
 https://docs.djangoproject.com/en/dev/ref/contrib/admin/#adminsite-
 attributes
 and maybe here too:
 https://docs.djangoproject.com/en/dev/ref/contrib/admin/#root-and-login-
 templates

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

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

[Django] #20774: Update the localflavor topic guide when django-localflavor is ready

2013-07-19 Thread Django

#20774: Update the localflavor topic guide when django-localflavor is ready
--+-
 Reporter:  loic84|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:  localflavor
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+-
 This ticket is a reminder that we need to update
 `docs/topics/localflavor.txt` when the consolidation of the individual
 localflavor packages (django-localflavor-*) into django-localflavor is
 complete.

 ML discussion about the consolidation effort is there:
 https://groups.google.com/forum/#!msg/django-
 developers/vxCStIvpXc4/o68setV25e4J

 Link to the current topic guide:
 https://docs.djangoproject.com/en/dev/topics/localflavor/

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

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

Re: [Django] #20760: Account enumeration through timing attack in password verification in django.contrib.auth

2013-07-19 Thread Django

Comment (by jpaglier):

I actually agree with you about the random delay - I only added the
alternate patch because I once had a colleague who insisted it's harder to
use statistics to mitigate the randomness of scheduling and network
transit if you add some more randomness to it. After that, the extra jump
from the try block failing could be picked up on and you're back in
business.

Sounds fallacious to me - randomness makes it harder to remove randomness?
He did have a stronger math background than me though... Eh anyway, the
initial patch is likely good enough - it will certainly change the attack
from a simple task into one that requires a fair amount of time and effort
before it can be useful.

As for tests, we could probably run authentication against both an
existing user and a nonexistent user a large number of times and do some
basic math to see if the two average computation times are reasonably
close to each other. I'll see what I can do over the next few days.

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

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

[Django] #20780: collectstatic --link causes IOError when dangling symlink exists

2013-07-19 Thread Django

#20780: collectstatic --link causes IOError when dangling symlink exists
-+
 Reporter:  vdboor   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  contrib.staticfiles  |Version:  1.5
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  1|  UI/UX:  0
-+
 When a symlink file already exists, but it's source was moved/renamed,
 `collectstatic` ends with an `IOError`.

 Here is a trackback example:

 {{{
 Linking '/srv/www/virtualenvs/demo.example.org/src/django-filebrowser-no-
 grappelli-django14/filebrowser/static/filebrowser/js/FB_TinyMCE.js'
 Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/srv/www/virtualenvs/demo.example.org/lib/python2.6/site-
 packages/django/core/management/__init__.py", line 443, in
 execute_from_command_line
 utility.execute()
   File "/srv/www/virtualenvs/demo.example.org/lib/python2.6/site-
 packages/django/core/management/__init__.py", line 382, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/srv/www/virtualenvs/demo.example.org/lib/python2.6/site-
 packages/django/core/management/base.py", line 196, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/srv/www/virtualenvs/demo.example.org/lib/python2.6/site-
 packages/django/core/management/base.py", line 232, in execute
 output = self.handle(*args, **options)
   File "/srv/www/virtualenvs/demo.example.org/lib/python2.6/site-
 packages/django/core/management/base.py", line 371, in handle
 return self.handle_noargs(**options)
   File "/srv/www/virtualenvs/demo.example.org/lib/python2.6/site-
 packages/django/contrib/staticfiles/management/commands/collectstatic.py",
 line 163, in handle_noargs
 collected = self.collect()
   File "/srv/www/virtualenvs/demo.example.org/lib/python2.6/site-
 packages/django/contrib/staticfiles/management/commands/collectstatic.py",
 line 113, in collect
 handler(path, prefixed_path, storage)
   File "/srv/www/virtualenvs/demo.example.org/lib/python2.6/site-
 packages/django/contrib/staticfiles/management/commands/collectstatic.py",
 line 275, in link_file
 os.symlink(source_path, full_path)
 OSError: [Errno 17] File exists
 }}}

 I switched moduled here, hence the symlinks of the previous "filebrowser"
 were still there, but no longer pointed to an existing file.
 The same also happens when one reorganized the project layout, while.

 How to reproduce:

 * Have a project with 1 app.
 * run `./manage.py collectstatic --link`
 * Rename that app, or move it to a sub package.
 * run `./manage.py collectstatic --link` again.

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

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

Re: [Django] #17001: Allow usage of custom querysets in prefetch_related

2013-07-19 Thread Django

#17001: Allow usage of custom querysets in prefetch_related
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  prefetch_related |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ethan.jucovy@…):

 * cc: ethan.jucovy@… (added)


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

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

Re: [Django] #6317: Typo / Error in Tutorial

2013-07-19 Thread Django

#6317: Typo / Error in Tutorial
-+-
 Reporter:  yak-man   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  Tutorial | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by anonymous):

 the question_startswith and pub_date_year are both not working for me.
 unsure what i am doing wrong

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

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

[Django] #20776: Multi-level Multi-table Inheritance - mismatched PKs / explicit db_columns

2013-07-19 Thread Django

#20776: Multi-level Multi-table Inheritance - mismatched PKs / explicit 
db_columns
---+
 Reporter:  dowstreet@…|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.5
 Severity:  Normal |   Keywords:  Muti-table Inheritance
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 There seems to be a problem with queries that (i) span several levels of
 multi-table inheritance subclassing when (ii) PKs do not match all the way
 up the hierarchy.  This situation can arise when a higher level object
 (e.g. parent) is created before a lower level object (e.g. grandchild).
 The query seems to use the PK of the grandchild's parent instead of
 walking the whole way up the hierarchy when looking up fields that are
 stored in the grandparent table.

 In the example below there are three levels in the class hierarchy.  When
 accessing the name field (which is stored in the Level1 base class) from
 an object in Level3, the query returns an unexpected value 'Top 1' instead
 of the expected 'Bot 1':

 {{{

 # models.py

 from django.db import models

 class Level1(models.Model):
  """ Top level base class """

  level1_id = models.AutoField(primary_key=True, db_column='Level1_ID')
  name = models.CharField(max_length=32, db_column='Name', blank=True,
 null=True)

  class Meta:
  db_table = 'Level1'


 class Level2(Level1):
  """ Middle level class """

  level2_id = models.AutoField(primary_key=True, db_column='Level2_ID')
  level1 = models.OneToOneField('Level1', db_column='Level1_ID',
 parent_link=True)  # parent class

  class Meta:
  db_table = 'Level2'


 class Level3(Level2):
  """ Bottom level class """

  level3_id = models.AutoField(primary_key=True, db_column='Level3_ID')
  level2 = models.OneToOneField('Level2', db_column='Level2_ID',
 parent_link=True)  # parent class

  class Meta:
  db_table = 'Level3'

 }}}

 Using the shell to add a Level1 object and then a Level3 object to an
 otherwise empty database:

 {{{

 from sc_test.models import *

 >>> top1 = Level1()
 >>> top1.name = 'Top 1'
 >>> top1.save()

 >>> bot1 = Level3()
 >>> bot1.name = 'Bot 1'
 >>> bot1.save()

 >>> l1 = Level1.objects.all()
 >>> l1
 [, ]

 >>> l2 = Level2.objects.all()
 >>> l2
 []

 >>> l3 = Level3.objects.all()
 >>> l3
 []

 >>> l1[0].name
 u'Top 1'

 >>> l1[1].name
 u'Bot 1'

 >>> l2[0].name
 u'Bot 1'

 >>> l3[0].name
 u'Top 1'   # WRONG!! - expected value is u'Bot
 1'

 }}}

 Note: In this example OneToOneField and ID/primary keys are manually added
 so that specific db_column names can be used.  It is unclear whether the
 problem is related to this combination, or whether it affects auto-
 generated OneToOneFields as well.

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

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

Re: [Django] #19353: Make it easier to extend UserCreationForm for custom user models

2013-07-19 Thread Django

#19353: Make it easier to extend UserCreationForm for custom user models
-+-
 Reporter:  bmispelon|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:
 Severity:  Normal   |  1.5-alpha-1
 Keywords:  UserCreationForm |   Resolution:
  AUTH_USER_MODEL| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mjumbewu):

 * cc: mjumbewu (added)


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

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

Re: [Django] #20765: HTML5 number input type not working for DecimalField with big decimal_places

2013-07-19 Thread Django

#20765: HTML5 number input type not working for DecimalField with big
decimal_places
--+--
 Reporter:  aleksey.kladov@…  |Owner:  charettes
 Type:  Bug   |   Status:  assigned
Component:  Forms |  Version:  1.6-beta-1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by matklad):

 Looks perfect!

 As a bonus, exponential form improves html readability.

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

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

Re: [Django] #13696: Admin Edit Inline templates don' t output hidden field for PK when it isn't an autoField and has editable=False

2013-07-19 Thread Django

#13696: Admin Edit Inline templates don' t output hidden field for PK when it 
isn't
an autoField and has editable=False
--+
 Reporter:  evan.reiser@… |Owner:  dArignac
 Type:  Bug   |   Status:  new
Component:  contrib.admin |  Version:  1.2
 Severity:  Normal|   Resolution:
 Keywords:  inline templates  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by kmtracey):

 Pull request with slightly altered fix:
 https://github.com/django/django/pull/1381

 The proposed fix duplicated the pk field on the inlines if there was a
 non-auto EDITABLE pk field already rendered. The pull request tests for
 that (previous fix would fail that test) in addition to testing for the
 non-auto non-editable pk.

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

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

[Django] #20781: Regression in form field _has_changed for fields with show_hidden_initial=True

2013-07-19 Thread Django

#20781: Regression in form field _has_changed for fields with
show_hidden_initial=True
+
 Reporter:  timo|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  1.6-beta-1
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Following [892bc91cb0] (affects 1.6.X), the `date_joined` and `last_login`
 fields always appear as "Changed" when editing a user in the admin. It
 looks like it affects fields with callable defaults. In this case,
 `django.forms.fields.Field._has_changed` returns `False` because
 `initial_value` is a string and `data_value` is a `datetime`.

 I discovered this working on #19019, the
 [https://github.com/django/django/pull/1380 PR] contains some TODOs which
 could be used as a regression test once this is fixed.

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

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

[Django] #20778: label_tag() escapes lazy labels twice

2013-07-19 Thread Django

#20778: label_tag() escapes lazy labels twice
+---
 Reporter:  sephi@… |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  1.5
 Severity:  Normal  |   Keywords:  label_tag
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+---
 If you use label_tag() on a field that uses a ugettext_lazy() string as a
 label, it gets escaped twice. That's easily reproducible with the
 following code:

 models.py
 {{{
 # _ is ugettext_lazy
 class MyModel(models.Model):
  name = models.CharField(_('My label'))
 }}}

 forms.py
 {{{
 class MyForm(forms.ModelForm):
  class Meta:
  model = MyModel
 }}}

 views.py
 {{{
 def my_view(request):
 myform = MyForm()
 assert False, myform['name'].label_tag()
 }}}

 If "My label" is translated as "My 'label'" (with single quotes around
 it), here's what you get:

 `My #39;label#39;`

 The expected behaviour would be to get the contents escaped but only once:

 `My label`

 That would then appear correctly in the template. Also if you use a simple
 string as a label in your model, it gets escaped correctly.

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

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

Re: [Django] #20760: Account enumeration through timing attack in password verification in django.contrib.auth

2013-07-19 Thread Django

#20760: Account enumeration through timing attack in password verification in
django.contrib.auth
-+-
 Reporter:  jpaglier@…   |Owner:  anonymous
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  security | Triage Stage:  Accepted
  authentication timing enumeration  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by erikr):

 Well, his point is somewhat valid. But, the time difference from a
 try/catch is incredibly small. And networks introduce quite a degree of
 randomness too, which I expect to be dramatically bigger than the
 try/catch. Password hashing, on the other hand, is something which is
 intentionally quite slow, which means it might still be visible through
 network jitter.

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

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

[Django] #20777: admin delete page proxy models

2013-07-19 Thread Django

#20777: admin delete page proxy models
-+
 Reporter:  CollinAnderson   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  contrib.admin|Version:  1.6-beta-1
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 This #18491 broke proxy model `__unicode__()` on the admin delete page:
 
https://github.com/django/django/commit/2b48fcc607010065c0f8107baf669dd41b164f3c

 The concrete model is being instantiated with no attributes except the
 primary key. This breaks `obj.__unicode__()` because it can't reference
 any of its fields. (It also means that we're displaying
 `BaseModel.__unicode__()` instead of `ProxyModel.__unicode__()`, which
 isn't a problem for me.)

 I have a simple project you can use to try it yourself:
 https://github.com/collinanderson/proxyadmin

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

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

Re: [Django] #18551: skipIfDBFeature/skipUnlessDBFeature cannot be used as class decorators

2013-07-19 Thread Django

#18551: skipIfDBFeature/skipUnlessDBFeature cannot be used as class decorators
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"6d52844b9b3c0bd18eea03ac9dc499782b84c36b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6d52844b9b3c0bd18eea03ac9dc499782b84c36b"
 Fixed #18551 -- Enabled skipIfDBFeature/skipUnlessDBFeature to decorate a
 class

 Thanks Tim Graham for the review and improved patch.
 }}}

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

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

Re: [Django] #8149: UploadedFile doesn't iterate over lines with \r line endings

2013-07-19 Thread Django

#8149: UploadedFile doesn't iterate over lines with \r line endings
--+
 Reporter:  mrmachine |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  File uploads/storage  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  UploadedFile  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * cc: timograham@… (added)
 * needs_better_patch:  0 => 1
 * needs_tests:  1 => 0


Comment:

 The test doesn't pass on Python 3.

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

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

Re: [Django] #20775: Incorrect description of startswith, istartswith, contains, icontains, endswith and iendswith (was: Incorrect description of istartswith)

2013-07-19 Thread Django

#20775: Incorrect description of startswith, istartswith, contains, icontains,
endswith and iendswith
+--
 Reporter:  a_nekhaychik@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Documentation   |  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 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.4a81f503ce3aa4caf21e2ef2c4ebc880%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20765: HTML5 number input type not working for DecimalField with big decimal_places

2013-07-19 Thread Django

#20765: HTML5 number input type not working for DecimalField with big
decimal_places
--+--
 Reporter:  aleksey.kladov@…  |Owner:  charettes
 Type:  Bug   |   Status:  assigned
Component:  Forms |  Version:  1.6-beta-1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by charettes):

 I think I've found a middleground. Parsing works flawlessly in
 [http://jsfiddle.net/cnSsU/12/ exponential form]. Submitting an updated
 patch.

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

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

[Django] #20775: Incorrect description of istartswith

2013-07-19 Thread Django

#20775: Incorrect description of istartswith
+
 Reporter:  a_nekhaychik@…  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Documentation   |Version:  1.5
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 istartswith

 On the page: https://docs.djangoproject.com/en/dev/ref/models/querysets
 /#field-lookups we can read:

 ''istartswith
 Case-insensitive starts-with.
 Example:
 Entry.objects.filter(headline__istartswith='will')
 SQL equivalent:
 SELECT ... WHERE headline ILIKE 'Will%';''

 But there is no db backend which uses ILIKE. LIKE will be used for MySQL.


 Again if you assume MySQL by default in documentation then:

 ''startswith
 Case-sensitive starts-with.
 Example:
 Entry.objects.filter(headline__startswith='Will')
 SQL equivalent:
 SELECT ... WHERE headline LIKE 'Will%';
 ''

 is incorrect because LIKE BINARY will be used.

 The same for contains, icontains, endswith and iendswith.

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

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

Re: [Django] #20479: Adding the concept predicates in the Django url routing

2013-07-19 Thread Django

#20479: Adding the concept predicates in the Django url routing
-+-
 Reporter:  rach |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  urlresolver, | Triage Stage:
  predicates |  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by rach):

 There is probably a better way to implement it and it's more in
 implementation to illustrate the concept to unloose the relationship
 between url routing and view lookup which are only one thing at this stage
 in Django.

 I m not fan of django-multiurl approach as it add one level of complexity
 at the url configuration level, but I agree that could be implemented
 following the same technique and wrap the urls into a container. I may
 implement it for my next django project.

 The usecases are numerous:

 - Organize function base view to treat XHR request
 - MultiForm submit on a same url
 - Build easily api from function base view to handle PUT/POST/GET/DELETE
 - create reusable condition to check url arguments without having to write
 crazy regexp
 - Call specific function base view base contentType
 - Not getting a MethodNotAllowed when it's not what you want
 - Call a specific view matter if the user is login or not ( ex: / ->
 welcom or home)
 ...

 More generics:

 - Organize code from function base view and get rid off redundant logic
 - Extending function base view without having to follow the Class Base
 view model

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

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

Re: [Django] #14656: Atom1Feed should write atom:published element

2013-07-19 Thread Django

#14656: Atom1Feed should write atom:published element
-+-
 Reporter:  ttencate@…   |Owner:  Deacalion
 Type:  Bug  |   Status:  closed
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"a269ea4fe0a9a7195f1bd8bf5d462f48c226d525"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a269ea4fe0a9a7195f1bd8bf5d462f48c226d525"
 Fixed #14656 -- Added Atom1Feed `published` element

 Some feed aggregators make use of the `published` element as well as
 the `updated` element (within the Atom standard -- http://bit.ly/2YySb).

 The standard allows for these two elements to be present in the same
 entry. `Atom1Feed` had implemented the `updated` element which was
 incorrectly taking the date from `pubdate`.
 }}}

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

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

[django/django] a269ea: Fixed #14656 -- Added Atom1Feed `published` elemen...

2013-07-19 Thread GitHub

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

https://github.com/django/django/commit/a269ea4fe0a9a7195f1bd8bf5d462f48c226d525
Author: Matt Deacalion Stevens
Date: 2013-07-19 (Fri, 19 Jul 2013)

Changed paths:
M AUTHORS
M django/contrib/syndication/views.py
M django/utils/feedgenerator.py
M docs/ref/contrib/syndication.txt
M docs/ref/utils.txt
M docs/releases/1.7.txt
M tests/syndication/feeds.py
M tests/syndication/fixtures/feeddata.json
M tests/syndication/models.py
M tests/syndication/tests.py
M tests/syndication/urls.py

Log Message:
---
Fixed #14656 -- Added Atom1Feed `published` element

Some feed aggregators make use of the `published` element as well as
the `updated` element (within the Atom standard -- http://bit.ly/2YySb).

The standard allows for these two elements to be present in the same
entry. `Atom1Feed` had implemented the `updated` element which was
incorrectly taking the date from `pubdate`.

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

Re: [Django] #10284: ModelFormSet - objects are deleted even if commit=False

2013-07-19 Thread Django

#10284: ModelFormSet - objects are deleted even if commit=False
+
 Reporter:  laureline.guerin@…  |Owner:  Wedg
 Type:  Bug |   Status:  assigned
Component:  Forms   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by loic84):

 +1 for this PR.

 As mentioned on IRC, this together with formally documenting
 `ModelFormSet.(new|changed|deleted)_objects` is IMO the cleanest solution
 to this problem.

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

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

Re: [Django] #10284: ModelFormSet - objects are deleted even if commit=False

2013-07-19 Thread Django

#10284: ModelFormSet - objects are deleted even if commit=False
+
 Reporter:  laureline.guerin@…  |Owner:  Wedg
 Type:  Bug |   Status:  assigned
Component:  Forms   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by timo):

 [https://groups.google.com/forum/#!topic/django-developers/fJGN0ZyC-AU
 django-dev thread] hasn't received any responses in an attempt to get a
 design decision.

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

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

Re: [Django] #17988: BaseModelFormset.save doesn't honor commit=False when deleting objects.

2013-07-19 Thread Django

#17988: BaseModelFormset.save doesn't honor commit=False when deleting objects.
+-
 Reporter:  rem |Owner:  tuxcanfly
 Type:  Bug |   Status:  closed
Component:  Forms   |  Version:  1.3
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+-
Changes (by timo):

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


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

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

Re: [Django] #20700: Tests does not report missing fixtures

2013-07-19 Thread Django

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

Comment:

OK so you now do get a warning when running a test such as the one in the
original description:

{{{
(django2) kmtracey@caktus006 10:26:34: ~/software/web/playground
--> ./manage.py test
Creating test database for alias 'default'...
/home/kmtracey/django/git-
django/django/core/management/commands/loaddata.py:218: UserWarning: No
fixture named 'filename' found.
warnings.warn("No fixture named '%s' found." % fixture_name)

.
--
Ran 1 test in 0.004s

OK
Destroying test database for alias 'default'...

}}}

That seems sufficient to me, even though the test does still "pass", I
don't think it's too much to expect that devs will note the warning and
investigate. So re-closing this as a dupe of #18990.

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

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

Re: [Django] #19900: Upgrade admin buttons

2013-07-19 Thread Django

Comment (by aaugustin):

Replying to [comment:14 timo]:
> I'd like to check this in. Can we defer the SVG/PNG issue to a separate
ticket?

Yes, better check-in the part that works rather than let it rot.

> According to [http://css-tricks.com/do-we-need-box-shadow-prefixes/ css
tricks], we can probably drop the vendor prefixes for border-radius. Any
objection to that?

I'm in favor of not including vendor prefixes when we have a sufficient
excuse to do so :) http://caniuse.com/#feat=css-boxshadow shows that
recent versions of browsers don't require vendor prefixes. At worst,
shadows aren't a big deal.

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

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

Re: [Django] #18213: loaddata should allow empty fixtures

2013-07-19 Thread Django

#18213: loaddata should allow empty fixtures
-+-
 Reporter:  lsaffre  |Owner:  haxoza
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * cc: timograham@… (added)
 * needs_better_patch:  0 => 1


Comment:

 No longer merges cleanly.

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

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

Re: [Django] #19900: Upgrade admin buttons

2013-07-19 Thread Django

#19900: Upgrade admin buttons
-+-
 Reporter:  Pedro Mourelle   |Owner:  anonymous
  |   Status:  assigned
 Type:   |  Version:
  Cleanup/optimization   |   Resolution:
Component:  contrib.admin| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  sprints-django-ar|  Patch needs improvement:  1
Has patch:  1|UI/UX:  1
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by timo):

 I'd like to check this in. Can we defer the SVG/PNG issue to a separate
 ticket?

 According to [http://css-tricks.com/do-we-need-box-shadow-prefixes/ css
 tricks], we can probably drop the vendor prefixes for border-radius. Any
 objection to that?

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

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

Re: [Django] #20773: contrib/gis/maps/google/gmap : script() string formating

2013-07-19 Thread Django

#20773: contrib/gis/maps/google/gmap : script() string formating
-+-
 Reporter:  martync  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mjtamlyn):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Ready for checkin
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

Re: [Django] #20760: Account enumeration through timing attack in password verification in django.contrib.auth

2013-07-19 Thread Django

* cc: eromijn@… (added)
* needs_tests: 0 => 1
* stage: Unreviewed => Accepted

Comment:

I agree with the problem and the patch. The timing difference is probably
large enough that this could actually be exploited as well.

However, I'm not sure whether the random delay is a good addition. With
your first patch, I already no longer see an opportunity for a timing
attack. Slowing down logins more seems a unnecessary service degradation.
I would also like to have a test for this, but I'm not sure hoe we could
test this effectively and reliably. Perhaps it can't be done.

Note that until recently, the password reset would also reveal whether not
an account exists, in a much more obvious way, but that was fixed in trunk
a few weeks ago.

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

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

[Django] #20773: contrib/gis/maps/google/gmap : script() string formating

2013-07-19 Thread Django

#20773: contrib/gis/maps/google/gmap : script() string formating
+
 Reporter:  martync |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  GIS |Version:  1.5
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 The property named "script" in contrib.gis.maps.google.gmap.GoogleMap has
 a wrong string formating.
 
https://github.com/django/django/blob/1.5c2/django/contrib/gis/maps/google/gmap.py#L134-L137


 {{{
 return format_html('%s\n  \n//\n  ',
 self.api_script, mark_safe(self.js))

 }}}

 while it should be :

 {{{
 return format_html('{0}\n  \n//\n  ',
 self.api_script, mark_safe(self.js))

 }}}

 I have created a pull request for this bug :
 https://github.com/django/django/pull/1379
 I will write a testcase.

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

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

Re: [Django] #20768: Create a reference of public Manager methods

2013-07-19 Thread Django

#20768: Create a reference of public Manager methods
---+
 Reporter:  ramiro |Owner:  nobody
 Type:  New feature|   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 timo):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #20769: add Python compatibility section to django1.6 release notes

2013-07-19 Thread Django

#20769: add Python compatibility section to django1.6 release notes
-+-
 Reporter:  CollinAnderson   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.6-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


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

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

[django/django] 496f31: [1.6.x] LocaleMiddleware isn't default anymore (co...

2013-07-19 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 496f319970fdc8d9ced6779f9866e7959b646bae
  
https://github.com/django/django/commit/496f319970fdc8d9ced6779f9866e7959b646bae
  Author: Sergio Oliveira 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  [1.6.x] LocaleMiddleware isn't default anymore (corrected docs)

Changed in @23229061fcb836ecca2195cc75f91e331279a5d1

Backport of cf6c754629 from master



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

[django/django] cf6c75: LocaleMiddleware isn't default anymore

2013-07-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cf6c754629a6348847cf0e83a0ffbc8a74547641
  
https://github.com/django/django/commit/cf6c754629a6348847cf0e83a0ffbc8a74547641
  Author: Sergio Oliveira 
  Date:   2013-07-18 (Thu, 18 Jul 2013)

  Changed paths:
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  LocaleMiddleware isn't default anymore

Changed in @23229061fcb836ecca2195cc75f91e331279a5d1


  Commit: e1c737b62fed5b77cb22c2abe01c304bf5aef6f7
  
https://github.com/django/django/commit/e1c737b62fed5b77cb22c2abe01c304bf5aef6f7
  Author: Tim Graham 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  Merge pull request #1374 from seocam/fix_i18n_docs

LocaleMiddleware isn't default anymore (corrected docs)


Compare: https://github.com/django/django/compare/4aa006efd0f7...e1c737b62fed

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

[django/django] 9386bb: [1.5.x] Updated the `databases` documentation

2013-07-19 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 9386bbc75f23a8b9bd747eb3b37bc220fe04563b
  
https://github.com/django/django/commit/9386bbc75f23a8b9bd747eb3b37bc220fe04563b
  Author: Matt Deacalion Stevens 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/ref/databases.txt

  Log Message:
  ---
  [1.5.x] Updated the `databases` documentation

 + Removed a reference about MySQL storage engines also being
   called 'table types', as this term has been deprecated for
   8 years and is no longer used.

 + Fixed the link to the official InnoDB storage engine docs.

 + Apache (versions >= 2.4) will always choose a multi-threaded
   MPM module on modern operating systems (later than 2002).

Backport of fa217d14a0 from master



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

[django/django] 9b26cb: [1.6.x] Updated the `databases` documentation

2013-07-19 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 9b26cb72d94d7d3b7bb85e55d71de35ee6c939d4
  
https://github.com/django/django/commit/9b26cb72d94d7d3b7bb85e55d71de35ee6c939d4
  Author: Matt Deacalion Stevens 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/ref/databases.txt

  Log Message:
  ---
  [1.6.x] Updated the `databases` documentation

 + Removed a reference about MySQL storage engines also being
   called 'table types', as this term has been deprecated for
   8 years and is no longer used.

 + Fixed the link to the official InnoDB storage engine docs.

 + Apache (versions >= 2.4) will always choose a multi-threaded
   MPM module on modern operating systems (later than 2002).

Backport of fa217d14a0 from master



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

[django/django] fa217d: Updated the `databases` documentation

2013-07-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fa217d14a040cb09f8359d8ac613cc1dac220619
  
https://github.com/django/django/commit/fa217d14a040cb09f8359d8ac613cc1dac220619
  Author: Matt Deacalion Stevens 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/ref/databases.txt

  Log Message:
  ---
  Updated the `databases` documentation

 + Removed a reference about MySQL storage engines also being
   called 'table types', as this term has been deprecated for
   8 years and is no longer used.

 + Fixed the link to the official InnoDB storage engine docs.

 + Apache (versions >= 2.4) will always choose a multi-threaded
   MPM module on modern operating systems (later than 2002).


  Commit: 4aa006efd0f7402f795bb0cf893d0747802d93f8
  
https://github.com/django/django/commit/4aa006efd0f7402f795bb0cf893d0747802d93f8
  Author: Tim Graham 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/ref/databases.txt

  Log Message:
  ---
  Merge pull request #1377 from Matt-Stevens/doc-fixes-ref-databases

Updated the `databases` documentation


Compare: https://github.com/django/django/compare/997e305d24b0...4aa006efd0f7

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

[django/django] c89cc4: [1.5.x] Fixed Croatia's country code in `localflav...

2013-07-19 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: c89cc4fc2932efc5fe89a5f3c2ce4795e5928c40
  
https://github.com/django/django/commit/c89cc4fc2932efc5fe89a5f3c2ce4795e5928c40
  Author: Matt Deacalion Stevens 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/ref/contrib/localflavor.txt

  Log Message:
  ---
  [1.5.x] Fixed Croatia's country code in `localflavor` docs

Backport of 97e5398629 from master



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

[django/django] e7435f: [1.6.x] Fixed Croatia's country code in `localflav...

2013-07-19 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: e7435fbe2f1e30570fced71d286edad98674fa51
  
https://github.com/django/django/commit/e7435fbe2f1e30570fced71d286edad98674fa51
  Author: Matt Deacalion Stevens 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/topics/localflavor.txt

  Log Message:
  ---
  [1.6.x] Fixed Croatia's country code in `localflavor` docs

Backport of 97e5398629 from master



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

[django/django] 97e539: Fix Croatia's country code in `localflavor` docs

2013-07-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 97e5398629e36a84d3553dbe7d6eeeaa7d87ae30
  
https://github.com/django/django/commit/97e5398629e36a84d3553dbe7d6eeeaa7d87ae30
  Author: Matt Deacalion Stevens 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/topics/localflavor.txt

  Log Message:
  ---
  Fix Croatia's country code in `localflavor` docs

Croatia's country code is 'HR', not 'CR'.


  Commit: 997e305d24b0245085a8364fe7ed15b8def82e0b
  
https://github.com/django/django/commit/997e305d24b0245085a8364fe7ed15b8def82e0b
  Author: Tim Graham 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/topics/localflavor.txt

  Log Message:
  ---
  Merge pull request #1375 from Matt-Stevens/master

Fixed Croatia's country code in `localflavor` docs


Compare: https://github.com/django/django/compare/466998622895...997e305d24b0

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

[django/django] cf2986: [1.5.x] Fixed #20772 -- Fixed minor typo in form m...

2013-07-19 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: cf2986c885d5d58ddf8f341d7aa456f0a7801b16
  
https://github.com/django/django/commit/cf2986c885d5d58ddf8f341d7aa456f0a7801b16
  Author: Loic Bistuer 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/topics/forms/media.txt

  Log Message:
  ---
  [1.5.x] Fixed #20772 -- Fixed minor typo in form media docs.

Backport of aa41eb9b8b from master



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

Re: [Django] #20772: Misprint

2013-07-19 Thread Django

#20772: Misprint
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"b7556a4980bb632059cdc1f1286507528c3e01ce"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b7556a4980bb632059cdc1f1286507528c3e01ce"
 [1.6.x] Fixed #20772 -- Fixed minor typo in form media docs.

 Backport of aa41eb9b8b from master
 }}}

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

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

[django/django] b7556a: [1.6.x] Fixed #20772 -- Fixed minor typo in form m...

2013-07-19 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: b7556a4980bb632059cdc1f1286507528c3e01ce
  
https://github.com/django/django/commit/b7556a4980bb632059cdc1f1286507528c3e01ce
  Author: Loic Bistuer 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/topics/forms/media.txt

  Log Message:
  ---
  [1.6.x] Fixed #20772 -- Fixed minor typo in form media docs.

Backport of aa41eb9b8b from master



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

Re: [Django] #20772: Misprint

2013-07-19 Thread Django

#20772: Misprint
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"cf2986c885d5d58ddf8f341d7aa456f0a7801b16"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cf2986c885d5d58ddf8f341d7aa456f0a7801b16"
 [1.5.x] Fixed #20772 -- Fixed minor typo in form media docs.

 Backport of aa41eb9b8b from master
 }}}

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

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

Re: [Django] #20772: Misprint

2013-07-19 Thread Django

#20772: Misprint
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"46699862289528f2bf0ff6c299c66b75bf4f37ce"]:
 {{{
 #!CommitTicketReference repository=""
 revision="46699862289528f2bf0ff6c299c66b75bf4f37ce"
 Merge pull request #1378 from loic/docs

 Fixed #20772 -- Fixed minor typo in form media 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.31cca02f006dcca0584c2ac346521d37%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20772: Misprint

2013-07-19 Thread Django

#20772: Misprint
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Loic Bistuer ):

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


Comment:

 In [changeset:"aa41eb9b8b2a12ffcaf81e48e3af331551ffa9e8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="aa41eb9b8b2a12ffcaf81e48e3af331551ffa9e8"
 Fixed #20772 -- Fixed minor typo in form media 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.43dee770d73877f9d8e0a463bda171de%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] aa41eb: Fixed #20772 -- Fixed minor typo in form media doc...

2013-07-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: aa41eb9b8b2a12ffcaf81e48e3af331551ffa9e8
  
https://github.com/django/django/commit/aa41eb9b8b2a12ffcaf81e48e3af331551ffa9e8
  Author: Loic Bistuer 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/topics/forms/media.txt

  Log Message:
  ---
  Fixed #20772 -- Fixed minor typo in form media docs.


  Commit: 46699862289528f2bf0ff6c299c66b75bf4f37ce
  
https://github.com/django/django/commit/46699862289528f2bf0ff6c299c66b75bf4f37ce
  Author: Tim Graham 
  Date:   2013-07-19 (Fri, 19 Jul 2013)

  Changed paths:
M docs/topics/forms/media.txt

  Log Message:
  ---
  Merge pull request #1378 from loic/docs

Fixed #20772 -- Fixed minor typo in form media docs.


Compare: https://github.com/django/django/compare/2fc6c9472cd2...466998622895

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

Re: [Django] #20772: Misprint

2013-07-19 Thread Django

#20772: Misprint
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by loic84):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * has_patch:  0 => 1
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Ready for checkin


Comment:

 Thanks for the report.

 PR https://github.com/django/django/pull/1378

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

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

Re: [Django] #19737: Deprecate and then remove "shell" management command

2013-07-19 Thread Django

Comment (by loic84):

Strong -1 for me.

This DJANGO_SETTINGS_MODULE is a burden IMO, it's overly verbose, and it's
everywhere: in the command line, inside manage.py, inside wsgi.py.

When we ask newcomers to try something in the REPL, on top of adding
`DJANGO_SETTINGS_MODULE=project.settings` to their command line, we'll
also have to ask them to run the following snippet to work around our lack
of a proper init sequence:

{{{
from django.db.models.loading import get_models
get_models()
}}}

TBH having `manage.py` as a single entry point is the only thing that
makes me bear with with the management commands API.

I'm celebrating most of this is env stuffing is being removed from
`runtests.py` in #19941 and with the `--selenium` argument, please let's
not require it for something as common as running a shell.

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

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

[Django] #20772: Misprint

2013-07-19 Thread Django

#20772: Misprint
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 https://docs.djangoproject.com/en/dev/topics/forms/media/#subsets-of-
 assets

 in code:
 >>> print(w.media)['css']

 should be:
 >>> print(w.media['css'])

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

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

[Django] #20771: importlib: more verbosity please

2013-07-19 Thread Django

#20771: importlib: more verbosity please
---+
 Reporter:  lu.nemec@… |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Utilities  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Hello, I recently debugged some code where relative imports were used
 Importlib threw an error "relative imports require the 'package' argument"

 But, it would be really handy to have it also write what is it trying to
 import...

 So I edited the file locally to this:

 importlib.py
 {{{
 #27 if not package:
 #28 raise TypeError("relative imports require the 'package' argument,
 package: %s" % name)
 }}}

 And I found the place where I forgot to look in seconds

 Cheers!

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

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

Re: [Django] #12422: Django overrides the default email charset behaviour for utf-8

2013-07-19 Thread Django

#12422: Django overrides the default email charset behaviour for utf-8
---+
 Reporter:  simonb |Owner:  susan
 Type:  Bug|   Status:  assigned
Component:  Core (Mail)|  Version:  1.1
 Severity:  Normal |   Resolution:
 Keywords:  charset utf-8  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by susan):

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


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

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

Re: [Django] #12422: Django overrides the default email charset behaviour for utf-8

2013-07-19 Thread Django

#12422: Django overrides the default email charset behaviour for utf-8
---+
 Reporter:  simonb |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Core (Mail)|  Version:  1.1
 Severity:  Normal |   Resolution:
 Keywords:  charset utf-8  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by anonymous):

 Tests pass. I made a PR to make it easier to merge into master.
 https://github.com/django/django/pull/1376/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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.da15625bd6c22fe156e60dec0617c954%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20765: HTML5 number input type not working for DecimalField with big decimal_places

2013-07-19 Thread Django

#20765: HTML5 number input type not working for DecimalField with big
decimal_places
--+--
 Reporter:  aleksey.kladov@…  |Owner:  charettes
 Type:  Bug   |   Status:  assigned
Component:  Forms |  Version:  1.6-beta-1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by matklad):

 This looks good. I can see only one very minor caveat. If decimal_places=0
 then step is equal to any, while 1 seems more reasonable.

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

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

59 matches

Mail list logo