[issue40032] Remove explicit inheriting of object in class definitions
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 understand (No new functionality, no bug fix). Not experienced enough to know about what makes code more maintainable. Why do you think it makes the code less clear, though? -- ___ Python tracker <https://bugs.python.org/issue40032> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40032] Remove explicit inheriting of object in class definitions
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: Remove explicit inheriting of object in class definitions versions: Python 3.9 ___ Python tracker <https://bugs.python.org/issue40032> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21041] pathlib.PurePath.parents rejects negative indexes
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 <https://bugs.python.org/issue21041> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38702] Adding new types to parser/unparse.py
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 tracker
<https://bugs.python.org/issue38702>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38702] Adding new types to parser/unparse.py
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 status: open title: Adding new types to parser/unparse.py type: enhancement versions: Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue38702> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38539] Update demo files
Julin added the comment: I've made a PR. Can you review it? -- ___ Python tracker <https://bugs.python.org/issue38539> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38539] Update demo files
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/issue38539> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38539] Update demo files
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 to spreadsheet.py (to make its purpose clearer) -- ___ Python tracker <https://bugs.python.org/issue38539> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38539] Update demo files
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 being on the same line, etc. It can easily mislead someone new to the language especially since it is part of the codebase and part of distribution as well. Can we update these files? Most of these seem have not been updated in some time. A discussion touching this problem on #python-dev suggested that the demos were written when the docs were yet to be polished and now that we have a fully fledged documentation, maybe the demo files can be dropped. But since the bpo has an option 'Demos and tools' under 'components', I guess maybe the demos are still considered essential. What do you all think? -- components: Demos and Tools messages: 355013 nosy: ju-sh priority: normal severity: normal status: open title: Update demo files type: enhancement versions: Python 3.6, Python 3.7, Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue38539> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38528] Docs for 2.7 version switcher still shows 3.8 as pre
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/issue38528> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38528] Docs for 2.7 version switcher still shows 3.8 as pre
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 it be changed as well? -- assignee: docs@python components: Documentation messages: 354950 nosy: docs@python, ju-sh priority: normal severity: normal status: open title: Docs for 2.7 version switcher still shows 3.8 as pre versions: Python 2.7 ___ Python tracker <https://bugs.python.org/issue38528> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
