date:20170209

Re: [Django] #27391: Support unittest.TestCase.debug() method

2017-02-09 Thread Django

#27391: Support unittest.TestCase.debug() method
-+-
 Reporter:  Pavel Savchenko  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  unittest | Triage Stage:  Accepted
  SimpleTestCase debug   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1


Comment:

 I think the test could be a bit cleaner. I sent some edits to the PR,
 though I broke some things too.

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

Re: [Django] #27697: JSONField with blank=True is rendered as non-required field in a ModelForm

2017-02-09 Thread Django

* needs_better_patch: 0 => 1

Comment:

The behavior with a field like `data = JSONField(blank=True)` still seems
confusing. It renders "null" in an initial form but then creates a "This
field is required." error if you try to save that. Before this PR, a value
of `{}` could be saved with such a field, but now it gives "This field is
required." for that input. Is this what you expected? If so, perhaps some
documentation clarification is in order as this doesn't seem intuitive.

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

Re: [Django] #20238: Support multiple open connections in LiveServerTestCase

2017-02-09 Thread Django

#20238: Support multiple open connections in LiveServerTestCase
---+
 Reporter:  jwxiao@…   |Owner:  Nadege
 Type:  New feature|   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 Tim Graham ):

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


Comment:

 In [changeset:"bece837829eafbc22f2598dadf82c9a8364b085a" bece8378]:
 {{{
 #!CommitTicketReference repository=""
 revision="bece837829eafbc22f2598dadf82c9a8364b085a"
 Fixed #20238 -- Added threading support to LiveServerTestCase.
 }}}

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

Re: [Django] #22669: bulk_create with empty model fields fails on oracle

2017-02-09 Thread Django

#22669: bulk_create with empty model fields fails on oracle
-+-
 Reporter:  sns1081@…|Owner:  Michael
 |  Nacharov
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
  QuerySet.bulk_create   |  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:"c4e2fc5d9872c9a0c9c052a2e124f8a9b87de9b4" c4e2fc5d]:
 {{{
 #!CommitTicketReference repository=""
 revision="c4e2fc5d9872c9a0c9c052a2e124f8a9b87de9b4"
 Fixed #22669 -- Fixed QuerySet.bulk_create() with empty model fields on
 Oracle.
 }}}

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

Re: [Django] #25898: test database creation on Oracle mistakes privilege error for existing database

2017-02-09 Thread Django

#25898: test database creation on Oracle mistakes privilege error for existing
database
-+-
 Reporter:  JorisBenschop|Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  oracle test  | 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:"965f678a39b79f8e0bdc8222df094916fd7f8ed4" 965f678a]:
 {{{
 #!CommitTicketReference repository=""
 revision="965f678a39b79f8e0bdc8222df094916fd7f8ed4"
 Fixed #25898 -- Made test database/user creation on Oracle reraise
 unexpected errors.

 Thanks Shai Berger and Tim Graham for review.
 }}}

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

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

Re: [Django] #24977: Template variables with a value of None are considered to be == to non-existent properties

2017-02-09 Thread Django

#24977: Template variables with a value of None are considered to be == to non-
existent properties
-+-
 Reporter:  Daniel Quinn |Owner:  Tim
 Type:   |  Martin
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  string, if,  | Triage Stage:  Accepted
  equivalence|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Martin):

 * needs_better_patch:  1 => 0


Comment:

 Thanks for the feedback, I've improved the 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/069.f1fba839d4522925903516548ec6194d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13295: Add a Meta.sequence option to models

2017-02-09 Thread Django

#13295: Add a Meta.sequence option to models
-+-
 Reporter:  Max Shabalihin   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sequence last_id | Triage Stage:  Accepted
  postgresql |
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Jadson Ribeiro):

 I wonder if there is already a solution after so many years for this
 problem?

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

Re: [Django] #27819: Display a warning when django.views.generic.ListView assumes the default template name

2017-02-09 Thread Django

#27819: Display a warning when django.views.generic.ListView assumes the default
template name
--+
 Reporter:  Maker Bajax   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Generic views |  Version:  1.8
 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 Tim Graham):

 * stage:  Unreviewed => Accepted


Comment:

 Accepting for further thought, though I'm not sure if anything can be
 done.

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

Re: [Django] #27813: BinaryField type inconsistent between sqlite3 (bytes) and postgresql (memoryview) (was: BinaryField is inconsistent between sqlite3 and postgresql)

2017-02-09 Thread Django

#27813: BinaryField type inconsistent between sqlite3 (bytes) and postgresql
(memoryview)
-+-
 Reporter:  Antonio Terceiro |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Cleanup/optimization


Comment:

 Django's test suite is also
 
[https://github.com/django/django/blob/e124d2da94cc1233729d8f0200809589f6c5afc8/tests/model_fields/test_binaryfield.py#L16
 casting to bytes] for comparison. Accepting for further investigation.

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

Re: [Django] #27820: RequestDataTooBig/TooManyFields fail to render the debug page (was: response_for_exception triggers 500 when exc is RequestDataTooBig)

2017-02-09 Thread Django

#27820: RequestDataTooBig/TooManyFields fail to render the debug page
-+-
 Reporter:  Amalia Souček|Owner:  Amalia
 |  Souček
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  DATA_UPLOAD_MAX_MEMORY_SIZE,   |
  RequestDataTooBig, |
  response_for_exception, 500|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * component:  Core (Other) => HTTP handling
 * stage:  Unreviewed => Accepted


Comment:

 I'm not certain if the fix is in the best spot. It looks like the issue
 also affects `TooManyFields`.

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

Re: [Django] #24028: Related instance caching causes abstraction leaks from Field.get_db_prep_save

2017-02-09 Thread Django

#24028: Related instance caching causes abstraction leaks from
Field.get_db_prep_save
-+-
 Reporter:  Jeremy Dunck |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 #27825 was a duplicate.

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

Re: [Django] #27825: ORM Object constructor does not cast types of it's attributes when called by reference

2017-02-09 Thread Django

#27825: ORM Object constructor does not cast types of it's attributes when
called
by reference
---+--
Reporter: Oleg Belousov |Owner: nobody
Type: Bug| Status: closed
Component: Testing framework | Version: 1.10
Severity: Normal | Resolution: duplicate
Keywords: ORM| Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 |UI/UX: 0
---+--
Changes (by Tim Graham):

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

Comment:

Your proposal is a duplicate of the proposal in #24028: "a flag to
`Model.save` which updates field attributes to the result of
`Field.to_python(value)`". As I said in that ticket, we could document the
current behavior if there's no consensus to change it. I think making this
casting behavior mandatory would probably have unacceptable performance
consequences for little benefit considering that it's a reasonable
expectation for developers to provide the correct type.

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

Re: [Django] #27825: ORM Object constructor does not cast types of it's attributes when called by reference

2017-02-09 Thread Django

#27825: ORM Object constructor does not cast types of it's attributes when 
called
by reference
---+--
 Reporter:  Oleg Belousov  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords:  ORM| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Oleg Belousov):

 Failing TestCase:

 {{{
 class Payment(models.Model):
  amount_cash = models.DecimalField(max_digits=6, decimal_places=2)
 }}}

 {{{

 from decimal import Decimal
 class TestSave(unittest.TestCase):
 def test_cast_on_save(self):
 data = {'amount_cash': 12.34}
 instance = Payment(**data)
 instance.save()
 self.assertIsInstance(instance, Decimal)

def test_truncate_on_save():
 data = {'amount_cash': Decimal(12.3456)}
 instance = Payment(**data)
 instance.save()
 self.assertEqual(5, len(str(instance.amount_cash)))
 }}}

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

Re: [Django] #27825: ORM Object constructor does not cast types of it's attributes when called by reference

2017-02-09 Thread Django

#27825: ORM Object constructor does not cast types of it's attributes when 
called
by reference
---+--
 Reporter:  Oleg Belousov  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords:  ORM| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Oleg Belousov):

 * component:  Database layer (models, ORM) => Testing framework


Comment:

 Update:
 The problem is actually that the type is not being casted on 'save', and
 you have to call 'refresh_from_db' to accomplish that (is that a bug, or
 is that by design?)

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

Re: [Django] #26610: Add a citext field for contrib.postgres

2017-02-09 Thread Django

#26610: Add a citext field for contrib.postgres
-+-
 Reporter:  Shadow   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.postgres |  Version:  1.11
 Severity:  Release blocker  |   Resolution:
 Keywords:  index charfield  | Triage Stage:  Accepted
  textfield case insensitive |
  optimisation db-indexes|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  1 => 0
 * version:  master => 1.11
 * stage:  Ready for checkin => Accepted


Comment:

 Further discussion on the mailing list suggests to add a separate case-
 insensitive field for `CharField`, `TextField`, `EmailField`, etc.

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

Re: [Django] #26551: Django ORM generates invalid PostgreSQL query with Inverted Q() object that crosses relations

2017-02-09 Thread Django

#26551: Django ORM generates invalid PostgreSQL query with Inverted Q() object 
that
crosses relations
-+-
 Reporter:  Erik B. Andersen |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Q(), postgreSQL  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e124d2da94cc1233729d8f0200809589f6c5afc8" e124d2d]:
 {{{
 #!CommitTicketReference repository=""
 revision="e124d2da94cc1233729d8f0200809589f6c5afc8"
 Fixed #26551 -- Fixed negated Q() queries that span relations.

 Prevented queries from reusing trimmed joins.
 }}}

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

Re: [Django] #27825: ORM Object constructor does not cast types of it's attributes when called by reference

2017-02-09 Thread Django

#27825: ORM Object constructor does not cast types of it's attributes when 
called
by reference
-+-
 Reporter:  Oleg Belousov|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * component:  Testing framework => Database layer (models, ORM)


Comment:

 Can you simplify the description at all? I'm not sure all the `deepcopy`
 stuff is required to explain the issue. A failing test case would be more
 clear than an annotated function.

 This might be related to, or a duplicate of, #24028.

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

[Django] #27825: ORM Object constructor does not cast types of it's attributes when called by reference

2017-02-09 Thread Django

#27825: ORM Object constructor does not cast types of it's attributes when 
called
by reference
-+
   Reporter:  Oleg Belousov  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing framework  |Version:  1.10
   Severity:  Normal |   Keywords:  ORM
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 My experience is that when using the `Constructor` (`ORM`) class by
 references with Django `1.10.5`
 There might be some inconsistencies in the data (i.e. the attributes of
 the created object may get the type of the input data instead of the
 casted type of the ORM object property)

 Example:
  `models`

 {{{
  class Payment(models.Model):
  amount_cash = models.DecimalField()
 }}}


 `some_test.py` - `object.create`

 {{{
 Class SomeTestCase:
  def generate_orm_obj(self, _constructor, base_data=None,
 modifiers=None):
objs = []
   if not base_data:
base_data = {'amount_case': 123.00}
for modifier in modifiers:
 actual_data = deepcopy(base_data)
 actual_data.update(modifier)
  _obj = _constructor.objects.create(**actual_data)
 print(type(_obj.amount_cash)) # Decimal
return objs
 }}}

  `some_test.py` - `Constructor()`

 {{{
 Class SomeTestCase:
 def generate_orm_obj(self, _constructor, base_data=None,
 modifiers=None):
 objs = []
 if not base_data:
  base_data = {'amount_case': 123.00}
  for modifier in modifiers:
 actual_data = deepcopy(base_data)
 actual_data.update(modifier)
  _obj = _constructor(**actual_data)
 print(type(_obj.amount_cash)) # Float
 objs.append(_obj) return objs
 }}}

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

Re: [Django] #27367: Document behaviour when several urls have the same name

2017-02-09 Thread Django

#27367: Document behaviour when several urls have the same name
-+-
 Reporter:  Christoph Schindler  |Owner:  Robert
 Type:   |  Roskam
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #26005: uri_to_iri() perfoms percent decoding incorrectly

2017-02-09 Thread Django

#26005: uri_to_iri() perfoms percent decoding incorrectly
---+-
 Reporter:  Chronial   |Owner:  varun naganathan
 Type:  Bug|   Status:  closed
Component:  Utilities  |  Version:  1.8
 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:"03281d8fe7a32f580a85235659d4fbb143eeb867" 03281d8]:
 {{{
 #!CommitTicketReference repository=""
 revision="03281d8fe7a32f580a85235659d4fbb143eeb867"
 Fixed #26005 -- Fixed some percent decoding cases in uri_to_iri().
 }}}

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

Re: [Django] #23919: Cleanups for when we drop Python 2 compatibility

2017-02-09 Thread Django

#23919: Cleanups for when we drop Python 2 compatibility
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:
 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 Tim Graham ):

 In [changeset:"500532c95db40b0b24654be7bb0d76b66b022bd5" 500532c9]:
 {{{
 #!CommitTicketReference repository=""
 revision="500532c95db40b0b24654be7bb0d76b66b022bd5"
 Refs #23919 -- Removed default 'utf-8' argument for str.encode()/decode().
 }}}

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

Re: [Django] #23919: Cleanups for when we drop Python 2 compatibility

2017-02-09 Thread Django

#23919: Cleanups for when we drop Python 2 compatibility
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:
 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 GitHub ):

 In [changeset:"21f13ff5b3d5a42d62f38398c010efcdce30dad7" 21f13ff5]:
 {{{
 #!CommitTicketReference repository=""
 revision="21f13ff5b3d5a42d62f38398c010efcdce30dad7"
 Refs #23919 -- Removed an used block in
 ExceptionReporter.get_traceback_data().

 The test from refs #20368 only runs this block on Python 2.
 }}}

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

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

Re: [Django] #20368: MemoryError can block rendering of traceback page

2017-02-09 Thread Django

#20368: MemoryError can block rendering of traceback page
--+
 Reporter:  ironfroggy|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Template system   |  Version:  1.3
 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
--+

Comment (by GitHub ):

 In [changeset:"21f13ff5b3d5a42d62f38398c010efcdce30dad7" 21f13ff5]:
 {{{
 #!CommitTicketReference repository=""
 revision="21f13ff5b3d5a42d62f38398c010efcdce30dad7"
 Refs #23919 -- Removed an used block in
 ExceptionReporter.get_traceback_data().

 The test from refs #20368 only runs this block on Python 2.
 }}}

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

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

Re: [Django] #27822: Audit Oracle's DatabaseIntrospection.data_types_reverse

2017-02-09 Thread Django

#27822: Audit Oracle's DatabaseIntrospection.data_types_reverse
-+-
 Reporter:  Tim Graham   |Owner:  felixxm
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"1b96dbdad0f9e65bf31764aa017f411d116682fc" 1b96dbda]:
 {{{
 #!CommitTicketReference repository=""
 revision="1b96dbdad0f9e65bf31764aa017f411d116682fc"
 Fixed #27822 -- Replaced deprecated cx_Oracle types in
 DatabaseIntrospection.data_types_reverse.
 }}}

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

Re: [Django] #26936: Stale content type deletion stops working if all models in an app are deleted

2017-02-09 Thread Django

#26936: Stale content type deletion stops working if all models in an app are
deleted
--+
 Reporter:  Baptiste Mispelon |Owner:  Pavel
 Type:  Bug   |   Status:  assigned
Component:  contrib.contenttypes  |  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 Pavel):

 Updated the pull request according to code review remarks

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

Re: [Django] #27391: Support unittest.TestCase.debug() method

Re: [Django] #27697: JSONField with blank=True is rendered as non-required field in a ModelForm

Re: [Django] #20238: Support multiple open connections in LiveServerTestCase

Re: [Django] #22669: bulk_create with empty model fields fails on oracle

Re: [Django] #25898: test database creation on Oracle mistakes privilege error for existing database

Re: [Django] #24977: Template variables with a value of None are considered to be == to non-existent properties

Re: [Django] #13295: Add a Meta.sequence option to models

Re: [Django] #27819: Display a warning when django.views.generic.ListView assumes the default template name

Re: [Django] #27813: BinaryField type inconsistent between sqlite3 (bytes) and postgresql (memoryview) (was: BinaryField is inconsistent between sqlite3 and postgresql)

Re: [Django] #27820: RequestDataTooBig/TooManyFields fail to render the debug page (was: response_for_exception triggers 500 when exc is RequestDataTooBig)

Re: [Django] #24028: Related instance caching causes abstraction leaks from Field.get_db_prep_save

Re: [Django] #27825: ORM Object constructor does not cast types of it's attributes when called by reference

Re: [Django] #27825: ORM Object constructor does not cast types of it's attributes when called by reference

Re: [Django] #27825: ORM Object constructor does not cast types of it's attributes when called by reference

Re: [Django] #26610: Add a citext field for contrib.postgres

Re: [Django] #26551: Django ORM generates invalid PostgreSQL query with Inverted Q() object that crosses relations

Re: [Django] #27825: ORM Object constructor does not cast types of it's attributes when called by reference

[Django] #27825: ORM Object constructor does not cast types of it's attributes when called by reference

Re: [Django] #27367: Document behaviour when several urls have the same name

Re: [Django] #26005: uri_to_iri() perfoms percent decoding incorrectly

Re: [Django] #23919: Cleanups for when we drop Python 2 compatibility

Re: [Django] #23919: Cleanups for when we drop Python 2 compatibility

Re: [Django] #20368: MemoryError can block rendering of traceback page

Re: [Django] #27822: Audit Oracle's DatabaseIntrospection.data_types_reverse

Re: [Django] #26936: Stale content type deletion stops working if all models in an app are deleted

25 matches

Site Navigation

Mail list logo

Footer information