New submission from Vladimir Ryabtsev :
There are code snippets on the package's page
(https://docs.python.org/3.10/library/abc.html) like this:
class C(ABC):
@classmethod
@abstractmethod
def my_abstract_classmethod(cls, ...):
...
Here, the author probably wanted
Vladimir Ryabtsev added the comment:
The issue won't be fixed, but other useful changes applied.
--
resolution: -> wont fix
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Vladimir Ryabtsev :
--
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.10 -Python 3.7
___
Python tracker
<https://bugs.python.org/i
Change by Vladimir Ryabtsev :
--
pull_requests: +22974
pull_request: https://github.com/python/cpython/pull/24145
___
Python tracker
<https://bugs.python.org/issue38
Vladimir Ryabtsev added the comment:
All right, you won. I hope beginner users will be happy :)
I removed my proposal paragraph about __cause__ and __context__ and kept only
changes about exception type (https://bugs.python.org/issue42179#msg380435
Vladimir Ryabtsev added the comment:
Also, the choice of the exception type in the example looks not very apt: you
raise "IOError" but the traceback message says "OSError" (which is due to
strange design decision "IOError = OSError"). For the tutorial, I would
Vladimir Ryabtsev added the comment:
We have automatic chaining, so you don't need to use "from X" unless you want
to have some control on the traceback message. Even without knowing of this
syntax (and without using "from exc"), a user will get a traceback message
simi
Vladimir Ryabtsev added the comment:
> I can not find confusion caused by this tutorial section
Inada, have you read the very first message in this ticket? It explains why
this wording may cause confusion (and it did in me), and describes the problem
part. A link for your convenience:
ht
Vladimir Ryabtsev added the comment:
1. Such understanding of a tutorial is debatable. Tutorial is just a material
for learning written with some system in mind, which is more interesting to
read than dry reference material. A tutorial, generally dpeaking, may be both
for beginners
Change by Vladimir Ryabtsev :
--
keywords: +patch
pull_requests: +22072
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23160
___
Python tracker
<https://bugs.python.org/issu
Change by Vladimir Ryabtsev :
--
pull_requests: +22071
pull_request: https://github.com/python/cpython/pull/23159
___
Python tracker
<https://bugs.python.org/issue38
New submission from Vladimir Ryabtsev :
A new section has been added to the page as a result of
https://bugs.python.org/issue37826. The change:
https://github.com/python/cpython/commit/dcfe111eb5602333135b8776996332a8dcf59392
The wording it uses (in the beginning of section 8.5), defines
Vladimir Ryabtsev added the comment:
Also the footnote requires some minor corrections (formatting and style). I
suggest the following wording:
To get loadable extension support, your Python must be compiled with
``-–enable-loadable-sqlite-extensions`` option in ``PYTHON_CONFIGURE_OPTS``.
I
Vladimir Ryabtsev added the comment:
May by I was wrong above and it uses system's Sqlite... But anyway it does not
cancel the fact that this section contradicts to another one.
--
___
Python tracker
<https://bugs.python.org/issue38
Vladimir Ryabtsev added the comment:
I see no point in researching the version of sqlite, since Python does not
allow user to specify it, you just use the compiled version that comes with
Python distribution.
10 years now to the commit that introduced that piece of text:
https://github.com
New submission from Vladimir Ryabtsev :
This is regarding the page https://docs.python.org/3.7/library/sqlite3.html.
I believe this section on the very bottom of the page has been kept here for
pretty long time, during that both SQLite and the sqlite3 module evolved and
improved. Now
16 matches
Mail list logo
