date:20140831

[django/django] e42a82: [1.7.x] Fixed #23391 -- Removed an erroneous backt...

2014-08-31 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: e42a82edf2acbe1cb32757072dc4965380f40e09
  
https://github.com/django/django/commit/e42a82edf2acbe1cb32757072dc4965380f40e09
  Author: Simon Charette 
  Date:   2014-08-31 (Sun, 31 Aug 2014)

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

  Log Message:
  ---
  [1.7.x] Fixed #23391 -- Removed an erroneous backtip from the form's 
documentation.

Thanks to Trac alias nessita for the report.

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

Re: [Django] #23391: Erroneous backtip on forms' documentation

2014-08-31 Thread Django

#23391: Erroneous backtip on forms' documentation
---+
 Reporter:  nessita|Owner:  nessita
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Simon Charette ):

 In [changeset:"e42a82edf2acbe1cb32757072dc4965380f40e09"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e42a82edf2acbe1cb32757072dc4965380f40e09"
 [1.7.x] Fixed #23391 -- Removed an erroneous backtip from the form's
 documentation.

 Thanks to Trac alias nessita for the report.

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

Re: [Django] #23391: Erroneous backtip on forms' documentation (was: Missing backtick on forms' documentation)

2014-08-31 Thread Django

#23391: Erroneous backtip on forms' documentation
---+
 Reporter:  nessita|Owner:  nessita
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by charettes):

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


Comment:

 From what I can see it looks like this is still an issue. I will commit a
 patch and give you attribution.

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

Re: [Django] #23391: Erroneous backtip on forms' documentation

2014-08-31 Thread Django

#23391: Erroneous backtip on forms' documentation
---+
 Reporter:  nessita|Owner:  nessita
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"ab9c886459e179a7741efd3be440653afe260dff"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ab9c886459e179a7741efd3be440653afe260dff"
 Fixed #23391 -- Removed an erroneous backtip from the form's
 documentation.

 Thanks to Trac alias nessita for the report.
 }}}

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

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

[django/django] ab9c88: Fixed #23391 -- Removed an erroneous backtip from ...

2014-08-31 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ab9c886459e179a7741efd3be440653afe260dff
  
https://github.com/django/django/commit/ab9c886459e179a7741efd3be440653afe260dff
  Author: Simon Charette 
  Date:   2014-08-31 (Sun, 31 Aug 2014)

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

  Log Message:
  ---
  Fixed #23391 -- Removed an erroneous backtip from the form's documentation.

Thanks to Trac alias nessita for the report.


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

Re: [Django] #20930: Arithmetic operations on aggregates

2014-08-31 Thread Django

#20930: Arithmetic operations on aggregates
-+-
 Reporter:  debanshuk|Owner:
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  aggregate, annotate  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timgraham):

 * status:  new => 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/067.17572b1fae0cc6c330d53f2c4734d427%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23391: Missing backtick on forms' documentation

2014-08-31 Thread Django

#23391: Missing backtick on forms' documentation
---+--
 Reporter:  nessita|Owner:  nessita
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 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 nessita):

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


Comment:

 Apparently this is already fixed in the repository, closing 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.6c539ff84e84c6d6c0f9e90858c60478%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23391: Missing backtick on forms' documentation

2014-08-31 Thread Django

#23391: Missing backtick on forms' documentation
---+-
 Reporter:  nessita|  Owner:  nessita
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 Current dev documentation, under the url:

 https://docs.djangoproject.com/en/dev/ref/forms/validation/#form-and-
 field-validation

 shows:

 "Finally, once those two methods are run for every field, the
 :meth:`Form.clean() method, or its override, is executed whether or not
 the previous methods have raised errors."

 There seems to be a missing backtick, attaching patch soon.

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

Re: [Django] #23391: Missing backtick on forms' documentation

2014-08-31 Thread Django

#23391: Missing backtick on forms' documentation
---+--
 Reporter:  nessita|Owner:  nessita
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by nessita):

 * status:  new => assigned
 * 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/065.df6895ee268e572a1650a95fb7f22a3e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23363: Field length in ORM

2014-08-31 Thread Django

Comment (by jarshwah):

I can't seem to find a ticket requesting an implementation of custom
functions (other than extensions to .extra()). #14030 will allow this
feature request to be implemented, but the original scope of 14030 was to
allow F() objects to be composed with aggregates.

I think we should open a new ticket that defines a list of functions to be
implemented by django (pending #14030), and close off any related tickets
such as this one as duplicates/wontfixes. I'm happy to open that new
ticket, but will have to do so later in the day.

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

Re: [Django] #20930: Arithmetic operations on aggregates

2014-08-31 Thread Django

#20930: Arithmetic operations on aggregates
-+-
 Reporter:  debanshuk|Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  aggregate, annotate  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by jarshwah):

 FYI - the implementation of #14030 satisfies this ticket.

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

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

Re: [Django] #23371: Change the first day of the week to Monday for en_GB

2014-08-31 Thread Django

#23371: Change the first day of the week to Monday for en_GB
-+-
 Reporter:  duncanparkes |Owner:
 Type:  Bug  |  duncanparkes
Component:   |   Status:  assigned
  Internationalization   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  locale, en_GB| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by duncanparkes):

 It certainly does - I've added something and pushed a new commit.

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

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

Re: [Django] #11078: Proxy models do not inherit META.app_label

2014-08-31 Thread Django

#11078: Proxy models do not inherit META.app_label
-+-
 Reporter:  gsong|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  proxy model  |  Needs documentation:  0
  app_label  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by aaugustin):

 This still happens after the app-loading refactor.

 I couldn't locate the code that copies the original model's meta
 attributes to the proxy's meta. It looks like it could be
 `Options.setup_proxy` but that method only deals with a few attributes.

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

Re: [Django] #9596: Comparing a DateTimeField to a date is too hard

2014-08-31 Thread Django

#9596: Comparing a DateTimeField to a date is too hard
-+-
 Reporter:  django@… |Owner:  aaugustin
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  lookup_type date |  Needs documentation:  0
  datetimefield compare comparison   |  Patch needs improvement:  1
  query_term field lookup|UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * owner:  nobody => aaugustin
 * 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/074.bc2b06248494a15be89d81c53ad4cdbb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #4070: unique_for_date and friends should create database indexes where possible

2014-08-31 Thread Django

#4070: unique_for_date and friends should create database indexes where possible
-+-
 Reporter:  sam@…|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 Since time zone support was added,
 [https://docs.djangoproject.com/en/stable/ref/models/fields/#unique-for-
 date the check is performed in the current time zone]. In general, it's
 impossible to make a database index change dynamically when the time zone
 changes in the application. If you have a more restricted use case, you
 can add the index with a migration.

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

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

Re: [Django] #2225: 'manage.py sql ...' gets confused when using tables from separate apps

2014-08-31 Thread Django

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

Comment:

I've looked at the patches proposed to fix this ticket. They are not
needed after the app-loading refactor. See
6b172a6d6dcfe88be4dc0e5052707a756c1c830c and follow-up commits that
touched `django/core/management/__init__.py`.

If you're still seeing this problem, please check that it happens with
Django 1.7 (RC3 at this time) and open a new ticket -- that will be more
convenient than reopening a 4 years old ticket. Thanks!

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

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

Re: [Django] #2495: db.models.TextField cannot be marked unique when using mysql backend

2014-08-31 Thread Django

#2495: db.models.TextField cannot be marked unique when using mysql backend
-+-
 Reporter:  anonymous|Owner:
 Type:  Bug  |  Honza_Kral
Component:  Database layer   |   Status:  new
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  mysql TextField  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 After eight years, and considering that the fix is far from easy, could we
 file this under "use a better database" and close the ticket?

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

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

Re: [Django] #23390: Clicking on the Add Group + in an Auth User's change-view results in a 400

2014-08-31 Thread Django

#23390: Clicking on the Add Group + in an Auth User's change-view results in a 
400
---+--
 Reporter:  yoyoma |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.admin  |  Version:  1.7-rc-3
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  auth,admin | 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
 * needs_better_patch:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Hi,

 The bug does appear on 1.7c3 but it's been fixed on the latest
 `stable/1.7.x` branch.

 Bisecting points to 3cbb7590cb0ece38f665b516db30cd5a9431f8c8 so it looks
 like this issue is a duplicate of #23329.

 If that's not the case, please reopen.

 Thanks.

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

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

Re: [Django] #19210: django.utils.timesince() does not account for leap years

2014-08-31 Thread Django

#19210: django.utils.timesince() does not account for leap years
---+
 Reporter:  jnns   |Owner:
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  date time  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by aaugustin):

 For what it's worth, I consider that timesince returns an order of
 magnitude for human consumption and a small inaccuracy isn't critical. I
 wouldn't mind if this ticket was closed as wontfix.

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

Re: [Django] #9699: Shouldn't entries be associated with many enclosures?

2014-08-31 Thread Django

#9699: Shouldn't entries be associated with many enclosures?
-+-
 Reporter:  directeur|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Utilities|  Version:  1.0
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  feedgenerator| Triage Stage:  Accepted
  enclosures |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 There has been very little interest for this ticket in the last 6 years
 and I'm not sure to understand what needs to be done to fix it.

 I'm not opposed to making changes, but if you want them, you'll have to
 write a patch, the reopen this ticket. Thanks!

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

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

Re: [Django] #22882: UnicodeDecodeError in command flush

2014-08-31 Thread Django

#22882: UnicodeDecodeError in command flush
-+-
 Reporter:  djbaldey |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.6
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  flush|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * component:  Uncategorized => Core (Management commands)


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

Re: [Django] #23380: Transient failure of admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey

2014-08-31 Thread Django

#23380: Transient failure of
admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey
---+
 Reporter:  charettes  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by aaugustin):

 * component:  Uncategorized => contrib.admin


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

[Django] #23390: Clicking on the Add Group + in an Auth User's change-view results in a 400

2014-08-31 Thread Django

#23390: Clicking on the Add Group + in an Auth User's change-view results in a 
400
---+
 Reporter:  yoyoma |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  contrib.admin  |Version:  1.7-rc-3
 Severity:  Normal |   Keywords:  auth,admin
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Using Django 1.7c3 with everything default on a brand new project, I
 visited a user's change-view in the admin, clicked the + next to Groups
 (since there are none by default), and was taken to the following URL in a
 popup window:
 http://127.0.0.1:8000/admin/auth/group/add/?_to_field=id&_popup=1. The {{{
 _to_field }}} param causes Django to return a {{{ Bad Request (400) }}}
 response.

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

Re: [Django] #6646: included template blocks are not being overridden by parent template.

2014-08-31 Thread Django

#6646: included template blocks are not being overridden by parent template.
-+-
 Reporter:  anonymous|Owner:
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  include, extends,| Triage Stage:  Accepted
  block  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 The [https://code.djangoproject.com/ticket/12008#comment:3 design decision
 on ticket 12008] states that blocks are evaluated before includes.

 As a consequence, the behavior should not be changed here.

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

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

Re: [Django] #8391: slugify template filter poorly encodes non-English strings

2014-08-31 Thread Django

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

Comment:

There's obviously more than one way to achieve slugification, depending on
your tastes and constraints.

If we try to be smart, we'll get dozens and dozens of tickets from people
who want to be smarter -- see the urlize filter for an example.

Django's implementation has the advantage of being simple and relying only
on the stdlib. Pretty good solutions are available externally.

The drawbacks of implementing something more complicated outweigh the
advantages at this stage.

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

Re: [Django] #14808: i18n is not safe.

2014-08-31 Thread Django

#14808: i18n is not safe.
---+
 Reporter:  steveire   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.2
 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):

 * component:  Template system => Documentation


Comment:

 I believe the only way forwards is to explain the current behavior and add
 warnings in the documentation.

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

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

Re: [Django] #22840: Use six.integer_types everywhere

2014-08-31 Thread Django

#22840: Use six.integer_types everywhere
-+-
 Reporter:  mjtamlyn |Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Python 2 |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by aaugustin):

 Like timo, I'm a skeptical about this change.

 If someone wants to audit each case and see if longs could cause an issue,
 why not.

 But if it was a common cause for bugs we would have heard about it before.

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

Re: [Django] #22879: Database errors coming from cursor iterator are not converted to Django database errors

2014-08-31 Thread Django

#22879: Database errors coming from cursor iterator are not converted to Django
database errors
-+-
 Reporter:  denisenkom@… |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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

Re: [Django] #20238: StoppableWSGIServer is not multithread support

2014-08-31 Thread Django

#20238: StoppableWSGIServer is not multithread support
---+--
 Reporter:  jwxiao@…   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.4
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 Considering that:

 - "the use case is somewhat fictional",
 - the ticket was reopened without any additional information,
 - more threading will certainly create more race conditions on shutdown,
 especially when it comes to the database connections — it's taken months
 to eliminate most from LiveServerTestCase, and I'm sure there are still
 some left,

 I don't think we should add threading without more compelling arguments.

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

Re: [Django] #23363: Field length in ORM

2014-08-31 Thread Django

#23363: Field length in ORM
-+-
 Reporter:  qurben   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  ORM, order_by,   |  Unreviewed
  QuerySet   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 Josh, I gather from your comment that this is covered by #14030, isn't it?

 If so, this ticket can be closed as a duplicate. If not, could you clarify
 what needs to be done to close it?

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

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

Re: [Django] #23371: Change the first day of the week to Monday for en_GB

2014-08-31 Thread Django

#23371: Change the first day of the week to Monday for en_GB
-+-
 Reporter:  duncanparkes |Owner:
 Type:  Bug  |  duncanparkes
Component:   |   Status:  assigned
  Internationalization   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  locale, en_GB| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * needs_docs:  0 => 1
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 Following the lead of Microsoft and Apple seems reasonable in this case.

 This change deserves a line in the release notes, doesn't it?

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

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

Re: [Django] #23389: overrideg to be able the checkbox widget in CheckboxSelectMultiple

2014-08-31 Thread Django

#23389: overrideg to be able the checkbox widget in CheckboxSelectMultiple
---+--
 Reporter:  brillgen   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Forms  |  Version:  1.6
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by claudep):

 * status:  new => closed
 * needs_better_patch:   => 0
 * component:  Uncategorized => Forms
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => needsinfo


Comment:

 Basically, if you need some special customization of
 `CheckboxSelectMultiple`, you should subclass the widget and try to
 override appropriate methods (maybe providing a custom renderer).

 If you have a specific use case which cannot be easily implemented by
 subclassing, please explain it in more details.

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

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

Re: [Django] #22734: Move SMTP / email settings to a dictionary

2014-08-31 Thread Django

Comment (by claudep):

>... that could just as easily be a new EMAIL_BACKEND_OPTIONS setting

Sure, as far as the default dictionary setting is empty in
global_settings.py, unless we would again be confronted to the same issue
of needing to redefine the entire dictionary to redefine only one key.

> Am I missing the benefits of doing this?

The main benefit is to have all logically-grouped settings in one
dictionary. And yes, there is some price to pay (cf. the django-developers
discussion: https://groups.google.com/d/msg/django-developers/t8ybImtdnpM
/esy-UDPTjoIJ).

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

Re: [Django] #22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url

2014-08-31 Thread Django

#22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url
---+-
 Reporter:  meenzam@…  |Owner:  ienzam
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Ready for checkin
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by claudep):

 Interesting case, but I think this should be a separate issue. This ticket
 is fixing the query string problem.

 Your example might be solved by short-circuiting the `unquote` part if the
 URL contains any non-safe character.

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

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

Re: [Django] #22920: AppConfig.create swallows informative exceptions during import time

2014-08-31 Thread Django

#22920: AppConfig.create swallows informative exceptions during import time
-+-
 Reporter:  bendavis78   |Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  AppConfig app-   | Triage Stage:  Accepted
  loading ImportError|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 I'm proposing a less invasive fix in
 [https://github.com/django/django/pull/3144 PR 3144].

 I've already rewritten that method entirely once to address issues I don't
 remember very well. I'd rather not restructure the logic drastically just
 to improve error reporting.

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

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

Re: [Django] #22770: Remove create_superuser from post_migrate signals

2014-08-31 Thread Django

#22770: Remove create_superuser from post_migrate signals
--+
 Reporter:  timo  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by yoyoma):

 I created https://github.com/django/django/pull/3143 to address the single
 remaining documentation straggler.

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

[django/django] 074b67: [1.7.x] Removed sentence from docs about migrate p...

2014-08-31 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 074b6785e09040eb6fd3b9bd3e4bf0cc6e1588f0
  
https://github.com/django/django/commit/074b6785e09040eb6fd3b9bd3e4bf0cc6e1588f0
  Author: Michael Angeletti 
  Date:   2014-08-31 (Sun, 31 Aug 2014)

  Changed paths:
M docs/topics/auth/index.txt

  Log Message:
  ---
  [1.7.x] Removed sentence from docs about migrate prompting to add a superuser.

Backport of 21a9e8adf0 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/54034e6bbd764_1f43fd9b393b29c4138d%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 21a9e8: Removed sentence from docs about migrate prompting...

2014-08-31 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 21a9e8adf06d5c132f5f0411fc6a89144363dbf8
  
https://github.com/django/django/commit/21a9e8adf06d5c132f5f0411fc6a89144363dbf8
  Author: Michael Angeletti 
  Date:   2014-08-31 (Sun, 31 Aug 2014)

  Changed paths:
M docs/topics/auth/index.txt

  Log Message:
  ---
  Removed sentence from docs about migrate prompting to add a superuser.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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/54034e1638588_645f3fb13cbbb2a063583%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23338: Warn when unique=True is set on ForeignKey

2014-08-31 Thread Django

#23338: Warn when unique=True is set on ForeignKey
--+
 Reporter:  funkybob  |Owner:  JLinden
 Type:  New feature   |   Status:  assigned
Component:  Core (System checks)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by JLinden):

 * owner:  nobody => JLinden
 * 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/066.6a61dd68580cf7cbb4b97908cc783420%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #3254: [patch] experimental fulltext search support for postgres, oracle and mssql

2014-08-31 Thread Django

#3254: [patch] experimental fulltext search support for postgres, oracle and 
mssql
-+-
 Reporter:  Ronny Pfannschmidt   |Owner:  mjtamlyn
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle fulltext  |  Needs documentation:  1
  search |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by MalikRumi):

 I was just reading in the documentation that full text search is only
 available for MySQL, and came over here to find out why. What can I do to
 help light a fire under this project?

 What are people doing in the meantime? Solr? Haystack?

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

[Django] #23389: overrideg to be able the checkbox widget in CheckboxSelectMultiple

2014-08-31 Thread Django

#23389: overrideg to be able the checkbox widget in CheckboxSelectMultiple
---+
 Reporter:  brillgen   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I'm using the CheckboxSelectMultiple form field but it does not have an
 option to be able to override the checkbox widget.

 Ideally the CheckboxSelectMultiple can just take a parameter for the
 actual widget instead of it being hard forced as:

 cb = CheckboxInput(final_attrs, check_test=lambda value: value in
 str_values)

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

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

Re: [Django] #23388: Allow the use of timezone.override as a decorator

2014-08-31 Thread Django

#23388: Allow the use of timezone.override as a decorator
-+-
 Reporter:  tchaumeny|Owner:  aaugustin
 Type:  New feature  |   Status:  closed
Component:  Utilities|  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 Aymeric Augustin ):

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


Comment:

 In [changeset:"032c091659666ea63f80f4c2d7f9b8bc72214f18"]:
 {{{
 #!CommitTicketReference repository=""
 revision="032c091659666ea63f80f4c2d7f9b8bc72214f18"
 Fixed #23388 -- Made django.utils.timezone.override usable as a decorator
 }}}

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

[django/django] 032c09: Fixed #23388 -- Made django.utils.timezone.overrid...

2014-08-31 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 032c091659666ea63f80f4c2d7f9b8bc72214f18
  
https://github.com/django/django/commit/032c091659666ea63f80f4c2d7f9b8bc72214f18
  Author: Thomas Chaumeny 
  Date:   2014-08-31 (Sun, 31 Aug 2014)

  Changed paths:
M django/utils/timezone.py
M docs/ref/utils.txt
M tests/utils_tests/test_timezone.py

  Log Message:
  ---
  Fixed #23388 -- Made django.utils.timezone.override usable as a decorator


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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/5402ca738da21_3d143fb2a478b2c0100228%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

43 matches

Mail list logo