Steven Hsu added the comment:
Thanks for the efficient help!
--
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/i
Change by Steven Hsu :
--
type: -> enhancement
___
Python tracker
<https://bugs.python.org/issue45341>
___
___
Python-bugs-list mailing list
Unsubscrib
New submission from Steven Hsu :
The full name of PyPI is "Python Package Index" at https://pypi.org/ , but it
is still "Python Packaging Index" in Docs
(https://github.com/python/cpython/blob/main/Doc/distributing/index.rst).
Therefore, an update of the term in t
Change by Steven Hsu :
--
keywords: +patch
pull_requests: +25890
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/27349
___
Python tracker
<https://bugs.python.org/issu
Steven Hsu added the comment:
Applying above suggestions, the first sentence of the entry "__future__" would
be replaced by:
A :ref:`future statement `, "from __future__ import *feature* ...",
directs the compiler to compile the current module using syntax or semanti
Steven Hsu added the comment:
It sounds like that both descriptions (pseudo- and real) are true in different
points of view on the __future__ module.
I have no idea how to resolve this contradiction of the original design of the
module. Any suggestion?
Thanks for reply
New submission from Steven Hsu :
In Doc/glossary.rst, the first sentence of the entry "__future__" is that "A
pseudo-module which programmers can use to enable new language features which
are not compatible with the current interpreter."
However, in Doc/library/__fut
Steven Hsu added the comment:
Thanks for reminding.
In the beginning, I didn't add a NEWS entry in the PR (#27032).
However, after 11 days when there was no progress of the PR, I doubted that
maybe I missed something, so I made a NEWS entry to make sure.
And soon after the NEWS entry
Change by Steven Hsu :
--
keywords: +patch
pull_requests: +25767
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/27226
___
Python tracker
<https://bugs.python.org/issu
Steven Hsu added the comment:
Thanks for your reply and suggestion.
I can totally understand your explanation about the definition of coercion.
In conclusion, I think this glossary entry may need some modification for
better understanding, or simply be deleted.
So what's the next step
New submission from Steven Hsu :
In Doc/glossary.rst, the definition about "coercion" is as below:
"The implicit conversion of an instance of one type to another during an
operation which involves two arguments of the same type."
However, in the example following this
Steven Hsu added the comment:
I have make a new PR (#27032), and the CLA was signed.
Thanks for review.
--
versions: -Python 3.9
___
Python tracker
<https://bugs.python.org/issue44
Change by Steven Hsu :
--
pull_requests: +25592
pull_request: https://github.com/python/cpython/pull/27032
___
Python tracker
<https://bugs.python.org/issue44
Change by Steven Hsu :
--
keywords: +patch
pull_requests: +25586
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/27027
___
Python tracker
<https://bugs.python.org/issu
New submission from Steven Hsu :
In https://github.com/python/cpython/blob/main/Doc/distributing/index.rst,
there are three expired hyperlinks:
.. _Project structure: \
https://packaging.python.org/tutorials/distributing-packages/
.. _Building and packaging the project: \
https
15 matches
Mail list logo
