New submission from Arthur Milchior :
I don't have permission to assign the issue, but I intend to post the change in
a few minutes as a PR
Copied from Richard Hyde's email to doc mailing list.
One of the examples of string formatting doesn't work. This applies to prior
ver
Change by Arthur Milchior :
--
keywords: +patch
pull_requests: +28345
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/30126
___
Python tracker
<https://bugs.python.org/issu
Arthur Milchior added the comment:
ipypthon3 does not print the loop content. python3 does. I only tested with
ipython. I beg your pardon. I didn't know about this difference in behavior
--
nosy: -eric.smith
title: Zip library documentation error -> format library docum
New submission from Arthur Milchior :
I find super documentation confusing because it uses multiple variables that
are never introduced. Once you understand super, the meaning of those variables
gets easier to understand, but still, I believe that it would help the
documentation to rephrase
Arthur Milchior added the comment:
Shouldn't those change be ported to 3.10 and maybe even earlier version? They
are great, but hard to find if you read the current version manual.
I'm just surprised by the term "dotted lookup". The remaining of the
documentation menti
Arthur Milchior added the comment:
I just realized that https://bugs.python.org/issue20751 already tackled some of
my issues. While I still believe that some things can be improved, this mean
that some of the critiques in my first messages are not entirely up to date.
--
versions
Arthur Milchior added the comment:
"a base class ``B`` following ``A``" shouldn't it be "the base class"? . After
all, there is at most one base class following ``A``.
Also, I find it unclear what means "``x`` is returned unchanged, since in this
context ``x``
Arthur Milchior added the comment:
"a base class ``B`` following ``A``" shouldn't it be "the base class"? . After
all, there is at most one base class following ``A``.
Also, I find it unclear what means "``x`` is returned unchanged, since in this
context ``x``
Arthur Milchior added the comment:
I do regret to have created a single bug, as I now realize that there are two
issues that are less related than I first imagined. Is there a way to split a
bug in two, so that both discussion can be discussed in different places.
Actually, after more
Change by Arthur Milchior :
--
pull_requests: +28486
pull_request: https://github.com/python/cpython/pull/30271
___
Python tracker
<https://bugs.python.org/issue20
New submission from Arthur Milchior :
In 3.8, int() default implementation changed, using __index__() if it is
available instead of __trunc__(). The file function.rst was updated
accordingly, but the redundant information in datamodel.rst contained out of
date information
I offer a
New submission from Arthur Milchior :
While floor/ceil 's documentation are very precise, `truncate` was not
explained. I actually had to search online to understand the difference between
`truncate` and `floor` (admittedly, once I remembered that numbers are signed,
and that flo
New submission from Arthur Milchior :
The grammar, in https://docs.python.org/3/reference/grammar.html , lacks some
utilities that the remaining of the documentation have.
While it remains usable, it is hard to navigate. As an example
https://www.python.org/dev/peps/pep-0634/ &#
New submission from Arthur Milchior :
https://docs.python.org/3/reference/executionmodel.html list all of the way a
variable may be bound. However, it seems that it was not updated. Indeed,
structural pattern matching in 3.10 also allows to bind a variable and is not
mentionned.
As a
Change by Arthur Milchior :
--
keywords: +patch
pull_requests: +27495
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/29232
___
Python tracker
<https://bugs.python.org/issu
New submission from Arthur Milchior :
In the current documentation, production tokens are not clickable. For example
in https://docs.python.org/3/reference/expressions.html#yield-expressions , you
highlight `yield_from` as a token but do not link to it.
I suppose that the goal, when using
Change by Arthur Milchior :
--
keywords: +patch
pull_requests: +27525
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/29260
___
Python tracker
<https://bugs.python.org/issu
New submission from Arthur Milchior :
According to the current documentation, I believe there is an error in
list_display, set_display and dict_display.
According to list display, this is a valid expression
[* l1 ^ l2]
parsed as
list_display:
"["
starred_list:
st
Arthur Milchior added the comment:
https://docs.python.org/3/reference/expressions.html#grammar-token-python-grammar-expression
is wrong
This line state:
`expression ::= conditional_expression | lambda_expr`
and it is a problem because, by the way sphinx understand reference
New submission from Arthur Milchior :
https://docs.python.org/3/reference/expressions.html#grammar-token-python-grammar-expression
is wrong
This line state:
`expression ::= conditional_expression | lambda_expr`
and it is a problem because, by the way sphinx understand reference
Change by Arthur Milchior :
--
title: "expression" is erroneous in the doc -> Star expression in comprehension
wrongly indicates to use or_expression after the star
___
Python tracker
<https://bugs.pytho
Arthur Milchior added the comment:
Message 405188 was supposed to be another bug report. My bad.
--
___
Python tracker
<https://bugs.python.org/issue45
Change by Arthur Milchior :
--
keywords: +patch
pull_requests: +27571
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/29303
___
Python tracker
<https://bugs.python.org/issu
Arthur Milchior added the comment:
I'm quite fan of your suggestion. Should I push it on the PR? Do you create
another PR? I'm not used to BPO, I beg your pardon, only to github
--
___
Python tracker
<https://bugs.python.o
Arthur Milchior added the comment:
Done
--
___
Python tracker
<https://bugs.python.org/issue45584>
___
___
Python-bugs-list mailing list
Unsubscribe:
Arthur Milchior added the comment:
Thank you very much Dennis. For two reasons.
First, because I like a lot what you wrote. I suspect that it would have saved
me time and make things less confusing.
That's not certain, because at the time I was reading the documentation of
or_expr,
New submission from Arthur Milchior :
On current main, f87ea0350286837e9e96de03f8bfa215176c2928 ,
```
cd cpython/Doc
make doctest
```
fails.
Due to:
Document: library/functions
---
Warning, treated as error
Arthur Milchior added the comment:
I know understand one thing I missed.
I needed to do `make venv` after changing the make file to get 3.10 in virtual
environment.
The issue being that this would make doc harder to create on ubuntu since 3.10
is not yet easily accessible through apt/snap
New submission from Arthur Milchior :
I would like to work on this documentation improvement. Before spending time on
it, I would like to know whether it would be accepted in principle and whether
the way I would intend to improve the documentation would be accepted.
# Problem:
In a lot of
Arthur Milchior added the comment:
Thanks for the warning about double link. I agree with you.
I guess it's another reason why it would be non trivial to automate here.
--
___
Python tracker
<https://bugs.python.org/is
30 matches
Mail list logo
