date:20140731

Re: [Django] #23088: Paginator.page_range is of inconsistent type in Py2/Py3

2014-07-31 Thread Django

#23088: Paginator.page_range is of inconsistent type in Py2/Py3
-+-
 Reporter:  Keryn Knight |Owner:  mardini
   |   Status:  closed
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:  fixed
Component:  Core (Other) | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by CollinAnderson):

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

Re: [Django] #23088: Paginator.page_range is of inconsistent type in Py2/Py3

2014-07-31 Thread Django

#23088: Paginator.page_range is of inconsistent type in Py2/Py3
-+-
 Reporter:  Keryn Knight |Owner:  mardini
   |   Status:  closed
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:  fixed
Component:  Core (Other) | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by CollinAnderson):

 I've been relying on this being a list. #23140

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

[Django] #23141: Proposal new Django Admin css style

2014-07-31 Thread Django

#23141: Proposal new Django Admin css  style
---+
 Reporter:  avelino|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  1
---+
 Hey guys!

 Django admin has a few years, it works fine (meets the need) only need to
 evolve the style following the evolution of UX today!

 We have a plan for change?

 What do you think of this style
 https://github.com/hersonls/djamin#screenshots ? Is django admin html +
 custom 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/050.c83a8be800dea32877355b2db759dcec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23140: page_range TypeError: sequence index must be integer, not 'slice'

2014-07-31 Thread Django

#23140: page_range TypeError: sequence index must be integer, not 'slice'
+--
 Reporter:  CollinAnderson  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Uncategorized   |Version:  1.7-rc-2
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+--
 For years I've running `page.paginator.page_range[:]` to make a copy of
 page_range. After #23088, I'm getting the error above. It might just be
 I'm the only one who's doing this, and should instead just call
 `list(page.paginator.page_range)`, though it seems to me we list this in
 backwards incompatibilities and/or defer until 1.8.

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

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

2014-07-31 Thread Django

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

Comment (by djbaldey):

 UPD: in command dumpdata
 {{{
 djbaldey@p633m project $ ../manage.py dumpdata users
 [Traceback (most recent call last):
   File "../manage.py", line 60, in 
 execute_from_command_line(sys.argv)
   File "/home/djbaldey/env-django1.6/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 399, in
 execute_from_command_line
 utility.execute()
   File "/home/djbaldey/env-django1.6/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 392, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/djbaldey/env-django1.6/lib/python2.7/site-
 packages/django/core/management/base.py", line 249, in run_from_argv
 stderr.write('%s: %s' % (e.__class__.__name__, force_str(e)))
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 30:
 ordinal not in range(128)
 }}}

 Patch in django/core/management/commands/base.py:
 {{{
 from django.utils.encoding import force_str, smart_text
 ...

 stderr.write('%s: %s' % (e.__class__.__name__, smart_text(e)))
 ...
 }}}

 After:

 {{{
 djbaldey@p633m project $ ../manage.py dumpdata users
 CommandError: Unable to serialize database: ОШИБКА:  отношение
 "users_permission" не существует
 LINE 1: "built_type", "users_permission"."codename" FROM "users_per...
  ^
 }}}

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

Re: [Django] #23138: please add min_length to django.db.models.fields.Field

2014-07-31 Thread Django

#23138: please add min_length to django.db.models.fields.Field
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by charettes):

 I think only SQLite doesn't enforce them.

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

Re: [Django] #23061: Oracle SQL compiler adding outer pagination selects causing ORA-00907: missing right parenthesis when used with select_for_update.

2014-07-31 Thread Django

#23061: Oracle SQL compiler adding outer pagination selects causing ORA-00907:
missing right parenthesis when used with select_for_update.
-+-
 Reporter:  michael.miller@… |Owner:  shai
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.7-rc-1
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  oracle sql compiler  |  Needs documentation:  0
  ORA-00907  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by shai):

 Full test-suite passed on both master and 1.7 (trivial cherry-pick) on
 Oracle.

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

Re: [Django] #23138: please add min_length to django.db.models.fields.Field

2014-07-31 Thread Django

#23138: please add min_length to django.db.models.fields.Field
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by dnozay):

 do all of the core databases support maximum length validation?

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

Re: [Django] #16193: Use qunit to test javascript in django source

2014-07-31 Thread Django

#16193: Use qunit to test javascript in django source
-+-
 Reporter:  mbraak@… |Owner:  slurms
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  testing javascript   | Triage Stage:  Accepted
  qunit  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by slurms):

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

Re: [Django] #16193: Use qunit to test javascript in django source

2014-07-31 Thread Django

#16193: Use qunit to test javascript in django source
-+-
 Reporter:  mbraak@… |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  testing javascript   | Triage Stage:  Accepted
  qunit  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by slurms):

 Figure we just want *something* to unit test the django admin javascript
 as a first pass to fixing the more general problem. PR here:
 https://github.com/django/django/pull/3003. Needs more tests, and still 31
 jshint errors.

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

Re: [Django] #23061: Oracle SQL compiler adding outer pagination selects causing ORA-00907: missing right parenthesis when used with select_for_update.

2014-07-31 Thread Django

#23061: Oracle SQL compiler adding outer pagination selects causing ORA-00907:
missing right parenthesis when used with select_for_update.
-+-
 Reporter:  michael.miller@… |Owner:  shai
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.7-rc-1
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  oracle sql compiler  |  Needs documentation:  0
  ORA-00907  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by shai):

 * has_patch:  0 => 1


Comment:

 Tests are still running locally, but
 [https://github.com/django/django/pull/3002  PR 3002] is up for review
 (it's a small one, the main issues with it are whether the partial
 solution is acceptable and whether querying connection features in `get()`
 is kosher).

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

Re: [Django] #23130: BooleanField should either forbid setting 'choices' or not override 'blank'

2014-07-31 Thread Django

#23130: BooleanField should either forbid setting 'choices' or not override 
'blank'
-+-
 Reporter:  jonash   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jonash):

 Expected behavior when pressing "Save": The message "this field is
 required" should appear, since it hasn't been filled out. This doesn't
 work as expected because 'blank' is always set to True in the
 BooleanField's `__init__` method. This is because a blank/absent value
 means False if the BooleanField widget is a checkbox. But if rendered as a
 choices list, things change. See initial description for a more elaborate
 description of the issue.

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

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

Re: [Django] #23130: BooleanField should either forbid setting 'choices' or not override 'blank'

2014-07-31 Thread Django

#23130: BooleanField should either forbid setting 'choices' or not override 
'blank'
-+-
 Reporter:  jonash   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jonash):

 "initial-form.png" shows the admin form right before pressing "Save".
 "form-after-save.png" shows the data that was actually saved.

 "bug23139.tar.gz" contains the code to produce this form. It's no more
 than a single BooleanField with some 'choices'.

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

[django/django] a0bfe4: Replaced django-admin.py with django-admin in the ...

2014-07-31 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a0bfe4ea984fbf1720c24de42310c48b72f75f08
  
https://github.com/django/django/commit/a0bfe4ea984fbf1720c24de42310c48b72f75f08
  Author: Florian Apolloner 
  Date:   2014-07-31 (Thu, 31 Jul 2014)

  Changed paths:
M docs/man/django-admin.1

  Log Message:
  ---
  Replaced django-admin.py with django-admin in the man page.


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

Re: [Django] #23061: Oracle SQL compiler adding outer pagination selects causing ORA-00907: missing right parenthesis when used with select_for_update.

2014-07-31 Thread Django

#23061: Oracle SQL compiler adding outer pagination selects causing ORA-00907:
missing right parenthesis when used with select_for_update.
-+-
Reporter: michael.miller@… |Owner: shai
Type: Bug | Status: assigned
Component: Database layer | Version: 1.7-rc-1
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Accepted
Keywords: oracle sql compiler | Needs documentation: 0
ORA-00907 | Patch needs improvement: 0
Has patch: 0|UI/UX: 0
Needs tests: 0|
Easy pickings: 0|
-+-

Comment (by shai):

Hi all,

The issue is very hard to solve. The change that introduced this is
[da79ccca], a change to the `get()` function that made it return only up
to 20 records (rather than all of them) when the criteria are not specific
enough to select a single record. This was done, essentially, by adding
`[:20]` to the queryset being used for `get()`.

The issue is that, as far as I can tell, select-for-update and
limit/offset cannot be done together on Oracle without some deep changes
in the ORM; perhaps, generally, not even then.

Currently, On Oracle, the limit/offset is done by wrapping the original
query in an external query that selects all the original query fields and
adds a "row-number" fields, which can then be filtered on. `FOR UPDATE`
cannot be added in this setup -- current code adds it to the inner query,
which results in the reported error; I tried to put it on the external
one, and that results in "ORA-02014: cannot select FOR UPDATE from view
with DISTINCT, GROUP BY, etc."

Apparently, the ways to achieve limit/offset with select-for-update
involve either putting the row-number much deeper in the query (using a
windowing function, which requires a whole new treatment of the order-by
clause) or limiting the fetch rather than the select (which is generally
inappropriate, as the lock would still apply to the whole set, but is good
enough for the case of `get()`). See
http://stackoverflow.com/questions/6337126/oracle-for-update-select-
first-10-rows. Each of the answers for that question also has problems in
combination with other ORM features, like `select_related()`.

We could solve the current problem by just disabling the `[:20]` feature
on Oracle, at least when selecting for update (after all, this feature is
mostly useful in debugging, and so is secondary to making correct code
work). This will not solve the more general limit/offset issue, but may be
good enough for many users. I propose that we take this route for now, if
it is good enough for Michael.

PR forthcoming,

Shai.

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

Re: [Django] #23061: Oracle SQL compiler adding outer pagination selects causing ORA-00907: missing right parenthesis when used with select_for_update.

2014-07-31 Thread Django

Comment (by ramiro):

Replying to [comment:4 michael.miller@…]:
> I have tried this with Django 1.7rc2 and the problem still exists. I can
confirm that with Django 1.6.5 the problem does not happen.
>
> Thank you for accepting this, hopefully you can get to it before the
release of Django 1.7. This bug is a blocker for us as we use
select_for_update with a get as part of our concurrency control system.

Thanks for your report.

The hardware requirements, licensing woes, changing versions, and the
general difficulty in setting it up make a working Oracle development
environment a scarce resource.

Considering that from what you express this ticket has such a high impact
for you I'd like to ask you to test the following and report back with the
results:

1. Please verify if 1.6 is affected by the issue.
2. If it isn't then please apply bisection method using git between the
good version (the 1.6 git tag) and the closest bad one (e.g. the 1.7rc1
git tag). This should give you the ID of the commit where the regression
got introduced.

This information could greatly enhance the possibility of a solution being
found before 1.7 gets released.

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

Re: [Django] #22808: ModelMultipleChoiceField does not properly check if value is valid

2014-07-31 Thread Django

#22808: ModelMultipleChoiceField does not properly check if value is valid
-+-
 Reporter:  mattias.lindvall@…   |Owner:  nip3o
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  modelform, afraid-   | Triage Stage:  Accepted
  to-commit  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"cdc25ac4747bf5a6cdc2e70461c2d43c54529d35"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cdc25ac4747bf5a6cdc2e70461c2d43c54529d35"
 Fixed #22808 -- Made ModelMultipleChoiceField validation more robust to
 invalid data types..

 Thanks Mattias Lindvall for the report and inital 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/084.b60a66b53d3748cef2214e53df287adc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] cdc25a: Fixed #22808 -- Made ModelMultipleChoiceField vali...

2014-07-31 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cdc25ac4747bf5a6cdc2e70461c2d43c54529d35
  
https://github.com/django/django/commit/cdc25ac4747bf5a6cdc2e70461c2d43c54529d35
  Author: Niclas Olofsson 
  Date:   2014-07-31 (Thu, 31 Jul 2014)

  Changed paths:
M AUTHORS
M django/forms/models.py
M tests/model_forms/tests.py

  Log Message:
  ---
  Fixed #22808 -- Made ModelMultipleChoiceField validation more robust to 
invalid data types..

Thanks Mattias Lindvall for the report and inital patch.


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

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

2014-07-31 Thread Django

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

 * needs_better_patch:  1 => 0


Comment:

 Don't forget to uncheck "Patch needs improvement" so the ticket goes back
 in the review queue. I'll try to review and commit this soon, 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/066.9071f5be8777daae8cb8131557942c92%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12432: After setting encoding in view, request.REQUEST is not deleted

2014-07-31 Thread Django

#12432: After setting encoding in view, request.REQUEST is not deleted
-+-
 Reporter:  xiaket   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  encoding | Triage Stage:  Accepted
  request.REQUEST http   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 `request.REQUEST` is deprecated and will be removed in Django 1.9, so I
 think we can "won't fix" this.

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

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

Re: [Django] #22718: django.core.files.File doesn't handle certain file-like objects (e.g. zipfile.ZipExtFile)

2014-07-31 Thread Django

#22718: django.core.files.File doesn't handle certain file-like objects (e.g.
zipfile.ZipExtFile)
--+
 Reporter:  linkjuggler@… |Owner:  mshafiq9
 Type:  Bug   |   Status:  closed
Component:  File uploads/storage  |  Version:  1.6
 Severity:  Normal|   Resolution:  wontfix
 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):

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


Comment:

 Closing based on last two comments.

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

Re: [Django] #23075: Type-specific input fields cause cross-browser issues and wrong error messages

2014-07-31 Thread Django

#23075: Type-specific input fields cause cross-browser issues and wrong error
messages
-+
 Reporter:  sehmaschine  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by timo):

 Yes, just `EmailInput` and `URLInput` were added to the admin in 1.7.

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

Re: [Django] #23138: please add min_length to django.db.models.fields.Field

2014-07-31 Thread Django

#23138: please add min_length to django.db.models.fields.Field
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by timo):

 If we added `min_length` to model fields, I'd think it should be enforced
 at the database level. Do all of the core databases support minimum length
 validation? (my guess is no.) In that case, it may be better to solve your
 use case (Python level validation) by adding a `MinLengthValidator()` to
 your field.

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

Re: [Django] #12810: Add validation for clashing ManyToManyField.db_table names

2014-07-31 Thread Django

#12810: Add validation for clashing ManyToManyField.db_table names
-+-
 Reporter:  strelnikovdmitrij|Owner:
 Type:  Bug  |  christopherdcunha
Component:  Core (System |   Status:  assigned
  checks)|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  ManyToManyField  | 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):

 * needs_better_patch:  0 => 1


Comment:

 Tests do not run. Please uncheck "Patch needs improvement" when you update
 it, 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/075.a05a0a4a5621e15a8dca4187a94c45fd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19802: HttpResponse.set_cookie doesn't handle unicode data

2014-07-31 Thread Django

#19802: HttpResponse.set_cookie doesn't handle unicode data
---+
 Reporter:  django@…   |Owner:  qingfeng
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  cookie | 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):

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


Comment:

 I left comments for improvement on PR. Please uncheck "Patch needs
 improvement" when you update it, 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/082.639483723bba68596ccf4616bcb70fa3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #2443: Add IntervalField to database models

2014-07-31 Thread Django

#2443: Add IntervalField to database models
-+-
 Reporter:  ben.tucker@… |Owner:  mjtamlyn
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  IntervalField|  Needs documentation:  1
  interval duration DurationField|  Patch needs improvement:  1
  feature|UI/UX:  1
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_docs:  0 => 1
 * needs_tests:  1 => 0


Comment:

 [https://github.com/django/django/pull/2995 WIP] from Marc.

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

[django/django] e2c129: [1.7.x] Used JsonResponse in CBV examples.

2014-07-31 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: e2c129fa5bfcb761a075db8fcce05b26eb07072d
  
https://github.com/django/django/commit/e2c129fa5bfcb761a075db8fcce05b26eb07072d
  Author: Loic Bistuer 
  Date:   2014-07-31 (Thu, 31 Jul 2014)

  Changed paths:
M docs/topics/class-based-views/generic-editing.txt
M docs/topics/class-based-views/mixins.txt

  Log Message:
  ---
  [1.7.x] Used JsonResponse in CBV examples.

Thanks Hiroki Kiyohara and Tim Graham for the reviews.

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

[django/django] 757908: Used JsonResponse in CBV examples.

2014-07-31 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 75790808993691d2869db577df6db47ecbef6f5a
  
https://github.com/django/django/commit/75790808993691d2869db577df6db47ecbef6f5a
  Author: Loic Bistuer 
  Date:   2014-07-31 (Thu, 31 Jul 2014)

  Changed paths:
M docs/topics/class-based-views/generic-editing.txt
M docs/topics/class-based-views/mixins.txt

  Log Message:
  ---
  Used JsonResponse in CBV examples.

Thanks Hiroki Kiyohara and Tim Graham for the reviews.


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

[Django] #23139: mysql backend should use CHAR instead of VARCHAR if model has a CharField of fixed length.

2014-07-31 Thread Django

#23139: mysql backend should use CHAR instead of VARCHAR if model has a 
CharField
of fixed length.
--+
 Reporter:  dnozay|  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 see as well https://code.djangoproject.com/ticket/23138 which asks for
 min_length to be added to `models.fields.Field`.

 For optimization purposes, if I have a model that wants exactly N
 characters for a field, then `CHAR` uses less bytes than `VARCHAR`.
 One way to detect that intent is if you have `CharField(min_length=N,
 max_length=N)` -- in other words `min_length == max_length`.

 common example: a hash always has the same length (always?).

 https://github.com/django/django/pull/2921

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

[django/django] 76f2f5: Fixed #22956 -- Made PermissionManager.get_by_natu...

2014-07-31 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 76f2f58a1853fd7a774f3df3fe454022a0206ff9
  
https://github.com/django/django/commit/76f2f58a1853fd7a774f3df3fe454022a0206ff9
  Author: Jürno Ader 
  Date:   2014-07-31 (Thu, 31 Jul 2014)

  Changed paths:
M django/contrib/auth/models.py
M django/contrib/auth/tests/test_models.py

  Log Message:
  ---
  Fixed #22956 -- Made PermissionManager.get_by_natural_key() use the correct 
database for content type lookup.


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

Re: [Django] #22956: PermissionManager.get_by_natural_key doesn't fetch ContentType from same DB

2014-07-31 Thread Django

#22956: PermissionManager.get_by_natural_key doesn't fetch ContentType from 
same DB
-+-
 Reporter:  jyrno@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  auth contenttype | Triage Stage:  Accepted
  natural_keys user permissions  |  Needs documentation:  0
  natural keys multiple databases|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"76f2f58a1853fd7a774f3df3fe454022a0206ff9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="76f2f58a1853fd7a774f3df3fe454022a0206ff9"
 Fixed #22956 -- Made PermissionManager.get_by_natural_key() use the
 correct database for content type lookup.
 }}}

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

Re: [Django] #23138: please add min_length to django.db.models.fields.Field

2014-07-31 Thread Django

#23138: please add min_length to django.db.models.fields.Field
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by dnozay):

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


Comment:

 edge case: `syncdb` command can inspect the fields and see that
 `min_length`== `max_length` and mysql backend could use `CHAR(N)` instead
 of `VARCHAR(N)` which results in less bytes being consumed, which could be
 important savings with lots of records.


 see https://github.com/django/django/pull/2921.

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

[Django] #23138: please add min_length to django.db.models.fields.Field

2014-07-31 Thread Django

#23138: please add min_length to django.db.models.fields.Field
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Use case is that an application may have requirements for a `CharField` to
 always have a minimum of N characters (e.g. git commit sha1 needs
 40characters); but the application may not use forms. Validators for
 `min_length` and `max_length` could move from the forms.fields to
 models.fields.

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

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

[django/django] faff72: [1.6.x] Updated timezone docs to use timezone.now(...

2014-07-31 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: faff723770adddf3d093291e51cada3a6ef16223
  
https://github.com/django/django/commit/faff723770adddf3d093291e51cada3a6ef16223
  Author: Tim Graham 
  Date:   2014-07-31 (Thu, 31 Jul 2014)

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

  Log Message:
  ---
  [1.6.x] Updated timezone docs to use timezone.now()

Thanks James Cleveland for the report and Aymeric for suggesting
the solution.

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

[django/django] 42bb04: [1.7.x] Updated timezone docs to use timezone.now(...

2014-07-31 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 42bb047d33afc2bc6205a2d9ffc24aeec626ce7f
  
https://github.com/django/django/commit/42bb047d33afc2bc6205a2d9ffc24aeec626ce7f
  Author: Tim Graham 
  Date:   2014-07-31 (Thu, 31 Jul 2014)

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

  Log Message:
  ---
  [1.7.x] Updated timezone docs to use timezone.now()

Thanks James Cleveland for the report and Aymeric for suggesting
the solution.

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

[django/django] da5990: Updated timezone docs to use timezone.now()

2014-07-31 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: da599022504995891bf745a6424e242ca9097b07
  
https://github.com/django/django/commit/da599022504995891bf745a6424e242ca9097b07
  Author: Tim Graham 
  Date:   2014-07-31 (Thu, 31 Jul 2014)

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

  Log Message:
  ---
  Updated timezone docs to use timezone.now()

Thanks James Cleveland for the report and Aymeric for suggesting
the solution.


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

Re: [Django] #22434: Ordering is cleared in Subqueries with limits

2014-07-31 Thread Django

#22434: Ordering is cleared in Subqueries with limits
-+-
 Reporter:  maciej.pawlisz@… |Owner:
 Type:  Bug  |  justhamade
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 If the tests that were added here pass on 1.4 we can do the backport. The
 backport isn't clean though, could you send a PR along with an added
 mention in the 1.6.6 release notes?

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

Re: [Django] #22434: Ordering is cleared in Subqueries with limits

2014-07-31 Thread Django

#22434: Ordering is cleared in Subqueries with limits
-+-
 Reporter:  maciej.pawlisz@… |Owner:
 Type:  Bug  |  justhamade
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by giovannibajo):

 This bug represents a regression; we just upgraded to from Django 1.4 to
 Django 1.6, we hit this bug, and we had to manually apply the patch to fix
 it; is there any plan to apply the patch to the 1.6 serie?

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

[django/django] 063e7e: [1.7.x] Fixed flake8 warnings.

2014-07-31 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 063e7e56bcd34d76e9072ebfa3b9f1d9679dc6e9
  
https://github.com/django/django/commit/063e7e56bcd34d76e9072ebfa3b9f1d9679dc6e9
  Author: Tim Graham 
  Date:   2014-07-31 (Thu, 31 Jul 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M tests/model_fields/models.py

  Log Message:
  ---
  [1.7.x] Fixed flake8 warnings.

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

Re: [Django] #16383: More specific errors when resolving template Variables

2014-07-31 Thread Django

#16383: More specific errors when resolving template Variables
-+-
 Reporter:  maraujop |Owner:
 Type:  New feature  |  anubhav9042
Component:  Template system  |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:  _resolve_lookup, |   Resolution:  fixed
  resolve, template, variable,   | Triage Stage:  Accepted
  exception  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"0dd05c9e66ebb5cb97136f84373f43582783e1a6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0dd05c9e66ebb5cb97136f84373f43582783e1a6"
 Fixed #16383 -- Raised the AttributeError raised in property of an object
 when used in a template.

 Thanks maraujop for the report and Hiroki and Tim Graham for 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/066.ac5dc07913c4f4960602de96e5483f4f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 0dd05c: Fixed #16383 -- Raised the AttributeError raised i...

2014-07-31 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0dd05c9e66ebb5cb97136f84373f43582783e1a6
  
https://github.com/django/django/commit/0dd05c9e66ebb5cb97136f84373f43582783e1a6
  Author: Anubhav Joshi 
  Date:   2014-07-31 (Thu, 31 Jul 2014)

  Changed paths:
M django/template/base.py
M tests/template_tests/tests.py

  Log Message:
  ---
  Fixed #16383 -- Raised the AttributeError raised in property of an object 
when used in a template.

Thanks maraujop for the report and Hiroki and Tim Graham for 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/53da42e86fa74_6adcb49d44839bd%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #7220: django.contrib.auth.models.AbstractBaseUser.last_login should allow null=True

2014-07-31 Thread Django

#7220: django.contrib.auth.models.AbstractBaseUser.last_login should allow
null=True
-+-
 Reporter:  veena|Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  contrib.auth |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  schemamigration  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by timo):

 I removed the data migration and added a mention in the release notes. It
 seems safer and is less code for us to maintain.

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

Re: [Django] #13163: Display link to change-form on inlines where model is registered in admin site

2014-07-31 Thread Django

#13163: Display link to change-form on inlines where model is registered in 
admin
site
---+
 Reporter:  DrMeers|Owner:  DrMeers
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  inline link| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"9d9f0acd7e245c9f9c30727a00318754c924"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9d9f0acd7e245c9f9c30727a00318754c924"
 Fixed #13163 -- Added ability to show change links on inline objects in
 admin.

 Thanks DrMeers for the suggestion.
 }}}

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

[django/django] 9d9f0a: Fixed #13163 -- Added ability to show change links...

2014-07-31 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9d9f0acd7e245c9f9c30727a00318754c924
  
https://github.com/django/django/commit/9d9f0acd7e245c9f9c30727a00318754c924
  Author: Nick Sandford 
  Date:   2014-07-31 (Thu, 31 Jul 2014)

  Changed paths:
M django/contrib/admin/options.py
M django/contrib/admin/sites.py
M django/contrib/admin/static/admin/css/base.css
M django/contrib/admin/templates/admin/edit_inline/stacked.html
M django/contrib/admin/templates/admin/edit_inline/tabular.html
M docs/ref/contrib/admin/index.txt
M docs/releases/1.8.txt
M tests/admin_inlines/admin.py
M tests/admin_inlines/tests.py
M tests/admin_ordering/tests.py
M tests/admin_registration/tests.py
M tests/generic_inline_admin/tests.py

  Log Message:
  ---
  Fixed #13163 -- Added ability to show change links on inline objects in admin.

Thanks DrMeers for the suggestion.


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

[django/django] 9a922d: Fixed flake8 warnings.

2014-07-31 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9a922dcad1e50afc91329009e8689e5c08c2a1bf
  
https://github.com/django/django/commit/9a922dcad1e50afc91329009e8689e5c08c2a1bf
  Author: Tim Graham 
  Date:   2014-07-31 (Thu, 31 Jul 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M tests/model_fields/models.py

  Log Message:
  ---
  Fixed flake8 warnings.


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

Re: [Django] #23061: Oracle SQL compiler adding outer pagination selects causing ORA-00907: missing right parenthesis when used with select_for_update.

2014-07-31 Thread Django

#23061: Oracle SQL compiler adding outer pagination selects causing ORA-00907:
missing right parenthesis when used with select_for_update.
-+-
 Reporter:  michael.miller@… |Owner:  shai
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.7-rc-1
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  oracle sql compiler  |  Needs documentation:  0
  ORA-00907  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * severity:  Normal => Release blocker


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

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

[Django] #23137: Error when use OSMapWidget.js

2014-07-31 Thread Django

#23137: Error when use OSMapWidget.js
+
 Reporter:  koyoyo  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  GIS |Version:  1.6
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I try to create my form with GeoDjango and I didn't found an good example
 in document.

 So, I use django/contrib/gis/static/gis/js/OSMapWidget.js and found that
 have some of bugs.

 First, in line 173 (miss .) eg. if geom_name = 'MultiPoint', then
 options['geom_type'] will be '''OpenLayers.GeometryMultiPoint'''

 {{{
 else options['geom_type'] = eval('OpenLayers.Geometry' +
 options['geom_name']);
 }}}

 changed to

 {{{
 else options['geom_type'] = eval('OpenLayers.Geometry.' +
 options['geom_name']);
 }}}

 Second, line 181 (check is_collection) It is wrong use of function
 "isinstanceof". It cannot check constructor isinstanceof constructor.

 {{{
 is_collection: options['geom_name'] instanceof
 OpenLayers.Geometry.Collection,
 }}}

 changed to

 {{{
 is_collection: (options['geom_name'].substr(0, 5) == 'Multi' || options[
 'geom_type' ] == 'GeometryCollection'),
 }}}

 Third,  in function getControls (line 366, 369, 372) These are not check
 for Collection.

 {{{
 if (this.options.geom_name == 'LineString'' || this.options.geom_name ==
 'Unknown') {
 if (this.options.geom_name == 'Polygon'  || this.options.geom_name ==
 'Unknown') {
 if (this.options.geom_name == 'Point'  || this.options.geom_name ==
 'Unknown') {
 }}}

 changed to

 {{{
 if (this.options.geom_name == 'LineString' || this.options.geom_name ==
 'MultiLineString' || this.options.geom_name == 'Unknown') {
 if (this.options.geom_name == 'Polygon' || this.options.geom_name ==
 'MultiPolygon' || this.options.geom_name == 'Unknown') {
 if (this.options.geom_name == 'Point' || this.options.geom_name ==
 'MultiPoint' || this.options.geom_name == 'Unknown') {
 }}}

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

47 matches

Mail list logo