Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
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:"52f6927d7fb7a4dca40afce0391d018b4c34dd6d" 52f6927]:
 {{{
 #!CommitTicketReference repository=""
 revision="52f6927d7fb7a4dca40afce0391d018b4c34dd6d"
 Refs #29738 -- Added test for serializing psycopg2's NumericRange with
 DecimalRangeField in migrations.
 }}}

-- 
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/069.acda0a807ac58e170339df8e4373bb27%40djangoproject.com.

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Jon Dufresne):

 The regression is being tracked in #30111

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

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jon Dufresne):

 * cc: jon.dufresne@… (added)


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

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

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Jon Dufresne):

 After running a bisect, I've found that this change caused a regression
 for my project. This occurs when running management commands. It looks
 like `from django.db.migrations.writer import MigrationWriter` is not safe
 at the module level when `django.setup()` is called. Here is the stack
 trace:

 {{{
 Traceback (most recent call last):
   File ".../myproject/manage.py", line 12, in 
 execute_from_command_line(sys.argv)
   File ".../django/django/core/management/__init__.py", line 381, in
 execute_from_command_line
 utility.execute()
   File ".../django/django/core/management/__init__.py", line 357, in
 execute
 django.setup()
   File ".../django/django/__init__.py", line 24, in setup
 apps.populate(settings.INSTALLED_APPS)
   File ".../django/django/apps/registry.py", line 91, in populate
 app_config = AppConfig.create(entry)
   File ".../django/django/apps/config.py", line 116, in create
 mod = import_module(mod_path)
   File "/usr/lib64/python3.7/importlib/__init__.py", line 127, in
 import_module
 return _bootstrap._gcd_import(name[level:], package, level)
   File "", line 1006, in _gcd_import
   File "", line 983, in _find_and_load
   File "", line 967, in
 _find_and_load_unlocked
   File "", line 677, in _load_unlocked
   File "", line 728, in exec_module
   File "", line 219, in
 _call_with_frames_removed
   File ".../django/django/contrib/postgres/apps.py", line 8, in 
 from django.db.migrations.writer import MigrationWriter
   File ".../django/django/db/migrations/writer.py", line 10, in 
 from django.db.migrations.loader import MigrationLoader
   File ".../django/django/db/migrations/loader.py", line 8, in 
 from django.db.migrations.recorder import MigrationRecorder
   File ".../django/django/db/migrations/recorder.py", line 9, in 
 class MigrationRecorder:
   File ".../django/django/db/migrations/recorder.py", line 22, in
 MigrationRecorder
 class Migration(models.Model):
   File ".../django/django/db/models/base.py", line 99, in __new__
 app_config = apps.get_containing_app_config(module)
   File ".../django/django/apps/registry.py", line 252, in
 get_containing_app_config
 self.check_apps_ready()
   File ".../django/django/apps/registry.py", line 135, in check_apps_ready
 raise AppRegistryNotReady("Apps aren't loaded yet.")
 django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
 }}}

 This change appears to fix it for me, but I haven't had a chance to fully
 verify its correctness or write a test.

 {{{
 diff --git a/django/contrib/postgres/apps.py
 b/django/contrib/postgres/apps.py
 index 97475de6f7..151450f4e4 100644
 --- a/django/contrib/postgres/apps.py
 +++ b/django/contrib/postgres/apps.py
 @@ -5,7 +5,6 @@ from psycopg2.extras import (
  from django.apps import AppConfig
  from django.db import connections
  from django.db.backends.signals import connection_created
 -from django.db.migrations.writer import MigrationWriter
  from django.db.models import CharField, TextField
  from django.test.signals import setting_changed
  from django.utils.translation import gettext_lazy as _
 @@ -22,6 +21,7 @@ def uninstall_if_needed(setting, value, enter,
 **kwargs):
  Undo the effects of PostgresConfig.ready() when
 django.contrib.postgres
  is "uninstalled" by override_settings().
  """
 +from django.db.migrations.writer import MigrationWriter
  if not enter and setting == 'INSTALLED_APPS' and
 'django.contrib.postgres' not in set(value):
  connection_created.disconnect(register_type_handlers)
  CharField._unregister_lookup(Unaccent)
 @@ -42,6 +42,7 @@ class PostgresConfig(AppConfig):
  verbose_name = _('PostgreSQL extensions')

  def ready(self):
 +from django.db.migrations.writer import MigrationWriter
  setting_changed.connect(uninstall_if_needed)
  # Connections may already exist before we are called.
  for conn in connections.all():
 }}}

-- 
Ticket URL: 

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
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:"7d3b3897c1d7b1ae4dfea6ae0d4f431d3e3dec1c" 7d3b3897]:
 {{{
 #!CommitTicketReference repository=""
 revision="7d3b3897c1d7b1ae4dfea6ae0d4f431d3e3dec1c"
 Refs #29738 -- Allowed registering serializers with MigrationWriter.
 }}}

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

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
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:"e192223ed996ed30fe83787efdfa7f2be6b1a2ee" e192223e]:
 {{{
 #!CommitTicketReference repository=""
 revision="e192223ed996ed30fe83787efdfa7f2be6b1a2ee"
 Fixed #29738 -- Allowed serializing psycopg2 range types in migrations.
 }}}

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

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Can Sarıgöl):

 * needs_better_patch:  1 => 0


Comment:

 [https://github.com/django/django/pull/10673 New PR] Could you review this
 last pr? i don't know why but there is a problem in "pull-requests-
 bionic/database=sqlite3,label=bionic-pr,python=python3" test. I checked in
 my local django-box and it was good.

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

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 New [https://code.djangoproject.com/ticket/29738 PR]. Still needs
 improvement. I'm not sure the general approach is suitable.

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

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Can Sarıgöl):

 When I check DateTimeTZRange, the result is like below. Is there any
 problem or does this usage make a problem?

 {{{
 >>> from psycopg2.extras import DateTimeTZRange
 >>> print(DateTimeTZRange().__class__)
 
 }}}

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

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
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
 * component:  contrib.postgres => Migrations
 * needs_tests:  1 => 0
 * easy:  1 => 0
 * needs_docs:  1 => 0
 * has_patch:  0 => 1


Comment:

 I tested the patch and noticed that while it worked for the use case in
 the ticket, it put `import psycopg2._range` in the migration rather than
 `from psycopg2.extras import DateTimeTZRange` that's in the models file.
 Maybe there's no way around that.

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

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Can Sarıgöl):

 [https://github.com/django/django/pull/10394]

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

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Can Sarıgöl):

 Can I change **serializer_factory** like this? so that all unserialized
 values can be tried to be available.


 {{{
 def serializer_factory(value):
 ...


 from django.utils.deconstruct import deconstructible
 deconstructible_value = deconstructible(
 value.__class__,
 path=value.__module__ + "." + value.__class__.__name__
 )
 value = deconstructible_value(value.__init__)
 return DeconstructableSerializer(value)

 raise ValueError(...)
 }}}

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

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Can Sarıgöl):

 * owner:  nobody => Can Sarıgöl
 * 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/069.7a7d19fe9682e09a324d0e4e9ee01123%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  grahammayer  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Description changed by Nick Pope:

Old description:

> Tried to use DateTimeTZRange(lower=None, upper=None, bounds='[)') as a
> default for a model field and get the following error when running
> 'python manage.py makemigrations':
>
> {{{
>  Traceback (most recent call last):
>   File "manage.py", line 12, in 
> execute_from_command_line(sys.argv)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/__init__.py", line 371, in
> execute_from_command_line
> utility.execute()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/__init__.py", line 365, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/base.py", line 288, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/base.py", line 335, in execute
> output = self.handle(*args, **options)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/commands/makemigrations.py", line 172, in
> handle
> self.write_migration_files(changes)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/commands/makemigrations.py", line 210, in
> write_migration_files
> migration_string = writer.as_string()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/writer.py", line 151, in as_string
> operation_string, operation_imports =
> OperationWriter(operation).serialize()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/writer.py", line 110, in serialize
> _write(arg_name, arg_value)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/writer.py", line 74, in _write
> arg_string, arg_imports = MigrationWriter.serialize(_arg_value)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/writer.py", line 279, in serialize
> return serializer_factory(value).serialize()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/serializer.py", line 203, in serialize
> return self.serialize_deconstructed(path, args, kwargs)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/serializer.py", line 90, in
> serialize_deconstructed
> arg_string, arg_imports = serializer_factory(arg).serialize()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/serializer.py", line 370, in
> serializer_factory
> "topics/migrations/#migration-serializing" % (value,
> get_docs_version())
> ValueError: Cannot serialize: DateTimeTZRange(None, None, '[)')
> }}}

New description:

 Tried to use {{{DateTimeTZRange(lower=None, upper=None, bounds='[)')}}} as
 a default for a model field and get the following error when running
 {{{python manage.py makemigrations}}}:

 {{{
  Traceback (most recent call last):
   File "manage.py", line 12, in 
 execute_from_command_line(sys.argv)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 371, in
 execute_from_command_line
 utility.execute()
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 365, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/base.py", line 335, in execute
 output = self.handle(*args, **options)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  grahammayer  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Simon Charette):

 * keywords:   => rangefield postgresql psycopg2 migrations removed


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

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
--+
 Reporter:  grahammayer   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  2.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Simon Charette):

 * keywords:  rangefield, postgresql, psycopg2, migrations =>


Old description:

> Tried to use {{{DateTimeTZRange(lower=None, upper=None, bounds='[)')}}}
> as a default for a model field and get the following error when running
> {{{python manage.py makemigrations}}}:
>
> {{{
>  Traceback (most recent call last):
>   File "manage.py", line 12, in 
> execute_from_command_line(sys.argv)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/__init__.py", line 371, in
> execute_from_command_line
> utility.execute()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/__init__.py", line 365, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/base.py", line 288, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/base.py", line 335, in execute
> output = self.handle(*args, **options)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/commands/makemigrations.py", line 172, in
> handle
> self.write_migration_files(changes)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/commands/makemigrations.py", line 210, in
> write_migration_files
> migration_string = writer.as_string()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/writer.py", line 151, in as_string
> operation_string, operation_imports =
> OperationWriter(operation).serialize()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/writer.py", line 110, in serialize
> _write(arg_name, arg_value)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/writer.py", line 74, in _write
> arg_string, arg_imports = MigrationWriter.serialize(_arg_value)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/writer.py", line 279, in serialize
> return serializer_factory(value).serialize()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/serializer.py", line 203, in serialize
> return self.serialize_deconstructed(path, args, kwargs)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/serializer.py", line 90, in
> serialize_deconstructed
> arg_string, arg_imports = serializer_factory(arg).serialize()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/serializer.py", line 370, in
> serializer_factory
> "topics/migrations/#migration-serializing" % (value,
> get_docs_version())
> ValueError: Cannot serialize: DateTimeTZRange(None, None, '[)')
> }}}

New description:

 Tried to use DateTimeTZRange(lower=None, upper=None, bounds='[)') as a
 default for a model field and get the following error when running 'python
 manage.py makemigrations':

 {{{
  Traceback (most recent call last):
   File "manage.py", line 12, in 
 execute_from_command_line(sys.argv)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 371, in
 execute_from_command_line
 utility.execute()
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 365, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/base.py", line 335, in execute
 output = self.handle(*args, **options)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  grahammayer  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  rangefield,  | Triage Stage:  Accepted
  postgresql, psycopg2, migrations   |
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Nick Pope):

 * component:  Migrations => contrib.postgres
 * needs_tests:  0 => 1
 * easy:  0 => 1
 * keywords:   => rangefield, postgresql, psycopg2, migrations
 * needs_docs:  0 => 1
 * stage:  Unreviewed => Accepted


Old description:

> Tried to use DateTimeTZRange(lower=None, upper=None, bounds='[)') as a
> default for a model field and get the following error when running
> 'python manage.py makemigrations':
>  Traceback (most recent call last):
>   File "manage.py", line 12, in 
> execute_from_command_line(sys.argv)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/__init__.py", line 371, in
> execute_from_command_line
> utility.execute()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/__init__.py", line 365, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/base.py", line 288, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/base.py", line 335, in execute
> output = self.handle(*args, **options)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/commands/makemigrations.py", line 172, in
> handle
> self.write_migration_files(changes)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/core/management/commands/makemigrations.py", line 210, in
> write_migration_files
> migration_string = writer.as_string()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/writer.py", line 151, in as_string
> operation_string, operation_imports =
> OperationWriter(operation).serialize()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/writer.py", line 110, in serialize
> _write(arg_name, arg_value)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/writer.py", line 74, in _write
> arg_string, arg_imports = MigrationWriter.serialize(_arg_value)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/writer.py", line 279, in serialize
> return serializer_factory(value).serialize()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/serializer.py", line 203, in serialize
> return self.serialize_deconstructed(path, args, kwargs)
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/serializer.py", line 90, in
> serialize_deconstructed
> arg_string, arg_imports = serializer_factory(arg).serialize()
>   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
> packages/django/db/migrations/serializer.py", line 370, in
> serializer_factory
> "topics/migrations/#migration-serializing" % (value,
> get_docs_version())
> ValueError: Cannot serialize: DateTimeTZRange(None, None, '[)')

New description:

 Tried to use {{{DateTimeTZRange(lower=None, upper=None, bounds='[)')}}} as
 a default for a model field and get the following error when running
 {{{python manage.py makemigrations}}}:

 {{{
  Traceback (most recent call last):
   File "manage.py", line 12, in 
 execute_from_command_line(sys.argv)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 371, in
 execute_from_command_line
 utility.execute()
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 365, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 

[Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
---+
   Reporter:  grahammayer  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Migrations   |Version:  2.0
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 Tried to use DateTimeTZRange(lower=None, upper=None, bounds='[)') as a
 default for a model field and get the following error when running 'python
 manage.py makemigrations':
  Traceback (most recent call last):
   File "manage.py", line 12, in 
 execute_from_command_line(sys.argv)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 371, in
 execute_from_command_line
 utility.execute()
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 365, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/base.py", line 335, in execute
 output = self.handle(*args, **options)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/commands/makemigrations.py", line 172, in
 handle
 self.write_migration_files(changes)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/core/management/commands/makemigrations.py", line 210, in
 write_migration_files
 migration_string = writer.as_string()
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/db/migrations/writer.py", line 151, in as_string
 operation_string, operation_imports =
 OperationWriter(operation).serialize()
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/db/migrations/writer.py", line 110, in serialize
 _write(arg_name, arg_value)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/db/migrations/writer.py", line 74, in _write
 arg_string, arg_imports = MigrationWriter.serialize(_arg_value)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/db/migrations/writer.py", line 279, in serialize
 return serializer_factory(value).serialize()
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/db/migrations/serializer.py", line 203, in serialize
 return self.serialize_deconstructed(path, args, kwargs)
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/db/migrations/serializer.py", line 90, in
 serialize_deconstructed
 arg_string, arg_imports = serializer_factory(arg).serialize()
   File "/home/grahammayer/logimeter/logimeter/lib/python3.6/site-
 packages/django/db/migrations/serializer.py", line 370, in
 serializer_factory
 "topics/migrations/#migration-serializing" % (value,
 get_docs_version())
 ValueError: Cannot serialize: DateTimeTZRange(None, None, '[)')

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