Re: [Django] #29116: Geometry editing issue when widget map_srid different from original value srid

[Django]

#29116: Geometry editing issue when widget map_srid different from original 
value
srid
-+
 Reporter:  Claude Paroz |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  2.0
 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 Tim Graham):

 * stage:  Unreviewed => Accepted


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

Re: [Django] #28960: Implement GEOS.BufferWithStyle

[Django]

#28960: Implement GEOS.BufferWithStyle
-+-
 Reporter:  Stanislav Karpov |Owner:  Stanislav
 |  Karpov
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  gis, geodjango,  | Triage Stage:  Accepted
  geos   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"6d794fb76212bb8a62fe2cd97cff173054e1c626" 6d794fb7]:
 {{{
 #!CommitTicketReference repository=""
 revision="6d794fb76212bb8a62fe2cd97cff173054e1c626"
 Fixed #28960 -- Added GEOSGeometry.buffer_with_style().
 }}}

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

Re: [Django] #24747: Allow transforms in order_by

[Django]

#24747: Allow transforms in order_by
-+-
 Reporter:  Ben Buchwald |Owner:  Matthew
 |  Wilkes
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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:"2162f0983de0dfe2178531638ce7ea56f54dd4e7" 2162f09]:
 {{{
 #!CommitTicketReference repository=""
 revision="2162f0983de0dfe2178531638ce7ea56f54dd4e7"
 Fixed #24747 -- Allowed transforms in QuerySet.order_by() and
 distinct(*fields).
 }}}

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

Re: [Django] #29118: QuerySet.order_by(Exists(...)) crashes

[Django]

#29118: QuerySet.order_by(Exists(...)) crashes
-+-
 Reporter:  Raphael Gaschignard  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 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
-+-

Comment (by Tim Graham ):

 In [changeset:"9b5ba2168c737c376a85f13d15808615b21b0b3a" 9b5ba216]:
 {{{
 #!CommitTicketReference repository=""
 revision="9b5ba2168c737c376a85f13d15808615b21b0b3a"
 [2.0.x] Fixed #29118 -- Fixed crash with QuerySet.order_by(Exists(...)).

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

Re: [Django] #29118: QuerySet.order_by(Exists(...)) crashes

[Django]

#29118: QuerySet.order_by(Exists(...)) crashes
-+-
 Reporter:  Raphael Gaschignard  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"bf26f66029bca94b007a2452679ac004598364a6" bf26f66]:
 {{{
 #!CommitTicketReference repository=""
 revision="bf26f66029bca94b007a2452679ac004598364a6"
 Fixed #29118 -- Fixed crash with QuerySet.order_by(Exists(...)).
 }}}

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

Re: [Django] #29118: QuerySet.order_by(Exists(...)) crashes (was: Uncertainty in proper signature for resolve_expression method)

[Django]

#29118: QuerySet.order_by(Exists(...)) crashes
-+-
 Reporter:  Raphael Gaschignard  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 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):

 * has_patch:  0 => 1
 * stage:  Unreviewed => 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/062.d9ecd6f6eb62735e616b5d13a01ba6eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29109: `undefined` show in auto-generated datetime/time input in admin form for Thai locale

[Django]

#29109: `undefined` show in auto-generated datetime/time input in admin form for
Thai locale
-+-
 Reporter:  Napat|Owner:
  Charoenlarpkul |  Manatsawin Hanmongkolchai
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.11
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  form datetime thai   | Triage Stage:  Accepted
  locale |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"a1286b5a64bc56c3e33e53ffac0eefce76f3efdb" a1286b5a]:
 {{{
 #!CommitTicketReference repository=""
 revision="a1286b5a64bc56c3e33e53ffac0eefce76f3efdb"
 [2.0.x] Fixed #29109 -- Fixed the admin time picker widget for the Thai
 locale.

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

Re: [Django] #29109: `undefined` show in auto-generated datetime/time input in admin form for Thai locale

[Django]

#29109: `undefined` show in auto-generated datetime/time input in admin form for
Thai locale
-+-
 Reporter:  Napat|Owner:
  Charoenlarpkul |  Manatsawin Hanmongkolchai
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.11
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  form datetime thai   | Triage Stage:  Accepted
  locale |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"1a1264f1494976c562c7cb832fe47f3e1e765b8f" 1a1264f1]:
 {{{
 #!CommitTicketReference repository=""
 revision="1a1264f1494976c562c7cb832fe47f3e1e765b8f"
 Fixed #29109 -- Fixed the admin time picker widget for the Thai locale.
 }}}

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

Re: [Django] #29122: Add a better font for Persian/Farsi to the admin (was: A better font for Persian/Farsi)

[Django]

#29122: Add a better font for Persian/Farsi to the admin
-+-
 Reporter:  Mohammad Hossein |Owner:  nobody
  Mojtahedi  |
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  Persian, font,   | Triage Stage:
  Farsi  |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Tim Graham):

 * easy:  1 => 0
 * stage:  Unreviewed => Someday/Maybe


Comment:

 A possible solution is to override the `{% extrastyle %}` block of the
 `base_site.html` template to add the styles you mentioned. I'm not sure if
 there would be consensus to vendor the extra font in Django. Discussion
 for ideas like this usually happens more readily on the
 DevelopersMailingList. If you have colleagues who may have an opinion,
 please ask them to chime in.

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

Re: [Django] #27795: Audit force_text invocations

[Django]

#27795: Audit force_text invocations
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 Type:   |  Paroz
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 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:"919d59811f10f5a0101aac7b854aad5ec13d1b2a" 919d5981]:
 {{{
 #!CommitTicketReference repository=""
 revision="919d59811f10f5a0101aac7b854aad5ec13d1b2a"
 Refs #27795 -- Removed force_text() usage in django/test/testcases.py.
 }}}

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

Re: [Django] #27795: Audit force_text invocations

[Django]

#27795: Audit force_text invocations
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 Type:   |  Paroz
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 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:"1f3852b708feb2a3e20bf7a65f6cab9366cf7296" 1f3852b]:
 {{{
 #!CommitTicketReference repository=""
 revision="1f3852b708feb2a3e20bf7a65f6cab9366cf7296"
 Refs #27795 -- Removed force_bytes() usage in
 django/template/loaders/cached.py.
 }}}

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

Re: [Django] #27795: Audit force_text invocations

[Django]

#27795: Audit force_text invocations
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 Type:   |  Paroz
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 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 Jon Dufresne ):

 In [changeset:"968329b5c254fc0d77bde78f81b8bcd17655b14e" 968329b]:
 {{{
 #!CommitTicketReference repository=""
 revision="968329b5c254fc0d77bde78f81b8bcd17655b14e"
 Refs #27795 -- Replaced force_text() calls with str() in
 django.utils.html.
 }}}

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

[Django] #29122: A better font for Persian/Farsi

[Django]

#29122: A better font for Persian/Farsi
-+-
   Reporter:  Mohammad   |  Owner:  nobody
  Hossein Mojtahedi  |
   Type:  New| Status:  new
  feature|
  Component: |Version:  2.0
  contrib.admin  |   Keywords:  Persian, font,
   Severity:  Normal |  Farsi
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  1  |
-+-
 Hi,

 By every definition of design, Tahoma, Arial, Times New Roman and other
 default fonts are horrible in Persian (Farsi) script and can't be read
 properly.

 There is this fantastic font called [https://github.com/rastikerdar/vazir-
 font Vazir] which has become the industry standard in open-source fonts.

 Should we fix this in Django admin? How?

 Should it be like this:

 {{{#!css
 html[lang='fa-IR']{
 font-family: 'Vazir', tahoma, Arial !important;
 }

 html[lang='fa-IR'] code,
 html[lang='fa-IR'] pre,
 html[lang='fa-IR'] kbd{
 font-family: 'Vazir-code', "Bitstream Vera Sans Mono", Monaco,
 "Courier New", Courier, monospace; // Vazir-Code is a monospace font based
 on Vazir
 }

 }}}

 And have a @font-face block before it or a {{{}}} in HTML?

 I'm looking for an approach that considers performance, font load time,
 multilingual.

 Or even more options for the future. Maybe even a SETTING variable which
 people could easily load a font for their admin, regardless of language.

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