date:20140812

[Django] #23279: REFERENCES constraints are not set to the fileds in an intermediate table created by syncdb for SQLite3

2014-08-12 Thread Django

#23279: REFERENCES constraints are not set to the fileds in an intermediate 
table
created by syncdb for SQLite3
---+---
 Reporter:  Annadel|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  syncdb manytomany
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 If I have the following class definition:

 class Foo(models.Model):
 bars = models.ManyToManyField('Bar')
 class Meta:
 db_table = 'foo'

 class Bar(models.Model):
 class Meta:
 db_table = 'bar'

 Then, syncdb will create in SQLite3 the following intermediate table. Note
 that there is no REFERENCES constrains defined.

 CREATE TABLE "foo_bars" (
 "id" integer NOT NULL PRIMARY KEY,
 "foo_id" integer NOT NULL,
 "bar_id" integer NOT NULL,
 UNIQUE ("foo_id", "bar_id")
 )
 CREATE INDEX "foo_bars_e69b476d" ON "foo_bars" ("bar_id");
 CREATE INDEX "foo_bars_ef315d12" ON "foo_bars" ("foo_id")

 If I define ManyToManyField in Bar class as opposed to Foo class, such as

 class Foo(models.Model):
 class Meta:
 db_table = 'foo'

 class Bar(models.Model):
 foos = models.ManyToManyField(Foo)
 class Meta:
 db_table = 'bar'

 Then, the intermediate table becomes:

 CREATE TABLE "bar_foos" (
 "id" integer NOT NULL PRIMARY KEY,
 "bar_id" integer NOT NULL,
 "foo_id" integer NOT NULL REFERENCES "foo" ("id"),
 UNIQUE ("bar_id", "foo_id")
 )
 CREATE INDEX "bar_foos_e69b476d" ON "foo_bars" ("bar_id");
 CREATE INDEX "bar_foos_ef315d12" ON "foo_bars" ("foo_id")

 Now only foo_id has REFERENCES constraint.

 If I choose MySQL instead of SQLite3, syncdb creates REFERENCE constrains
 for both foo_id and bar_id, as follows:

 CREATE TABLE `bar_foos` (
   `id` int(11) NOT NULL AUTO_INCREMENT,
   `bar_id` int(11) NOT NULL,
   `foo_id` int(11) NOT NULL,
   PRIMARY KEY (`id`),
   UNIQUE KEY `bar_id` (`bar_id`,`foo_id`),
   KEY `bar_foos_e69b476d` (`bar_id`),
   KEY `bar_foos_ef315d12` (`foo_id`),
   CONSTRAINT `bar_id_refs_id_9d8d0296` FOREIGN KEY (`bar_id`) REFERENCES
 `bar` (`id`),
   CONSTRAINT `foo_id_refs_id_27f38014` FOREIGN KEY (`foo_id`) REFERENCES
 `foo` (`id`)
 ) ENGINE=InnoDB

 So, there seems an issue when syncdb creates an intermediate table derived
 from ManyToManyField for SQLite3.

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

Re: [Django] #23277: set good url examples in 1.7

2014-08-12 Thread Django

Comment (by mlavin):

I don't have a strong objection to the doc changes. I don't find the
inconsistency that hard to grasp and I'm not sure most readers will even
notice it. But I'm also not new to Django and I'm aware of the change in
1.8 which is not true for many readers. At the same time, I don't think
there is a need to future-proof the 1.7 docs for upcoming changes. Users
will have two release cycles to adjust to the change once 1.8 is released.
If there is a question I would also error on the side of conservative
changes to 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/072.38080269d8c8d37cf311b79e02593bd3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23277: set good url examples in 1.7

2014-08-12 Thread Django

Comment (by carljm):

Yeah, I can see that too. Probably clearest and simplest to just leave 1.7
alone, so that the deprecation, startproject, and all the docs change with
the same release. It's a nice idea to give people an extra release "jump"
on this particular deprecation timeline, but I don't think it's worth the
extra fuss of having to explain to people "well, this is the new preferred
way, used throughout the 1.7 docs, but startproject doesn't use it yet
until 1.8". This is not a difficult deprecation to adjust to, projects
started under 1.7 (and people referring to the 1.7 docs) will be fine,
just like all the people with projects started in every earlier version of
Django.

If you prefer to go ahead with the docs changes, I don't think the
inconsistency would be a huge deal either. But I'd lean towards leaving
1.7 alone.

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

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

Re: [Django] #23277: set good url examples in 1.7

2014-08-12 Thread Django

#23277: set good url examples in 1.7
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.7-rc-2
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by timgraham):

 Okay, how do you guys feel about the rest of the doc changes then? I guess
 it could be confusing for newbies if they see `patterns()` in their new
 project but no where else.

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

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

[django/django] d38a00: Updated tests for added newlines in 68686430638215...

2014-08-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d38a00332ed012b889cce00d8ea51da728023ead
  
https://github.com/django/django/commit/d38a00332ed012b889cce00d8ea51da728023ead
  Author: Tim Graham 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

  Changed paths:
M tests/generic_views/test_dates.py
M tests/staticfiles_tests/tests.py
M tests/syndication_tests/tests.py
M tests/template_tests/test_loaders.py

  Log Message:
  ---
  Updated tests for added newlines in 68686430638215b5405b20bd767c0be392c9221d.


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

Re: [Django] #23277: set good url examples in 1.7

2014-08-12 Thread Django

Comment (by carljm):

FWIW, I think mlavin is correct here; we need far better reasons than this
to violate the promises made in our release-process docs. Someone who has
already published a book about Django 1.7 based on the behavior of a
release-candidate is not doing anything wrong; they are simply relying on
the commitments we've made. That's why those commitments exist. Advance
publishing is good for us and for the community; it means that
Django-1.7-targetted resources can be available the moment 1.7 final comes
out. It would be bad behavior on our part to violate our documented
process and render the book apparently obsolete/wrong in the eyes of its
readers.

I don't think there is any need for an added "remove this" step in the
tutorial creating an "awkward moment" in the docs. Let the deprecation
timeline work normally. {{{patterns}}} is not deprecated yet in Django
1.7, and that's fine.

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

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

Re: [Django] #23277: set good url examples in 1.7

2014-08-12 Thread Django

#23277: set good url examples in 1.7
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.7-rc-2
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by mlavin):

 Django has a working deprecation timeline. Using {{{patterns}}} with 1.7
 will not cause any unexpected behavior or raise any level of deprecation
 warning. The same is true for 1.6, 1.5, 1.4 and so on. It is completely
 acceptable usage. Starting with 1.8 {{{patterns}}} will be deprecated and
 that cruft will be removed in due time. I'm happy to see it go and
 thankful for your work in helping remove it but there is no need to rush
 the process here.

 The people helped by this change are those who start a project on 1.7,
 don't read the release notes or deprecation warnings for the next 2-3
 years, and are bitten by the removal of {{{patterns}}} when they try to
 upgrade to 2.0. I personally have very little sympathy for 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/072.001c28ed15dc20d0178d1ac971c67271%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23250: Improve Error Message / Handling for ModelMultipleChoiceField and queryset attribute

2014-08-12 Thread Django

#23250: Improve Error Message / Handling for ModelMultipleChoiceField and 
queryset
attribute
--+
 Reporter:  wraus |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * component:  Forms => Documentation
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I have used this pattern before as well, however, I think it would be best
 to document that `queryset` may be `None` if you want to specify it later.
 Making it optional seems likely to trip up newbies.

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

Re: [Django] #23182: squashmigrations having trouble with auth.User foreign key

2014-08-12 Thread Django

#23182: squashmigrations having trouble with auth.User foreign key
-+-
 Reporter:  wkschwartz@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  migrations,  | Triage Stage:
  squashmigrations   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Please reopen if you can provide additional 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/078.8ea948c3ba1600ca50e31e2cf945a950%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23236: forms.Form should support a Meta class like forms.ModelForm

2014-08-12 Thread Django

#23236: forms.Form should support a Meta class like forms.ModelForm
-+--
 Reporter:  django@… |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 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 timgraham):

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

[django/django] 686864: Added newlines to the ends of CSS, HTML, and JavaS...

2014-08-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 68686430638215b5405b20bd767c0be392c9221d
  
https://github.com/django/django/commit/68686430638215b5405b20bd767c0be392c9221d
  Author: Trey Hunner 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

  Changed paths:
M django/contrib/admin/static/admin/css/ie.css
M django/contrib/admin/static/admin/css/rtl.css
M django/contrib/auth/tests/templates/registration/logged_out.html
M django/contrib/auth/tests/templates/registration/login.html
M django/contrib/auth/tests/templates/registration/password_change_form.html
M 
django/contrib/auth/tests/templates/registration/password_reset_complete.html
M django/contrib/auth/tests/templates/registration/password_reset_done.html
M django/contrib/auth/tests/templates/registration/password_reset_form.html
M django/contrib/flatpages/tests/templates/404.html
M django/contrib/formtools/tests/templates/base.html
M django/contrib/gis/templates/gis/admin/osm.html
M django/contrib/gis/templates/gis/google/google-multi.js
M django/contrib/gis/templates/gis/google/google-single.js
M docs/_theme/djangodocs/genindex.html
M docs/_theme/djangodocs/layout.html
M docs/_theme/djangodocs/modindex.html
M docs/_theme/djangodocs/search.html
M docs/_theme/djangodocs/static/default.css
M docs/_theme/djangodocs/static/homepage.css
M tests/generic_views/templates/generic_views/apple_detail.html
M tests/generic_views/templates/generic_views/artist_detail.html
M tests/generic_views/templates/generic_views/artist_form.html
M tests/generic_views/templates/generic_views/author_confirm_delete.html
M tests/generic_views/templates/generic_views/author_detail.html
M tests/generic_views/templates/generic_views/author_form.html
M tests/generic_views/templates/generic_views/author_list.html
M tests/generic_views/templates/generic_views/author_objects.html
M tests/generic_views/templates/generic_views/author_view.html
M tests/generic_views/templates/generic_views/book_archive_day.html
M tests/generic_views/templates/generic_views/book_archive_month.html
M tests/generic_views/templates/generic_views/book_archive_week.html
M tests/generic_views/templates/generic_views/book_detail.html
M tests/generic_views/templates/generic_views/book_list.html
M tests/generic_views/templates/generic_views/confirm_delete.html
M tests/generic_views/templates/generic_views/detail.html
M tests/generic_views/templates/generic_views/form.html
M tests/generic_views/templates/generic_views/list.html
M tests/generic_views/templates/generic_views/page_template.html
M tests/generic_views/templates/registration/login.html
M tests/staticfiles_tests/project/documents/cached/absolute.css
M tests/staticfiles_tests/project/documents/cached/css/window.css
M tests/staticfiles_tests/project/documents/cached/relative.css
M tests/staticfiles_tests/project/documents/cached/styles.css
M tests/staticfiles_tests/project/documents/cached/styles_insensitive.css
M tests/staticfiles_tests/project/documents/cached/url.css
M tests/syndication_tests/templates/syndication/description.html
M tests/syndication_tests/templates/syndication/description_context.html
M tests/syndication_tests/templates/syndication/title.html
M tests/syndication_tests/templates/syndication/title_context.html
M tests/template_tests/templates/test_context.html
M tests/template_tests/templates/test_include_error.html
M tests/templates/base.html
M tests/templates/extended.html
M tests/templates/form_view.html
M tests/templates/login.html
M tests/templates/views/article_archive_month.html
M tests/templates/views/article_confirm_delete.html
M tests/templates/views/article_list.html
M tests/templates/views/datearticle_archive_month.html

  Log Message:
  ---
  Added newlines to the ends of CSS, HTML, and JavaScript files missing them.


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

Re: [Django] #23277: set good url examples in 1.7

2014-08-12 Thread Django

Comment (by timgraham):

Yes, I am torn between making this change and obsoleting some print books
that have sold before Django 1.7 is finalized and the benefit that
everyone who starts a project in the next 9-12 months will reap with
respect to not having to eventually remove deprecated behavior from their
projects. In doubt, I guess we should stick with our official policy and
not make the change in the template. Assuming we don't make the change, we
could add a step to the tutorial telling users how to remove the
deprecated behavior. Of course, I am biased to the path that doesn't lead
to this awkward moment in the Django docs.

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

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

Re: [Django] #23265: runserver crashes with some locales on Python 2 (was: Django don't start on French Windows with Python 2.7 (but only in February, August and December!))

2014-08-12 Thread Django

#23265: runserver crashes with some locales on Python 2
-+-
 Reporter:  SpaceFox |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.6
  commands)  |   Resolution:
 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 timgraham):

 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


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

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

[Django] #23278: django.db.backends.schema logger isn't documented

2014-08-12 Thread Django

#23278: django.db.backends.schema logger isn't documented
+--
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  1.7-rc-2
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+--
 It should be added to the list in docs/topics/logging.txt.

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

Re: [Django] #23277: set good url examples in 1.7

2014-08-12 Thread Django

#23277: set good url examples in 1.7
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.7-rc-2
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by mlavin):

 For example "Test-Driven Web Development with Python" has sold printed
 copied stating that the generated {{{urls.py}}} will use {{{patterns}}}
 Django 1.7
 http://chimera.labs.oreilly.com/books/123400754/ch03.html#_urls_py The
 online version can be updated but those already printed cannot. Technical
 authors understand that their books will become out of date very quickly
 but Harry has worked too hard and his book helps this community too much
 to deserve this change.

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

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

Re: [Django] #23271: Makemessages can corrupt existing .po files on Windows

2014-08-12 Thread Django

#23271: Makemessages can corrupt existing .po files on Windows
-+-
 Reporter:  danielmenzel |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  master
  Internationalization   |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  makemessages utf8|  Needs documentation:  0
  unicode|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

 * version:  1.7-rc-2 => master


Comment:

 [cdfefbec721b59695e28] has been reverted on the 1.7.x branch. I've applied
 [67870137b9e1f1] instead to fix #22686, but I'd like to keep the more
 extensive fix on master. The release blocking flag is now only applicable
 to 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/070.14755bede2a76c62a758cc2330282c0d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] e705d8: [1.7.x] Revert "Applied unicode_literals to makeme...

2014-08-12 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: e705d8c4b49d5c5ee747075f12709011f55b7a8a
  
https://github.com/django/django/commit/e705d8c4b49d5c5ee747075f12709011f55b7a8a
  Author: Claude Paroz 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

  Changed paths:
M django/core/management/commands/makemessages.py
M django/utils/translation/trans_real.py

  Log Message:
  ---
  [1.7.x] Revert "Applied unicode_literals to makemessages command"

This reverts commit cdfefbec7 as it caused a regression (#23271).


  Commit: 67870137b9e1f1384af7465b4eb978d0f4dab3b7
  
https://github.com/django/django/commit/67870137b9e1f1384af7465b4eb978d0f4dab3b7
  Author: Claude Paroz 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

  Changed paths:
M django/core/management/commands/makemessages.py

  Log Message:
  ---
  [1.7.x] Fixed #22686 -- Prevented makemessages crash with unicode filename

A more extensive fix has been reverted on the 1.7.x branch, so this
minimal fix replaces it.


Compare: https://github.com/django/django/compare/72fdd62e93cf...67870137b9e1

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

Re: [Django] #23277: set good url examples in 1.7

2014-08-12 Thread Django

#23277: set good url examples in 1.7
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.7-rc-2
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by mlavin):

 Some people in the community (including myself) are working on tutorials,
 books and other resources targeting 1.7 and deserve the stability
 guaranteed by the release process docs to create those materials.
 https://docs.djangoproject.com/en/1.7/internals/release-process/#phase-
 three-bugfixes states

 > After the release candidate, only release blockers and documentation
 fixes should be backported.

 But this exceeds a documentation change.

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

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

Re: [Django] #22686: makemessages crashes with unicode filename and verbose > 1

2014-08-12 Thread Django

#22686: makemessages crashes with unicode filename and verbose > 1
--+
 Reporter:  arthurk   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Internationalization  |  Version:  1.6
 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 Claude Paroz ):

 In [changeset:"67870137b9e1f1384af7465b4eb978d0f4dab3b7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="67870137b9e1f1384af7465b4eb978d0f4dab3b7"
 [1.7.x] Fixed #22686 -- Prevented makemessages crash with unicode filename

 A more extensive fix has been reverted on the 1.7.x branch, so this
 minimal fix replaces 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/065.3cf930768beb00f5291930cd18c808ad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23277: set good url examples in 1.7 (was: Backport patterns() documentation changes to 1.7)

2014-08-12 Thread Django

#23277: set good url examples in 1.7
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.7-rc-2
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  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/072.28997579e863ebc98d7eef9f4c7d9da3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23277: Backport patterns() documentation changes to 1.7

2014-08-12 Thread Django

#23277: Backport patterns() documentation changes to 1.7
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.7-rc-2
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by collinanderson):

 * component:  Documentation => 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/072.ef1d49bf7cea8cdb893502ccc39492e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23277: Backport patterns() documentation changes to 1.7

2014-08-12 Thread Django

#23277: Backport patterns() documentation changes to 1.7
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.7-rc-2
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by collinanderson):

 I also am personally a little hesitant with removing `patterns()` from
 project_template this late in the game, but in theory, it's just for new
 projects. I'm hoping that the next 9-12 months worth of `manage.py
 startproject` will be happy that this change was made.

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

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

Re: [Django] #23277: Backport patterns() documentation changes to 1.7

2014-08-12 Thread Django

#23277: Backport patterns() documentation changes to 1.7
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.7-rc-2
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 Mark, could you elaborate on your concerns as to the negative consequences
 changing the project template would have? It would be nice to propagate
 best practices for everyone starting a new project, but you can convince
 me otherwise.

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

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

Re: [Django] #23277: Backport patterns() documentation changes to 1.7

2014-08-12 Thread Django

#23277: Backport patterns() documentation changes to 1.7
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.7-rc-2
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by mlavin):

 Please don't change the output of {{{startproject}}} this late in the
 release cycle.

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

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

Re: [Django] #23277: Backport patterns() documentation changes to 1.7

2014-08-12 Thread Django

#23277: Backport patterns() documentation changes to 1.7
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.7-rc-2
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by collinanderson):

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


Comment:

 This also changes the url.py created by `startproject`.
 https://github.com/django/django/pull/3051

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

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

[Django] #23277: Backport patterns() documentation changes to 1.7

2014-08-12 Thread Django

#23277: Backport patterns() documentation changes to 1.7
--+--
 Reporter:  collinanderson|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.7-rc-2
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+--
 #22218 deprecated patterns in 1.8, though I think it would be good to at
 least set a good example in the 1.7 documentation. See also #23276

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

Re: [Django] #23262: FilteredSelectMultiple SelectFilter2.js don't submit form if user pressed Enter

2014-08-12 Thread Django

#23262: FilteredSelectMultiple SelectFilter2.js don't submit form if user 
pressed
Enter
+--
 Reporter:  CollinAnderson  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"85c22dd4c4a406301b4378a4682456dfa1900830"]:
 {{{
 #!CommitTicketReference repository=""
 revision="85c22dd4c4a406301b4378a4682456dfa1900830"
 Fixed #23262 -- Made SelectFilter2.js move items on enter Key press.
 }}}

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

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

[django/django] 85c22d: Fixed #23262 -- Made SelectFilter2.js move items o...

2014-08-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 85c22dd4c4a406301b4378a4682456dfa1900830
  
https://github.com/django/django/commit/85c22dd4c4a406301b4378a4682456dfa1900830
  Author: Collin Anderson 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

  Changed paths:
M django/contrib/admin/static/admin/js/SelectFilter2.js
M tests/admin_widgets/tests.py

  Log Message:
  ---
  Fixed #23262 -- Made SelectFilter2.js move items on enter Key press.


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

Re: [Django] #22985: call_command() ignores dest from make_option() and uses kwarg name instead

2014-08-12 Thread Django

#22985: call_command() ignores dest from make_option() and uses kwarg name 
instead
-+-
 Reporter:  giuliettamasina  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"2cc8ffe258008096a70791115b2daa12f0ef0192"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2cc8ffe258008096a70791115b2daa12f0ef0192"
 Fixed #22985 -- Made call_command accept option name parameter

 Thanks giulettamasina for the report and Tim Graham for the review.
 }}}

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

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

[django/django] 2cc8ff: Fixed #22985 -- Made call_command accept option na...

2014-08-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2cc8ffe258008096a70791115b2daa12f0ef0192
  
https://github.com/django/django/commit/2cc8ffe258008096a70791115b2daa12f0ef0192
  Author: Claude Paroz 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

  Changed paths:
M django/core/management/__init__.py
M docs/ref/django-admin.txt
M docs/releases/1.8.txt
M tests/user_commands/management/commands/dance.py
M tests/user_commands/tests.py

  Log Message:
  ---
  Fixed #22985 -- Made call_command accept option name parameter

Thanks giulettamasina for the report and Tim Graham for the review.


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

Re: [Django] #23271: Makemessages can corrupt existing .po files on Windows

2014-08-12 Thread Django

#23271: Makemessages can corrupt existing .po files on Windows
-+-
 Reporter:  danielmenzel |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.7-rc-2
  Internationalization   |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  makemessages utf8|  Needs documentation:  0
  unicode|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by andrewgodwin):

 I am also without a dev environment. If we have to remove the patch from
 1.7, and we think we can do it cleanly, then it's an option.

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

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

Re: [Django] #23275: Migrations - unmanaged models doesn't get autodetected

2014-08-12 Thread Django

#23275: Migrations - unmanaged models doesn't get autodetected
-+
 Reporter:  shulcsm  |Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   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 Andrew Godwin ):

 In [changeset:"72fdd62e93cf8bc3a6bfad4d24b06a474ad56942"]:
 {{{
 #!CommitTicketReference repository=""
 revision="72fdd62e93cf8bc3a6bfad4d24b06a474ad56942"
 [1.7.x] Fixed #23275: Unmanaged models kept by autodetector, ignored by
 ops
 }}}

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

Re: [Django] #23275: Migrations - unmanaged models doesn't get autodetected

2014-08-12 Thread Django

#23275: Migrations - unmanaged models doesn't get autodetected
-+
 Reporter:  shulcsm  |Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   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 Andrew Godwin ):

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


Comment:

 In [changeset:"8f9862cd4d0e9706babf947079739fd476455df7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8f9862cd4d0e9706babf947079739fd476455df7"
 Fixed #23275: Unmanaged models kept by autodetector, ignored by ops
 }}}

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

[django/django] 72fdd6: [1.7.x] Fixed #23275: Unmanaged models kept by aut...

2014-08-12 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 72fdd62e93cf8bc3a6bfad4d24b06a474ad56942
  
https://github.com/django/django/commit/72fdd62e93cf8bc3a6bfad4d24b06a474ad56942
  Author: Andrew Godwin 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M django/db/migrations/operations/base.py
M tests/migrations/test_autodetector.py
M tests/migrations/test_operations.py

  Log Message:
  ---
  [1.7.x] Fixed #23275: Unmanaged models kept by autodetector, ignored by ops


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

[django/django] 8f9862: Fixed #23275: Unmanaged models kept by autodetecto...

2014-08-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8f9862cd4d0e9706babf947079739fd476455df7
  
https://github.com/django/django/commit/8f9862cd4d0e9706babf947079739fd476455df7
  Author: Andrew Godwin 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M django/db/migrations/operations/base.py
M tests/migrations/test_autodetector.py
M tests/migrations/test_operations.py

  Log Message:
  ---
  Fixed #23275: Unmanaged models kept by autodetector, ignored by ops


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

Re: [Django] #23275: Migrations - unmanaged models doesn't get autodetected

2014-08-12 Thread Django

#23275: Migrations - unmanaged models doesn't get autodetected
-+
 Reporter:  shulcsm  |Owner:  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   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 andrewgodwin):

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

Re: [Django] #23275: Migrations - unmanaged models doesn't get autodetected

2014-08-12 Thread Django

#23275: Migrations - unmanaged models doesn't get autodetected
-+
 Reporter:  shulcsm  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   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 andrewgodwin):

 Yeah, this is valid, the autodetector ignores unmanaged models. I'm pretty
 sure there's a reasonable fix, similar to the handling of proxy models.

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

Re: [Django] #23276: Deprecate passing views as strings to url()

2014-08-12 Thread Django

#23276: Deprecate passing views as strings to url()
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (URLs)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 I am okay with 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/067.29dda13bd36d6a39749be2b4b0cdd63b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23276: Deprecate passing views as strings to url()

2014-08-12 Thread Django

#23276: Deprecate passing views as strings to url()
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (URLs)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Collin Anderson ):

 In [changeset:"8f9dd9f256239d77ef20d6b4d2f48f08208e504a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8f9dd9f256239d77ef20d6b4d2f48f08208e504a"
 [1.7.x] Refs #23276: Removed bad examples of passing views as strings to
 url()

 partial backport of a9fd740d22 from master
 }}}

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

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

[django/django] 8f9dd9: [1.7.x] Refs #23276: Removed bad examples of passi...

2014-08-12 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 8f9dd9f256239d77ef20d6b4d2f48f08208e504a
  
https://github.com/django/django/commit/8f9dd9f256239d77ef20d6b4d2f48f08208e504a
  Author: Collin Anderson 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

  Changed paths:
M docs/intro/overview.txt
M docs/ref/contrib/admin/index.txt
M docs/ref/contrib/sitemaps.txt
M docs/topics/http/urls.txt
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  [1.7.x] Refs #23276: Removed bad examples of passing views as strings to url()

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

[django/django] 6745b6: Fixed typo in previous commit.

2014-08-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6745b6fd7a57c493d9e050dc76799cef810bed01
  
https://github.com/django/django/commit/6745b6fd7a57c493d9e050dc76799cef810bed01
  Author: Tim Graham 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

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

  Log Message:
  ---
  Fixed typo in previous commit.


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

Re: [Django] #23276: Deprecate passing views as strings to url()

2014-08-12 Thread Django

#23276: Deprecate passing views as strings to url()
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (URLs)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by collinanderson):

 I'm a little hesitant to remove patterns() unless we also remove it from
 `project_template`, but here is a rough backport of this change only in
 the docs: https://github.com/django/django/pull/3050

 If we're ok with removing `patterns()` from project_template this late in
 the game (it's just for new projects, right?), I can make a patch for that
 too.

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

Re: [Django] #23016: Review FAQs

2014-08-12 Thread Django

#23016: Review FAQs
-+-
 Reporter:  aaugustin|Owner:
 Type:   |  olasitarska
  Cleanup/optimization   |   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 Tim Graham ):

 In [changeset:"49419ffd050d34c4f0948a0e9b68eb081985277b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="49419ffd050d34c4f0948a0e9b68eb081985277b"
 [1.7.x] Fixed #23016 -- Updated FAQs per Aymeric's suggestions.

 Backport of 549284faa4 from master
 }}}

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

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

[django/django] 49419f: [1.7.x] Fixed #23016 -- Updated FAQs per Aymeric's...

2014-08-12 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 49419ffd050d34c4f0948a0e9b68eb081985277b
  
https://github.com/django/django/commit/49419ffd050d34c4f0948a0e9b68eb081985277b
  Author: Ola Sitarska 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

  Changed paths:
M docs/faq/admin.txt
M docs/faq/general.txt
M docs/faq/install.txt
M docs/faq/models.txt
M docs/faq/usage.txt
M docs/ref/databases.txt
M docs/topics/install.txt

  Log Message:
  ---
  [1.7.x] Fixed #23016 -- Updated FAQs per Aymeric's suggestions.

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

Re: [Django] #23016: Review FAQs

2014-08-12 Thread Django

#23016: Review FAQs
-+-
 Reporter:  aaugustin|Owner:
 Type:   |  olasitarska
  Cleanup/optimization   |   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 Tim Graham ):

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


Comment:

 In [changeset:"549284faa4c58de420918ecd3120607db473787f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="549284faa4c58de420918ecd3120607db473787f"
 Fixed #23016 -- Updated FAQs per Aymeric's suggestions.
 }}}

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

Re: [Django] #23276: Deprecate passing views as strings to url()

2014-08-12 Thread Django

#23276: Deprecate passing views as strings to url()
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (URLs)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"a9fd740d22bc4fed5fdb280c036618000ee13df1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a9fd740d22bc4fed5fdb280c036618000ee13df1"
 Fixed #23276 -- Deprecated passing views as strings to url().
 }}}

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

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

[django/django] a9fd74: Fixed #23276 -- Deprecated passing views as string...

2014-08-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a9fd740d22bc4fed5fdb280c036618000ee13df1
  
https://github.com/django/django/commit/a9fd740d22bc4fed5fdb280c036618000ee13df1
  Author: Tim Graham 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

  Changed paths:
M django/conf/urls/__init__.py
M django/conf/urls/i18n.py
M django/conf/urls/static.py
M django/contrib/auth/tests/urls.py
M django/contrib/staticfiles/urls.py
M django/contrib/staticfiles/views.py
M django/views/static.py
M docs/internals/deprecation.txt
M docs/intro/overview.txt
M docs/ref/contrib/admin/index.txt
M docs/ref/contrib/sitemaps.txt
M docs/ref/urls.txt
M docs/releases/1.8.txt
M docs/topics/http/urls.txt
M docs/topics/i18n/translation.txt
M tests/admin_scripts/urls.py
M tests/generic_views/urls.py
M tests/middleware/extra_urls.py
M tests/middleware/urls.py
M tests/model_permalink/urls.py
M tests/template_tests/urls.py
M tests/test_client/urls.py
M tests/urlpatterns_reverse/erroneous_urls.py
M tests/urlpatterns_reverse/namespace_urls.py
M tests/urlpatterns_reverse/urls.py
M tests/view_tests/generic_urls.py
M tests/view_tests/regression_21530_urls.py
M tests/view_tests/urls.py

  Log Message:
  ---
  Fixed #23276 -- Deprecated passing views as strings to url().


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

Re: [Django] #23276: Deprecate passing views as strings to url()

2014-08-12 Thread Django

#23276: Deprecate passing views as strings to url()
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (URLs)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 On backporting the docs, every change conflicts because we also removed
 `patterns()` on master so we'd want to backport those doc changes first.
 I'd welcome a patch, but not sure I want to do it myself.

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

Re: [Django] #23276: Deprecate passing views as strings to url()

2014-08-12 Thread Django

#23276: Deprecate passing views as strings to url()
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (URLs)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by 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/067.8c05f268832d896bc61f348fe5714a35%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #2273: django.contrib.auth.models.User: username is case-sensitive

2014-08-12 Thread Django

#2273: django.contrib.auth.models.User: username is case-sensitive
--+--
 Reporter:  mderk@…   |Owner:  adrian
 Type:  defect|   Status:  closed
Component:  Contrib apps  |  Version:
 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
--+--

Comment (by timgraham):

 The appropriate place to have discussion on a ticket that's been closed as
 "won't fix" is the DevelopersMailingList.

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

Re: [Django] #23276: Deprecate passing views as strings to url()

2014-08-12 Thread Django

#23276: Deprecate passing views as strings to url()
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (URLs)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by collinanderson):

 Is it too late to back-port the docs changes to 1.7, so we stop setting
 bad examples earlier?

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

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

Re: [Django] #2273: django.contrib.auth.models.User: username is case-sensitive

2014-08-12 Thread Django

#2273: django.contrib.auth.models.User: username is case-sensitive
--+--
 Reporter:  mderk@…   |Owner:  adrian
 Type:  defect|   Status:  closed
Component:  Contrib apps  |  Version:
 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
--+--

Comment (by collinanderson):

 This is why I use mysql :). If nothing else, would it be possible to at
 least move towards the direction of, by default, not allowing a new user
 if there's a `username__iexact` match? That way at least it wouldn't be
 possible to get duplicate usernames in the database before this issue gets
 noticed.

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

Re: [Django] #23272: Extra join on filtered + exclude + annotate query

2014-08-12 Thread Django

#23272: Extra join on filtered + exclude + annotate query
-+-
 Reporter:  doctormo |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by doctormo):

 Confirmed fixed on django 1.6.5, the sql is more messy but I get the right
 result.

 Thanks for the advice.

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

Re: [Django] #23276: Deprecate passing views as strings to url()

2014-08-12 Thread Django

#23276: Deprecate passing views as strings to url()
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (URLs)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * stage:  Accepted => Ready for checkin


Comment:

 The patch looks good. We might see some more dependency issues with this
 change in some projects, but hopefully nothing unsolvable.

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

Re: [Django] #19570: call_command option kwargs differ from command line options (was: call_command options)

2014-08-12 Thread Django

#19570: call_command option kwargs differ from command line options
-+-
 Reporter:  leftmoose|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:  duplicate
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:  call_command, docs   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timgraham):

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


Comment:

 Marking as a duplicate given Claude's fix.

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

Re: [Django] #2273: django.contrib.auth.models.User: username is case-sensitive

2014-08-12 Thread Django

#2273: django.contrib.auth.models.User: username is case-sensitive
--+--
 Reporter:  mderk@…   |Owner:  adrian
 Type:  defect|   Status:  closed
Component:  Contrib apps  |  Version:
 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 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/073.c546128edff1c13fb6fb3c1ec9d175ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 0e9d6a: [1.7.x] Fixed indentation typo in docs/ref/contrib...

2014-08-12 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 0e9d6ad54ac5e34bd0a1577353e651a500fa52a7
  
https://github.com/django/django/commit/0e9d6ad54ac5e34bd0a1577353e651a500fa52a7
  Author: Tim Graham 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

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

  Log Message:
  ---
  [1.7.x] Fixed indentation typo in docs/ref/contrib/sitemaps.txt.

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

[django/django] db1cfb: [1.6.x] Fixed indentation typo in docs/ref/contrib...

2014-08-12 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: db1cfbc1a9d8bafdf14ac2cda321b15f9a77e3d2
  
https://github.com/django/django/commit/db1cfbc1a9d8bafdf14ac2cda321b15f9a77e3d2
  Author: Tim Graham 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

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

  Log Message:
  ---
  [1.6.x] Fixed indentation typo in docs/ref/contrib/sitemaps.txt.

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

[django/django] 2003cb: Fixed indentation typo in docs/ref/contrib/sitemap...

2014-08-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2003cb23d4f1b3be717855d41b562d4d5cfebe99
  
https://github.com/django/django/commit/2003cb23d4f1b3be717855d41b562d4d5cfebe99
  Author: Tim Graham 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

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

  Log Message:
  ---
  Fixed indentation typo in docs/ref/contrib/sitemaps.txt.


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

Re: [Django] #22391: fallback to pymysql if MySQLdb not available

2014-08-12 Thread Django

#22391: fallback to pymysql if MySQLdb not available
-+-
 Reporter:  CollinAnderson   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by collinanderson):

 Sorry, I should link to the django-developers ghost-thread, and maybe bump
 it. https://groups.google.com/d/topic/django-
 developers/n-TI8mBcegE/discussion

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

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

Re: [Django] #19716: Support microsecond precision in MySQL ORM DateTimeField

2014-08-12 Thread Django

#19716: Support microsecond precision in MySQL ORM DateTimeField
-+-
 Reporter:  erik@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 After seeing that the tests were successful with the first commit, I
 pushed a second commit which should really add microseconds support with
 MySQL 5.6.4 and up. However, it is completely untested yet (and the CI
 server has still MySQL 5.5).

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

Re: [Django] #22985: call_command() ignores dest from make_option() and uses kwarg name instead

2014-08-12 Thread Django

#22985: call_command() ignores dest from make_option() and uses kwarg name 
instead
-+-
 Reporter:  giuliettamasina  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #18707: Test client doesn't allow testing 500 responses content

2014-08-12 Thread Django

#18707: Test client doesn't allow testing 500 responses content
---+
 Reporter:  ricardokirkner@…   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  1.6
 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 nicbou):

 * version:  1.3 => 1.6


Comment:

 I am in the same situation as David. Our 500 page is a redirect that needs
 to be tested. Although it's a fairly easy to test for 404s and the like,
 we can't test that our 500 handler works.

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

Re: [Django] #19716: Support microsecond precision in MySQL ORM DateTimeField

2014-08-12 Thread Django

#19716: Support microsecond precision in MySQL ORM DateTimeField
-+-
 Reporter:  erik@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 As for my patch, I think that the fact that the current test suite pass
 (I'll make a PR to test this) should be sufficient.
 Of course, when we really support microseconds, the
 `supports_microsecond_precision` db feature will have to depend on the
 MySQL version.
 PR: https://github.com/django/django/pull/3049

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

Re: [Django] #23275: Migrations - unmanaged models doesn't get autodetected

2014-08-12 Thread Django

#23275: Migrations - unmanaged models doesn't get autodetected
-+
 Reporter:  shulcsm  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   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 collinanderson):

 I can reproduce it using the models above.

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

Re: [Django] #23276: Deprecate passing views as strings to url()

2014-08-12 Thread Django

#23276: Deprecate passing views as strings to url()
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (URLs)  |   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 timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/3048 PR]

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

[Django] #23276: Deprecate passing views as strings to url()

2014-08-12 Thread Django

#23276: Deprecate passing views as strings to url()
-+-
   Reporter:  timgraham  |  Owner:  timgraham
   Type: | Status:  new
  Cleanup/optimization   |Version:  master
  Component:  Core   |   Keywords:
  (URLs) |  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 Now that we've deprecated `patterns()` and recommended importing your
 views module and referencing your view functions (or classes) directly
 (#22218), it's time to deprecate the "Django String Magic" that lets you
 use strings as views in `url()`, e.g. `url('^$', 'myapp.views.myview')`.
 (originally raised in #22384)

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

Re: [Django] #2273: django.contrib.auth.models.User: username is case-sensitive

2014-08-12 Thread Django

Comment (by ollytheninja):

This is clearly a sore point for some people judging by my googling. I
understand that the change would have been hard 8 years ago and is now
near impossible.

Shouldn't there at least be a note added to the documentation, I currently
see nothing about this in the documentation (maybe I missed it?)?

Simply adding "Note: usernames '''are''' case sensitive" to

[https://docs.djangoproject.com/en/dev/ref/contrib/auth/#django.contrib.auth.models.User.username]
would be a step in the right direction.

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

Re: [Django] #23274: Bad exception management: custom template tags

2014-08-12 Thread Django

#23274: Bad exception management: custom template tags
-+-
 Reporter:  micfan   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.5
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  custom template  | Triage Stage:
  tags   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by micfan):

 * status:  new => closed
 * needs_docs:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_better_patch:   => 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/064.0e233e4af8661afa44ffc1950c77ec0d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23275: Migrations - unmanaged models doesn't get autodetected

2014-08-12 Thread Django

#23275: Migrations - unmanaged models doesn't get autodetected
-+
 Reporter:  shulcsm  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   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 bmispelon):

 * stage:  Unreviewed => Accepted


Comment:

 Yes, this does appear to be a serious issue.

 Thanks.

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

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

Re: [Django] #23275: Migrations - unmanaged models doesn't get autodetected

2014-08-12 Thread Django

#23275: Migrations - unmanaged models doesn't get autodetected
-+--
 Reporter:  shulcsm  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   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 collinanderson):

 * cc: cmawebsite@… (added)
 * severity:  Normal => Release blocker


Comment:

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

Re: [Django] #23275: Migrations - unmanaged models doesn't get autodetected

2014-08-12 Thread Django

#23275: Migrations - unmanaged models doesn't get autodetected
+--
 Reporter:  shulcsm |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-rc-2
 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 shulcsm):

 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * 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.62e0da1f1032d85a6201f4fc54efbbe1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23275: Migrations - unmanaged models doesn't get autodetected

2014-08-12 Thread Django

#23275: Migrations - unmanaged models doesn't get autodetected
---+--
 Reporter:  shulcsm|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Migrations |Version:  1.7-rc-2
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 Running migration with fk to unmanaged model fails with ValueError.

 Models:
 {{{
 from django.db import models


 class SomeModel(models.Model):
 unmanaged_rel = models.OneToOneField('UnmanagedModel', null=True)


 class UnmanagedModel(models.Model):
 some_field = models.TextField()

 class Meta:
 managed = False
 }}}

 Autogenreated migration:

 {{{
 class Migration(migrations.Migration):

 dependencies = [
 ]

 operations = [
 migrations.CreateModel(
 name='SomeModel',
 fields=[
 ('id', models.AutoField(verbose_name='ID',
 serialize=False, auto_created=True, primary_key=True)),
 ('unmanaged_rel', models.OneToOneField(null=True,
 to='testproj.UnmanagedModel')),
 ],
 options={
 },
 bases=(models.Model,),
 ),
 ]

 }}}

 Stacktrace:
 {{{
   Applying testproj.0001_initial...Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/martins/Projects/django-
 playground/django/django/core/management/__init__.py", line 385, in
 execute_from_command_line
 utility.execute()
   File "/home/martins/Projects/django-
 playground/django/django/core/management/__init__.py", line 377, in
 execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/martins/Projects/django-
 playground/django/django/core/management/base.py", line 288, in
 run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/martins/Projects/django-
 playground/django/django/core/management/base.py", line 338, in execute
 output = self.handle(*args, **options)
   File "/home/martins/Projects/django-
 playground/django/django/core/management/commands/migrate.py", line 160,
 in handle
 executor.migrate(targets, plan, fake=options.get("fake", False))
   File "/home/martins/Projects/django-
 playground/django/django/db/migrations/executor.py", line 63, in migrate
 self.apply_migration(migration, fake=fake)
   File "/home/martins/Projects/django-
 playground/django/django/db/migrations/executor.py", line 91, in
 apply_migration
 if self.detect_soft_applied(migration):
   File "/home/martins/Projects/django-
 playground/django/django/db/migrations/executor.py", line 135, in
 detect_soft_applied
 apps = project_state.render()
   File "/home/martins/Projects/django-
 playground/django/django/db/migrations/state.py", line 89, in render
 model=lookup_model,
 ValueError: Lookup failed for model referenced by field
 testproj.SomeModel.unmanaged_rel: testproj.UnmanagedModel
 }}}

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

[Django] #23274: Bad exception management: custom template tags

2014-08-12 Thread Django

#23274: Bad exception management: custom template tags
-+--
 Reporter:  micfan   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.5
 Severity:  Normal   |   Keywords:  custom template tags
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+--
 Hey, I am writing a simple custom tags demo following
 (https://docs.djangoproject.com/en/dev/howto//#writing-custom-template-
 tags).

 This line give me an exception: `actual_date =
 self.date_to_be_formatted.resolve(context)`.

 I think the mangement of exception is not good. See that
 
https://github.com/django/django/blob/stable/1.7.x/django/template/base.py#L690,
 it add a judgement, however, this judgement did not control that
 https://github.com/django/django/blob/stable/1.7.x/django/template/base.py#L699
 `float(var)` function's Exception, which tips me that:

 {{{
 #!div style="font-size: 80%, background: #ffc;"
   {{{#!python
 TypeError at /
 float() argument must be a string or a number
 Request Method: GET
 Request URL:http://localhost:8000/
 Django Version: 1.5
 Exception Type: TypeError
 Exception Value:
 float() argument must be a string or a number
 Exception Location: /usr/local/lib/python2.7/dist-
 packages/django/template/base.py in __init__, line 695
 Python Executable:  /usr/bin/python
 Python Version: 2.7.6
   }}}
 }}}

 did you any good man catch this evil bug, please?

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

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

Re: [Django] #18757: Examine ways to get rid of DB backend convert_values()

2014-08-12 Thread Django

* needs_better_patch: 0 => 1
* has_patch: 0 => 1

Comment:

POC at https://github.com/django/django/pull/3047

I agree with your comments akaariai - will try to update to use that
approach. Most of the code is currently in removing `convert_values`
rather than in the details of what happens afterwards. If I get the POC
all green, the performance *should* be easier.

For my own notes, I believe #21565 should get fixed by this as well, and
so I should write a failing test for it. At least if I can get a working
spatialite setup anyway...

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

Re: [Django] #23215: Warning: Field 'id' doesn't have a default value

2014-08-12 Thread Django

#23215: Warning: Field 'id' doesn't have a default value
-+-
 Reporter:  duduklein|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7-rc-2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  model default value  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by BlindHunter):

 Simply mysqldump and restore your database from dump.

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

Re: [Django] #20133: Admin: Add deletion summary

2014-08-12 Thread Django

#20133: Admin: Add deletion summary
---+
 Reporter:  jonash |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Anyone is welcome to rebase the patch and test it. I would just say that
 I'd prefer that commits separated refactoring of logic from the adding of
 new features if possible as this makes the diffs smaller and easier to
 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/064.743d842f40fdcb90e50ac91b30311f1c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 5b0375: Fixed #23001 -- Fixed mixing defer and annotations

2014-08-12 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5b0375ec3e7473fcc29c21003fef80c0d0be183f
  
https://github.com/django/django/commit/5b0375ec3e7473fcc29c21003fef80c0d0be183f
  Author: Josh Smeaton 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

  Changed paths:
M django/db/models/query.py
M tests/aggregation/tests.py

  Log Message:
  ---
  Fixed #23001 -- Fixed mixing defer and annotations


  Commit: f7dba61881ff5c26ad1c9a6dff71a8dc4ebede5a
  
https://github.com/django/django/commit/f7dba61881ff5c26ad1c9a6dff71a8dc4ebede5a
  Author: Anssi Kääriäinen 
  Date:   2014-08-12 (Tue, 12 Aug 2014)

  Changed paths:
M django/db/models/query_utils.py
M tests/defer_regress/tests.py

  Log Message:
  ---
  Avoided creation of deferred model from another deferred model

Also never create deferred model when no attrs are deferred.


Compare: https://github.com/django/django/compare/954e7b8aad3f...f7dba61881ff

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

Re: [Django] #23001: Annotation breaks with deferred fields and select_related

2014-08-12 Thread Django

#23001: Annotation breaks with deferred fields and select_related
-+-
 Reporter:  smeatonj |Owner:  jarshwah
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [changeset:"5b0375ec3e7473fcc29c21003fef80c0d0be183f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5b0375ec3e7473fcc29c21003fef80c0d0be183f"
 Fixed #23001 -- Fixed mixing defer and annotations
 }}}

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

Re: [Django] #18757: Examine ways to get rid of DB backend convert_values()

2014-08-12 Thread Django

Comment (by akaariai):

I have tested a bit in this area and we really can't call
field.from_db_value for every field. It is just plain too expensive. We
are talking about 2-3x performance slowdown for models with ten fields. A
single method call is somewhere around 5% slowdown in model initialization
speed. For 10 fields the above field.from_db_value() definition will cause
3 calls per field, so that is 5% * 3 * 10 = 150% slowdown.

Instead we need to do the following:
1) Collect converters for each field before we start iterating the
result set.
2) Not all fields define a converter - in fact almost all fields in core
do not need a converter at all.
3) At the same time we also collect converters from the database
backend.
4) When we have collected the converters, start iterating through the
result set. Pass the values through the found converters.

This is needed so that if a field doesn't define any converter, then there
is no overhead for that field. For this reason I would also try to avoid
doing backend specific conversion in the field's from_db method - this
means that if any backend needs from_db support, then all backends need to
pay the overhead of calling the method for no benefit at all.

I don't think the new way needs to be backwards compatible to the old
convert_values way. We just need to ensure the old way works for backwards
compatibility period.

So, alternate proposal:
1) Add field.get_db_value_converters(connection) method. The method
returns a list of converters or None if no converters are needed.
2) Add backend.get_value_converter(field) method. By default this method
returns [backend.convert_values] if that is defined for the backend,
otherwise it returns None.
3) Collect all converters before iterating results.
4) When iterating through the results, the converters will be called
with just value as argument (we could likely also add connection here)
5) Deprecate SubfieldBase, deprecate backend.convert_values.

As for how to do the convert_values collection, look for
https://github.com/akaariai/django/tree/custom_lookups for one
implementation. Unfortunately that implementation is mixed with unrelated
changes.

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

Re: [Django] #18757: Examine ways to get rid of DB backend convert_values()

2014-08-12 Thread Django

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

Comment:

`convert_values` is currently run under the following conditions:

- When aggregates are run. This means sqlite, oracle, mssql, and gis all
have special cases, and the default backend has handling for floats and
IntegerFields (which is not always called in a `super()` for sqlite and
oracle...)
- When the compiler defines `resolve_columns` and this calls
`convert_values`. This means oracle, all gis.

It is worth noting that the work done in `resolve_columns` on mysql
probably should be in `convert_values` (make boolean fields into a boolean
value).

Like with many things, we need to support both third party backends and
third party fields appropriately here. So we need to make sure that
mssql's use of `convert_values` is still possible to handle SQLServer's
weird datetime formatting, and also support a third party (or builtin)
field which has its own storage. There are two possible steps - one is
normalisation of the returned data so all backends operate the same, and
the second is further conversion from the "backend" version to the full
model version (this would solve #14462). Both steps should be possible at
both levels in my opinion - so the field level method should still receive
the connection object.

On top of this, all data conversion at the moment is done using
`get_internal_type` so for backwards compatibility we need to make sure we
respect any field with that set to a real internal type. This means we
cannot move all of the conversion currently done to field level (at least
outside of gis I think).

A possible plan of action:

- make `SQLCompiler.results_iter` always call
`SQLCompiler.resolve_columns`, and make sure subclasses (which are still
needed) call the `super()` as needed.
- For each field and row call `field.from_db_value(value, connection)`. By
default this would look like:
{{{
def field.from_db_value(value, connection):
internal_type = self.get_internal_type()
converter_name = 'convert_%s_value' % internal_type.lower()
func = getattr(connection.ops, converter_name, None)
if func:
value = func(value)
return value
}}}

An individual field can override `from_db_value` if it wants to do custom
conversions, and backends add `convert_myfield_value` methods rather than
`convert_values` with a stupid number of if statements in it. Individual
`convert_myfield_value` methods should be coded defensively in case
conversion is already done - there are cases where you get a different
value depending on whether it is an aggregate or a direct value.

I think this will allow me to remove some complexity from gis and mysql at
least, and remove `convert_values` as it is all together. It would be
backwards incompat for third party backends using `convert_values`,
although this could easily be included with a deprecation warning in the
default `from_db_value` if needed (if hasattr). Given how mssql's
`convert_values` is written anyway, I think this will be an improvement
anyway.

POC coming up soon hopefully!

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

Re: [Django] #20205: PositiveIntegerfield does not handle empty values well

2014-08-12 Thread Django

Comment (by akaariai):

The problem here likely comes from HTML form submissions: there "" is the
natural None value for all fields that do not accept "" directly as a
value. My interpretation is that empty_values should be those values that
should be converted to None in validation. For IntegerField this should be
None and "", for CharField just None (as "" is a valid value directly).

I am not sure if we can change the logic so that all empty_values are
converted to None without breaking backwards compatibility badly.

I am not sure why we skip field validation for empty_values. Backwards
compatibility?

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

Re: [Django] #22224: Non-nullable blank string-based model field validation doesn't prevent or clean `None`

2014-08-12 Thread Django

* needs_better_patch: 0 => 1

Comment:

It seems the problem here is that for HTML forms, "" is the natural None
value, so for example IntegerField="" should validate and set the field to
Zero. But for model validation this isn't the case. In that use case
providing "" for IntegerField doesn't make sense. We could maybe make
forms treat "" specially (convert to None unless the underlying field
accepts empty strings), and then remove "" from empty_values for
practically every field. Unfortunately changes here seem problematic as
the problem isn't that large currently, but the backwards compatibility
issues will be large.

Also, maybe we could just remove "" from empty values for all fields that
accept "" directly as a value. The logic is that while "" is kinda special
value for CharField, it is just one value in its domain. However, for
IntegerField (and other fields that do not accept "" directly) the empty
string is not in their domain, and thus it can be treated as None.

I'm marking patch needs improvement for lack of better marker. What is
needed here is a design decision of how we want to treat "" in CharFields.

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

Re: [Django] #22125: Unnecessary creation of index for ManyToManyField

2014-08-12 Thread Django

* needs_better_patch: 0 => 1

Comment:

I don't think the solution in PR2578 is the right solution at all.

If I read the patch correctly it removes all indexes for fields that are
already first element in some unique_together index. There are valid cases
for asking a separate index for a field even if it is part of an
unique_together index. The most important reason for this is that a
single-field index is faster than multicolumn index. In addition we
shouldn't override what users have asked explicitly.

We should just skip index creation for m2m tables unless the user asks for
single column index. I am not sure if we should add flags to m2m field for
creation or skipping of these indexes.

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

Re: [Django] #19463: Add UUID Field to core

2014-08-12 Thread Django

* needs_better_patch: 0 => 1

Comment:

There seems to be one issue that needs solving: should we use SubfieldBase
or not? SubfieldBase is used so that the field's to_python method is
called any time a value is assigned to a model instance. In particular
this happens when setting a value in `model.__init__`. So, if a database
value is just bytes or string, then when the model is initialized from the
database we get correctly UUID instance in the uuid field because
to_python is called.

There isn't any field in core that uses to_python. There are some
disadvantages when using to_python:
1. It doesn't work when using .values('uuid_field')
2. There is a small performance penalty when setting the field value,
in particular model.__init__ will be 10-20% slower for each field that
uses SubfieldBase.
3. Fields with subfieldbase work a bit differently from other core
fields. SubfieldBase fields do value conversion on assignment, so:
{{{
>>> s = SomeModel()
>>> s.uuid_field = "f47ac10b-58cc-4372-a567-0e02b2c3d479"
>>> s.uuid_field
OUT: uuid("f47ac10b-58cc-4372-a567-0e02b2c3d479") when using SubfieldBase
OUT: "f47ac10b-58cc-4372-a567-0e02b2c3d479" when not using SubfieldBase
}}}
Now, one could consider this to be a feature. But, no other field in core
or contrib does this kind of conversion on assignment, so we should avoid
this if possible.

Other ways forward are:
1. Add a more generic field value conversion framework: add
field.from_db_value(value, connection). This is a larger amount of work,
but is needed in any case. This solution would work in .values(), and it
would also be considerably faster than the current SubfieldBase way of
doing things. Unfortunately this means that we can't merge this ticket
before we have added the from_db_value method.
2. Use backend specific converters. Unfortunately it seems one needs to
create custom compilers for each backend (see
django/db/backends/oracle/compiler.py for example)

So, in the end there seems to be just two choices: wait for
field.from_db_value() or use SubfieldBase (with the possibility of
removing use of SubfieldBase when field.from_db_value is introduced).

I'll mark patch needs improvement for lack of better marker that this
isn't ready for merge before we agree on a solution on the SubfieldBase
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/065.336749a953b5498ba1bb38e04b832df5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22391: fallback to pymysql if MySQLdb not available

2014-08-12 Thread Django

#22391: fallback to pymysql if MySQLdb not available
-+-
 Reporter:  CollinAnderson   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * needs_better_patch:  0 => 1


Comment:

 If I understand correctly we at least need CI support for testing pymysql
 builds? Also, if In understand correctly there are still some errors with
 pymysql?

 The best way forward is to ask for CI support for pymysql builds on
 django-developers mailing list.

 I'll set patch needs improvement for lack of better marker that this
 ticket isn't ready for merge.

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

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

Re: [Django] #19716: Support microsecond precision in MySQL ORM DateTimeField

2014-08-12 Thread Django

#19716: Support microsecond precision in MySQL ORM DateTimeField
-+-
 Reporter:  erik@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * needs_tests:  0 => 1


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

Re: [Django] #23273: MigrationRecorder does not obey db_router allow_migrate rules

2014-08-12 Thread Django

#23273: MigrationRecorder does not obey db_router allow_migrate rules
+--
 Reporter:  froomzy |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-rc-2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by akaariai):

 #22583 is somewhat related. It deals with the inability to skip
 RunSQL/RunPython operations on given database.

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

Re: [Django] #23272: Extra join on filtered + exclude + annotate query

2014-08-12 Thread Django

#23272: Extra join on filtered + exclude + annotate query
-+-
 Reporter:  doctormo |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

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


Comment:

 Which version of Django are you using? If you are using 1.5 as indicated
 by the version field, this might have been fixed in later releases. There
 have been many bug fixes to join generation logic recently, so checking
 with master branch of Django would be helpful.

 To reproduce what is happening here I need the model definitions (or
 simplified versions of them). A sample project attached or model
 definitions posted inside a comment are both OK ways to provide the model
 definitions.

 Also, it seems the e variable is actually the same thing as the b variable
 (used in .exclude(b)).

 Don't use qs.query.group_by = [], that isn't supported API. You should get
 the same results by doing .values('id').annotate(p_value=...)

 I'll close this as needsinfo, please reopen when you provide the models
 needed to reproduce the error.

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

Re: [Django] #18731: "makemessages" management command should handle import aliases

2014-08-12 Thread Django

Comment (by tkhyn):

To people who - like me lately - would land here after a google search and
want to add gettext extra keywords to Django < 1.7 without having to patch
Django, you may want to use [https://bitbucket.org/tkhyn/django-

extra_keywords/src/ced532843875/extra_keywords/management/commands/makemessages.py
this management command override] which will work with Django 1.6 and
earlier. Or simply use the [https://pypi.python.org/pypi/django-
extra_keywords django-extra_keywords] package.

It uses an approach that differs from what is suggested above, by monkey-
patching `popen_wrapper` (>= 1.6) or `_popen` (< 1.6) in
`core.management.commands.makemessages` and adding arguments to the
command. A bit hackish, but it does the job.

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

Re: [Django] #23273: MigrationRecorder does not obey db_router allow_migrate rules

2014-08-12 Thread Django

#23273: MigrationRecorder does not obey db_router allow_migrate rules
+--
 Reporter:  froomzy |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-rc-2
 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 jarshwah):

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


Comment:

 I don't think you've implemented your router correctly, but I'd need to
 check the router code to see if it's called multiple times
 (num_dbs*num_models) to be sure. This is how we implement our routers for
 allow_migrate:

 {{{
 def allow_migrate(self, db, model):
 if db == 'other':
 return model._meta.app_label == 'legacy_app' # allow migration
 for new django models implemented in legacy db
 elif model._meta.app_label == 'legacy_app':  # do not allow
 migration for legacy on any other db
 return False
 return None # this router not responsible
 }}}

 So, I'm not sure if there is a bug or not (I'll let someone more familiar
 answer that), but this is what works for us.

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

91 matches

Mail list logo