Re: [Django] #7018: Make ModelForm multiple inheritance possible

[Django]

#7018: Make ModelForm multiple inheritance possible
-+
 Reporter:  bear330  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  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 mitar):

 Now with Django 1.9, the approaches mentioned in this ticket do not work
 anymore, because get_declared_fields is not available anymore. What would
 be a new approach?

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

Re: [Django] #13033: MySQL full text search in admin

[Django]

#13033: MySQL full text search in admin
---+
 Reporter:  simon29|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  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 sasha0):

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


Comment:

 This is already implemented -
 
https://github.com/django/django/blob/917cc288a38f3c114a5440f0749b7e5e1086eb36/django/contrib/admin/options.py#L888.

 I believe ticket could be closed.

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

Re: [Django] #26066: Admin listview could handle a table wider than the screen more elegantly

[Django]

#26066: Admin listview could handle a table wider than the screen more elegantly
-+-
 Reporter:  chozabu  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  admin css style  | Triage Stage:  Accepted
  layout |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by sasha0):

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

Re: [Django] #26180: Altering unique_together still sometimes missing deleted fields

[Django]

#26180: Altering unique_together still sometimes missing deleted fields
---+
 Reporter:  julianandrews  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Migrations |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Bug
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

Re: [Django] #26177: Using a Postgres database with TIME_ZONE set to None and USE_TZ set to False causes an exception

[Django]

#26177: Using a Postgres database with TIME_ZONE set to None and USE_TZ set to
False causes an exception
-+-
 Reporter:  jensen-cochran   |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  postgres postgresql  | Triage Stage:  Accepted
  time zone time_zone|
  TIME_ZONE=None |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #26177: Using a Postgres database with TIME_ZONE set to None and USE_TZ set to False causes an exception

[Django]

#26177: Using a Postgres database with TIME_ZONE set to None and USE_TZ set to
False causes an exception
-+-
 Reporter:  jensen-cochran   |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  postgres postgresql  | Triage Stage:  Accepted
  time zone time_zone|
  TIME_ZONE=None |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #26175: Use create_user() managers in tests instead of hardcoding sha1 hashes

[Django]

#26175: Use create_user() managers in tests instead of hardcoding sha1 hashes
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"015fad9060a8a6fb273a33b8e8457e504ed26131" 015fad9]:
 {{{
 #!CommitTicketReference repository=""
 revision="015fad9060a8a6fb273a33b8e8457e504ed26131"
 Fixed #26175 -- Removed SHA1 password hashes in tests.
 }}}

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

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

Re: [Django] #26066: Admin listview could handle a table wider than the screen more elegantly

[Django]

#26066: Admin listview could handle a table wider than the screen more elegantly
-+-
 Reporter:  chozabu  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  admin css style  | Triage Stage:  Accepted
  layout |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by sasha0):

 Do you have a real-life example of wide admin table to test 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/065.299662a7034e905d7ba3d1c94a522760%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.