[Django] #29761: GIS test failures

[Django]

#29761: GIS test failures
---+
   Reporter:  Sergey Fedoseev  |  Owner:  nobody
   Type:  Uncategorized| Status:  new
  Component:  GIS  |Version:  2.1
   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|
---+
 {{{
 ==
 FAIL: test_raster_transform
 (gis_tests.gdal_tests.test_raster.GDALRasterTests)
 --
 Traceback (most recent call last):
   File "/usr/lib/python3.6/unittest/case.py", line 59, in testPartExecutor
 yield
   File "/usr/lib/python3.6/unittest/case.py", line 605, in run
 testMethod()
   File
 "/home/sergey/dev/django/tests/gis_tests/gdal_tests/test_raster.py", line
 517, in test_raster_transform
 self.assertAlmostEqual(target.origin[0], 9124842.791079799)
   File "/usr/lib/python3.6/unittest/case.py", line 878, in
 assertAlmostEqual
 raise self.failureException(msg)
 AssertionError: 9124842.791069636 != 9124842.791079799 within 7 places

 ==
 FAIL: test_transform_3d (gis_tests.geos_tests.test_geos.GEOSTest)
 --
 Traceback (most recent call last):
   File "/usr/lib/python3.6/unittest/case.py", line 59, in testPartExecutor
 yield
   File "/usr/lib/python3.6/unittest/case.py", line 605, in run
 testMethod()
   File "/home/sergey/dev/django/tests/gis_tests/geos_tests/test_geos.py",
 line 1121, in test_transform_3d
 self.assertEqual(p3d.z, 100)
   File "/usr/lib/python3.6/unittest/case.py", line 829, in assertEqual
 assertion_func(first, second, msg=msg)
   File "/usr/lib/python3.6/unittest/case.py", line 822, in
 _baseAssertEqual
 raise self.failureException(msg)
 AssertionError: 100.1595821232 != 100

 --
 }}}

 I'm using Debian testing and have libgdal20=2.3.1+dfsg-3 and
 libproj13=5.1.0-2 installed. Probably these failures are related to
 libproj.

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

Re: [Django] #29761: GIS test failures

[Django]

#29761: GIS test failures
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  Uncategorized|   Status:  assigned
Component:  GIS  |  Version:  2.1
 Severity:  Normal   |   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 Sergey Fedoseev):

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

Re: [Django] #23646: Add QuerySet.bulk_update() to to efficiently update many models

[Django]

#23646: Add QuerySet.bulk_update() to to efficiently update many models
-+-
 Reporter:  Brillgen Developers  |Owner:  Tom
 |  Forbes
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 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 Simon Charette):

 > It requires a custom join on VALUES which I'm really not sure how to
 implement. If you have any idea I'd love a point in the right direction.

 Hmm I'll have to dig into it a bit more as well but I was hoping it would
 be possible without introducing a new type of JOIN by having
 `SQLUpdateCompiler` do the heavy lifting.

 I suppose having a look at how `QuerySet.extra(tables, where)` is
 implemented could guide us towards implementing it at the `UpdateQuery`
 level though some form of JOIN.

 From my local tests it seems like we could use `UNION ALL` to replace
 `VALUES` on MySQL at least.

 {{{#!sql
 UPDATE table, (
 SELECT 1 id, 2 first, 3 second
 UNION ALL SELECT 2, 3, 4
 UNION ALL ...
 ) AS table_update
 SET table.first = table_update.first, table.second = table_update.second
 WHERE table.id IN (...) AND table.id = table_update.id
 }}}

 I haven't tested performance on SQLite and MySQL but the query seem to
 perform significantly faster (3-5x) on PostgreSQL using `VALUES()` instead
 of `CASE(WHEN)` when updating two columns on 1k rows of a table with 10k
 rows. The performance difference was getting larger as more columns were
 updated (I tried 1 to 5).

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

Re: [Django] #29760: Cursors are being closed explicitly in autocommit mode

[Django]

#29760: Cursors are being closed explicitly in autocommit mode
-+-
 Reporter:  dhargan  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  cursor, sql, | Triage Stage:
  database, autocommit,  |  Unreviewed
  transactions, postrgresql, |
  psycopg|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Duplicate of #29257?

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

Re: [Django] #29760: Cursors are being closed explicitly in autocommit mode (was: Cursors are closing explicitly in autocommit mode)

[Django]

#29760: Cursors are being closed explicitly in autocommit mode
-+-
 Reporter:  dhargan  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  cursor, sql, | Triage Stage:
  database, autocommit,  |  Unreviewed
  transactions, postrgresql, |
  psycopg|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  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/065.43ac1ab01c8036ebb7c080ebb90f9b2a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29760: Cursors are closing explicitly in autocommit mode

[Django]

#29760: Cursors are closing explicitly in autocommit mode
-+-
   Reporter:  dhargan|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.1
  layer (models, ORM)|   Keywords:  cursor, sql,
   Severity:  Normal |  database, autocommit, transactions,
   Triage Stage: |  postrgresql, psycopg
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Recently we started to get this exception time to time:

 {{{
 OperationalError: cursor “_django_curs_” does not exist
 }}}

 especially when our traffic is higher than usual. Each time the error is
 in a different line of the code so it is not easy to follow but
 appearantly it is a synchronisation issue; the cursor is being closed
 before the transaction ended.

 In django.db.models.sql.compiler.SQLAggregateCompiler:


 {{{
 def cursor_iter(cursor, sentinel, col_count, itersize):
 """
 Yield blocks of rows from a cursor and ensure the cursor is closed
 when
 done.
 """
 try:
 for rows in iter((lambda: cursor.fetchmany(itersize)), sentinel):
 yield rows if col_count is None else [r[:col_count] for r in
 rows]
 finally:
 cursor.close()
 }}}

 According to [http://initd.org/psycopg/docs/usage.html#server-side-cursors
 psycopg documentation], server-side cursors should not be closed
 explicitly if it is in autocommit mode.

 According to
 [https://docs.djangoproject.com/en/2.1/topics/db/transactions/#autocommit
 Django documentation], Django sets autocommit mode true in default
 settings.

 Of course it is possible to set withhold setting to false. In this case,
 cursor.close() must be called at the end but otherwise, according to the
 documentation, it should not be called at all.  So if I am not mistaken
 there should be a conditional statement before calling cursor.close().

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

Re: [Django] #23646: Add QuerySet.bulk_update() to to efficiently update many models

[Django]

#23646: Add QuerySet.bulk_update() to to efficiently update many models
-+-
 Reporter:  Brillgen Developers  |Owner:  Tom
 |  Forbes
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 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 Tom Forbes):

 Replying to [comment:13 Simon Charette]:
 > As mentioned on the PR I think it'd be worth investigating (in a follow
 up ticket) if we could push the primary conditional update logic to the
 compiler level (`UpdateQuery`/`SQLUpdateCompiler`) in order to use
 `VALUES` instead of `CASE(WHEN))` on backends that support it. Given this
 API is meant to be used for large number of objects I assume using
 `VALUES` would perform significantly better because it'd be easier for
 query planners to inspect the query.
 >
 > FWIW `UpdateQuery` already has an `update_batch` method used by model
 deletion but it doesn't support per-primary key values.

 Yep, in #29037 I noted that Postgres has specific syntax for it and I was
 going to open a ticket once (or if!) this is merged. I'm not sure what
 other databases support this, and I spent today looking at how to
 implement it. It requires a custom join on `VALUES` which I'm really not
 sure how to implement. If you have any idea I'd love a point in the right
 direction.

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

Re: [Django] #23646: Add QuerySet.bulk_update() to to efficiently update many models (was: Add QuerySet.bulk_save() to to efficiently update many models)

[Django]

#23646: Add QuerySet.bulk_update() to to efficiently update many models
-+-
 Reporter:  Brillgen Developers  |Owner:  Tom
 |  Forbes
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 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 Simon Charette):

 As mentioned on the PR I think it'd be worth investigating (in a follow up
 ticket) if we could push the primary conditional update logic to the
 compiler level (`UpdateQuery`/`SQLUpdateCompiler`) in order to use
 `VALUES` instead of `CASE(WHEN))` on backends that support it. Given this
 API is meant to be used for large number of objects I assume using
 `VALUES` would perform significantly better because it'd be easier for
 query planners to inspect the query.

 FWIW `UpdateQuery` already has an `update_batch` method used by model
 deletion but it doesn't support per-primary key values.

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

Re: [Django] #29757: Document that easy connect string can be used to connect to pluggable databases on Oracle.

[Django]

#29757: Document that easy connect string can be used to connect to pluggable
databases on Oracle.
-+-
 Reporter:  Jani Tiainen |Owner:  Jani
 Type:   |  Tiainen
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | 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 felixxm):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #29745: Argument based equality check of BaseExpression causes unstable migration state

[Django]

#29745: Argument based equality check of BaseExpression causes unstable 
migration
state
-+-
 Reporter:  bacilla  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  migration meta   | Triage Stage:  Accepted
  ordering expression|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * 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/068.7fc61b35b0a4b4b93e451374c1c8d651%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] #29757: Document that easy connect string can be used to connect to pluggable databases on Oracle.

[Django]

#29757: Document that easy connect string can be used to connect to pluggable
databases on Oracle.
-+-
 Reporter:  Jani Tiainen |Owner:  Jani
 Type:   |  Tiainen
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jani Tiainen):

 * has_patch:  0 => 1


Comment:

 PR: [https://github.com/django/django/pull/10393]

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

Re: [Django] #29759: Add support for cx_Oracle 7

[Django]

#29759: Add support for cx_Oracle 7
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Oracle   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"430966c2fc23eeca038b0268c995a894c4b8b154" 430966c2]:
 {{{
 #!CommitTicketReference repository=""
 revision="430966c2fc23eeca038b0268c995a894c4b8b154"
 [2.1.x] Fixed #29759 -- Fixed crash on Oracle when fetching a returned
 insert id with cx_Oracle 7.

 Backport of da92ec79621fc0bba671d8afa52b7f6884962fe5 from master
 }}}

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

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

Re: [Django] #29759: Add support for cx_Oracle 7

[Django]

#29759: Add support for cx_Oracle 7
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Oracle   | 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 GitHub ):

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


Comment:

 In [changeset:"da92ec79621fc0bba671d8afa52b7f6884962fe5" da92ec7]:
 {{{
 #!CommitTicketReference repository=""
 revision="da92ec79621fc0bba671d8afa52b7f6884962fe5"
 Fixed #29759 -- Fixed crash on Oracle when fetching a returned insert id
 with cx_Oracle 7.
 }}}

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

Re: [Django] #29757: Document that easy connect string can be used to connect to pluggable databases on Oracle.

[Django]

#29757: Document that easy connect string can be used to connect to pluggable
databases on Oracle.
-+-
 Reporter:  Jani Tiainen |Owner:  Jani
 Type:   |  Tiainen
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jani Tiainen):

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

Re: [Django] #29667: path converters don't handle spaces well.

[Django]

#29667: path converters don't handle spaces well.
-+-
 Reporter:  Keryn Knight |Owner:  Jeff
 Type:  Bug  |   Status:  assigned
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  converters path  | Triage Stage:  Accepted
  _route_to_regex|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Vishvajit Pathak):

 Tim, Adam,
 So do we want to raise `ImproperlyConfigured` when whitespace is used ?

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