#20356: Remove no more needed workaround for Python builtins
-------------------------------------+-------------------------------------
       Reporter:  hivert             |        Owner:
           Type:  defect             |       Status:  needs_info
       Priority:  major              |    Milestone:  sage-7.2
      Component:  documentation      |   Resolution:
       Keywords:  Documentation      |    Merged in:
  links                              |    Reviewers:
        Authors:  Florent Hivert     |  Work issues:
Report Upstream:  N/A                |       Commit:
         Branch:                     |  4fcb397e86802192727613678e4ca099fcf6a380
  u/hivert/remove_no_more_needed_workaround_for_python_builtins|     Stopgaps:
   Dependencies:                     |
-------------------------------------+-------------------------------------
Description changed by slelievre:

Old description:

> Python's builtins such as {{{str, set, frozenset}}} used to be documented
> as function instead of as classes. We had a workaround for that which is
> not working anymore for {{{object,str}}}, an many of the issues have
> already been solved as Python's level.
>
> See for examples the Base classes that are broken for the two following
> classes
>
> [[http://doc.sagemath.org/html/en/reference/combinat/sage/combinat/words/word_generators.html#sage.combinat.words.word_generators.WordGenerator|WordGenerator]]
> [[http://doc.sagemath.org/html/en/reference/misc/sage/misc/lazy_format.html?highlight=lazy%20format
> #module-sage.misc.lazy_format|lazy_format]]
>
> Unfortunately, It's still needed for tuple:
>
> [[http://doc.sagemath.org/html/en/reference/combinat/sage/combinat/shard_order.html|shard_order]]
>
> Indeed, the overall situation seems to be unclear from the Python's side:
>
> See https://bugs.python.org/issue11975

New description:

 Python's builtins such as `str`, `set`, `frozenset` used to be documented
 as functions instead of as classes. We had a workaround for that which is
 no longer working for `object`, `str`, and many of the issues have already
 been solved at Python's level.

 See for examples the base classes that are broken for the two following
 classes:

 
[[http://doc.sagemath.org/html/en/reference/combinat/sage/combinat/words/word_generators.html#sage.combinat.words.word_generators.WordGenerator|WordGenerator]]
 
[[http://doc.sagemath.org/html/en/reference/misc/sage/misc/lazy_format.html?highlight=lazy%20format
 #module-sage.misc.lazy_format|lazy_format]]

 Unfortunately, it's still needed for tuples:

 
[[http://doc.sagemath.org/html/en/reference/combinat/sage/combinat/shard_order.html|shard_order]]

 Indeed, the overall situation seems to be unclear from the Python side,
 see https://bugs.python.org/issue11975

--

--
Ticket URL: <http://trac.sagemath.org/ticket/20356#comment:4>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to