Matthias, no, that was not apparently the intent, see the last two messages of that bug report: http://bugs.python.org/issue5845#msg215784 The bug report was tracking multiple issues, and someone forgot about this one (and later said that they did, and said "should have gone back to being a release blocker after the alpha release to fix the tab-as-indent issue"). The intent of that bug report was to enable tab to complete, but also still allow tab in the interpreter as indentation (so a tab at the start of a (continuation) line would indent, and a tab after a non-whitespace character would complete). They requested that this issue be raised in a new bugreport on the python bug tracker -- doing that now. Is it reasonable for me to set this bug back to confirmed?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315733 Title: Python interactive interpreter does not indent with tabs, tries to tab-complete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1315733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
