date:20151026

Re: [Django] #9368: Clean up code for getting columns for select query

2015-10-26 Thread Django

#9368: Clean up code for getting columns for select query
-+-
 Reporter:  adunar   |Owner:
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

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


Comment:

 There is likely more we can clean in select clause generation, but the
 main issue of this ticket (duplication of login) has been 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/064.6c12558f07473eea8cbdeb1a1675a877%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9025: Nested Inline Support in Admin

2015-10-26 Thread Django

#9025: Nested Inline Support in Admin
---+
 Reporter:  pixelcort  |Owner:  auvipy
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  Bug?   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+

Comment (by datakid):

 I can't see how I remove myself from the cc list of this ticket?

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

Re: [Django] #9025: Nested Inline Support in Admin

2015-10-26 Thread Django

Comment (by auvipy):

Replying to [comment:190 BertrandBordage]:
> **@auvipy**: You can copy a part of the work I did on django-super-
inlines and integrate it in Django if you want (as soon as you mention my
name). The Javascript part is especially valuable, it took me a lot of
time to write it from scratch in a much more readable object-oriented way.
It also fixes a few weird issues I found in the current inline code (a bug
when removing an unsaved inline after its form did not validate + an
invalid HTML generation). The Python part is a bit hacky, I tried to avoid
rewriting formsets and other sensible parts I honestly don’t master.

ok dude

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

Re: [Django] #25614: MigrationAutodetector is too greedy when ForeignKey(on_delete=...) is changed

2015-10-26 Thread Django

#25614: MigrationAutodetector is too greedy when ForeignKey(on_delete=...) is
changed
+--
 Reporter:  jdunck  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by jdunck):

 And now I've tracked it to #23288, but still think adding on_delete was
 likely unneeded.

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

Re: [Django] #25614: MigrationAutodetector is too greedy when ForeignKey(on_delete=...) is changed

2015-10-26 Thread Django

#25614: MigrationAutodetector is too greedy when ForeignKey(on_delete=...) is
changed
+--
 Reporter:  jdunck  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by jdunck):

 Here's the [https://github.com/django/django/commit/b5784048e085e8d
 commit] that introduced on_delete on ForeignKey.on_delete.Perhaps
 Andrew recalls the rationale of adding it.

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

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

[Django] #25614: MigrationAutodetector is too greedy when ForeignKey(on_delete=...) is changed

2015-10-26 Thread Django

#25614: MigrationAutodetector is too greedy when ForeignKey(on_delete=...) is
changed
--+
Reporter: jdunck | Owner: nobody
Type: Bug | Status: new
Component: Migrations |Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--+
Recently I changed the on_delete attributes of many ForeignKeys on a MySQL
database.

This resulted in an auto-detected migration that drops and recreates the
constraint for each FK, despite the effective constraint remaining the
same (e.g. FOREIGN KEY (`modified_by_id`) REFERENCES `common_user`
(`id`); )

The

[https://github.com/django/django/blob/1.8.5/django/db/migrations/autodetector.py#L848
autodetection] just compares the deconstruction.

The

[https://github.com/django/django/blob/1.8.5/django/db/backends/base/schema.py#L486
schema editor] drops the FK and recreates it.

It's not entirely clear to me which part needs to be changed - whether the
deconstruction should not include on_delete, or whether the autodetector
should discard on_delete from consideration, or whether the editor should
check for parameters that actually change the effective FK.

What is clear is that dropping and recreating FKs isn't a fast operation
on large databases, and it would be good to avoid where possible.

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

Re: [Django] #25597: Python 3 compatibility error in PostgreSQL array form fields

2015-10-26 Thread Django

#25597: Python 3 compatibility error in PostgreSQL array form fields
--+
 Reporter:  BertrandBordage   |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.8
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #25596: Can't change user's password in admin when using custom User model

2015-10-26 Thread Django

#25596: Can't change user's password in admin when using custom User model
-+-
 Reporter:  user0007 |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.9b1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #25611: Use a common descriptor signature

2015-10-26 Thread Django

#25611: Use a common descriptor signature
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"0b5d32facaa1badc0553934f6935507070cfea1b" 0b5d32fa]:
 {{{
 #!CommitTicketReference repository=""
 revision="0b5d32facaa1badc0553934f6935507070cfea1b"
 Fixed #25611 -- Standardized descriptor signatures.
 }}}

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

Re: [Django] #7623: Multi-table inheritance: Add the ability create child instance from existing parent

2015-10-26 Thread Django

#7623: Multi-table inheritance: Add the ability create child instance from
existing parent
-+-
 Reporter:  brooks.travis@…  |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  model-inheritance,   | Triage Stage:  Accepted
  multi-table-inheritance|
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * owner:  elektrrrus =>
 * status:  assigned => new


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

Re: [Django] #25438: Oracle GIS test failures for Django 1.9

2015-10-26 Thread Django

#25438: Oracle GIS test failures for Django 1.9
+
 Reporter:  timgraham   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  oracle 1.9  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Old description:

> After the patch for #24688 to add support for new-style GIS functions,
> some test failures remain:
> {{{
> gis_tests.geoapp.test_functions.GISFunctionsTests.test_difference
>
> Traceback (most recent call last):
>   File "/mnt/jenkinsdata/workspace/pull-requests-
> oracle/database/oragis11/python/python3.5/django/test/testcases.py", line
> 1093, in skip_wrapper
> return test_func(*args, **kwargs)
>   File "/mnt/jenkinsdata/workspace/pull-requests-
> oracle/database/oragis11/python/python3.5/tests/gis_tests/geoapp/test_functions.py",
> line 180, in test_difference
> self.assertEqual(c.mpoly.difference(geom), c.diff)
> AssertionError:  !=  object at 0x7f768d1df2b8>
>
> gis_tests.geoapp.test_functions.GISFunctionsTests.test_intersection
>
> Traceback (most recent call last):
>   File "/mnt/jenkinsdata/workspace/pull-requests-
> oracle/database/oragis11/python/python3.5/django/test/testcases.py", line
> 1093, in skip_wrapper
> return test_func(*args, **kwargs)
>   File "/mnt/jenkinsdata/workspace/pull-requests-
> oracle/database/oragis11/python/python3.5/tests/gis_tests/geoapp/test_functions.py",
> line 234, in test_intersection
> self.assertEqual(c.inter, expected)
> AssertionError: '' != 
>
> gis_tests.geoapp.test_functions.GISFunctionsTests.test_difference_mixed_srid
>
> Traceback (most recent call last):
>   File "/mnt/jenkinsdata/workspace/pull-requests-
> oracle/database/oragis11/python/python3.5/django/db/utils.py", line 102,
> in inner
> return func(*args, **kwargs)
>   File "/mnt/jenkinsdata/workspace/pull-requests-
> oracle/database/oragis11/python/python3.5/django/db/backends/oracle/base.py",
> line 516, in fetchmany
> return tuple(_rowfactory(r, self.cursor) for r in
> self.cursor.fetchmany(size))
> cx_Oracle.DatabaseError: ORA-13199: SRID does not exist.
> ORA-06512: at "MDSYS.MD", line 1723
> ORA-06512: at "MDSYS.MDERR", line 17
> ORA-06512: at "MDSYS.SDO_CS", line 5264
> ORA-06512: at "MDSYS.SDO_CS", line 3034
>
> gis_tests.geoapp.tests.GeoQuerySetTest.test_gml
>
> Traceback (most recent call last):
>   File "/mnt/jenkinsdata/workspace/pull-requests-
> oracle/database/oragis11/python/python3.5/django/test/testcases.py", line
> 1093, in skip_wrapper
> return test_func(*args, **kwargs)
>   File "/mnt/jenkinsdata/workspace/pull-requests-
> oracle/database/oragis11/python/python3.5/tests/gis_tests/geoapp/tests.py",
> line 635, in test_gml
> self.assertTrue(gml_regex.match(ptown.gml))
> AssertionError: None is not true
>
> gis_tests.geogapp.tests.GeographyFunctionTests.test_distance_function
>
> Traceback (most recent call last):
>   File "/mnt/jenkinsdata/workspace/pull-requests-
> oracle/database/oragis11/python/python3.5/django/test/testcases.py", line
> 1093, in skip_wrapper
> return test_func(*args, **kwargs)
>   File "/mnt/jenkinsdata/workspace/pull-requests-
> oracle/database/oragis11/python/python3.5/tests/gis_tests/geogapp/tests.py",
> line 120, in test_distance_function
> self.assertAlmostEqual(z.distance.m, ref, 2)
> AssertionError: 4899.67677194225 != 4891.2 within 2 places
> }}}

New description:

 After the patch for #24688 to add support for new-style GIS functions,
 some test failures remain:
 {{{
 gis_tests.geoapp.test_functions.GISFunctionsTests.test_difference

 Traceback (most recent call last):
   File "/mnt/jenkinsdata/workspace/pull-requests-
 oracle/database/oragis11/python/python3.5/django/test/testcases.py", line
 1093, in skip_wrapper
 return test_func(*args, **kwargs)
   File "/mnt/jenkinsdata/workspace/pull-requests-
 
oracle/database/oragis11/python/python3.5/tests/gis_tests/geoapp/test_functions.py",
 line 180, in test_difference
 self.assertEqual(c.mpoly.difference(geom), c.diff)
 AssertionError:  != 

 gis_tests.geoapp.test_functions.GISFunctionsTests.test_intersection

 Traceback (most recent call last):
   File "/mnt/jenkinsdata/workspace/pull-requests-
 oracle/database/oragis11/python/python3.5/django/test/testcases.py", line
 1093, in skip_wrapper
 return test_func(*args, **kwargs)
   File "/mnt/jenkinsdata/workspace/pull-requests-
 
oracle/database/oragis11/python/python3.5/tests/gis_tests/geoapp/test_functions.py",
 line 234, in test_intersection
 self.assertEqual(c.inter, expected)
 AssertionError: '' != 

 gis_tests.geoapp.test_

Re: [Django] #25427: Trying to do a full text search query on a database field (non model field), the .annotate(val=RawSQL(...)).filter(val=VAL1) doesn't work.

2015-10-26 Thread Django

#25427: Trying to do a full text search query on a database field (non model
field), the .annotate(val=RawSQL(...)).filter(val=VAL1) doesn't work.
-+-
 Reporter:  vladiibine   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by rpkilby):

 btw, it looks like the PR for #25506 more or less resolved this ticket.
 Our tests passed when using the stable/1.8.x branch.

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

Re: [Django] #25613: Transactional Cache TestCase

2015-10-26 Thread Django

#25613: Transactional Cache TestCase
---+--
 Reporter:  pykler |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Testing framework  |  Version:  1.8
 Severity:  Normal |   Resolution:  duplicate
 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 pykler):

 Yup its a duplicate! just couldn't find it when I searched

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

Re: [Django] #25613: Transactional Cache TestCase (was: Trasactional Cache TestCase)

2015-10-26 Thread Django

#25613: Transactional Cache TestCase
---+--
 Reporter:  pykler |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Testing framework  |  Version:  1.8
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 As far as I can tell, this is a duplicate of #11505. If not, please
 describe the issue and proposed solution in a bit more detail. 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/064.c7ad43273fe2bcb2c4d9d08b305549fd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

2015-10-26 Thread Django

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
---+
 Reporter:  stevejalim |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sqlite | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by lsemel):

 This is affecting us also, randomly dying during our automated tests.  It
 is entirely repeatable, but unpredictable where it will break. It happens
 both locally on our Macs (sqlite v3.7.13) and on Linux.  Upgrading to
 sqlite 3.8 just makes it worse.  It happens between tests, where Django
 tries to rollback the test transaction.

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

[Django] #25613: Trasactional Cache TestCase

2015-10-26 Thread Django

#25613: Trasactional Cache TestCase
---+
 Reporter:  pykler |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Testing framework  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 TLDR; Having the cache backend refresh much like databases would make life
 a lot easier

 Caching is truly awful in django and testing custom cache mixins are hard.
 The exact problem I am having is a mix of `make_middleware_decorator` +
 `FetchFromCacheMiddleware` which i used to create a CacheMixin for
 selective caching, to be used alongside UpdateCacheMiddleware (which I
 also had to override so it doesn't vary on google analytics cookies and
 what not). This is starting to be more about why Caching logged in content
 is problematic in django rather than the feature request.

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

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

Re: [Django] #8065: Calling queyset.in_bulk (without any arguments) should evaluate the whole queryset.

2015-10-26 Thread Django

#8065: Calling queyset.in_bulk (without any arguments) should evaluate the whole
queryset.
-+-
 Reporter:  ElliottM |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  in_bulk filter list  | 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):

 * easy:  0 => 1


Comment:

 Marking as "Easy pickings" since it looks to me like updating this patch
 shouldn't be too difficult. Check it with the PatchReviewChecklist.

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

Re: [Django] #9025: Nested Inline Support in Admin

2015-10-26 Thread Django

Comment (by BertrandBordage):

**@auvipy**: You can copy a part of the work I did on django-super-inlines
and integrate it in Django if you want (as soon as you mention my name).
The Javascript part is especially valuable, it took me a lot of time to
write it from scratch in a much more readable object-oriented way. It also
fixes a few weird issues I found in the current inline code (a bug when
removing an unsaved inline after its form did not validate + an invalid
HTML generation). The Python part is a bit hacky, I tried to avoid
rewriting formsets and other sensible parts I honestly don’t master.

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

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

Re: [Django] #25611: Use a common descriptor signature

2015-10-26 Thread Django

#25611: Use a common descriptor signature
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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

Re: [Django] #9025: Nested Inline Support in Admin

2015-10-26 Thread Django

#9025: Nested Inline Support in Admin
---+
 Reporter:  pixelcort  |Owner:  auvipy
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  Bug?   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+
Changes (by auvipy):

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

Re: [Django] #9976: Generic Foreign Keys should have a nice widget(ala raw_id)

2015-10-26 Thread Django

#9976: Generic Foreign Keys should have a nice widget(ala raw_id)
-+-
 Reporter:  Alex |Owner:  auvipy
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  design_ux| Triage Stage:  Accepted
  raw_id_fields  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by auvipy):

 * owner:  Alex => auvipy
 * version:  1.0 => 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/062.b39c33f38e1cfb2f4eb6d2687c8a2e65%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #11560: let proxy models multiple-inherit from the same concrete base model

2015-10-26 Thread Django

#11560: let proxy models multiple-inherit from the same concrete base model
-+-
 Reporter:  rfk  |Owner:  auvipy
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by auvipy):

 * status:  new => assigned
 * owner:  nobody => auvipy
 * version:  1.1-beta => 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/061.06d1d751728074c1855b1c7ab37a7bc3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25610: url template tag ignores request.current_app

2015-10-26 Thread Django

#25610: url template tag ignores request.current_app
-+-
 Reporter:  knbk |Owner:  knbk
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 Indeed that's what my
 
[https://github.com/django/django/commit/5e450c52aafb62b9d83c8ac08892e0b92cbec4aa
 #diff-45fa5fdd90e8a31a18a1e55ec2f94fa3L441 original instructions] said.
 Sorry, I missed that when reviewing
 5e450c52aafb62b9d83c8ac08892e0b92cbec4aa.

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

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

Re: [Django] #18201: smallint and tinyint fields + auto increment

2015-10-26 Thread Django

#18201: smallint and tinyint fields + auto increment
-+-
 Reporter:  michael.frere@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 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):

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


Comment:

 I believe this is a duplicate of #13774 -- Add model `Field.rel_db_type()`
 method.

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

Re: [Django] #24979: Remove usage of inspect.getargspec()

2015-10-26 Thread Django

#24979: Remove usage of inspect.getargspec()
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"6b631b5c0bd88f7868308b966e8117b8da335669" 6b631b5c]:
 {{{
 #!CommitTicketReference repository=""
 revision="6b631b5c0bd88f7868308b966e8117b8da335669"
 [1.8.x] Refs #24979 -- Used inspect.getargspec() on Python 3.2.

 inspect.signature() was added in Python 3.3.
 }}}

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

Re: [Django] #25612: django.contrib.auth should include support for 2fa out of the box

2015-10-26 Thread Django

#25612: django.contrib.auth should include support for 2fa out of the box
--+-
 Reporter:  alex  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by timgraham):

 * stage:  Unreviewed => Someday/Maybe


Comment:

 [https://groups.google.com/d/topic/django-
 developers/T-kBSvry6z0/discussion django-developers] discussion.

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

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

[Django] #25612: django.contrib.auth should include support for 2fa out of the box

2015-10-26 Thread Django

#25612: django.contrib.auth should include support for 2fa out of the box
+
   Reporter:  alex  |  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  contrib.auth  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Django did a tremendous service to its users by making strong password
 hashing be the default. The world is pushing forward, and now 2fa is the
 next standard that many sites fail to meet.

 Django should include support for 2fa out of the box, ideally with support
 for both u2f and TOTP (Google Authenticator).

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

Re: [Django] #25611: Use a common descriptor signature

2015-10-26 Thread Django

#25611: Use a common descriptor signature
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  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
--+
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

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

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

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

[Django] #25611: Use a common descriptor signature

2015-10-26 Thread Django

#25611: Use a common descriptor signature
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Currently we have [https://github.com/django/django/pull/5226 several
 different signatures] for descriptor methods `__get__()` and `__set__()`:

 Curtis proposed:

 * "instance_type" is explicit
 * "cls" is a common convention for passing a class
 * "owner" is in the docs {but so are others}
 * and "type" I think is a bit confusing...

 So... my preference, upon reflection, would be: `def __get__(self,
 instance, cls=None)`

 This got several +1s [https://groups.google.com/forum/#!topic/django-
 developers/3eSHhZUzxv4 on the mailing list].

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

Re: [Django] #24244: Document contrib.admin.models.LogEntry

2015-10-26 Thread Django

#24244: Document contrib.admin.models.LogEntry
--+-
 Reporter:  timgraham |Owner:  sholleman
 Type:  New feature   |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+-

Comment (by alexmorozov):

 @sholleman, won't you mind if I'll take this ticket?

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

Re: [Django] #25609: Add a more useful error message for invalid nested lookup on a related field

2015-10-26 Thread Django

#25609: Add a more useful error message for invalid nested lookup on a related
field
-+-
 Reporter:  Ian-Foote|Owner:  Ian-Foote
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (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 timgraham):

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

Re: [Django] #25610: url template tag ignores request.current_app

2015-10-26 Thread Django

#25610: url template tag ignores request.current_app
-+-
 Reporter:  knbk |Owner:  knbk
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"34af2bc523321da828a02bcf8f225ec393ed75cf" 34af2bc5]:
 {{{
 #!CommitTicketReference repository=""
 revision="34af2bc523321da828a02bcf8f225ec393ed75cf"
 Fixed #25610 -- Reverted removal of request.current_app in {% url %} tag.

 The deprecation removal in 5e450c52aafb62b9d83c8ac08892e0b92cbec4aa
 removed too much.
 }}}

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

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

Re: [Django] #25606: Add support for "__" lookup in RelatedOnlyFieldListFilter (was: field_paths do not work in list_filter when using RelatedOnlyFieldListFilter)

2015-10-26 Thread Django

#25606: Add support for "__" lookup in RelatedOnlyFieldListFilter
---+
 Reporter:  quarkness  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

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


Comment:

 The [https://github.com/django/django/pull/5479 PR] from duplicate ticket
 #25608 also lacks 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.cb07c8ccd177e6d1e5c911ab24fb1f7a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25608: Add support for "__" lookup in RelatedOnlyFieldListFilter

2015-10-26 Thread Django

#25608: Add support for  "__" lookup in RelatedOnlyFieldListFilter
---+-
 Reporter:  jack-cvr   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by timgraham):

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


Comment:

 Duplicate of #25606

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

Re: [Django] #24979: Remove usage of inspect.getargspec()

2015-10-26 Thread Django

#24979: Remove usage of inspect.getargspec()
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"e2ea30c4403fca1b0a2032aae7a783f8705fc08b" e2ea30c]:
 {{{
 #!CommitTicketReference repository=""
 revision="e2ea30c4403fca1b0a2032aae7a783f8705fc08b"
 [1.8.x] Fixed #24979 -- Removed usage of inspect.getargspec().

 Backport of 3872a33132a4bb6aa22b237927597bbfdf6f21d7 from master
 }}}

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

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

Re: [Django] #23763: Python 3.5 compatibility

2015-10-26 Thread Django

#23763: Python 3.5 compatibility
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"2a36a9bb15f0f1dee66a52f5fe7e0de57a6bd2e1" 2a36a9bb]:
 {{{
 #!CommitTicketReference repository=""
 revision="2a36a9bb15f0f1dee66a52f5fe7e0de57a6bd2e1"
 [1.8.x] Refs #23763 -- Fixed Python 3.5 PendingDeprecationWarning in
 LazyStream.

 Fixed "PendingDeprecationWarning: generator
 'LazyStream.read..parts'
 raised StopIteration" per PEP 0479.

 Backport of 3f2de803181ca3c5526ec9d708b2098b8f683808 from master
 }}}

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

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

Re: [Django] #23763: Python 3.5 compatibility

2015-10-26 Thread Django

#23763: Python 3.5 compatibility
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"95b1ae76ba23367146824188d07bcb0141fed69a" 95b1ae76]:
 {{{
 #!CommitTicketReference repository=""
 revision="95b1ae76ba23367146824188d07bcb0141fed69a"
 [1.8.x] Refs #23763 -- Fixed SMTPServer Python 3.5 deprecation warning in
 mail test.

 Backport of 7d97c5745e420e3edc22965a2c68c8c9d2eab374 from master
 }}}

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

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

Re: [Django] #25608: Add support for "" lookup in RelatedOnlyFieldListFilter (was: RelatedOnlyFieldListFilter with "" lookup)

2015-10-26 Thread Django

#25608: Add support for  "__" lookup in RelatedOnlyFieldListFilter
---+
 Reporter:  jack-cvr   |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:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted
 * needs_tests:   => 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/066.52199a5671b2d7b975582d30d75e20d9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25610: url template tag ignores request.current_app

2015-10-26 Thread Django

#25610: url template tag ignores request.current_app
-+-
 Reporter:  knbk |Owner:  knbk
 Type:  Bug  |   Status:  assigned
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #25610: url template tag ignores request.current_app

2015-10-26 Thread Django

#25610: url template tag ignores request.current_app
-+--
 Reporter:  knbk |Owner:  knbk
 Type:  Bug  |   Status:  assigned
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by knbk):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/5481

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

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

[Django] #25610: url template tag ignores request.current_app

2015-10-26 Thread Django

#25610: url template tag ignores request.current_app
-+
 Reporter:  knbk |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (URLs)  |Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 The commit that removed `context.current_app`
 (5e450c52aafb62b9d83c8ac08892e0b92cbec4aa) inadvertently removed the use
 of `context.request.current_app` as well. The latter should remain as a
 way to explicitly override the namespace that is used to reverse the 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/047.b86e9d922cdf1a577c26844580426877%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25610: url template tag ignores request.current_app

2015-10-26 Thread Django

#25610: url template tag ignores request.current_app
-+--
 Reporter:  knbk |Owner:  knbk
 Type:  Bug  |   Status:  assigned
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by knbk):

 * status:  new => assigned
 * cc: marten.knbk@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => knbk
 * 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/062.a3c31981f0937ebc918d794441186d23%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

42 matches

Mail list logo