Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"6014b812e2608eae1b0950eed8a5891cadc6ca77" 6014b812]:
 {{{
 #!CommitTicketReference repository=""
 revision="6014b812e2608eae1b0950eed8a5891cadc6ca77"
 [3.2.x] Refs #3 -- Fixed
 PickleabilityTestCase.test_annotation_with_callable_default() crash on
 Oracle.

 Grouping by LOBs is not allowed on Oracle. This moves a binary field to
 a separate model.
 Backport of d3a64bea51676fcf8a0ae593cf7b103939e12c87 from main
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.8b7bc6b8d3d467609793c4646f5fba92%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"7bde53a7ae7db5b97bcc3ef8eed2a7195cc0f258" 7bde53a]:
 {{{
 #!CommitTicketReference repository=""
 revision="7bde53a7ae7db5b97bcc3ef8eed2a7195cc0f258"
 [4.0.x] Refs #3 -- Fixed
 PickleabilityTestCase.test_annotation_with_callable_default() crash on
 Oracle.

 Grouping by LOBs is not allowed on Oracle. This moves a binary field to
 a separate model.
 Backport of d3a64bea51676fcf8a0ae593cf7b103939e12c87 from main
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.3100fdfa5481a7abe5f7df4caa7659ff%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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
-+-

Comment (by GitHub ):

 In [changeset:"d3a64bea51676fcf8a0ae593cf7b103939e12c87" d3a64be]:
 {{{
 #!CommitTicketReference repository=""
 revision="d3a64bea51676fcf8a0ae593cf7b103939e12c87"
 Refs #3 -- Fixed
 PickleabilityTestCase.test_annotation_with_callable_default() crash on
 Oracle.

 Grouping by LOBs is not allowed on Oracle. This moves a binary field to
 a separate model.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.972591530b6097f3fc824999a7f37456%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"cb724ef6c0fd71cd5bdbdc27c02f4da0f7e2ad08" cb724ef6]:
 {{{
 #!CommitTicketReference repository=""
 revision="cb724ef6c0fd71cd5bdbdc27c02f4da0f7e2ad08"
 [3.2.x] Fixed #3 -- Fixed setUpTestData() crash with
 models.BinaryField on PostgreSQL.

 This makes models.BinaryField pickleable on PostgreSQL.

 Regression in 3cf80d3fcf7446afdde16a2be515c423f720e54d.

 Thanks Adam Zimmerman for the report.

 Backport of 2c7846d992ca512d36a73f518205015c88ed088c from main.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.fe16ce09dabaa7f95e4627a4252b55f8%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"2c20883cb0df8c56ecbb9a093fc4252410140b59" 2c20883]:
 {{{
 #!CommitTicketReference repository=""
 revision="2c20883cb0df8c56ecbb9a093fc4252410140b59"
 [4.0.x] Fixed #3 -- Fixed setUpTestData() crash with
 models.BinaryField on PostgreSQL.

 This makes models.BinaryField pickleable on PostgreSQL.

 Regression in 3cf80d3fcf7446afdde16a2be515c423f720e54d.

 Thanks Adam Zimmerman for the report.

 Backport of 2c7846d992ca512d36a73f518205015c88ed088c from main.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.2f2de8016947df610ced5ad058a5343c%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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 GitHub ):

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


Comment:

 In [changeset:"2c7846d992ca512d36a73f518205015c88ed088c" 2c7846d]:
 {{{
 #!CommitTicketReference repository=""
 revision="2c7846d992ca512d36a73f518205015c88ed088c"
 Fixed #3 -- Fixed setUpTestData() crash with models.BinaryField on
 PostgreSQL.

 This makes models.BinaryField pickleable on PostgreSQL.

 Regression in 3cf80d3fcf7446afdde16a2be515c423f720e54d.

 Thanks Adam Zimmerman for the report.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.2e126b0a5175201c44f347a9c412d214%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  nobody => Mariusz Felisiak
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/15144 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.e7ee4f77f3abca69f7bc7fe2ac5db06a%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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 Mariusz Felisiak):

 > Should we submit a patch meant to be backported to 3.2 and 4.0 in
 setUpTestData that solely deals with this particular edge case of models
 and queryset with a BinaryField on Postgres to circumvent #27813?

 Yes, it should be feasible by juggling with `__getstate__()/__reduce__()`
 hooks 樂 I think we should treat this as a release blocker because
 `BinaryField` is built-in into Django and
 3cf80d3fcf7446afdde16a2be515c423f720e54d broke previously working tests.

 > What if we get other reports of users who ignored the deprecation
 warning for other non-pickleable objects assigned during setUpTestData?

 That would not be a release blocker, IMO, unless any other built-in is
 non-pickleable.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.588a83f97dd0a6730f4bad0830c261e7%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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 Simon Charette):

 > considering changing memoryview to bytes might have serious memory
 implications not plainly visible in tests.

 Fixing #27813 would be somewhat of a breaking change on PostgreSQL as a
 different type would be returned but I doubt it would have memory
 implications in the sense of elevated memory usage.

 In the end `memoryview` is a pointer to a sequence of bytes but these
 bytes have to live somewhere when returned from the database backend and
 made available to the client. Returning them proxied by a `memoryview`
 instance or not should not make a significant difference in memory usage
 beyond the size of the `memoryview` instance itself.

 ---

 Mariusz, how do you want to proceed here? I have to admit I'm not sure how
 to navigate the current state of things.

 Should we submit a patch meant to be backported to 3.2 and 4.0 in
 `setUpTestData` that solely deals with this particular edge case of models
 and queryset with a `BinaryField` on Postgres to circumvent #27813? What
 if we get other reports of users who ignored the deprecation warning for
 other non-pickleable objects assigned during `setUpTestData`?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.4398de57566216e3a3141843dc473445%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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 Mariusz Felisiak):

 We have also a ticket about `BinaryField` inconsistency, see #27813.

 > What about writing a workaround for setuptestData in 4.0 ...

 For me it is a 3.2 release blocker.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.a7a9c2bdd0a3a5132c84307d599d999a%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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 Simon Charette):

 Given we're pretty close to the 4.0 release date I'm not against including
 a limited hack for `setUpTestData` that special cases `Model` and
 `QuerySet` instances.

 It does feel weird that we're treating this as a release blocker now
 thought given it has been broken since `BinaryField` was introduced and
 `setUpTestData`
 
[https://github.com/django/django/commit/3cf80d3fcf7446afdde16a2be515c423f720e54d
 #diff-
 7833da5b45a68d00834388d97dd5c4413e3796497c7bc5e0cc2621b08a2d0df1R1108-R1120
 has been emitting deprecation warnings about it since Django 3.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.ccd0279f153063194cbdef5b5c0a7939%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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 Claude Paroz):

 Simon, your diagnostic might be right, but I think it's late in the 4.0
 release cycle to make such changes now, also considering changing
 `memoryview` to `bytes` might have serious memory implications not plainly
 visible in tests.

 What about writing a workaround for `setuptestData` in 4.0, and make a
 more proper and thorough fix in 4.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.23c4081b625dd448dbb5c20b78a4079b%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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 Simon Charette):

 My first instinct would be to have `BinaryField.from_db_value` use
 `force_bytes` to store `bytes` instead of `memoryview` in `_state` or
 introduce a hook to allow `Field` subclass to define a hook using during
 serialization and have the model machinery

 To me that's more of a long standing issue with `BinaryField` and less of
 a regression cause by 3cf80d3fcf7446afdde16a2be515c423f720e54d.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.26cbb57ec99d59d46213df34e22e4ca5%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL.

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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 Simon Charette):

 * stage:  Unreviewed => Accepted


Comment:

 Feels like the issue should be solved at the model level because while it
 break `setupTestData` (3cf80d3fcf7446afdde16a2be515c423f720e54d) it also
 breaks any form of `QuerySet` or `Model` pickling


 {{{#!python
 MyModel.objects.create(binary=b'y')
 pickle.dumps(MyModel.objects.all())
 }}}

 This can be reproduced by adding a `BinaryField` to
 
[https://github.com/django/django/blob/ca9872905559026af82000e46cde6f7dedc897b6/tests/queryset_pickle/models.py#L48
 models] in the test `queryset_pickle` apps.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.3630cec4d6b97ea54947bd8dd9cf869c%40djangoproject.com.

Re: [Django] #33333: Models with a BinaryField fail to deepcopy in setUpTestData() on PostgreSQL. (was: Models with a BinaryField fail to deepcopy)

[Django]

#3: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-+-
 Reporter:  Adam Zimmerman   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * cc: Simon Charette (added)
 * severity:  Normal => Release blocker


Comment:

 Thanks for the report! Regression in
 3cf80d3fcf7446afdde16a2be515c423f720e54d. I was able to reproduce this
 issue on PostgreSQL with the following test:
 {{{#!python
 class MyTests(TestCase):
 @classmethod
 def setUpTestData(cls):
 MyModel.objects.create(binary=b'y')
 cls.my_binary = MyModel.objects.get()

 def test_1(self):
 self.my_binary.binary = b'z'
 self.my_binary.save()
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.77ec18d3174df57e47e8bc04589a85c2%40djangoproject.com.