➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2018-07-02 15:03 by kayhayen, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg320888 - (view) | Author: Kay Hayen (kayhayen) | Date: 2018-07-02 15:03 | |
Hello, things like list(sequence = something) ought to work in Python 3.6 back to the oldest Python2 I know. However, in 3.7 this raises an exception about not accepting keyword arguments. I noticed the same for tuple, int, float(x=9.0), and probably a lot others. It is not described in the release notes either. I think it's a bug and might affect existing code. Or is this how thing will be from now on? Yours, Kay |
|||
| msg320889 - (view) | Author: Ned Deily (ned.deily) *  |
Date: 2018-07-02 15:08 | |
Alas, it's not a bug. That was a deliberate change (see https://bugs.python.org/issue29695 for the discussion leading up to the change) and is documented in the "What's New in 3.7" document here: https://docs.python.org/3.7/whatsnew/3.7.html#api-and-feature-removals |
|||
| msg320893 - (view) | Author: Kay Hayen (kayhayen) | Date: 2018-07-02 15:26 | |
Hello Ned, sorry for noise. I checked that, but oversaw it. Maybe I also wasn't expecting this. There has been such a huge trend towards * and ** support for like everything, e.g. class definitions in 3.6, that this felt like a move in the opposite direction. But I got the information I need for Nuitka to follow this. I agree with your close and my apology. Yours, Kay |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:02 | admin | set | github: 78205 |
| 2018-07-02 15:26:40 | kayhayen | set | messages: + msg320893 |
| 2018-07-02 15:08:49 | ned.deily | set | status: open -> closed nosy: + ned.deily messages: + msg320889 resolution: not a bug stage: resolved |
| 2018-07-02 15:03:21 | kayhayen | create | |