Max Slimmer's profile - activity
2022-09-27 17:16:09 -0500 | commented question | yapf indent setting I have a similar problem (want to use tabs vs spaces) and as mentioned in comments, it might be enough to know where the |
2020-01-22 20:00:17 -0500 | received badge | Famous Question (source) |
2020-01-22 20:00:17 -0500 | received badge | Notable Question (source) |
2020-01-22 20:00:17 -0500 | received badge | Popular Question (source) |
2019-10-07 10:23:42 -0500 | received badge | Teacher ( source ) |
2019-10-07 10:12:54 -0500 | answered a question | How to install packages using pip from within Wing You could manage your project in a virtual environment, do the pip install there and set your wing project to use that e |
2019-03-07 08:48:54 -0500 | received badge | Student (source) |
2019-03-07 08:48:52 -0500 | marked best answer | Shell History Location I would like to clear my python shell history, where does Wing keep this information? I've looked in the Settings Directory and and Cache Directory.Edit: The "Clear" option does clear the console and the "Restart Shell" option does restart the shell, which also clears the console output. But neither of those clear the input history. I can still "up arrow" through my input history. Restarting the Wing process does clear the input history so this is a sufficient workaround for me. Version: 5.1.12OS: Win 10 |
2019-03-07 08:13:30 -0500 | marked best answer | Traceback is printed to Debug I/O window after exception reported. Debugger:Exception settings are In my exception handler I am logging the exception with logging.exception(...) so the debugger stops at the logging statement (as expected) and the logging output has been displayed in the Debug I/O window. The Exceptions toolbox window also shows a stack trace which is navigable by clicking (really nice by the way).The problem is that when I continue another stack trace is printed to the Debug I/O window. This behavior is different than what I would see on stderr when running the code from a console. Behavior remains even if I ignore this exception location from the Exceptions tool.Wing version 5.1.12 (I plan on upgrading soon)Python 2.7.14Windows 10 Thanks |
2018-05-21 15:10:00 -0500 | answered a question | Traceback is printed to Debug I/O window after exception reported. It was mostly an annoyance while debugging but its awesome that it turned up a more significant issue. Now I just have t |
2018-05-19 12:04:00 -0500 | asked a question | Traceback is printed to Debug I/O window after exception reported. Traceback is printed to Debug I/O window after exception reported. Debugger:Exception settings are Report Exceptions: Wh |
2018-01-05 13:55:00 -0500 | commented answer | Shell History Location The python-shell.history is written on project close | save. So as long as the same project is successfully reopened and |
2018-01-04 18:21:00 -0500 | commented answer | Shell History Location I've edited my original post. Your answer led me to check what happens on a restart and that behavior is "good enough" f |
2018-01-04 13:00:00 -0500 | asked a question | Shell History Location Shell History Location I would like to clear my python shell history, where does Wing keep this information? I've looked |