date:20160129

[Django] #26157: Unify database loggers to use same log record API

2016-01-29 Thread Django

#26157: Unify database loggers to use same log record API
+-
   Reporter:  MarkusH   |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Utilities |Version:  master
   Severity:  Normal|   Keywords:  logging
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+-
 While writing https://markusholtermann.eu/2016/01/syntax-highlighting-for-
 djangos-sql-query-logging/ I noticed that the `django.db.backends` and
 `django.db.backends.schema` loggers are not using the same "higher level"
 API for the log records.

 While the backends looger puts the query `duration`, `sql` and `params`
 into the log record, the schema logger only passes the arguments for
 string formatting.

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

Re: [Django] #26156: Add a link to creating a superuser in the admin docs.

2016-01-29 Thread Django

#26156: Add a link to creating a superuser in the admin docs.
-+-
 Reporter:  yoongkang|Owner:  yoongkang
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by yoongkang):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => yoongkang
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization


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

[Django] #26156: Add a link to creating a superuser in the admin docs.

2016-01-29 Thread Django

#26156: Add a link to creating a superuser in the admin docs.
---+
 Reporter:  yoongkang  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The documentation for the Django Admin site lists the steps to enable the
 Django admin site, but doesn't tell you that you need to first create a
 superuser to be able to login.

 It would be nice if there was a link to the createsuperuser command.

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

Re: [Django] #26098: Support Geodjango admin widgets on SSL

2016-01-29 Thread Django

#26098: Support Geodjango admin widgets on SSL
-+-
 Reporter:  fmalina  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by blueyed):

 > suggested to use protocol-relative schemes

 It would be better to use https always by now.

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

Re: [Django] #26134: Update MySQL GIS function names to OpenGIS standard.

2016-01-29 Thread Django

#26134: Update MySQL GIS function names to OpenGIS standard.
-+-
 Reporter:  fmalina  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"c47364ef0c368c9a0257dba68534d8781019cee4" c47364ef]:
 {{{
 #!CommitTicketReference repository=""
 revision="c47364ef0c368c9a0257dba68534d8781019cee4"
 Fixed #26134 -- Used new OpenGIS names for recent MySQL

 Thanks František Malina for the report.
 }}}

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

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

Re: [Django] #14402: help_text is not displayed for ManyToMany raw_id fields

2016-01-29 Thread Django

#14402: help_text is not displayed for ManyToMany raw_id fields
-+-
 Reporter:  tyrion   |Owner:  sasha0
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  raw_id_fields| Triage Stage:  Ready for
 |  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/064.c7cf6d1428c8c9bc997835500d1677fa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26134: Update MySQL GIS function names to OpenGIS standard.

2016-01-29 Thread Django

#26134: Update MySQL GIS function names to OpenGIS standard.
-+-
 Reporter:  fmalina  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 [https://github.com/django/django/pull/6065 PR] from Claude looks good.

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

Re: [Django] #11313: list_editable fields don't support 'save' in multiuser environment

2016-01-29 Thread Django

#11313: list_editable fields don't support 'save' in multiuser environment
-+-
 Reporter:  margieroginski   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.1-beta
 Severity:  Normal   |   Resolution:
 Keywords:  model formsets   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_docs:  1 => 0
 * 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/072.067cd9a9b55702b54f43627408d809a6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26149: Invalid migration generated when using order_with_respect_to and a unique_together constraint

2016-01-29 Thread Django

#26149: Invalid migration generated when using order_with_respect_to and a
unique_together constraint
+
 Reporter:  richardxia  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by anabelensc):

 thank you, I am working on 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/068.ea0712c298d738c52b49d83def43fce7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26149: Invalid migration generated when using order_with_respect_to and a unique_together constraint

2016-01-29 Thread Django

#26149: Invalid migration generated when using order_with_respect_to and a
unique_together constraint
+
 Reporter:  richardxia  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by timgraham):

 * has_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 A test will be needed, probably in
 `tests/migrations/test_autodetector.py`. If the patch fixes the test and
 doesn't break any other tests, it might be a good candidate!

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

Re: [Django] #14402: help_text is not displayed for ManyToMany raw_id fields

2016-01-29 Thread Django

#14402: help_text is not displayed for ManyToMany raw_id fields
---+
 Reporter:  tyrion |Owner:  sasha0
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  raw_id_fields  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by sasha0):

 * status:  new => assigned
 * needs_better_patch:  1 => 0
 * ui_ux:  1 => 0
 * owner:  nobody => sasha0


Comment:

 [https://github.com/django/django/pull/6064 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/064.8b7c0a95057bf651917def780e9fa329%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26149: Invalid migration generated when using order_with_respect_to and a unique_together constraint

2016-01-29 Thread Django

#26149: Invalid migration generated when using order_with_respect_to and a
unique_together constraint
+
 Reporter:  richardxia  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by anabelensc):

 Hello,
 Could you check this patch, please?
 I changed "db/migrations/autodetector.py" and now there is no bug.

 python manage.py makemigrations

 Migrations for 'p1':
 p1/migrations/0001_initial.py:
 Create model Bar
 Create model Foo
 Set order_with_respect_to on foo to bar
 Alter unique_together for foo (1 constraint(s))

 python manage.py migrate

 Operations to perform:
 Apply all migrations: admin, auth, contenttypes, p1, sessions
 Running migrations:
 Rendering model states... DONE
 Applying contenttypes.0001_initial... OK
 Applying auth.0001_initial... OK
 Applying admin.0001_initial... OK
 Applying admin.0002_logentry_remove_auto_add... OK
 Applying contenttypes.0002_remove_content_type_name... OK
 Applying auth.0002_alter_permission_name_max_length... OK
 Applying auth.0003_alter_user_email_max_length... OK
 Applying auth.0004_alter_user_username_opts... OK
 Applying auth.0005_alter_user_last_login_null... OK
 Applying auth.0006_require_contenttypes_0002... OK
 Applying auth.0007_alter_validators_add_error_messages... OK
 Applying auth.0008_alter_user_username_max_length... OK
 Applying p1.0001_initial... OK
 Applying sessions.0001_initial... OK

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

Re: [Django] #26149: Invalid migration generated when using order_with_respect_to and a unique_together constraint

2016-01-29 Thread Django

#26149: Invalid migration generated when using order_with_respect_to and a
unique_together constraint
+
 Reporter:  richardxia  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.9
 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 anabelensc):

 * Attachment "migration-bug.patch" 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/068.2b398ee2b3b252d38f59f6183ec11ab8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25415: Django 1.8 regression: tests no longer run checks

2016-01-29 Thread Django

#25415: Django 1.8 regression: tests no longer run checks
---+
 Reporter:  adamchainz |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.8
 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:  0
---+

Comment (by timgraham):

 Created a [https://groups.google.com/d/topic/django-developers/GyuVJ-
 E6Or4/discussion django-developers discussion]. Maybe it would be
 acceptable to use the approach suggested by Shai, "it would seem that the
 best default is to run checks unless specific tests are selected."

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

Re: [Django] #26022: Use the context manager version of assertRaises decorators where appropriate

2016-01-29 Thread Django

#26022: Use the context manager version of assertRaises decorators where
appropriate
-+-
 Reporter:  hramezani|Owner:  hramezani
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


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

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

Re: [Django] #26022: Use the context manager version of assertRaises decorators where appropriate

2016-01-29 Thread Django

#26022: Use the context manager version of assertRaises decorators where
appropriate
-+-
 Reporter:  hramezani|Owner:  hramezani
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  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:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"26ad01719d73823e65c0358a2ee9941e0a888a63" 26ad0171]:
 {{{
 #!CommitTicketReference repository=""
 revision="26ad01719d73823e65c0358a2ee9941e0a888a63"
 Refs #26022 -- Replaced six.assertRaisesRegex with assertRaisesMessage as
 appropriate.
 }}}

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

Re: [Django] #26155: Skip URL checks if settings.ROOTURL_CONF isn't defined

2016-01-29 Thread Django

#26155: Skip URL checks if settings.ROOTURL_CONF isn't defined
--+
 Reporter:  BuddyL|Owner:  BuddyL
 Type:  Bug   |   Status:  assigned
Component:  Core (System checks)  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 You may do it. Please include a mention in the 1.9.2 release notes 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/064.2330dd025a4cfb76fc4c17f09fb0e881%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26152: django.setup() hangs django if ever used in a module that's imported by an app

2016-01-29 Thread Django

#26152: django.setup() hangs django if ever used in a module that's imported by 
an
app
--+
 Reporter:  hjwp  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by hjwp):

 I might be wrong but, given the use of threading.Lock(), isn't the
 RunTimeError if self.app_configs theoretically impossible?

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

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

Re: [Django] #26152: django.setup() hangs django if ever used in a module that's imported by an app

2016-01-29 Thread Django

#26152: django.setup() hangs django if ever used in a module that's imported by 
an
app
--+
 Reporter:  hjwp  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 Yes, I was thinking of adding a boolean flag when the process starts.

 I /think/ we discussed using a RLock before and rejected it, but I'm not
 sure. I have to investigate. I'll try to find time.

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

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

Re: [Django] #26022: Use the context manager version of assertRaises decorators where appropriate

2016-01-29 Thread Django

#26022: Use the context manager version of assertRaises decorators where
appropriate
-+-
 Reporter:  hramezani|Owner:  hramezani
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  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:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"253adc2b8a52982139d40c4f55b3fd446e1cb8f3" 253adc2]:
 {{{
 #!CommitTicketReference repository=""
 revision="253adc2b8a52982139d40c4f55b3fd446e1cb8f3"
 Refs #26022 -- Used context manager version of assertRaisesMessage in
 tests.
 }}}

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

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

Re: [Django] #25240: Add "week" lookup to DateField/DateTimeField

2016-01-29 Thread Django

#25240: Add "week" lookup to DateField/DateTimeField
-+-
 Reporter:  foresmac |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by borfast):

 * cc: borfast@… (added)


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

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

Re: [Django] #26022: Use the context manager version of assertRaises decorators where appropriate

2016-01-29 Thread Django

#26022: Use the context manager version of assertRaises decorators where
appropriate
-+-
 Reporter:  hramezani|Owner:  hramezani
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  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:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"3d0dcd7f5af378d3ab6adb303b913e6c7b2e0ee5" 3d0dcd7]:
 {{{
 #!CommitTicketReference repository=""
 revision="3d0dcd7f5af378d3ab6adb303b913e6c7b2e0ee5"
 Refs #26022 -- Used context manager version of assertRaises in tests.
 }}}

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

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

Re: [Django] #26155: Skip URL checks if settings.ROOTURL_CONF isn't defined

2016-01-29 Thread Django

#26155: Skip URL checks if settings.ROOTURL_CONF isn't defined
--+
 Reporter:  BuddyL|Owner:  BuddyL
 Type:  Bug   |   Status:  assigned
Component:  Core (System checks)  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by BuddyL):

 I see what you are after.

 Just tried that and it works, is an easier solution too. You want me to
 fix it, add tests, and submit a PR? Or you?

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

Re: [Django] #26155: Skip URL checks if settings.ROOTURL_CONF isn't defined

2016-01-29 Thread Django

#26155: Skip URL checks if settings.ROOTURL_CONF isn't defined
--+
 Reporter:  BuddyL|Owner:  BuddyL
 Type:  Bug   |   Status:  assigned
Component:  Core (System checks)  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 I mean something like this:
 {{{
 @register(Tags.urls)
 def check_url_config(app_configs, **kwargs):
 from django.urls import get_resolver
 if getattr(settings, ROOT_URLCONF, None):
 resolver = get_resolver()
 return check_resolver(resolver)
 return []
 }}}

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

Re: [Django] #26155: Skip URL checks if settings.ROOTURL_CONF isn't defined

2016-01-29 Thread Django

#26155: Skip URL checks if settings.ROOTURL_CONF isn't defined
--+
 Reporter:  BuddyL|Owner:  BuddyL
 Type:  Bug   |   Status:  assigned
Component:  Core (System checks)  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by BuddyL):

 If you return `None` for the settings of `ROOT_URLCONF` you get the
 following excpetion:

 {{{
 Traceback (most recent call last):
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/urlresolvers.py", line 419, in url_patterns
 iter(patterns)
 TypeError: 'NoneType' object is not iterable

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 353, in
 execute_from_command_line
 utility.execute()
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 345, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/management/base.py", line 348, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/management/base.py", line 398, in execute
 self.check()
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/management/base.py", line 426, in check
 include_deployment_checks=include_deployment_checks,
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/checks/registry.py", line 75, in run_checks
 new_errors = check(app_configs=app_configs)
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/checks/urls.py", line 10, in check_url_config
 return check_resolver(resolver)
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/checks/urls.py", line 19, in check_resolver
 for pattern in resolver.url_patterns:
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/utils/functional.py", line 33, in __get__
 res = instance.__dict__[self.name] = self.func(instance)
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/urlresolvers.py", line 426, in url_patterns
 raise ImproperlyConfigured(msg.format(name=self.urlconf_name))
 django.core.exceptions.ImproperlyConfigured: The included URLconf 'None'
 does not appear to have any patterns in it. If you see valid patterns in
 the file then the issue is probably caused by a circular import.
 }}}

 I modified the method to be. Not exactly sure how you  mean to use an `if`
 in this case.
 {{{#!python
 @lru_cache.lru_cache(maxsize=None)
 def get_resolver(urlconf=None):
 if urlconf is None:
 from django.conf import settings
 urlconf = getattr(settings, 'ROOT_URLCONF', None)
 return RegexURLResolver(r'^/', urlconf)
 }}}

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

Re: [Django] #26155: Skip URL checks if settings.ROOTURL_CONF isn't defined

2016-01-29 Thread Django

#26155: Skip URL checks if settings.ROOTURL_CONF isn't defined
--+
 Reporter:  BuddyL|Owner:  BuddyL
 Type:  Bug   |   Status:  assigned
Component:  Core (System checks)  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 `if getattr(settings, ROOT_URLCONF, None)`?

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

Re: [Django] #26155: Skip URL checks if settings.ROOTURL_CONF isn't defined

2016-01-29 Thread Django

Comment (by BuddyL):

I don't think it would because when I set `settings.ROOT_URLCONF` to an
empty string it tries to run through the url resolver code which erros
because it can't find the app it is assigned to, or any urlpatterns as it
tries to resolve them.

I tried to tweak on what is returned where the ROOT_URLCONF is accessed,
and the few things I tried didn't help.

Here is where the code is trying to access the attribute and is throwing
the exception:

https://github.com/django/django/blob/1.9.1/django/core/urlresolvers.py#L147-L152

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

Re: [Django] #26155: Skip URL checks if settings.ROOTURL_CONF isn't defined

2016-01-29 Thread Django

#26155: Skip URL checks if settings.ROOTURL_CONF isn't defined
--+
 Reporter:  BuddyL|Owner:  BuddyL
 Type:  Bug   |   Status:  assigned
Component:  Core (System checks)  |  Version:  1.9
 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 BuddyL):

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


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

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

Re: [Django] #26155: Skip URL checks if settings.ROOTURL_CONF isn't defined (was: Can not Disable `check_url_config` Url Check)

2016-01-29 Thread Django

#26155: Skip URL checks if settings.ROOTURL_CONF isn't defined
--+
 Reporter:  BuddyL|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (System checks)  |  Version:  1.9
 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
 * stage:  Unreviewed => Accepted
 * needs_tests:   => 0


Comment:

 Would a `if hasattr(settings, 'ROOT_URLCONF')` check be sufficient?

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

[Django] #26155: Can not Disable `check_url_config` Url Check

2016-01-29 Thread Django

#26155: Can not Disable `check_url_config` Url Check
--+
 Reporter:  BuddyL|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (System checks)  |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 If you try to create a migration with `makemigrations` it throws an error
 (below) because it is running the `check_url_config` system check. There
 currently isn't a way to disable this check, and the use case we have we
 don't need/use urls.

 {{{
 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 353, in
 execute_from_command_line
 utility.execute()
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 345, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/management/base.py", line 348, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/management/base.py", line 398, in execute
 self.check()
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/management/base.py", line 426, in check
 include_deployment_checks=include_deployment_checks,
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/checks/registry.py", line 75, in run_checks
 new_errors = check(app_configs=app_configs)
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/checks/urls.py", line 9, in check_url_config
 resolver = get_resolver()
   File "/home/buddy/.venv/sk-client/lib/python3.4/functools.py", line 448,
 in wrapper
 result = user_function(*args, **kwds)
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/core/urlresolvers.py", line 151, in get_resolver
 urlconf = settings.ROOT_URLCONF
   File "/home/buddy/.venv/sk-client/lib/python3.4/site-
 packages/django/conf/__init__.py", line 56, in __getattr__
 return getattr(self._wrapped, name)
 AttributeError: 'Settings' object has no attribute 'ROOT_URLCONF'
 }}}

 Here are the steps to reproduce this error:

 {{{
 ./manage.py startproject demo
 cd blog
 vim blog/settings.py# comment out ROOT_URLCONF
 ./manage.py startapp blog
 vim blog/models.py# add model below
 ./manage.py makemigrations
 }}}

 {{{#!python
 from django.db import models

 class Post(models.Model):
 title = models.CharField(max_length=, blank=True)
 description = models.TextField(blank=True)
 }}}

 That should be enough to reproduce the error.

 My thought is we need to add a way to disable the `check_url_config`
 check.

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

Re: [Django] #25833: Add support for non-atomic migrations (was: Non-atomic migrations)

2016-01-29 Thread Django

#25833: Add support for non-atomic migrations
-+
 Reporter:  Pankrat  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  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:  0
-+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Left some comments for improvement on the pull request.

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

Re: [Django] #26107: Add an option to int_list_validator to allow negative integers (was: CommaSeparatedIntegerField doesn't allow negative integers)

2016-01-29 Thread Django

#26107: Add an option to int_list_validator to allow negative integers
+
 Reporter:  cooperjbrandon  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Core (Other)|  Version:  1.9
 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:  0
+
Changes (by timgraham):

 * stage:  Someday/Maybe => Accepted


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

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

[Django] #26154: Deprecate CommaSeparatedIntegerField

2016-01-29 Thread Django

#26154: Deprecate CommaSeparatedIntegerField
-+-
   Reporter:  timgraham  |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Database   |Version:  master
  layer (models, ORM)|
   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  |
-+-
 As [https://groups.google.com/d/topic/django-
 developers/wfp9qNpNpaQ/discussion proposed on django-developers],
 `CommaSeparatedIntegerField` could be replaced with
 `CharField(validators=[validate_comma_separated_integer_list])`.

 The only database storage difference is on Oracle:
 {{{
 'CharField': 'NVARCHAR2(%(max_length)s)',
 'CommaSeparatedIntegerField': 'VARCHAR2(%(max_length)s)',
 }}}
 There are some upgrade considerations described on the mailing list
 that'll need to be mentioned for Oracle users.

 See [https://docs.djangoproject.com/en/dev/topics/migrations
 /#considerations-when-removing-model-fields the migration topic guide] for
 an explanation of how to deprecate the field, as well as the
 [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /submitting-patches/#deprecating-a-feature deprecating a feature guide].

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

Re: [Django] #26117: Add database routers support to initial migration detection

2016-01-29 Thread Django

#26117: Add database routers support to initial migration detection
-+---
 Reporter:  scottsexton  |Owner:  scottsexton
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/6036 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/069.e66e1a086f19f2a417abb3f5a8110363%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26119: Catch ValueError while parsing urls in URLValidator

2016-01-29 Thread Django

#26119: Catch ValueError while parsing urls in URLValidator
--+
 Reporter:  EnTeQuAk  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  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:  0
--+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 As noted on the pull request, looks like a few test cases are missing.

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

Re: [Django] #26120: Make HStoreField cast its key/values to strings

2016-01-29 Thread Django

#26120: Make HStoreField cast its key/values to strings
--+
 Reporter:  CGenie|Owner:  gchp
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.postgres  |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"8dea9f089dcb8aea2c417c91344c4e680431e972" 8dea9f0]:
 {{{
 #!CommitTicketReference repository=""
 revision="8dea9f089dcb8aea2c417c91344c4e680431e972"
 Fixed #26120 -- Made HStoreField cast keys and values to strings.

 HStoreField now converts all keys and values to string before they're
 saved to the 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/064.4244ad62106ae4a8e166315a5e47155c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #7923: Add links when using raw_id_fields in admin

2016-01-29 Thread Django

#7923: Add links when using raw_id_fields in admin
-+-
 Reporter:  julianb  |Owner:  hobarrera
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin raw_id_fields  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Left comments for improvement on the pull request.

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

Re: [Django] #25971: BrokenLinkEmailsMiddleware shouldn't report 404s when URL = Referer + "/"

2016-01-29 Thread Django

#25971: BrokenLinkEmailsMiddleware shouldn't report 404s when URL = Referer + 
"/"
-+-
 Reporter:  jribbens |Owner:
 |  harikrishnakanchi
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  1.8
 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:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1
 * easy:  1 => 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/066.b78ed8113f87891471486adf2e73db9b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26137: Document steps needed to install spatialite on Ubuntu 15.04+

2016-01-29 Thread Django

#26137: Document steps needed to install spatialite on Ubuntu 15.04+
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"d6d8fd3b821a3e1d6bcbeddc658f7486a567af5e" d6d8fd3b]:
 {{{
 #!CommitTicketReference repository=""
 revision="d6d8fd3b821a3e1d6bcbeddc658f7486a567af5e"
 [1.9.x] Fixed #26137 -- Confirmed support for SpatiaLite 4.2/4.3 and added
 instructions.

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

Re: [Django] #26137: Document steps needed to install spatialite on Ubuntu 15.04+

2016-01-29 Thread Django

#26137: Document steps needed to install spatialite on Ubuntu 15.04+
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"93897a6a75754c1c17d8a60dee188c86f13de232" 93897a6]:
 {{{
 #!CommitTicketReference repository=""
 revision="93897a6a75754c1c17d8a60dee188c86f13de232"
 Fixed #26137 -- Confirmed support for SpatiaLite 4.2/4.3 and added
 instructions.
 }}}

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

Re: [Django] #26153: Allow get_extra_descriptor_filter to return Q-objects

2016-01-29 Thread Django

#26153: Allow get_extra_descriptor_filter to return Q-objects
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 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:  0
-+-
Changes (by timgraham):

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

Re: [Django] #26129: bound forms do not display disabled field initial values

2016-01-29 Thread Django

#26129: bound forms do not display disabled field initial values
-+-
 Reporter:  dieselmachine|Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.9
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  disabled fields, | Triage Stage:  Accepted
  forms  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"01db3249e5048093c85de33e5395ba737d330d0a" 01db324]:
 {{{
 #!CommitTicketReference repository=""
 revision="01db3249e5048093c85de33e5395ba737d330d0a"
 [1.9.x] Fixed #26129 -- Made invalid forms display initial values of
 disabled fields.

 Backport of 04564eb74d2d92eaf88b22ab8cec7ef45978111e 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/071.f3014e8846245ad4f47dcb24e71fd247%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26151: Refactor MigrationWriter.serialize()

2016-01-29 Thread Django

#26151: Refactor MigrationWriter.serialize()
-+-
 Reporter:  yoongkang|Owner:  yoongkang
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by MarkusH):

 Since a discussion on #django-dev came up earlier I posted to the
 developer mailing list to get other people's input:
 https://groups.google.com/forum/#!topic/django-developers/yGKl7ZkLac4

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

Re: [Django] #26129: bound forms do not display disabled field initial values

2016-01-29 Thread Django

#26129: bound forms do not display disabled field initial values
-+-
 Reporter:  dieselmachine|Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.9
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  disabled fields, | Triage Stage:  Accepted
  forms  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"04564eb74d2d92eaf88b22ab8cec7ef45978111e" 04564eb]:
 {{{
 #!CommitTicketReference repository=""
 revision="04564eb74d2d92eaf88b22ab8cec7ef45978111e"
 Fixed #26129 -- Made invalid forms display initial values of disabled
 fields.
 }}}

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

Re: [Django] #26152: django.setup() hangs django if ever used in a module that's imported by an app

2016-01-29 Thread Django

Comment (by hjwp):

Just been digging into this. And I am not an experienced coder of
multithreaded code, so I probably shouldn't be allowed.

Here's the current code:

{{{
# populate() might be called by two threads in parallel on servers
# that create threads before initializing the WSGI callable.
with self._lock:
if self.ready:
return

# app_config should be pristine, otherwise the code below
won't
# guarantee that the order matches the order in
INSTALLED_APPS.
if self.app_configs:
raise RuntimeError("populate() isn't reentrant")

# [...] rest of populate code
self.ready = True

}}}

So switching _lock to being a threading.RLock will have the desired effect
of raising the "populate isn't reentrant" exception that's already been
defined, if populate is ever called recursively by the same thread.

I'm not sure I understand the code though. Under what circumstances, with
the current threading.Lock(), would we expect the RuntimeError to be
encountered?

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

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

Re: [Django] #26152: django.setup() hangs django if ever used in a module that's imported by an app

2016-01-29 Thread Django

#26152: django.setup() hangs django if ever used in a module that's imported by 
an
app
--+
 Reporter:  hjwp  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by hjwp):

 Hi Aymeric,  there's a couple of ways I can think of that would detect
 cycles and then a couple of things we could do with it:

 detect options:
 - import the traceback module and examine the call stack for a previous
 call to django.setup()
 - set some global variable in the module, _setup_called = True, or
 whatever it may be.  (there is already a class variable called .ready,
 which is set to true at the end of the apps.populate() call.  So maybe we
 could just add a second class variable that's set at the beginning)

 what to do:
 - raise an exception
 - or, just an early return.  Maybe setup() should just be idempotent

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

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

[Django] #26153: Allow get_extra_descriptor_filter to return Q-objects

2016-01-29 Thread Django

#26153: Allow get_extra_descriptor_filter to return Q-objects
-+-
   Reporter:  akaariai   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.9
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 In django 1.8 it was possible to return Q-objects from
 ForeignObject.get_extra_descriptor_filter(). In Django 1.9 the return
 value must be a dictionary.

 The problem is that in Django 1.9 it is impossible to return an OR
 combined condition. While the get_extra_descriptor_filter() is private API
 I'd like to maintain the ability to return Q-objects. This is
 straightforward patch with little regression risks.

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

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

Re: [Django] #24974: Cannot create subclass of form created by `modelform_factory()`, e.g. in `ModelAdmin.get_form()`

2016-01-29 Thread Django

#24974: Cannot create subclass of form created by `modelform_factory()`, e.g. in
`ModelAdmin.get_form()`
-+-
 Reporter:  mrmachine|Owner:  yoongkang
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  form modelform   | Triage Stage:  Accepted
  modelform_factory modeladmin   |
  get_site metaclass |
  modelformmetaclass |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by yoongkang):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/6048 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.8c2c7c9fed70a73512b97de1167c959b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26152: django.setup() hangs django if ever used in a module that's imported by an app

2016-01-29 Thread Django

#26152: django.setup() hangs django if ever used in a module that's imported by 
an
app
--+
 Reporter:  hjwp  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 We may be able to detect that case and raise an exception instead of
 hanging. (I didn't look at the code too closely.)

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

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

49 matches

Mail list logo