#36329: Remove non-code custom link text when cross-referencing Python objects 
in
docs
-------------------------------------+-------------------------------------
     Reporter:  Clifford Gama        |                    Owner:  Clifford
         Type:                       |  Gama
  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 Natalia Bidart):

 * stage:  Unreviewed => Accepted

Comment:

 Thank you Clifford for this work. I have reviewed some of the examples,
 particularly those changed in the PR, and I have mixed feelings about the
 need to do any change. I do understand that the method/classes "links" are
 formatted as monospaced code-like text,  but OTOH the resulting "links"
 read/flow nicely in the paragraphs.

 Concretely, I am happy to accept the ticket and review the PR in detail.
 However, I would appreciate it if you could expand a bit on the motivation
 for this change, particularly the broader reasoning or philosophy behind
 it.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36329#comment:3>
Django <https://code.djangoproject.com/>
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 visit 
https://groups.google.com/d/msgid/django-updates/01070196405ddeb2-14dcb427-235a-4d64-81ca-cc1c5930d0f8-000000%40eu-central-1.amazonses.com.

Reply via email to