Re: [Django] #25850: Migrations ignore inconsistent history silently

[Django]

#25850: Migrations ignore inconsistent history silently
--+
 Reporter:  shaib |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Uran198):

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


Comment:

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

Re: [Django] #21454: Ignoring certain fields on INSERT and UPDATE queries

[Django]

#21454: Ignoring certain fields on INSERT and UPDATE queries
-+-
 Reporter:  mpessas  |Owner:  owais
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by owais):

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

Re: [Django] #21454: Ignoring certain fields on INSERT and UPDATE queries

[Django]

#21454: Ignoring certain fields on INSERT and UPDATE queries
-+-
 Reporter:  mpessas  |Owner:  mpessas
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by owais):

 == Update ==

 Moved the delegation logic from models closer to the code that generates
 the queries. This makes the implementation a bit more robust as most
 higher level APIs should just work without the need to update anything. It
 also allowed me to add support to querysets for delegation.

 == Field Options ==

 === `delegated=True|False` ===
 A shortcut that automatically sets the the following option to True when
 no value is provided for them.


 === `delegated_on_insert=True|False` ===
 If True, the value of this field will not be skipped from the `INSERT`
 statement completely. This automatically sets `return_on_insert` to `True`
 if not value is given. Supported on all backends.


 === `delegated_on_update=True|False` ===
 If True, the value of this field will not be skipped from the `UPDATE`
 statement completely. This automatically sets `return_on_update` to `True`
 if not value is given. Supported on all backends.


 === `return_on_insert=True|False` ===
 If True, the value for field is loaded and assigned from the database
 along with the `INSERT` statement. Supported on PostgreSQL using the
 `RETURNING` clause and Oracle using the `RETURNING INTO` clause.


 === `return_on_update=True|False` ===
 If True, the value for field is loaded and assigned from the database
 along with the `UPDATE` statement. Supported on PostgreSQL using the
 `RETURNING` clause and Oracle using the `RETURNING INTO` clause.



 == Model API Changes ==

 `save()` method now takes an optional argument called `ignore_delegated`
 which can be a list of delegated field names. This negates the behavior of
 `delegated_on_insert` and `delegated_on_update`.


 == Queryset/Manager API Changes ==

 Querysets have a new method call `ignore_delegated` which takes names of
 delegated fields as arguments and negates the behavior of
 `delegated_on_insert` and `delegated_on_update` for any subsequent
 operations. For example, if we have a delegated field called `created_at`
 on a model, we can temporarily disable delegation to DB for a single
 query.
 {{{
 class MyModel(models.Model):
  pytthon_ts = fields.DatetimeField()
  db_ts = fields.DatetimeField(delegated=True)


 # This will only update python_ts as `db_ts` is delegated to database
 MyModel.objects.update(db_ts=now(), python_ts=now())


 # However, this will update both
 MyModel.objects.ignore_delegated('db_ts').update(db_ts=now(),
 python_on=now())
 }}}

 The above example also applies to `Model.objects.create()`.

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

Re: [Django] #25878: APPEND_SLASH doesn't work with DEBUG=False when template/404.html is erroneous

[Django]

#25878: APPEND_SLASH doesn't work with DEBUG=False when template/404.html is
erroneous
-+-
 Reporter:  kuna |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  1.9
 Severity:  Release blocker  |   Resolution:
 Keywords:  slash,debug  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by pulsedemon):

 Replying to [comment:21 timgraham]:
 > Right, so with 434d309ef6dbecbfd2b322d3a1da78aa5cb05fa8 (#24720) your
 `handler404` (which is only used when `DEBUG=False`, must return a 404
 status code, otherwise `APPEND_SLASH` won't work correctly. I don't think
 this is an unreasonable requirement, but it needs to be mentioned in the
 1.9 release notes as a backwards-incompatible change (unless someone
 thinks this needs to go through a deprecation path and thus we should
 revert the original patch on 1.9). We could add logging as I mentioned in
 comment 19 to help developers find this mistake in their handler.

 I think a warning and comment about this in the release
 notes/documentation is good enough personally.  It's not unreasonable to
 expect the status_code be set manually when implementing a custom handler.

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

Re: [Django] #25922: migrate --fake-initial fails to handle ManyToManyFields created by AddField

[Django]

#25922: migrate --fake-initial fails to handle ManyToManyFields created by 
AddField
-+-
 Reporter:  tkhyn|Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.9
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  migrate, syncdb, | Triage Stage:  Ready for
  migrations |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by tkhyn):

 Thanks a lot Tim, everything seems to work perfectly now.

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

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

Re: [Django] #26025: manage.py syncdb command isn't working

[Django]

#26025: manage.py syncdb command isn't working
-+-
 Reporter:  davidmukiibi |Owner:
 |  davidmukiibi
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  manage.py, syncdb,   | Triage Stage:
  cmd|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Please see TicketClosingReasons/UseSupportChannels for ways to get help.
 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/070.0484f5786801648f41f12a4139e43b15%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26025: manage.py syncdb command isn't working

[Django]

#26025: manage.py syncdb command isn't working
-+-
 Reporter:  davidmukiibi |Owner:
 |  davidmukiibi
 Type:  Uncategorized|   Status:  assigned
Component:  Uncategorized|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  manage.py, syncdb,   | Triage Stage:
  cmd|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by davidmukiibi):

 i've tried that and its still doing the same

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

Re: [Django] #26025: manage.py syncdb command isn't working

[Django]

#26025: manage.py syncdb command isn't working
-+-
 Reporter:  davidmukiibi |Owner:
 |  davidmukiibi
 Type:  Uncategorized|   Status:  assigned
Component:  Uncategorized|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  manage.py, syncdb,   | Triage Stage:
  cmd|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by kangfend):

 Replying to [ticket:26025 davidmukiibi]:
 > when i type "manage.py syncdb" in my cmd, it opens  manage.py file in my
 text editor instead of creating tables for my models how can i fix
 that ? thanks... (am a beginner in python and django programming...)
 `manage.py syncdb` is deprecated, try to use `manage.py migrate`

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

Re: [Django] #26025: manage.py syncdb command isn't working

[Django]

#26025: manage.py syncdb command isn't working
-+-
 Reporter:  davidmukiibi |Owner:
 |  davidmukiibi
 Type:  Uncategorized|   Status:  assigned
Component:  Uncategorized|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  manage.py, syncdb,   | Triage Stage:
  cmd|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by davidmukiibi):

 * owner:  nobody => davidmukiibi
 * needs_better_patch:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[Django] #26025: manage.py syncdb command isn't working

[Django]

#26025: manage.py syncdb command isn't working
---+
 Reporter:  davidmukiibi   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:  manage.py, syncdb, cmd
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 when i type "manage.py syncdb" in my cmd, it opens  manage.py file in my
 text editor instead of creating tables for my models how can i fix
 that ? thanks... (am a beginner in python and django programming...)

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

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

Re: [Django] #26011: allow_reuse_address = 1 on WSGIServer can cause random test failures in LiveServerTestCase on Windows

[Django]

#26011: allow_reuse_address = 1 on WSGIServer can cause random test failures in
LiveServerTestCase on Windows
---+
 Reporter:  knbk   |Owner:  knbk
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by knbk):

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


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

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

Re: [Django] #26020: Standardize restructed text header convention in docs

[Django]

#26020: Standardize restructed text header convention in docs
--+
 Reporter:  timgraham |Owner:  elif
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by elif):

 I deleted the comment before seeing your answer :/.

 Ok thank you.

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

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

Re: [Django] #26020: Standardize restructed text header convention in docs

[Django]

#26020: Standardize restructed text header convention in docs
--+
 Reporter:  timgraham |Owner:  elif
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by timgraham):

 Not quite; you can remove `.. _glossary:` and if there are any links
 pointing to it, you'll update them to use `:doc:` instead of `:ref:`.

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

Re: [Django] #26020: Standardize restructed text header convention in docs

[Django]

#26020: Standardize restructed text header convention in docs
--+
 Reporter:  timgraham |Owner:  elif
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by elif):

 @timgraham
 >Note that any top level .. _ links can be removed. These are replaced
 with :doc:.

 Does that mean that I should replace "{{{.. _glossary:}}}" with
 "{{{:doc:`glossary`}}}"?

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

Re: [Django] #26023: Importing GenericForeignKey on Django 1.9

[Django]

#26023: Importing GenericForeignKey on Django 1.9
-+-
 Reporter:  Chris7   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.9
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  generic foreign  | Triage Stage:
  keys   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 You must call `django.setup()` as highlighted in the 1.7 release notes.

 https://docs.djangoproject.com/en/1.7/releases/1.7/#standalone-scripts

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

Re: [Django] #26024: ConditionalGetMiddleware's ETag is broken

[Django]

#26024: ConditionalGetMiddleware's ETag is broken
-+-
 Reporter:  samifahed|Owner:  samifahed
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  Etags| Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by samifahed):

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


Old description:

> ETag support is broken in ConditionalGetMiddleware
>
> django.utils.cache.get_conditional_response's etag argument needs to be
> *unquoted*, however the etag passed by CommonMiddleware's make_response
> is quoted or the GZipMiddleware is modifying it while keeping it quoted.

New description:

 ETag support is broken in ConditionalGetMiddleware

 django.utils.cache.get_conditional_response's etag argument needs to be
 *unquoted*, however the etag passed by CommonMiddleware's make_response is
 quoted or the GZipMiddleware is modifying it while keeping it quoted.

 Pull request with Regression Test:
 https://github.com/django/django/pull/5919

--

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

Re: [Django] #26020: Standardize restructed text header convention in docs

[Django]

#26020: Standardize restructed text header convention in docs
--+
 Reporter:  timgraham |Owner:  elif
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by elif):

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

[Django] #26024: ConditionalGetMiddleware's ETag is broken

[Django]

#26024: ConditionalGetMiddleware's ETag is broken
-+---
 Reporter:  samifahed|  Owner:  samifahed
 Type:  Bug  | Status:  new
Component:  Core (Cache system)  |Version:  1.9
 Severity:  Normal   |   Keywords:  Etags
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  0|  UI/UX:  0
-+---
 ETag support is broken in ConditionalGetMiddleware

 django.utils.cache.get_conditional_response's etag argument needs to be
 *unquoted*, however the etag passed by CommonMiddleware's make_response is
 quoted or the GZipMiddleware is modifying it while keeping it quoted.

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

Re: [Django] #21549: Fixture loading warning when the file is not found should be an exception

[Django]

#21549: Fixture loading warning when the file is not found should be an 
exception
-+-
 Reporter:  mpasternak   |Owner:  soon
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by timgraham):

 Thanks for that research. We can keep it as is.

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

Re: [Django] #21549: Fixture loading warning when the file is not found should be an exception

[Django]

#21549: Fixture loading warning when the file is not found should be an 
exception
-+-
 Reporter:  mpasternak   |Owner:  soon
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by soon):

 Replying to [comment:3 timgraham]:
 > The warning about "No fixture data found" in that same file might be
 able to be changed as well. Some tests will need to be adapted and we'll
 need a mention in the release notes.

 ''"No fixture data found"'' was an error before 2013, however it has been
 changed to a warning with [https://github.com/django/django/pull/799 PR
 #799]. Should it be implemented as error again?

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

Re: [Django] #26011: allow_reuse_address = 1 on WSGIServer can cause random test failures in LiveServerTestCase on Windows

[Django]

#26011: allow_reuse_address = 1 on WSGIServer can cause random test failures in
LiveServerTestCase on Windows
---+
 Reporter:  knbk   |Owner:  knbk
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"b551eda9c5670e70b8f4bc7569e46fc617d87ff8" b551eda]:
 {{{
 #!CommitTicketReference repository=""
 revision="b551eda9c5670e70b8f4bc7569e46fc617d87ff8"
 Refs #26011 -- Fixed AttributeError in test_port_bind 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/062.faab1c73b7f9fcd6cb4dc9568c566a76%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26023: Importing GenericForeignKey on Django 1.9

[Django]

#26023: Importing GenericForeignKey on Django 1.9
-+-
 Reporter:  Chris7   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.9
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:
 Keywords:  generic foreign  | Triage Stage:
  keys   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 I'm not sure about fixing the issue in general, but in that case I'd
 suggest dropping compatibility with Django < 1.8 since those versions are
 unsupported.

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

Re: [Django] #26023: Importing GenericForeignKey on Django 1.9

[Django]

#26023: Importing GenericForeignKey on Django 1.9
-+-
 Reporter:  Chris7   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.9
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:
 Keywords:  generic foreign  | Triage Stage:
  keys   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Chris7):

 The case is for the app [https://github.com/wooey/Wooey/ Wooey] and this
 [https://github.com/wooey/Wooey/issues/101 issue].

 We have an option that bootstraps the installation process which entails
 setting up Django project with pre-determined settings. For compatibility
 with older versions of Django, there is a compatibility shim to handle
 cases like GFK's import location being changed and the template engine's
 get_string method. So at the onset, there is no INSTALLED_APPS. It's a
 python script importing GFK. I could move these imports to another shim
 (or do some other workarounds) but this approach works in other Django
 versions -- although it could entirely be fortunate this behavior was not
 flagged.

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

Re: [Django] #26011: allow_reuse_address = 1 on WSGIServer can cause random test failures in LiveServerTestCase on Windows

[Django]

#26011: allow_reuse_address = 1 on WSGIServer can cause random test failures in
LiveServerTestCase on Windows
---+
 Reporter:  knbk   |Owner:  knbk
 Type:  Bug|   Status:  new
Component:  Testing framework  |  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 knbk):

 * has_patch:  0 => 1


Comment:

 New PR: https://github.com/django/django/pull/5918

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

Re: [Django] #26023: Importing GenericForeignKey on Django 1.9

[Django]

#26023: Importing GenericForeignKey on Django 1.9
-+-
 Reporter:  Chris7   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.9
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:
 Keywords:  generic foreign  | Triage Stage:
  keys   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Could you clarify the use case? You need to have
 `django.contrib.contentypes` in `INSTALLED_APPS`, I believe.

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

Re: [Django] #26023: Importing GenericForeignKey on Django 1.9

[Django]

#26023: Importing GenericForeignKey on Django 1.9
-+-
 Reporter:  Chris7   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.9
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:
 Keywords:  generic foreign  | Triage Stage:
  keys   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Chris7:

Old description:

> It appears it is not possible to import GenericForeignKey from outside a
> live Django project in 1.9.  To reproduce this error:
>

> {{{
> from django.conf import settings
> settings.configure()
> from django.contrib.contenttypes.fields import GenericForeignKey
> }}}
>
> Produces:
>
> {{{
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
> packages/django/contrib/contenttypes/fields.py", line 5, in 
> from django.contrib.contenttypes.models import ContentType
>   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
> packages/django/contrib/contenttypes/models.py", line 159, in 
> class ContentType(models.Model):
>   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
> packages/django/db/models/base.py", line 94, in __new__
> app_config = apps.get_containing_app_config(module)
>   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
> packages/django/apps/registry.py", line 239, in get_containing_app_config
> self.check_apps_ready()
>   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
> packages/django/apps/registry.py", line 124, in check_apps_ready
> raise AppRegistryNotReady("Apps aren't loaded yet.")
> django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
> }}}
>
> My guess is contenttypes is attempting to build the list of models, but
> failing because there is no app to initialize.

New description:

 It appears it is not possible to import GenericForeignKey from outside a
 live Django project in 1.9.  To reproduce this error:


 {{{
 from django.conf import settings
 settings.configure()
 from django.contrib.contenttypes.fields import GenericForeignKey
 }}}

 Produces:

 {{{
 Traceback (most recent call last):
   File "", line 1, in 
   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
 packages/django/contrib/contenttypes/fields.py", line 5, in 
 from django.contrib.contenttypes.models import ContentType
   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
 packages/django/contrib/contenttypes/models.py", line 159, in 
 class ContentType(models.Model):
   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
 packages/django/db/models/base.py", line 94, in __new__
 app_config = apps.get_containing_app_config(module)
   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
 packages/django/apps/registry.py", line 239, in get_containing_app_config
 self.check_apps_ready()
   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
 packages/django/apps/registry.py", line 124, in check_apps_ready
 raise AppRegistryNotReady("Apps aren't loaded yet.")
 django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
 }}}

 This seems to be occurring because ModelBase is attempting to get the app
 config, but the configuration step has not occurred.

--

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

[Django] #26023: Importing GenericForeignKey on Django 1.9

[Django]

#26023: Importing GenericForeignKey on Django 1.9
--+--
 Reporter:  Chris7|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.contenttypes  |Version:  1.9
 Severity:  Normal|   Keywords:  generic foreign keys
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 It appears it is not possible to import GenericForeignKey from outside a
 live Django project in 1.9.  To reproduce this error:


 {{{
 from django.conf import settings
 settings.configure()
 from django.contrib.contenttypes.fields import GenericForeignKey
 }}}

 Produces:

 {{{
 Traceback (most recent call last):
   File "", line 1, in 
   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
 packages/django/contrib/contenttypes/fields.py", line 5, in 
 from django.contrib.contenttypes.models import ContentType
   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
 packages/django/contrib/contenttypes/models.py", line 159, in 
 class ContentType(models.Model):
   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
 packages/django/db/models/base.py", line 94, in __new__
 app_config = apps.get_containing_app_config(module)
   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
 packages/django/apps/registry.py", line 239, in get_containing_app_config
 self.check_apps_ready()
   File "/home/chris/.virtualenvs/wooey/local/lib/python2.7/site-
 packages/django/apps/registry.py", line 124, in check_apps_ready
 raise AppRegistryNotReady("Apps aren't loaded yet.")
 django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
 }}}

 My guess is contenttypes is attempting to build the list of models, but
 failing because there is no app to initialize.

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

Re: [Django] #25316: Can't use order_by and values(_list) together after annotating

[Django]

#25316: Can't use order_by and values(_list) together after annotating
-+-
 Reporter:  adrian17 |Owner:
 |  varunnaganathan
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  annotate, order_by   | 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:"5770c2382a4ebeebaaf3c2736e3934a191265a18" 5770c23]:
 {{{
 #!CommitTicketReference repository=""
 revision="5770c2382a4ebeebaaf3c2736e3934a191265a18"
 [1.9.x] Fixed #25316 -- Fixed a crash with order_by() and values() after
 annotate().

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

Re: [Django] #25316: Can't use order_by and values(_list) together after annotating

[Django]

#25316: Can't use order_by and values(_list) together after annotating
-+-
 Reporter:  adrian17 |Owner:
 |  varunnaganathan
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  annotate, order_by   | 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:"f6b4893a9fcc3f9888491820e31c02e074d86341" f6b4893]:
 {{{
 #!CommitTicketReference repository=""
 revision="f6b4893a9fcc3f9888491820e31c02e074d86341"
 [1.8.x] Fixed #25316 -- Fixed a crash with order_by() and values() after
 annotate().

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

Re: [Django] #25316: Can't use order_by and values(_list) together after annotating

[Django]

#25316: Can't use order_by and values(_list) together after annotating
-+-
 Reporter:  adrian17 |Owner:
 |  varunnaganathan
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  annotate, order_by   | 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:"3eba9638ee69138c73efb1d1c1d1b806ddafc6cf" 3eba9638]:
 {{{
 #!CommitTicketReference repository=""
 revision="3eba9638ee69138c73efb1d1c1d1b806ddafc6cf"
 Fixed #25316 -- Fixed a crash with order_by() and values() after
 annotate().
 }}}

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

Re: [Django] #26011: allow_reuse_address = 1 on WSGIServer can cause random test failures in LiveServerTestCase on Windows

[Django]

#26011: allow_reuse_address = 1 on WSGIServer can cause random test failures in
LiveServerTestCase on Windows
---+
 Reporter:  knbk   |Owner:  knbk
 Type:  Bug|   Status:  new
Component:  Testing framework  |  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):

 * status:  closed => new
 * has_patch:  1 => 0
 * resolution:  fixed =>


Comment:

 Saw this error on Jenkins with Python 2:
 {{{
 Traceback (most recent call last):
   File "/home/jenkins/workspace/django-master-
 trusty/database/sqlite3/label/trusty/python/python2.7/tests/servers/tests.py",
 line 191, in test_port_bind
 if e.ernrno == errno.EADDRINUSE:
 AttributeError: 'error' object has no attribute 'ernrno'
 }}}

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

Re: [Django] #26016: Django 1.9 dropped compatibility with py-bcrypt (as an alternative to bcrypt)

[Django]

#26016: Django 1.9 dropped compatibility with py-bcrypt (as an alternative to
bcrypt)
--+-
 Reporter:  rhertzog  |Owner:  timgraham
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.9
 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:"2f4be218e1e6605ecbb84365d761c206c241e221" 2f4be21]:
 {{{
 #!CommitTicketReference repository=""
 revision="2f4be218e1e6605ecbb84365d761c206c241e221"
 [1.9.x] Fixed #26016 -- Restored contrib.auth hashers compatibility with
 py-bcrypt.

 Reverted "Explicitly passed rounds as rounds to bcrypt.gensalt()"

 This reverts commit 23529fb19594ffcc6ba6d716356b828157200288.

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

Re: [Django] #26016: Django 1.9 dropped compatibility with py-bcrypt (as an alternative to bcrypt)

[Django]

#26016: Django 1.9 dropped compatibility with py-bcrypt (as an alternative to
bcrypt)
--+-
 Reporter:  rhertzog  |Owner:  timgraham
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.9
 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
--+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"f0ad641628a3ddc4e1c208e481b9cd0e9304dc3d" f0ad6416]:
 {{{
 #!CommitTicketReference repository=""
 revision="f0ad641628a3ddc4e1c208e481b9cd0e9304dc3d"
 Fixed #26016 -- Restored contrib.auth hashers compatibility with py-
 bcrypt.

 Reverted "Explicitly passed rounds as rounds to bcrypt.gensalt()"

 This reverts commit 23529fb19594ffcc6ba6d716356b828157200288.
 }}}

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

Re: [Django] #25316: Can't use order_by and values(_list) together after annotating

[Django]

#25316: Can't use order_by and values(_list) together after annotating
-+-
 Reporter:  adrian17 |Owner:
 |  varunnaganathan
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  annotate, order_by   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #26016: Django 1.9 dropped compatibility with py-bcrypt (as an alternative to bcrypt)

[Django]

#26016: Django 1.9 dropped compatibility with py-bcrypt (as an alternative to
bcrypt)
--+-
 Reporter:  rhertzog  |Owner:  timgraham
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  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):

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


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

Re: [Django] #26016: Django 1.9 dropped compatibility with py-bcrypt (as an alternative to bcrypt)

[Django]

#26016: Django 1.9 dropped compatibility with py-bcrypt (as an alternative to
bcrypt)
--+
 Reporter:  rhertzog  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by funkybob):

 No, no reason... I believe the original motive was "explicit is better
 than implicit" ... a vague hope to protect ourselves against future
 prototype changes.

 Well, we spotted the change... but didn't it didn't protect us.

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

Re: [Django] #26009: contenttypes_tests fail when run in isolation

[Django]

#26009: contenttypes_tests fail when run in isolation
---+
 Reporter:  knbk   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timgraham):

 Okay, I've moved the shared tests to `base_tests.py`. There's a small
 design decision I commented about in the
 [https://github.com/django/django/pull/5915 pull request].

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

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

Re: [Django] #26008: setup() missing 1 required positional argument: 'parallel' when running runtest.py --pair or runtests.py --bisect

[Django]

#26008: setup() missing 1 required positional argument: 'parallel' when running
runtest.py --pair or runtests.py --bisect
---+
 Reporter:  knbk   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.9
 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
---+

Comment (by Tim Graham ):

 In [changeset:"151027beabc9827b72cb14326bffc594b0a13f10" 151027be]:
 {{{
 #!CommitTicketReference repository=""
 revision="151027beabc9827b72cb14326bffc594b0a13f10"
 [1.9.x] Fixed #26008 -- Added parallel argument to paired_tests and
 bisect_tests

 Backport of 0db6367fe2aa6ab3fd152eacf172d57db45c1ffb 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/062.ed664c21b72a6bddd20a1c2df8c6c3cb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26008: setup() missing 1 required positional argument: 'parallel' when running runtest.py --pair or runtests.py --bisect

[Django]

#26008: setup() missing 1 required positional argument: 'parallel' when running
runtest.py --pair or runtests.py --bisect
---+
 Reporter:  knbk   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.9
 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 Attila Tovt ):

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


Comment:

 In [changeset:"0db6367fe2aa6ab3fd152eacf172d57db45c1ffb" 0db6367f]:
 {{{
 #!CommitTicketReference repository=""
 revision="0db6367fe2aa6ab3fd152eacf172d57db45c1ffb"
 Fixed #26008 -- Added parallel argument to paired_tests and bisect_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/062.570239b3d7ca65445e9e4ffd74ba5ef9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.