Julin added the comment:
I just thought it looked different compared to the usual code that some of us
were used to. Though it is probably familiar enough to the people who actually
maintain the cpython code base.
I agree with everything that you mentioned with regards to what I could
New submission from Julin :
In the source, many class definitions still explicitly inherit from `object`
though it is no longer necessary in Python3.
Can't we change it?
--
components: Library (Lib)
messages: 364739
nosy: ju-sh
priority: normal
severity: normal
status: open
title
Julin added the comment:
Can't this be implemented? This is something that a user would expect.
Intuitive. And it looks as if it is an easy change to make that doesn't disturb
anything else.
--
nosy: +ju-sh
___
Python tracker
<ht
Julin added the comment:
Okay.
But can lines like
if first:first = False
else: self.write(", ")
be changed to span across more number of lines?
Because things like
first:first
looks like a type hint.
--
___
Python track
New submission from Julin :
The parser/unparse.py file lacks functions to handle the `Str`, `Num`, `Bytes`
and `NameConstant` types.
Can we add them since it seems to be simple enough?
--
components: Demos and Tools
messages: 356050
nosy: ju-sh
priority: normal
severity: normal
Julin added the comment:
I've made a PR. Can you review it?
--
___
Python tracker
<https://bugs.python.org/issue38539>
___
___
Python-bugs-list mailin
Change by Julin :
--
keywords: +patch
pull_requests: +16428
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/16890
___
Python tracker
<https://bugs.python.org/issu
Julin added the comment:
Okay. While I'm at it, can I make a few minor change as well? Like
- Use fstrings
- change range(0, val) to range(val) as range()'s first argument has default
value 0.
- Change `for i in range(len(groups)):` to enumerated (redemo.py)
- rename ss1.py
New submission from Julin :
The demo programs inside Tools/demo, which is to guide people new to the
language (that's the purpose, right?), makes use of several bad coding
practices.
Like
- `while 1:` being used instead of `while True:`
- star import
- function call and an `if` statement
Julin added the comment:
A PR (16848) has been opened now for the change for pre (3.8) to `3.8.0`. Is
the same acceptable for `3.9`?
--
___
Python tracker
<https://bugs.python.org/issue38
New submission from Julin :
The version switcher in the docs for Python2.7 still shows version 3.8 as `pre
(3.8)`. Can we change it to `3.8.0` to mirror that in docs of 3.8?
Also, 2.7 docs version switcher at the moment show `dev (3.9)` for 3.9 whereas
the 3.8 docs say `3.9.0a0` can
11 matches
Mail list logo