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
backgroundjobs related magic functions are all missing #844
Comments
Hi, I'm afraid it was a victim of the large refactoring that took place towards 0.11. I don't recall right now the precise reasons that led to this one being cut out, it could have been accidental, but @bgranger might have a better recollection as he did the grunt work of that large reorganization. Part of the problem is that this functionality was all threads-based, and in python, starting background threads for anything cpu intensive isn't a very good idea. But I can see how it could be useful for certain scenarios, and if we can bring it back without creating problems for the new Qt console or notebook, we can look into it. Could you give us some feedback on your use scenarios and how important this is for you? Feedback like this will help us gauge how critical this should be in terms of prioritizing effort. Note that the code is all there, it's just in the 0.10.2 tag in the git repository. So it wouldn't be too hard to revive it, if someone steps up to help out and we do it with proper documentation and testing. |
Thank you very much for the reply. On Mon, Oct 10, 2011 at 5:04 AM, Fernando Perez <
|
On Sun, Oct 9, 2011 at 6:28 PM, digitalsatori
Well, there's a reasonable amount of work involved in bringing it Interesting and possibly useful, but at this point in time somewhat I'll leave this open though, so others can find it, and if an |
Please see gh-856 for further details. When that gets merged, some of this functionality will indeed come back. |
closed by PR #856 |
@minrk, reopening it b/c I never brought |
Oh, sorry. There was a series of Issues that should have been autoclosed by PRs that weren't, and I guess I got overzealous. |
On Tue, Oct 18, 2011 at 4:33 PM, Min RK
No worries! I'm glad to see you closing, I definitely have a similar And an unknown number non-triaged (without labels). Cheers, f |
On Tue, Oct 18, 2011 at 16:38, Fernando Perez <
I've used my issues script to keep a handle on unlabeled Issues. We have A) assigned to a milestone I pretty aggressively labeled most things as 0.12 milestone, so we at least
|
On Tue, Oct 18, 2011 at 4:55 PM, Min RK
Excellent! BTW, mind putting your script in tools/? That way we can No need for a PR for that, just go ahead and do it at your leisure. |
This has been resolved with the new Example:
|
Thanks ! Closing then ! |
It would be still great to have %bg back.. not just external script background execution. |
I have Monte-Carlo simulations that run for around two hours, but may converge earlier. Useful conclusions and earlier convergence detection can be be done when running them in background and dumping intermediate results in a file. A perfect job for %bg, so please reopen |
Magics do not have to be part of IPython to be available, you are free to publish a package on PyPI that exposes a |
sorry for the dumb question, but where are those magics:
%jobs, %bg etc.
ipython prompted Magic function 'xxx' not found whenever I type these magic phrase in ipython, and it seems really missing in the "core/magic.py" . I also found that nowhere in ipython actually refer to the lib/backgroundjobs.py where background jobs handling process defined.
The text was updated successfully, but these errors were encountered: