date:20160910

Re: [Django] #26524: Change foreign key id list_display reference to display only the id

2016-09-10 Thread Django

#26524: Change foreign key id list_display reference to display only the id
-+-
 Reporter:  cristianocca |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  admin list_display   | Triage Stage:  Accepted
  changelist |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * Attachment "26524-regress.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/070.ab839f2f38816006db810499acc4a0d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26401: Allow auth machinery to be used without installing auth app

2016-09-10 Thread Django

#26401: Allow auth machinery to be used without installing auth app
-+-
 Reporter:  satchamo |Owner:  andkon
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  auth | 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 GitHub ):

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


Comment:

 In [changeset:"1ec1633cb294d8ce2a65ece6b56c258483596fba" 1ec1633c]:
 {{{
 #!CommitTicketReference repository=""
 revision="1ec1633cb294d8ce2a65ece6b56c258483596fba"
 Fixed #26401 -- Added BaseAuthConfig to use auth without migrations.
 }}}

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

Re: [Django] #26524: Change foreign key id list_display reference to display only the id

2016-09-10 Thread Django

* has_patch: 1 => 0
* version: 1.9 => master
* severity: Normal => Release blocker

Comment:

This caused a regression in using a `ManyToManyField` in
`ModelAdmin.readonly_fields`. I'm attaching a regression test that passes
on the stable/1.10.x branch. The `{% include %}` in the admin template
started silently failing in the commit for this ticket and then in
331ca5391eb64cbac3a001209257beb93522d587, that silent failure become an
exception because of the deprecation warning. Fixing this will also fix
the two selenium test failures that use the `Pizza` admin.

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

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

Re: [Django] #26524: Change foreign key id list_display reference to display only the id

2016-09-10 Thread Django

#26524: Change foreign key id list_display reference to display only the id
-+-
 Reporter:  cristianocca |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  admin list_display   | Triage Stage:  Accepted
  changelist |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #27208: It does not work when using the download image ImageField via Admin since Django 1.10.1

2016-09-10 Thread Django

#27208: It does not work when using the download image ImageField via Admin 
since
Django 1.10.1
-+-
 Reporter:  evtifiev |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  1.10
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:  ImageField   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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


Comment:

 I suppose it's related or a duplicate of #27178. Do you have a default
 value for your `ImageField`?

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

[Django] #27208: It does not work when using the download image ImageField via Admin since Django 1.10.1

2016-09-10 Thread Django

#27208: It does not work when using the download image ImageField via Admin 
since
Django 1.10.1
--+
 Reporter:  evtifiev  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  File uploads/storage  |Version:  1.10
 Severity:  Normal|   Keywords:  ImageField
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Do not download pictures in the folder is registered in the model. The
 database does not store the path. This problem is observed only in version
 1.10.1, with an installed library Pillow 3.3.1. In Django version 1.10
 works.

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

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

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

2016-09-10 Thread Django

#27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with
double slash
--+
 Reporter:  andrewbadr|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.staticfiles   |  Version:  1.10
 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 andrewbadr):

 Replying to [comment:9 charettes]:
 >
 > How would you suggest we generate a manifest of you static assets
 without parsing your CSS files?

 We're getting a bit off-topic, but the current implementation would work
 even if it didn't parse or alter the contents of any CSS files. To use
 this ticket as an example, the font file without a hash in its filename
 ("CrimsonText-Bold.ttf") would load just fine. Of course, this makes
 setting caching headers a little more complicated, but then again, Django
 can't guarantee, for example, that you aren't dynamically loading some
 static assets with JavaScript. Those paths in JS would not get converted
 in the current manifest system.  What we have now is an incomplete and (to
 me, a little) surprising solution. There's a case to be made that the path
 rewriting should make it easier to distinguish altered paths from original
 ones in order to address this caching issue.

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

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

Re: [Django] #26097: UserCreationForm isn't using password_validators_help_text_html

2016-09-10 Thread Django

#26097: UserCreationForm isn't using password_validators_help_text_html
--+
 Reporter:  ataylor32 |Owner:  sasha0
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.9
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"536db42cf01ebe0dd633b131c3dbfc0bf743064f" 536db42]:
 {{{
 #!CommitTicketReference repository=""
 revision="536db42cf01ebe0dd633b131c3dbfc0bf743064f"
 Fixed #26097 -- Added password_validators_help_text_html to
 UserCreationForm.
 }}}

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

Re: [Django] #26401: Allow auth machinery to be used without installing auth app

2016-09-10 Thread Django

#26401: Allow auth machinery to be used without installing auth app
-+-
 Reporter:  satchamo |Owner:  andkon
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  auth | 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


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

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

2016-09-10 Thread Django

#27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with
double slash
--+
 Reporter:  andrewbadr|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.staticfiles   |  Version:  1.10
 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 charettes):

 > I guess I'm surprised that Django is parsing my CSS to begin with.

 How would you suggest we generate a manifest of you static assets without
 parsing your CSS files?

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

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

2016-09-10 Thread Django

#27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with
double slash
--+
 Reporter:  andrewbadr|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.staticfiles   |  Version:  1.10
 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 andrewbadr):

 Thanks, aaugustin. I guess I'm surprised that Django is parsing my CSS to
 begin with.

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

Re: [Django] #27207: Replace with tag in admin templates

2016-09-10 Thread Django

#27207: Replace  with  tag in admin templates
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admin |  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:"2d26b4637f0318736955b54b34f270fe9500f795" 2d26b46]:
 {{{
 #!CommitTicketReference repository=""
 revision="2d26b4637f0318736955b54b34f270fe9500f795"
 Fixed #27207 -- Replaced  tag with  in admin help texts.
 }}}

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

[Django] #27207: Replace with tag in admin templates

2016-09-10 Thread Django

#27207: Replace  with  tag in admin templates
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.admin |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 To allow block elements such as lists in help text (for example, password
 validators help text in #26097), replace  with  in the admin
 templates and CSS.

 It's implemented in the first commit of the
 [https://github.com/django/django/pull/6031 PR] for #26097.

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

Re: [Django] #27206: Incorrect DATE_FORMAT for et locale

2016-09-10 Thread Django

#27206: Incorrect DATE_FORMAT for et locale
--+
 Reporter:  merike|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  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 claudep):

 Wikipedia refers to http://www.eki.ee/books/ekk09/index.php?p=2=10 for
 Estonian, which confirms this report.

 It would be nice to completely review `formats.py` for Estonian, as it
 looks like partial currently.

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

Re: [Django] #27192: Allow pluralizing admin URLs

2016-09-10 Thread Django

#27192: Allow pluralizing admin URLs
---+--
 Reporter:  AlJohri|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  1.10
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by charettes):

 > The default can be changed in the next (major?) release and for new
 projects via settings.py.

 The bar to introduce new settings is pretty high as they're another global
 switches we need to account for in the test suite. As others have already
 stated I'm not convinced this is worth the additional complexity.

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

Re: [Django] #27192: Allow pluralizing admin URLs

2016-09-10 Thread Django

Comment (by AlJohri):

Replying to [comment:2 aaugustin]:
> I'm not convinced it's worth breaking every admin URL — lots of people
bookmark these — just for this reason.
>
> Also using the singular for the changelist view means that if you're on
the changeform view, you can chop off the number and get to the changelist
view. Some people do that.

I was thinking that this can just be configurable as opposed to breaking
every admin URL. The default can be changed in the next (major?) release
and for new projects via settings.py.

Wouldn't that still work? If you're on /articles/1/change/ (changeform
view) you can move to /articles/ (changelist view)?

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

Re: [Django] #24607: Serialization (and deserialization) of MTI models doesn't work with natural keys (was: dumpdata (with natural keys) / loaddata failure for model inheriting from User)

2016-09-10 Thread Django

#24607: Serialization (and deserialization) of MTI models doesn't work with 
natural
keys
--+
 Reporter:  denys-duchier |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Serialization)  |  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 charettes):

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

Re: [Django] #5711: Allow non-field attributes to be serialized (was: serialize doesn't work with extra())

2016-09-10 Thread Django

#5711: Allow non-field attributes to be serialized
--+
 Reporter:  valankar@…|Owner:  senko
 Type:  Bug   |   Status:  assigned
Component:  Core (Serialization)  |  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
--+

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

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

Re: [Django] #27205: Allow doing a substring search in JSONField array (was: Allow doing a substring search in ArrayField)

2016-09-10 Thread Django

#27205: Allow doing a substring search in JSONField array
-+-
 Reporter:  Dean-Christian-  |Owner:  nobody
  Armada |
 Type:  New feature  |   Status:  closed
Component:  contrib.postgres |  Version:  1.10
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  postgresql,  | Triage Stage:  Accepted
  arrayfield |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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


Comment:

 I'll close as duplicate of #26511 as this ticket has nothing to do with
 `ArrayField`; it's asking about allowing to perform a search against a
 `JSONField` array which is the same underlying issue as the aforementioned
 ticked.

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

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

Re: [Django] #27159: Pickling query with an __in=inner_qs lookup causes evaluation evaluation of inner_qs

2016-09-10 Thread Django

#27159: Pickling query with an __in=inner_qs lookup causes evaluation 
evaluation of
inner_qs
-+-
 Reporter:  jtiai|Owner:  jtiai
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (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 charettes):

 * needs_better_patch:  0 => 1


Comment:

 Left some comments on the 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/063.f1919024ee0599d45d21de9f5c3a86ef%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27200: router.allow_migrate without a model/hint, what is it supposed to do? Does it make sense to make that call?

2016-09-10 Thread Django

#27200: router.allow_migrate without a model/hint, what is it supposed to do? 
Does
it make sense to make that call?
-+-
 Reporter:  JBKahn   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  makemigrations,  | Triage Stage:
  router, allow_migrate  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by shaib):

 c93ac9cf42bff259ab71b70a89b693b9c38e4666 was an attempt to clarify a
 little the relationship between `makemigrations`, `migrate` and
 `allow_migrate()`. If you can suggest how and where to add better
 explanations, that could help. If you think there's a real problem here,
 requiring more than a documentation fix, please explain that.

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

Re: [Django] #27088: GEOSGeometry should accept Python 2.7 memoryview

2016-09-10 Thread Django

#27088: GEOSGeometry should accept Python 2.7 memoryview
+
 Reporter:  carljm  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  py2 | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by jtiai):

 Documentation
 
https://docs.djangoproject.com/en/1.10/ref/contrib/gis/geos/#django.contrib.gis.geos.GEOSGeometry.wkb
 at refers value type to be "Python buffer". Couldn't actually to find any
 examples where buffer is used as an input so wonder how many would be
 affected by the change.

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

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

Re: [Django] #27205: Allow doing a substring search in ArrayField (was: Django Postgres ArrayField __contain lookup does not behave expectedly)

2016-09-10 Thread Django

#27205: Allow doing a substring search in ArrayField
-+-
 Reporter:  Dean-Christian-  |Owner:  nobody
  Armada |
 Type:  New feature  |   Status:  new
Component:  contrib.postgres |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql,  | Triage Stage:  Accepted
  arrayfield |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * type:  Uncategorized => New feature
 * component:  Database layer (models, ORM) => contrib.postgres
 * 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/079.f62b2847632df47a3b5575a8af99e3fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26511: Document how to do a substring search in JSONField

2016-09-10 Thread Django

#26511: Document how to do a substring search in JSONField
--+
 Reporter:  eoinmurray|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  postgres, jsonb   | 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):

 See #27205 for the same issue as it applies to `ArrayField`.

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

Re: [Django] #27206: Incorrect DATE_FORMAT for et locale

2016-09-10 Thread Django

#27206: Incorrect DATE_FORMAT for et locale
--+
 Reporter:  merike|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  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
 * stage:  Unreviewed => Accepted
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Please send a pull request and have an Estonian colleague +1 the change
 and/or provide a reference.

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

Re: [Django] #26401: Allow auth machinery to be used without installing auth app

2016-09-10 Thread Django

#26401: Allow auth machinery to be used without installing auth app
--+
 Reporter:  satchamo  |Owner:  andkon
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  auth  | 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.d21bcecb0c48dacfb2e1170f80c5b363%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27203: Update tests that use assertQuerysetEqual lambda o: o to use assertSequenceEqual

2016-09-10 Thread Django

#27203: Update tests that use assertQuerysetEqual lambda o: o to use
assertSequenceEqual
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

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


Comment:

 [https://github.com/django/django/pull/7226 PR] but it only replaces
 `lambda o: o` and not other letters that might be used in the expression.

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

Re: [Django] #27083: Add support for weak ETags

2016-09-10 Thread Django

#27083: Add support for weak ETags
---+
 Reporter:  marfire|Owner:  marfire
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"4ef0e019b7dd3d2bf93b5c705b3b7df9cdb77561" 4ef0e019]:
 {{{
 #!CommitTicketReference repository=""
 revision="4ef0e019b7dd3d2bf93b5c705b3b7df9cdb77561"
 Fixed #27083 -- Added support for weak ETags.
 }}}

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

[Django] #27206: Incorrect DATE_FORMAT for et locale

2016-09-10 Thread Django

#27206: Incorrect DATE_FORMAT for et locale
--+
 Reporter:  merike|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Internationalization  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 https://github.com/django/django/blob/master/django/conf/locale/et/formats.py
 seems to specify
 'j F Y'
 but correct would be
 'j. F Y'
 as in Estonian dates are considered to be ordinal numbers and should be
 followed by a period.

 I'm unsure what the authoritative resource nowadays is but such date is
 grammatically wrong without a period.

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

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

2016-09-10 Thread Django

#27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with
double slash
--+
Reporter: andrewbadr|Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.staticfiles | Version: 1.10
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):

'''Regarding path normalization in general'''

I don't care either way (which I why I haven't commented). I don't mind if
sloppy coding results in exceptions. I don't mind either if we restore
some form normalization -- as long as it's done properly, unlike the
implementation I removed. Normalizing redundant slashes should only touch
the path, not the other bits of the URL. You need to parse it and
reassemble the URL.

'''Regarding this bug report'''

Based on the example shown in the report, I suspect the problem only
arises if the duplicate slash is found just after STATIC_URL, which Django
strips at some point (if memory serve). Stripping slashes on the left of
the URL just after stripping STATIC_URL could be the correct resolution
here. If so, it should be fairly easy to write a patch and a test.

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

Re: [Django] #27198: QueryDict getlist allows data to be mutated

2016-09-10 Thread Django

#27198: QueryDict getlist allows data to be mutated
---+
 Reporter:  frasern|Owner:  jtiai
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  1.10
 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 jtiai):

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

Re: [Django] #27198: QueryDict getlist allows data to be mutated

2016-09-10 Thread Django

#27198: QueryDict getlist allows data to be mutated
---+
 Reporter:  frasern|Owner:  jtiai
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  1.10
 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 jtiai):

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


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

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

Re: [Django] #27063: Regex url routing + Localization (prefix_default_language)

2016-09-10 Thread Django

#27063: Regex url routing + Localization (prefix_default_language)
--+
 Reporter:  keithhackbarth|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

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

Re: [Django] #27159: Pickling query with an __in=inner_qs lookup causes evaluation evaluation of inner_qs (was: Pickling query from queryset causes unintended queryset evaluation)

2016-09-10 Thread Django

#27159: Pickling query with an __in=inner_qs lookup causes evaluation 
evaluation of
inner_qs
-+-
 Reporter:  jtiai|Owner:  jtiai
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 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 jtiai):

 * owner:  DavidFozo => jtiai


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

Re: [Django] #26524: Change foreign key id list_display reference to display only the id

Re: [Django] #26401: Allow auth machinery to be used without installing auth app

Re: [Django] #26524: Change foreign key id list_display reference to display only the id

Re: [Django] #26524: Change foreign key id list_display reference to display only the id

Re: [Django] #27208: It does not work when using the download image ImageField via Admin since Django 1.10.1

[Django] #27208: It does not work when using the download image ImageField via Admin since Django 1.10.1

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

Re: [Django] #26097: UserCreationForm isn't using password_validators_help_text_html

Re: [Django] #26401: Allow auth machinery to be used without installing auth app

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

Re: [Django] #27207: Replace with tag in admin templates

[Django] #27207: Replace with tag in admin templates

Re: [Django] #27206: Incorrect DATE_FORMAT for et locale

Re: [Django] #27192: Allow pluralizing admin URLs

Re: [Django] #27192: Allow pluralizing admin URLs

Re: [Django] #24607: Serialization (and deserialization) of MTI models doesn't work with natural keys (was: dumpdata (with natural keys) / loaddata failure for model inheriting from User)

Re: [Django] #5711: Allow non-field attributes to be serialized (was: serialize doesn't work with extra())

Re: [Django] #27205: Allow doing a substring search in JSONField array (was: Allow doing a substring search in ArrayField)

Re: [Django] #27159: Pickling query with an __in=inner_qs lookup causes evaluation evaluation of inner_qs

Re: [Django] #27200: router.allow_migrate without a model/hint, what is it supposed to do? Does it make sense to make that call?

Re: [Django] #27088: GEOSGeometry should accept Python 2.7 memoryview

Re: [Django] #27205: Allow doing a substring search in ArrayField (was: Django Postgres ArrayField __contain lookup does not behave expectedly)

Re: [Django] #26511: Document how to do a substring search in JSONField

Re: [Django] #27206: Incorrect DATE_FORMAT for et locale

Re: [Django] #26401: Allow auth machinery to be used without installing auth app

Re: [Django] #27203: Update tests that use assertQuerysetEqual lambda o: o to use assertSequenceEqual

Re: [Django] #27083: Add support for weak ETags

[Django] #27206: Incorrect DATE_FORMAT for et locale

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

Re: [Django] #27198: QueryDict getlist allows data to be mutated

Re: [Django] #27198: QueryDict getlist allows data to be mutated

Re: [Django] #27063: Regex url routing + Localization (prefix_default_language)

Re: [Django] #27159: Pickling query with an __in=inner_qs lookup causes evaluation evaluation of inner_qs (was: Pickling query from queryset causes unintended queryset evaluation)

34 matches

Site Navigation

Mail list logo

Footer information