Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to toggle pausing history logging #716

Open
spyder-bot opened this issue Feb 17, 2015 · 6 comments
Open

Ability to toggle pausing history logging #716

spyder-bot opened this issue Feb 17, 2015 · 6 comments

Comments

@spyder-bot
Copy link
Collaborator

From [email protected] on 2011-07-27T09:57:38Z

What steps will reproduce the problem?

  1. Execute a code block
    1. See how the entire block gets listed in the history log. What is the expected output? What do you see instead? I would expect no output to the history log, as the coding iterations on the block quickly floods the log, hiding from view code snippets that are worth keeping at hand. What version of the product are you using? On what operating system? Spyder 2.0.12 within Pythonxy 2.6.6.2

Original issue: http://code.google.com/p/spyderlib/issues/detail?id=716

@spyder-bot
Copy link
Collaborator Author

From ccordoba12 on 2011-08-01T21:15:16Z

I don't know about this one. It could be configurable trough an option because I don't think all people would agree that everything that goes in a block is not important.

Can you give a concrete example to show us your point?

Labels: -Type-Defect Type-Enhancement Cat-HistoryLog

@spyder-bot
Copy link
Collaborator Author

From [email protected] on 2011-08-02T06:04:20Z

Well, say you are prototyping an algorithm and it depends on some numerical parameters, call them x, y, z. Let's assume the algorithm is of the form:

x = 5; y = 23; z = 4.5e-3;
for i in range(x-1,x**2):
do_something_in_several_lines
for k in range(y):
do_a_lot_more
print z

And suppose it spans 40 lines of code. Every single time you change either x, y, or z, or tweak the code and rerun the whole thing, well, you end up with mostly redundant output in the history log, and that's not useful.

@spyder-bot
Copy link
Collaborator Author

From ccordoba12 on 2011-08-04T12:07:01Z

It would be easier if you put your block in a function that depended in x, y, z. That way you would be calling the function instead of sending to the console the whole block again and again. It would also be faster for you.

The idea is kind of interesting but I don't see a strong case for it. We could suspend history logging with a button, so the user could decide what he/she wants to log and what not. But suppress only blocks seems hard to do and not so important.

@spyder-bot
Copy link
Collaborator Author

From [email protected] on 2011-08-04T13:29:24Z

I think it would be a good compromise to add that button/option to supress history log output at will.

Your suggestion to encapsulate in a function is useful, as well. But in the case of code tweaks within the block (not just parameter value changes), supressing somehow the output to the history log seems to me the only reasonable solution. So we need the button/option aforementioned.

@spyder-bot
Copy link
Collaborator Author

From ccordoba12 on 2011-08-05T20:46:01Z

I'm glad we've found a compromise. Now we have to see how to implement it :)

Summary: Suspend output to history log at user's will with a button/option

@spyder-bot
Copy link
Collaborator Author

From pierre.raybaut on 2012-03-18T14:06:02Z

Labels: -Type-Enhancement Type-Enh

@CAM-Gerlach CAM-Gerlach changed the title Suspend output to history log at user's will with a button/option Ability to toggle pausing history logging Feb 18, 2018
@CAM-Gerlach CAM-Gerlach added this to the wishlist milestone Feb 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants