News for hackers. Stuff that matters.
Re:Django 3 by andrewgodwin on Monday December 02, 2019 @11:21AM (#21683816)
I've replied to the post on the forum, but if this is the default way Jupyter runs then we're going to have to figure something out longer-term. Calling the Django ORM from an async thread just isn't safe...
Re:Django 3 by m_ke on Monday December 02, 2019 @11:44AM (#21684076)
Thanks for the reply and all of the great work.

Using django in a notebook is definitely not a typical use case so I wouldn't worry about it too much.

Ideally the ORM would be a standalone package that could be used outside of the web server context. (I know sqlalchemy is an option but then you lose all of the benefits of django)

Re:Django 3 by aeyes on Monday December 02, 2019 @05:19PM (#21687675)
Our developers love to work in notebooks running Django, it lets you iterate extremely fast.
Re:Django 3 by m_ke on Monday December 02, 2019 @05:39PM (#21687867)
Andrew already has a PR to fix this issue https://github.com/django/django/pull/12172