[Django] #24967: FORCE_SCRIPT_NAME causes HttpResponseRedirect to fail

[Django]

#24967: FORCE_SCRIPT_NAME causes HttpResponseRedirect to fail
-+-
 Reporter:   |  Owner:  nobody
  seanherron |
 Type:  Bug  | Status:  new
Component:  Core |Version:  1.8
  (URLs) |   Keywords:  SCRIPT_NAME,
 Severity:  Normal   |  FORCE_SCRIPT_NAME,redirect,HttpResponseRedirect
 Triage Stage:   |  Has patch:  0
  Unreviewed |
Easy pickings:  0|  UI/UX:  0
-+-
 When FORCE_SCRIPT_NAME is set in settings, redirects using
 HttpResponseRedirect seem to fail.

 '''Expected behavior:'''
 While FORCE_SCRIPT_NAME is enabled (set to `foo`), HttpResponseRedirect
 should return the user to a correct path, prepended with the script name.
 (eg, `/foo/bar`).

 '''Actual behavior:'''
 HttpResponseRedirect doubles the script name and redirects the user to
 `/foo/foo/bar`.


 As a workaround, I created a utility function to reconstruct a full URL to
 redirect the user to, but this should not be necessary.


 {{{
 from django.shortcuts import redirect
 from django.core.urlresolvers import reverse
 from django.conf import settings

 def absolute_redirect(url, args=None):
 """
 This is a function that I needed to make because
 Django's default redirect function doesn't work properly when
 FORCE_SCRIPT_NAME is set. It returns a full URL for redirection
 """

 reverse_url = reverse(url, args=args)

 if settings.URL_ROOT:
 reverse_url = reverse(url, args=args)
 return redirect('%s%s' % (settings.URL_ROOT, reverse_url))
 else:
 return redirect(reverse_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/053.edeb148ea836b14671769917ead39ce1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22404: Make front-end getext catalog available as JSON

[Django]

#22404: Make front-end getext catalog available as JSON
-+-
 Reporter:  ian.morrison.a@… |Owner:
 |  sergeykolosov
 Type:  New feature  |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 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 sergeykolosov):

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

Re: [Django] #24965: Make LiveServerTestCase.live_server_url accessible from class

[Django]

#24965: Make LiveServerTestCase.live_server_url accessible from class
-+-
 Reporter:  MoritzS  |Owner:  MoritzS
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  selenium tests live  | Triage Stage:  Accepted
  server test case url   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by MoritzS):

 How should I do that?
 I could do something like
 {{{
 class TestLiveServerTestCase(LiveServerTestCase):
 @classmethod
 def setUpClass(cls):
 super(TestLiveServerTestCase, cls).setUpClass()
 if isinstance(cls.live_server_url, str):
 cls._test_worked = True
 else:
 cls._test_worked = False

 def test_worked(self):
 self.assertTrue(self._test_worked)
 }}}

 But that feels really hackish.
 And instanciating `LiveServerTestCase` inside a `SimpleTestCase` isn't
 that trivial, I think.

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

Re: [Django] #24965: Make LiveServerTestCase.live_server_url accessible from class

[Django]

#24965: Make LiveServerTestCase.live_server_url accessible from class
-+-
 Reporter:  MoritzS  |Owner:  MoritzS
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  selenium tests live  | Triage Stage:  Accepted
  server test case url   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 I don't think so. A simple test for `live_server_url` being accessible as
 a class property might be useful if it's easy.

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

Re: [Django] #24914: Include basic permission mixins into Django

[Django]

#24914: Include basic permission mixins into Django
--+
 Reporter:  raphaelm  |Owner:  MarkusH
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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 MarkusH):

 Here's a PR that adopts django-braces' mixins:
 https://github.com/django/django/pull/4844

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

Re: [Django] #24965: Make LiveServerTestCase.live_server_url accessible from class

[Django]

#24965: Make LiveServerTestCase.live_server_url accessible from class
-+-
 Reporter:  MoritzS  |Owner:  MoritzS
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  selenium tests live  | Triage Stage:  Accepted
  server test case url   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MoritzS):

 * needs_better_patch:  1 => 0


Comment:

 Updated PR.
 Is some additional documentation needed?

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

Re: [Django] #24966: Unconfigured Allowed_Hosts Setting Should Raise ImproperlyConfigured Error

[Django]

#24966: Unconfigured Allowed_Hosts Setting Should Raise ImproperlyConfigured 
Error
-+-
 Reporter:  raiderrobert |Owner:
 Type:   |  raiderrobert
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  setting  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by carljm):

 * component:  Uncategorized => Core (Other)
 * 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/070.f3327a82cf00072c71e401000ef2c6bb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24966: Unconfigured Allowed_Hosts Setting Should Raise ImproperlyConfigured Error

[Django]

#24966: Unconfigured Allowed_Hosts Setting Should Raise ImproperlyConfigured 
Error
-+-
 Reporter:  raiderrobert |Owner:
 Type:   |  raiderrobert
  Cleanup/optimization   |   Status:  assigned
Component:  Uncategorized|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  setting  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by raiderrobert):

 * owner:   => raiderrobert
 * needs_better_patch:   => 0
 * status:  new => assigned
 * 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/070.714fed04b0c2bfc9a73da43c9c1a653d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24966: Unconfigured Allowed_Hosts Setting Should Raise ImproperlyConfigured Error

[Django]

#24966: Unconfigured Allowed_Hosts Setting Should Raise ImproperlyConfigured 
Error
--+-
 Reporter:  raiderrobert  |  Owner:
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  1.8
 Severity:  Normal|   Keywords:  setting
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 Allowed_Hosts is a required setting. When debug mode is off, and
 Allowed_Hosts is not implemented, this should raise an
 ImproperlyConfigured Error.

 See conversation here: https://groups.google.com/forum/#!topic/django-
 developers/nIrbGjyOsNY

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

Re: [Django] #24965: Make LiveServerTestCase.live_server_url accessible from class

[Django]

#24965: Make LiveServerTestCase.live_server_url accessible from class
-+-
 Reporter:  MoritzS  |Owner:  MoritzS
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  selenium tests live  | Triage Stage:  Accepted
  server test case url   |
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


Comment:

 `django.utils.decorators` seems like 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/065.7d7a91562657ee86b4a5a08eaa2f0a63%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24965: Make LiveServerTestCase.live_server_url accessible from class

[Django]

#24965: Make LiveServerTestCase.live_server_url accessible from class
-+-
 Reporter:  MoritzS  |Owner:  MoritzS
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  selenium tests live  | Triage Stage:
  server test case url   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by MoritzS):

 Yes that would be better and I thought about it, but I didn't want to add
 a new decorator just for one property.
 Should the `classproperty` go into some utils module then?

 I don't see were else it would make sense to use, so I guess that's ok.

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

Re: [Django] #24965: Make LiveServerTestCase.live_server_url accessible from class

[Django]

#24965: Make LiveServerTestCase.live_server_url accessible from class
-+-
 Reporter:  MoritzS  |Owner:  MoritzS
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  selenium tests live  | Triage Stage:
  server test case url   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 Would an approach like this be better than adding a method?
 {{{
 diff --git a/django/test/testcases.py b/django/test/testcases.py
 index b17b392..22ab3c1 100644
 --- a/django/test/testcases.py
 +++ b/django/test/testcases.py
 @@ -1245,6 +1245,13 @@ class LiveServerThread(threading.Thread):
  self.httpd.server_close()


 +class classproperty(object):
 +def __init__(self, f):
 +self.f = f
 +def __get__(self, obj, owner):
 +return self.f(owner)
 +
 +
  class LiveServerTestCase(TransactionTestCase):
  """
  Does basically the same as TransactionTestCase but also launches a
 live
 @@ -1259,7 +1266,7 @@ class LiveServerTestCase(TransactionTestCase):

  static_handler = _StaticFilesHandler

 -@property
 +@classproperty
  def live_server_url(self):
  return 'http://%s:%s' % (
  self.server_thread.host, self.server_thread.port)
 }}}
 Is it okay for the attribute to fail when not using `setUpClass`? For
 example:
 {{{
 >>> from django.test.testcases import LiveServerTestCase
 >>> LiveServerTestCase.live_server_url
 Traceback (most recent call last):
   File "", line 1, in 
   File "/home/tim/code/django/django/test/testcases.py", line 1252, in
 __get__
 return self.f(owner)
   File "/home/tim/code/django/django/test/testcases.py", line 1272, in
 live_server_url
 self.server_thread.host, self.server_thread.port)
 AttributeError: type object 'LiveServerTestCase' has no attribute
 'server_thread'
 }}}

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

Re: [Django] #24965: Make LiveServerTestCase.live_server_url accessible from class

[Django]

#24965: Make LiveServerTestCase.live_server_url accessible from class
-+-
 Reporter:  MoritzS  |Owner:  MoritzS
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  selenium tests live  | Triage Stage:
  server test case url   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MoritzS):

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

Re: [Django] #24965: Make LiveServerTestCase.live_server_url accessible from class

[Django]

#24965: Make LiveServerTestCase.live_server_url accessible from class
-+-
 Reporter:  MoritzS  |Owner:  MoritzS
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  selenium tests live  | Triage Stage:
  server test case url   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MoritzS):

 * owner:   => MoritzS
 * needs_better_patch:   => 0
 * status:  new => assigned
 * 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.3001fd180e9d0995006197913bff3dcf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24965: Make LiveServerTestCase.live_server_url accessible from class

[Django]

#24965: Make LiveServerTestCase.live_server_url accessible from class
-+-
 Reporter:  MoritzS  |  Owner:
 Type:   | Status:  new
  Cleanup/optimization   |
Component:  Testing framework|Version:  master
 Severity:  Normal   |   Keywords:  selenium tests live
 |  server test case url
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 Consider following test:
 {{{
 class MySeleniumTest(LiveServerTestCase):
 @classmethod
 def setUpClass(cls):
 super(MySeleniumTest, cls).setUpClass()
 # initialize selenium driver
 cls.selenium = WebDriver()
 # initialize browser state, live_server_url is needed here
 cls.selenium.get(cls.live_server_url)
 # [...]
 }}}

 Right now this doesn't work, because `live_server_url` is a property even
 though it only consists of class attributes.

 Since class properties are a bit more complicated I suggest adding a
 `get_live_server_url` classmethod and keeping the `live_server_url`.
 An alternative is to deprecate `live_server_url` but I don't think that's
 really necessary.

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

Re: [Django] #24914: Include basic permission mixins into Django

[Django]

#24914: Include basic permission mixins into Django
--+
 Reporter:  raphaelm  |Owner:  MarkusH
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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 MarkusH):

 I just added some tests to check for the mixin stacking.

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

Re: [Django] #24954: Adding an explicit UUID id doesn't change type of ManyToMany fields pointing to it (was: ManyToMany field fails with non-integer ids)

[Django]

#24954: Adding an explicit UUID id doesn't change type of ManyToMany fields
pointing to it
--+
 Reporter:  cloudOver |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  ManyToMany, UUID  | 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):

 * stage:  Unreviewed => Accepted


Comment:

 I could reproduce this with an initial model (implicit `AutoField` `id`):
 {{{
 class SomeModel(models.Model):
 blockers = models.ManyToManyField('self', symmetrical=False,
 blank=True)
 }}}
 then adding an explicit `id` as `id = models.UUIDField(primary_key=True,
 default=uuid.uuid4, editable=False)`. The `from_X_id` and `to_X_id` fields
 in the many to many table where still 'integer' type (SQLite).

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

Re: [Django] #24933: Make FormSet management forms optional

[Django]

#24933: Make FormSet management forms optional
--+
 Reporter:  patrys|Owner:  nobody
 Type:  Cleanup/optimization  |   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
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #23548: Transform.relabeled_clone calls own constructor with wrong number of arguments

[Django]

#23548: Transform.relabeled_clone calls own constructor with wrong number of
arguments
-+-
 Reporter:  ris  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  lookup transform | Triage Stage:  Accepted
  orm subquery   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ris):

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


Comment:

 This appears to be fixed in commit
 08232ef84d4959826ad5136f183c9fc5bedf0599 (also backported to 1.8.x @
 b4b13759f82e9e09951bb72875b1c6e384dca6a9). Closing.

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

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

Re: [Django] #24914: Include basic permission mixins into Django

[Django]

#24914: Include basic permission mixins into Django
--+
 Reporter:  raphaelm  |Owner:  MarkusH
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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 raphaelm):

 I don't really see an easy and obvious way to support stacking of
 ``UserPassesTestMixin``. You could either do something like

 {{{#!python
 class CheckOneMixin(UserPassesTestMixin):
 def test_func(self, user):
 return something_is_true_or_false and super().test_func()
 }}}

 or make the API more complex by allowing each subclass to set/append to a
 list of test functions in some way.

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

Re: [Django] #24940: unhashable type: 'RelatedManager' when deleting a model using django admin that has GenericRelation and related_query_name

[Django]

#24940: unhashable type: 'RelatedManager' when deleting a model using django 
admin
that has GenericRelation and related_query_name
-+
 Reporter:  jmfederico   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.8
 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 timgraham):

 * Attachment "24940-test.diff" 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.31ff6cbc58a2ec2e2024438c576707ca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24914: Include basic permission mixins into Django

[Django]

#24914: Include basic permission mixins into Django
--+
 Reporter:  raphaelm  |Owner:  MarkusH
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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 MarkusH):

 Thanks for mentioning that, Rundll. The current implementation does not
 support stacking them (braces' `LoginRequired` and `PermissionRequired`
 mixins do, though). However, neither our `UserPassesTestMixin` nor braces'
 allows stacking inherited mixins, either.

 That makes me wonder how one is supposed to combine different permission
 checks that are used separately and together:

 {{{#!python
 class CheckOneMixin(UserPassesTestMixin):
 def test_func(self, user):
 return something_is_true_or_false

 class CheckTwoMixin(UserPassesTestMixin):
 def test_func(self, user):
 return something_else_is_true_or_false

 class MyView1(CheckOneMixin, View):
 pass

 class MyView2(CheckTwoMixin, View):
 pass

 class MyView3(CheckOneMixin, CheckTwoMixin, View):
 pass
 }}}

 Effectively, `MyView3` will never bother about the value of
 `something_else_is_true_or_false` as that function is never called.

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

Re: [Django] #24940: unhashable type: 'RelatedManager' when deleting a model using django admin that has GenericRelation and related_query_name

[Django]

#24940: unhashable type: 'RelatedManager' when deleting a model using django 
admin
that has GenericRelation and related_query_name
-+
 Reporter:  jmfederico   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.8
 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 timgraham):

 * cc: MarkusH (added)
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 Bisected to aa5ef0d4fc67a95ac2a5103810d0c87d8c547bac. Attaching a
 regression test for Django's test suite.

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

Re: [Django] #24963: Missing `seekable()` method in Files

[Django]

#24963: Missing `seekable()` method in Files
--+
 Reporter:  carsongee |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  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
--+

Comment (by carsongee):

 I have now submitted a patch with tests:
 https://github.com/django/django/pull/4842

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

Re: [Django] #24950: Add unicode_literals to startapp's template models.py

[Django]

#24950: Add unicode_literals to startapp's template models.py
--+
 Reporter:  MarkusH   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 I just think our time could be better spent, but if you have interest,
 might as well just do it rather than spend time debating.

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

Re: [Django] #24959: date_interval_sql Implementations for Database Backends Do Not Handle Negative timedelta Objects Properly

[Django]

#24959: date_interval_sql Implementations for Database Backends Do Not Handle
Negative timedelta Objects Properly
-+-
 Reporter:  fredpalmer   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  date_interval_sql,   | Triage Stage:  Accepted
  timedelta, F, orm  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  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/068.6daa0eea2538cc543667314d94d97887%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12685: Serialized objects' save function does not respect force_insert

[Django]

#12685: Serialized objects' save function does not respect force_insert
-+-
 Reporter:  dcotruta |Owner:  Russell
 |  Keith-Magee 
 Type:  New feature  |   Status:  closed
Component:  Core |  Version:  1.1
  (Serialization)|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  save, force_insert,  | Triage Stage:  Accepted
  force_update   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Russell Keith-Magee ):

 * status:  new => closed
 * owner:   => Russell Keith-Magee 
 * resolution:   => fixed


Comment:

 In [changeset:"9851e54121b3eebd3a7a29de3ed874d82554396b" 9851e541]:
 {{{
 #!CommitTicketReference repository=""
 revision="9851e54121b3eebd3a7a29de3ed874d82554396b"
 Merge pull request #4811 from mthornhill/12685

 Fixed #12685 - Ensure that deserialised model instances honor the same
 arguments as normal 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/066.57556ce527c0be9b592f04b71df32927%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24203: Optimisation: adding multiple fields to same model should attempt to run single ALTER TABLE statement

[Django]

#24203: Optimisation: adding multiple fields to same model should attempt to run
single ALTER TABLE statement
-+-
 Reporter:  peterlauri   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  migration| Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ambivalentno):

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

Re: [Django] #24363: Combine ALTER TABLE .. MODIFY statements for multiple columns into one statement.

[Django]

#24363: Combine ALTER TABLE .. MODIFY statements for multiple columns into one
statement.
-+-
 Reporter:  slachinger   |Owner:
 |  ambivalentno
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  Modify Field Column  | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ambivalentno):

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

Re: [Django] #24951: Error deleting from table with Foreign Key being Primary Key at the same point

[Django]

#24951: Error deleting from table with Foreign Key being Primary Key at the same
point
-+-
 Reporter:  grumbler |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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):

 * Attachment "24951-test.diff" 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.4eea32c0a2e710f6807ad53037573dd2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24951: Error deleting from table with Foreign Key being Primary Key at the same point

[Django]

#24951: Error deleting from table with Foreign Key being Primary Key at the same
point
-+-
 Reporter:  grumbler |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Bisected to 20bab2cf9d02a5c6477d8aac066a635986e0d3f3. Attaching a
 regression test for Django's test suite.

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

Re: [Django] #24964: Infinite migrations with empty help_text via ugettext_lazy

[Django]

#24964: Infinite migrations with empty help_text via ugettext_lazy
-+-
 Reporter:  gimbo|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  internationalisation   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * severity:  Normal => Release blocker
 * 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/063.acf23d55ce834832cc36d8bb079f12b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24962: Objects with primary keys containing newlines do not get links to being edited in the admin list view

[Django]

#24962: Objects with primary keys containing newlines do not get links to being
edited in the admin list view
---+
 Reporter:  alito  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * needs_tests:   => 1
 * needs_docs:   => 0


Comment:

 A regression test is also needed.

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

Re: [Django] #24964: Infinite migrations with empty help_text via ugettext_lazy

[Django]

#24964: Infinite migrations with empty help_text via ugettext_lazy
-+-
 Reporter:  gimbo|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  migrations,  | Triage Stage:
  internationalisation   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by davea):

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


Comment:

 A quick `git bisect` indicates this was introduced in
 
[https://github.com/django/django/commit/11f307a5a8fa66605652e0496c7385e584bfcad7
 11f307a5a8fa66605652e0496c7385e584bfcad7].

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

Re: [Django] #16860: Provide hooks for password policy

[Django]

#16860: Provide hooks for password policy
--+
 Reporter:  PaulM |Owner:  erikr
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"55b3bd84681a87266f6bef72480aaef48a7c295f" 55b3bd8]:
 {{{
 #!CommitTicketReference repository=""
 revision="55b3bd84681a87266f6bef72480aaef48a7c295f"
 Refs #16860 -- Minor edits and fixes to password validation.
 }}}

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

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

Re: [Django] #24963: Missing `seekable()` method in Files

[Django]

#24963: Missing `seekable()` method in Files
--+
 Reporter:  carsongee |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  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
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 An acceptable option might be to implement the method only on Python 3 if
 it's not part of the standard interface on Python 2.

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

[Django] #24964: Infinite migrations with empty help_text via ugettext_lazy

[Django]

#24964: Infinite migrations with empty help_text via ugettext_lazy
+--
 Reporter:  gimbo   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.8
 Severity:  Normal  |   Keywords:  migrations, internationalisation
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+--
 I've come across something which seems to be a bug; I've asked about it on
 django-users and was encouraged to raise it here.

 There's a fuller explanation and easily runnable example on github:
 https://github.com/gimbo/django-ugettext_lazy_migrations

 In short, given the following model (note the empty `help_text` string),
 {{{
 from django.db import models
 from django.utils.translation import ugettext_lazy as _

 class X(models.Model):
 y = models.CharField(help_text=_(''), max_length=10)
 }}}
 repeated calls of `manage.py makemigrations` will, after the initial
 migration, produce an infinite series of new migrations, each of which
 contains an `AlterField`, but which does nothing.  The expected behaviour
 would be to produce an initial migration and then no further migrations,
 of course.

 The problems goes away if you do any of the following:

 * Remove the `help_text` parameter
 * Use a non-empty `help_text`
 * Don't internationalise the `help_text` value
 * Use `ugettext` instead of `ugettext_lazy` (which, I understand, you
 shouldn't)

 I've reproduced it on all released 1.8.x Django versions up to 1.8.2, but
 it doesn't exhibit on any 1.7.x versions I've tried.

 I haven't tried any development versions.

 I mentioned it on django-users, and Carl Meyer suggested the following:

 I would guess the problem has to do with a careless `if help_text:`
 somewhere in the migration detection code. It would be worth checking
 whether the same problem exists with any other similar field parameters
 (e.g. `label`).

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

Re: [Django] #24954: ManyToMany field fails with non-integer ids

[Django]

#24954: ManyToMany field fails with non-integer ids
--+--
 Reporter:  cloudOver |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  ManyToMany, UUID  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by synotna):

 This also applies to changing the primary key of the referenced model; a
 migration to update the existing column is not detected/generated

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

Re: [Django] #24943: Update contributing tutorial to use virtualenv

[Django]

#24943: Update contributing tutorial to use virtualenv
-+-
 Reporter:  timgraham|Owner:
 Type:   |  giuliettamasina
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by giuliettamasina):

 Also note that the Windows code blocks use 'none' for Pygments,
 [http://pygments.org/docs/lexers/#lexers-for-various-shells any of the
 shell types] would generate quite confusing syntax highlighting, at least
 locally.

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

Re: [Django] #24943: Update contributing tutorial to use virtualenv

[Django]

#24943: Update contributing tutorial to use virtualenv
-+-
 Reporter:  timgraham|Owner:
 Type:   |  giuliettamasina
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by giuliettamasina):

 Updated the pull request with some notes and Windows instructions, have
 another look.

 I'm not at a Windows computer right now, but I would want to go through
 the entire tutorial on Windows before this is merged. Hopefully that can
 happen later today.

 (Still getting similar build failures, but for other jobs.)

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