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
remove irunner, iplogger #4706
remove irunner, iplogger #4706
Conversation
and mkdoctests, which was the only user of it
Is it worth doing a deprecation cycle - i.e. removing the The test failures are because you removed the module and left the tests in place ;-) |
I removed them, I just failed to push. Should be there now. |
I guess this was discussed internally :-) |
Yep, I asked Min and Paul about it, and the consensus was that we're not likely to revive it anyway, and we have no evidence that anyone is actually using it. |
why is irunner removed? |
Told you we'd find someone who uses it ;-) |
More seriously: @juliantaylor , what do you do with irunner to test C extensions that can't be done with a normal .py script, or a .ipy script if the need arises? |
usually just %timeit stuff and then running it under a profiler (e..g perf), quick and convenient |
the scripts were removed in ipython#4706, but not their manpages
now that irunner is gone a while I notice it a lot more that its missing. So I must ask again as I didn't get an answer last time why was it removed? Is it hard to maintain? |
I don't think it was especially hard to maintain, but none of us knew of any good reason to use it, we've not advertised its existence for years, and we're trying to reduce the number of scripts we install ( Feel free to ask on the mailing list, but given that no-one else has complained about its removal so far, I doubt there were many people using it. I'm still not quite clear on what you were using it for, to be honest. |
remove irunner, iplogger
the scripts were removed in ipython#4706, but not their manpages
and mkdoctests, which was the only user of irunner