date:20211003

Re: [Django] #33107: ImportError: partially initialized module '...' has no attribute '...'

2021-10-03 Thread Django

#33107: ImportError: partially initialized module '...' has no attribute '...'
-+-
 Reporter:  Collin Anderson  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  4.0
 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:"a3185a670169eb67f1ce5c774fe7af555f80163b" a3185a6]:
 {{{
 #!CommitTicketReference repository=""
 revision="a3185a670169eb67f1ce5c774fe7af555f80163b"
 Refs #33107 -- Optimized cached_import() helper.
 }}}

-- 
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/072.51b03375a82d8d57d30b15fa432e7420%40djangoproject.com.

Re: [Django] #27694: Improve documentation of supported lookups on HStore & JSON fields

2021-10-03 Thread Django

#27694: Improve documentation of supported lookups on HStore & JSON fields
-+-
 Reporter:  Stephen Burrows  |Owner:  Sarah
 Type:   |  Abderemane
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


-- 
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/066.c1c1e6617fc54e30f40e5eb77963f93b%40djangoproject.com.

Re: [Django] #27694: Improve documentation of supported lookups on HStore & JSON fields

2021-10-03 Thread Django

#27694: Improve documentation of supported lookups on HStore & JSON fields
-+-
 Reporter:  Stephen Burrows  |Owner:  Sarah
 Type:   |  Abderemane
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"51e4dbfeb24d6b3bb1df6a328f8243761dba087a" 51e4dbfe]:
 {{{
 #!CommitTicketReference repository=""
 revision="51e4dbfeb24d6b3bb1df6a328f8243761dba087a"
 [3.2.x] Refs #27694 -- Doc'd lookups that can be chained with HStoreField
 key transforms.

 Backport of 1953dd02b6719ee89fddbc3098d86968d79f3cd7 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/066.d46b0f174a13ccf0b0698548b4a59f68%40djangoproject.com.

Re: [Django] #27694: Improve documentation of supported lookups on HStore & JSON fields

2021-10-03 Thread Django

#27694: Improve documentation of supported lookups on HStore & JSON fields
-+-
 Reporter:  Stephen Burrows  |Owner:  Sarah
 Type:   |  Abderemane
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"7fa946c76b25ec84752d0ddf6d4afb0cfdc25c93" 7fa946c7]:
 {{{
 #!CommitTicketReference repository=""
 revision="7fa946c76b25ec84752d0ddf6d4afb0cfdc25c93"
 [4.0.x] Refs #27694 -- Doc'd lookups that can be chained with HStoreField
 key transforms.

 Backport of 1953dd02b6719ee89fddbc3098d86968d79f3cd7 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/066.a164f576222405fa5e4a5c4593972fc0%40djangoproject.com.

Re: [Django] #27694: Improve documentation of supported lookups on HStore & JSON fields

2021-10-03 Thread Django

#27694: Improve documentation of supported lookups on HStore & JSON fields
-+-
 Reporter:  Stephen Burrows  |Owner:  Sarah
 Type:   |  Abderemane
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"533f345c09c935ce0117f52aa124599c52ffa80b" 533f345]:
 {{{
 #!CommitTicketReference repository=""
 revision="533f345c09c935ce0117f52aa124599c52ffa80b"
 Refs #27694 -- Added more tests for chaining lookups with HStoreField key
 transforms.
 }}}

-- 
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/066.b199ef6933000dbfc60451a17935e178%40djangoproject.com.

Re: [Django] #27694: Improve documentation of supported lookups on HStore & JSON fields

2021-10-03 Thread Django

#27694: Improve documentation of supported lookups on HStore & JSON fields
-+-
 Reporter:  Stephen Burrows  |Owner:  Sarah
 Type:   |  Abderemane
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"1953dd02b6719ee89fddbc3098d86968d79f3cd7" 1953dd0]:
 {{{
 #!CommitTicketReference repository=""
 revision="1953dd02b6719ee89fddbc3098d86968d79f3cd7"
 Refs #27694 -- Doc'd lookups that can be chained with HStoreField key
 transforms.
 }}}

-- 
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/066.761efd828930171ae68c1ea0e8d36b6f%40djangoproject.com.

Re: [Django] #32888: Document that select_for_update() doesn't lock tables when their columns are not selected. (was: Using select_for_update with self as an of-argument gets dropped when only selecti

2021-10-03 Thread Django

#32888: Document that select_for_update() doesn't lock tables when their columns
are not selected.
-+-
 Reporter:  Hannes Ljungberg |Owner:  Hannes
 Type:   |  Ljungberg
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 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
-+-
Changes (by Mariusz Felisiak):

 * owner:  nobody => Hannes Ljungberg
 * status:  new => assigned
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.151aa9931965e71e20014d0e94ac55f5%40djangoproject.com.

Re: [Django] #33164: UUID URL converter should support uppercase hexadecimal digits

2021-10-03 Thread Django

#33164: UUID URL converter should support uppercase hexadecimal digits
+--
Reporter: Renato Alencar |Owner: nobody
Type: New feature | Status: closed
Component: Core (URLs) | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: uuid, url | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 |UI/UX: 0
+--
Changes (by Mariusz Felisiak):

* status: new => closed
* type: Bug => New feature
* resolution: => wontfix

Comment:

Thanks for this ticket, however this is a
[https://docs.djangoproject.com/en/3.2/topics/http/urls/#path-converters
document] and intended behavior which prevents multiple URLs from mapping
to the same page:

> `uuid` - Matches a formatted UUID. To prevent multiple URLs from mapping
to the same page, dashes must be included and **letters must be
lowercase**. For example, `075194d3-6885-417e-a8a8-6c931e272f00`. Returns
a UUID instance.

See #28883 for a related discussion.

--
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/071.6c676b5a033ed0e1e57d3d662362f0c2%40djangoproject.com.

Re: [Django] #33165: DateInput default date is not shown when localization is on

2021-10-03 Thread Django

#33165: DateInput default date is not shown when localization is on
---+--
 Reporter:  Marco Zatta|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  3.2
 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
---+--

Comment (by Tim Graham):

 This sounds like a browser issue and not Django's fault?

-- 
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.16680adc4bf225033c8417d45c15f734%40djangoproject.com.

[Django] #33166: Missing context when rendering form widgets

2021-10-03 Thread Django

#33166: Missing context when rendering form widgets
-+-
Reporter: Jacob | Owner: nobody
Rief |
Type: | Status: new
Cleanup/optimization |
Component: Forms |Version: 4.0
Severity: Normal | Keywords: form, widget,
Triage Stage: | context
Unreviewed | Has patch: 0
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-+-
Unsure if this shall be a feature request, but I noticed that when
rendering a field label, the template's rendering context additionally
contains the `field`- and the `form`-object. If however, I render the
widget itself, this information is not available inside the widget's
template rendering context. Apart from this inconsistency, being able to
access the `field`- and/or the `form`-object, when rendering a widget is
really useful.

Example:
I would like to use the `form`-attribute inside some ``-widgets,
so that each field can refer to its corresponding form. See
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-form
for details. The `form`-object itself provides a name, which is used as
the ``. Therefore each widget has to know their form's
name. This information currently can not be determined inside the widget's
template.

--
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/048.bebaf88df8eeacb4bb27ec9164a185aa%40djangoproject.com.

Re: [Django] #32948: Optimise Q combination and inversion

2021-10-03 Thread Django

#32948: Optimise Q combination and inversion
-+-
 Reporter:  Keryn Knight |Owner:  Nick Pope
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (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
-+-
Changes (by Nick Pope):

 * owner:  Keryn Knight => Nick Pope
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.87fe0d00a38ac36e4701e64e2a4c79be%40djangoproject.com.

Re: [Django] #27694: Improve documentation of supported lookups on HStore & JSON fields

2021-10-03 Thread Django

#27694: Improve documentation of supported lookups on HStore & JSON fields
-+-
 Reporter:  Stephen Burrows  |Owner:  Sarah
 Type:   |  Abderemane
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Jacob Walls):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/14930 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/066.a9ce6e0245606a63e2ef3d1132685039%40djangoproject.com.

Re: [Django] #32672: Primary Key, type double and type unsigned integer ain't detected correctly for Sqlite3 Database

2021-10-03 Thread Django

#32672: Primary Key, type double and type unsigned integer ain't detected 
correctly
for Sqlite3 Database
-+-
 Reporter:  jgr88|Owner:  Anvesh
 Type:   |  Mishra
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  SQLite3 PrimaryKey   | Triage Stage:  Accepted
  Datatypes  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Anvesh Mishra):

 So as per Charettes's comment on my PR
 https://github.com/django/django/pull/14878#discussion_r713268066, I
 implemented this issue with `sqlparse` but failed testcases one of them
 was `inspectdb.tests.InspectDBTestCase`. The change which I did was
 {{{
 method_match = sqlparse.parse(field_desc)[0]
 if method_match:
 if len(method_match.tokens) == 3 and method_match.tokens[0].value ==
 "PRIMARY":
 column_name_token = str(method_match.tokens[2])
 column_name = column_name_token[4:len(column_name_token) - 1]
 return column_name
 elif len(method_match.tokens) > 6 and method_match.tokens[6].value ==
 "PRIMARY":
 return str(method_match.tokens[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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.e3348c057751b91214c43bf22c914b2f%40djangoproject.com.

Re: [Django] #32723: Add a GitHub action to run the Sphinx linkcheck builder.

2021-10-03 Thread Django

#32723: Add a GitHub action to run the Sphinx linkcheck builder.
-+-
 Reporter:  Nick Pope|Owner:  Sarah
 Type:   |  Abderemane
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  linkcheck, github,   | Triage Stage:
  action |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Sarah Abderemane):

 Thanks Nick and Jacob for your replies. I understand better what it
 implies to do before this ticket, I'll follow up to see how it will
 involves.
 I agree, the triage stage is confusing, even more for me when I didn't
 know what it implies really. I think it will be good to have many more
 entries for better understanding for everyone.

-- 
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/065.0d2aa363944b6a39201236af68e33512%40djangoproject.com.

[Django] #33165: DateInput default date is not shown when localization is on

2021-10-03 Thread Django

#33165: DateInput default date is not shown when localization is on
-+
   Reporter:  m-zat  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Forms  |Version:  3.2
   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  |
-+
 Step to reproduce:

 - Create a Model with a date field
 - Create a ModelForm based on said model with a widget entry to make the
 date a DateInput (otherwise it is shown as text field)
 - With localization turned on set LANGUAGE='it-ch'
 - Open a webpage showing the form with {{ form }} in the template

 With 'it-ch' the default value is not shown because the value passed to
 the field is not understood by the browser (in this case '%d/%m/%Y'),
 while it is shown when using 'en-us' (in this case '%Y-%m-%d is passed)

 Expected behavior:
 The default date is shown independently of the locale selected server side

-- 
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/048.2dd9bc49602a52f6264c36b0914f1f44%40djangoproject.com.

Re: [Django] #30398: Check database connection's health before it is reused

2021-10-03 Thread Django

#30398: Check database connection's health before it is reused
-+-
 Reporter:  Przemysław Suliga|Owner:
 |  Przemysław Suliga
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (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
-+-
Changes (by Jacob Walls):

 * needs_docs:  1 => 0
 * needs_tests:  1 => 0


Comment:

 [https://github.com/django/django/pull/14899 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/065.ef0aff7847abcec5652701ae3df9b9b4%40djangoproject.com.

Re: [Django] #23408: Add makemigrations warning for unique fields with callable defaults

2021-10-03 Thread Django

#23408: Add makemigrations warning for unique fields with callable defaults
-+---
 Reporter:  Harper04 |Owner:  Jacob Walls
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  dev
 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
-+---
Changes (by Jacob Walls):

 * owner:  nobody => Jacob Walls
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.f07dc6ff11ddc5c7295e59777850a0b9%40djangoproject.com.

Re: [Django] #28919: Add support for Common Table Expression (CTE) queries

2021-10-03 Thread Django

#28919: Add support for Common Table Expression (CTE) queries
-+-
 Reporter:  Daniel Miller|Owner:  Moses
 |  Mugisha
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by John Speno):

 * cc: John Speno (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.7ba55f0346f17eecb7d169553ecd8530%40djangoproject.com.

Re: [Django] #32723: Add a GitHub action to run the Sphinx linkcheck builder.

2021-10-03 Thread Django

Comment (by Nick Pope):

Thanks for looking into this Jacob.

So, yes, I was waiting for the feature to be added to Sphinx, but there
were some complications over the implementation, so it is only part of
what would be needed. It's on my very long list of things to look into.
The main problem is that substituting the captures from the source pattern
into the target pattern using back-references precludes the use of back-
references for repeating captured groups within the target pattern.

At this stage I think we still need to wait until something further is
implemented in Sphinx. That is why I flagged this "Someday/Maybe". I think
we'd require a great many more entries because we can't make it generic
enough. On top of that, one of the reasons for wanting to be able to
substitute from the source to the target is to ensure that we're actually
redirected to the right page. This whole thing is intended to make
linkcheck useful for documentation sites that redirect for language and
version, but not mask other potential issues.

--
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/065.db517c16af59fd208eb6f78c12da092e%40djangoproject.com.

Re: [Django] #33107: ImportError: partially initialized module '...' has no attribute '...'

Re: [Django] #27694: Improve documentation of supported lookups on HStore & JSON fields

Re: [Django] #27694: Improve documentation of supported lookups on HStore & JSON fields

Re: [Django] #27694: Improve documentation of supported lookups on HStore & JSON fields

Re: [Django] #27694: Improve documentation of supported lookups on HStore & JSON fields

Re: [Django] #27694: Improve documentation of supported lookups on HStore & JSON fields

Re: [Django] #32888: Document that select_for_update() doesn't lock tables when their columns are not selected. (was: Using select_for_update with self as an of-argument gets dropped when only selecti

Re: [Django] #33164: UUID URL converter should support uppercase hexadecimal digits

Re: [Django] #33165: DateInput default date is not shown when localization is on

[Django] #33166: Missing context when rendering form widgets

Re: [Django] #32948: Optimise Q combination and inversion

Re: [Django] #27694: Improve documentation of supported lookups on HStore & JSON fields

Re: [Django] #32672: Primary Key, type double and type unsigned integer ain't detected correctly for Sqlite3 Database

Re: [Django] #32723: Add a GitHub action to run the Sphinx linkcheck builder.

[Django] #33165: DateInput default date is not shown when localization is on

Re: [Django] #30398: Check database connection's health before it is reused

Re: [Django] #23408: Add makemigrations warning for unique fields with callable defaults

Re: [Django] #28919: Add support for Common Table Expression (CTE) queries

Re: [Django] #32723: Add a GitHub action to run the Sphinx linkcheck builder.

19 matches

Site Navigation

Mail list logo

Footer information