[issue29339] Interactive: Move to same indentation level as previousline

2017-03-14 Thread 12345 67890
12345 67890 added the comment: Folks, I have decided that I no longer have the time to resolve this issue. -- ___ Python tracker <http://bugs.python.org/issue29

[issue29339] Interactive: Move to same indentation level as previousline

2017-03-14 Thread 12345 67890
Changes by 12345 67890 : -- nosy: -12345 67890 ___ Python tracker <http://bugs.python.org/issue29339> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue20486] msilib: can't close opened database

2016-12-19 Thread 12345 67890
12345 67890 added the comment: This is still present in Python 3.5. There is no way to unlock the MSI file without killing the Python process first. -- nosy: +12345 67890 versions: +Python 3.5 ___ Python tracker <http://bugs.python.org/issue20

[issue20486] msilib: can't close opened database

2016-12-19 Thread 12345 67890
12345 67890 added the comment: I will prefix this by saying that I have not contributed to the Python source before and this patch is probably wrong, but here is my attempt at a fix. -- Added file: http://bugs.python.org/file45970/_msi.c ___ Python

[issue20486] msilib: can't close opened database

2016-12-19 Thread 12345 67890
Changes by 12345 67890 : -- keywords: +patch Added file: http://bugs.python.org/file45971/Add_ability_to_close_MSI_database_.patch ___ Python tracker <http://bugs.python.org/issue20

[issue20486] msilib: can't close opened database

2016-12-19 Thread 12345 67890
Changes by 12345 67890 : Removed file: http://bugs.python.org/file45970/_msi.c ___ Python tracker <http://bugs.python.org/issue20486> ___ ___ Python-bugs-list mailin

[issue20486] msilib: can't close opened database

2016-12-27 Thread 12345 67890
12345 67890 added the comment: The method is now capitalized. Unfortunately, none of the methods are compliant with PEP formatting, but it's far too late to do anything about that. -- Added file: http://bugs.python.org/file46056/Add_ability_to_close_MSI_database_.

[issue20486] msilib: can't close opened database

2016-12-27 Thread 12345 67890
Changes by 12345 67890 : Removed file: http://bugs.python.org/file45971/Add_ability_to_close_MSI_database_.patch ___ Python tracker <http://bugs.python.org/issue20

[issue29339] Interactive: Move to same indentation level as previous line

2017-01-21 Thread 12345 67890
New submission from 12345 67890: Not sure if anyone has ever thought about this, but it would be nice if the interactive interpreter set the same indentation level as the previous line. Of course this isn't urgent, but what do others think? -- messages: 285970 nosy: 12345

[issue29339] Interactive: Move to same indentation level as previous line

2017-01-23 Thread 12345 67890
12345 67890 added the comment: I did not mark this as a bug. I marked it as an "enhancement" and I said that the priority was low. "I'm not exactly sure what you mean" In an IDE when developing in python, each time you press enter, the cursor is set to the same

[issue29339] Interactive: Move to same indentation level as previous line

2017-01-23 Thread 12345 67890
12345 67890 added the comment: I hope I haven't been rude; the idea here was to see what the feeling of the core developers was about this idea. As for the patch, that will probably come after the Python workflow has been fixed because doing it then will save everyone time and as I have

[issue29339] Interactive: Move to same indentation level as previous line

2017-01-23 Thread 12345 67890
12345 67890 added the comment: It probably won't be trivial, but it definitely is possible. Suplemon has the exact functionality needed and it's only dependency is CPython. The only question is: how much code is this going to add? [1]: https://github.com/richr

[issue29339] Interactive: Move to same indentation level as previous line

2017-01-23 Thread 12345 67890
12345 67890 added the comment: In addition, windows allows direct console control via the win32 API and the code for that isn't too lengthy. -- ___ Python tracker <http://bugs.python.org/is

[issue29339] Interactive: Move to same indentation level as previousline

2017-02-01 Thread 12345 67890
12345 67890 added the comment: That one is pretty tricky. The only way that I can think of is to delay indentation until the first character is typed, and not to indent if it is a space or tab. From: Serhiy Storchaka Sent: Wednesday, February 1, 2017 2:39 PM To: xov...@gmail.com Subject

[issue29339] Interactive: Move to same indentation level as previousline

2017-02-02 Thread 12345 67890
12345 67890 added the comment: The user is going to have to outdent anyway if we return them to the previous indentation level. Essentially it would be this: [ENTER] set_cursor_to_previous_indentation_level() if first_char_in_is_space: erase_first_char_in

[issue29339] Interactive: Move to same indentation level as previousline

2017-02-11 Thread 12345 67890
12345 67890 added the comment: I guess the workflow has been fixed so that I can submit a PR! I wasn't expecting this so soon, but I will get around to this as soon as I have time. -- ___ Python tracker <http://bugs.python.org/is